Hi all,

I am gearing up for production of a device using the EFM8SB2.

I want to be able to provide my board manufacturer with a program and test device so that the manufacturer can plug the board into a test rig, the device is programmed and runs a self test. Success can be indicated by an LED on the device.

I was hoping to implement this with a simple single board computer without a display. I am hoping to use the UART bootloader. I have read AN945 have read the Bootloader document "Factory Bootloader User's Guide" but it only seems to document the use of the bootloader with Windows and Python based tools. It mentions the use of "simple transport firmware" but I can't find any documentation on how it can be used. I am also puzzled about how to hook up the UART in order to use this method.

Is there any example of the simple transport firmware and documentation of how to connect the UART of the programming device to the MCU to be programmed?

Thanks in advance,

Rob

According to EFM8BB3 Reference Manual Rev 0.6, p.117 Figure 11.4. Full Crossbar Map
, it is possible to use UART1 in ports P2.2 and P2.3.

Tests :

    Note: P2.0 and P2.1 defined as GPIO

        MOV    P0SKIP,#11001111B    
        MOV    P1SKIP,#11111111B    
        MOV    P2SKIP,#00000011B

        MOV    XBR0,#00000001B        ;bit0 = UART0 I/O Enable
        MOV    XBR1,#00000000B        
        MOV    XBR2,#01000001B        ;bit0 = UART1 I/O Enable

    Result:
         ...............................;P2.0 = 1 (PIN 17 IC)
        CPL    P2.0        
         ...............................;P2.0 = 1 (PIN 17 IC)
        CPL    P2.0            
        ................................;P2.0 = 1 (PIN 17 IC)

         ...............................;P2.1 = 1 (PIN 16 IC)
          CPL    P2.1        
        ................................;P2.1 = 1 (PIN 16 IC)
        CPL    P2.1            
        ................................;P2.1 = 1 (PIN 16 IC)
    
        MOV    SFRPAGE,#20H
        MOV    A,#01010101B
        MOV    SBUF1,A            
        ................................;P2.0 = 01010101B (PIN 17 IC)

 

        ............................................................................................................................

        ................................;P2.2 = 1
        CPL    P2.2            
        ................................;P2.2 = 0 

        ................................;P2.3 = 1
        CPL    P2.3            
        ................................;P2.3 = 0

Conclusion:
P2.0 and P2.1 become UART1, and P2.2, P2.3 become GPIO

 

Thanks,

Valter

 

 

 

I am using a C8051F300 and the Simplicity Studio IDE (updated about 2 weeks ago).

In the startup assembler code I use the DB directive to set two bytes towards the end of memory.   I can build the code, download it, and then read it back - and see that these bytes are indeed set as I intended by the DB statements.

After setting the stack pointer, disabling the watchdog timer, disabling all interrupts, and clearing the IDATA memory space, I have assembly code load the bytes corresponding to the  DB statements into the ACC.  Nothing is done with these values (its just for debug). 

I then have the assembler code call a C function (before main is called).  This C function will test the memory locations which correspond to the addresses from the assembly code's DB statements, and if they are as defined in the assembly code, the C function calculates the programs checksum, then saves it to those same memory locations.

I set breakpoints in the assembler code, and at the start of the C function that is called from the assembly code.

I then run "debug", the code is built, downloaded, and started.  The IDE stops at the statement:   "?C_STARTUP:     LJMP    STARTUP1" at address 0000.   I then step through the code.  At the point where the bytes towards the end of memory are loaded into the ACC register, I can plainly see that the C function called from the assembler code has already run. 

So, it is as if the CPU is programmed with my code, allowed to execute for some period of time, then reset, and re-run, and stops at the point where the breakpoints are set.  I can click RESUME - and the IDE will stop at all of the breakpoints.

 

What can I do to stop this behavior ?

 

 

 

 

As I understand, this is possible. I'm trying to make it happen, but I don't have a logic analyzer and can't figure out how to do it. The signal output should look like this:

|_________     |_________     |_________     |_________     |_________     |_________   
|               ___|                ___|               ___|                ___|               ___|               ___,

So, sequence of 3 clocks HIGH on output pin folllowed by 1xLOW, repeated 256 (or 255) times. Can this be achieved? And how?

We have a range of custom designed boards using the 8 bit C8051F581 MCU.  I've been programming these boards without any trouble using the Silicon Labs MCU Production Programmer software and the DEBUGADPTR1-USB.  This particular device shows up in the programming software as an EC3003BB934.

A colleague recently purchased a new DEBUGADPTR1-USB, which reports in the programming software as an EC30054805B.  I've just been testing this device and it keeps throwing the following error:

'Cannot Erase Code Space on Debug Adapter: EC30054805B'

I know the board etc. is perfectly OK because replacing the new adapter with my older one allows a complete erase/program/verify process.  I've been using v2.90 of the programming software up until now without any problem, I've tried v3.70 as well, but this makes no difference.  The problem still occurs.  I'm running the software on Windows 7 Enterprise 64 bit.

I'm not discounting that the adapter is faulty out of the box, but want to make sure I've not missed anything before we return it for replacement.  Unfortunately, I've not been able to find any reference anywhere on the different device numbers (ie EC3003x and EC3005x) the adapters are reporting, so I have no idea what they indicate...

 

I'm trying to figure out if I can use PWM functionality for this. What I want to do is to send a pulse (low-high-low) with a width of 1 clock cycle (max two). I could write directly to a port pin (assembly clr, then setb), but was hoping to use the MCU-s functionality if it exists.

Hi

I am running two programs on my Flash of si1060/c8051f930
Firmware_1 : On Address 0x0000-0x6FFF
Firmware_2 : On Address 0x7000-0xFFFFFirmware 1 upon run complete runs Firmware_2.I want to lock Firmware_1 memory pages. Therefore, the lock byte(E4) is written from within Firmware_1 to address0x FBFF before jumping to Firmware_2 . However,  if I try to load inside rest of half flash i.e firmware_2 that is not locked, the USB debugger gives me an error Target Failed to respond, Target Disconnect. Moreover, Firmware_2 never executes. It looks like the entire memory is locked from read/write and erase.  I also observed that after writing the lock byte my firmware_1 switches to startup code i.e inside STARTUP.A51. 

This is how I write the lock byte : ///////////// Define Lock Byte /////////////////////
PSCTL |= 0x01;
VDM0CN = 0xA0; // Enable VDD monitor and high threshold
RSTSRC = 0x02; // Enable VDD monitor as a reset source
FLKEY = 0xA5; // Key Sequence 1
FLKEY = 0xF1; // Key Sequence 2 ((U8 xdata *) 0xFBFF) = 0xE4;PSCTL &= ~0x03; // PSWE = 0 which disable writes///////////// End of Define Lock byte ///////////// (edited) 

Please advise me how to lock half pages of flash or what is sequence. 

Thanks,

For the c8051F320

How would i determine how long it takes to complete an instruction?

for the below function i can pass an unsigned char "count" so i can adjust the delay ….so lets say I pass 1 how long would it take to complete in ms both for loops especially the second where j exceeds 112 and exits the for loop ?
 

void delay(unsigned int count)  
{
 int i,j;
 for(i=0;i<count;i++)
 for(j=0;j<112;j++);
}

 

I am developing an application with simplicity studio v4 using the MCU EFM8BB10F2I-QFN20, but during the execution of this code link below, the while loop has a strange behavior, the loop break before (uint16_t) cnt_pressed_time reaches zero, more specifically, the loop is interrupted when (uint16_t) cnt_pressed_time is equal to 255.

 

	   while(1){
		   cnt_pressed_time = 500;
		   while( cnt_pressed_time > 0){}; // <- This while break when cnt_pressed_time reaches 255
		   LED = 1;
		   cnt_pressed_time = 500;
		   while( cnt_pressed_time > 0){};
		   LED = 0;

	   }

 

cnt_pressed_time is decremented within the interruption of timer 2 until it reaches zero using the code below:

if (cnt_pressed_time> 0) cnt_pressed_time--;

I already checked that part of the code and it is working correctly.
I couldn't understand why this is happening, any help is very welcome.

Thank you,

I know this might be a strange question, but has anyone here been able to successfully get the BME280 to work with any micro in the EFM8 family? 

Hi

 

where can I Download the J-link Firmware ?

I can't connect to target MCU, because the adaptater is see as "custom board" and the debug mode is OFF ( normally debug mode is MCU ), i don't know how it

happened but i want to reflash J-Link adaptater.

 

If i want to change the debug mode, a prompt tell that the kit is in bootloader mode, ( I try push reset when plugging usb but don't work )

Thanks.

 

I am working on a project based on the EFM8BB21F16A-QFN20 that makes use of the SMBus peripheral for I2C Master communications in SS5 with Keil v9.60.0

After reviewing available example code, I have based my I2C implementation around the EFM8BB2_SMBus_MasterMultibyte example.

As a somewhat simplified case, here is what I am seeing when calling something like:

SMB_DATA_OUT[0] = 0xE0;
SMB_DATA_OUT[1] = 0x01;
TARGET = SLAVE_ADDR;
SMB_Write();

SMB_DATA_OUT[0] = 0xAA;
SMB_DATA_OUT[1] = 0x00;
TARGET = SLAVE_ADDR;
SMB_Write();

This sends a Start, then the address of the slave with a write bit, then 0xAA, 0x00, followed by a Stop for BOTH calls to SMB_Write().

Somehow, the first SMB_DATA_OUT[] array values are being overwritten by the second set of values, prior to the second call to SMB_Write().

In searching for remedies, I have tried memset'ing SMB_DATA_OUT[] to zero between the calls, declaring the array as volatile, inserting a delay between the calls, and even turning down compiler optimizations as far as they'll go while still allowing the code to fit on the device, all with no apparent effect on this behavior.

Interestingly, calling SMB_Read() between the write commands does NOT produce this result.

For example:

SMB_DATA_OUT[0] = 0xE0;
SMB_DATA_OUT[1] = 0x01;
TARGET = SLAVE_ADDR;
SMB_Write();

SMB_Read();

SMB_DATA_OUT[0] = 0xAA;
SMB_DATA_OUT[1] = 0x00;
TARGET = SLAVE_ADDR;
SMB_Write();

Sends a Start, then the address of the slave with a write bit, then 0xE0, 0x01, followed by a Stop...

then sends the address of the slave with a read bit, the byte read from the slave, then a Stop..

Then sends a Start, the address of the slave with a write bit, then 0xAA, 0x00, followed by a Stop...

Exactly as would be expected.

 

The nature of the slave device in use mandates multiple subsequent write commands which I wouldn't normally expect to be an issue.

I feel like I must be missing some obvious flag here somewhere but I have no idea where else to look.

Any suggestions would be greatly appreciated.

 

I use Simplicity Version SV5.0.2.0

When I use Energy Profiler to monitor sleepy bee 8 bits MCU current consumption, the code on MCU will not able to run. I use EFM8SB2 starter kit, the version is "PCB5100 Rev A02, BDR5100A Rev A03".

I check my SLWSTK6006A, the Energy Profiler works fine.

The reset button on Kit is also not function. But when it push down, the Energy profiler can shows the current changing.

Does anyone can help me out? It is urgent for project.

Thanks,

Mark