The EFM8BB1 Low Cost Kit is an easy to use yet powerful evaluation tool and development starting point. It contains an integrated debugger and a simple USB micro connection to allow rapid prototyping. The board is fully supported in Simplicity Studio including code examples for every peripheral and demos to take advantage of the on board button and LED.
Kit Contents
1 x EFM8 BB1 Low Cost Board (EFM8BB1LCB)
Free Keil compiler license, no code limit
Free IDE and toolset with Simplicity Studio
1 x EFM8 quick start card
Kit Features
On board USB to C2 Debugger
EFM8BB10F8G-A-QSOP24
1 x LED
1 x user button
1 x reset button
Breakout headers for every pin · 20 pin connector for expansion cards, example BGX
SOT-223 voltage regulator footprint for 3.3V rail (LM317 compatible)
Solder jumpers for advanced debugging and developing options
I have a custom board equipped with a 8051F582-IM, the implemented circuit for the C2 and RST interface is attached.
With the weak pull-ups activated (XBR2 = 0x40) there are no issues with debugging over C2 using the USB Debug Adapter.
With the weak pull-ups disabled (XBR2 = 0xC0) I have the following behaviour:
- If I set a break-point before my main-loop it (almost every time) re-triggers the same break-point, or with multiple break-points it "jumps" backwards as if the device did a reset.
- If setting a break-point inside the main loop (or no break-point at all), everything works fine. As well pausing and continuing execution works. Have had a program running for 2-3 hours now without an issue.
- The debugger seems to have more communication faults as well. Forcing me to un-powered it, and restating Simplicity Studio in order to get the debugger up and running again.
The PCB track for the C2 interface is no more than 20-25 mm with the pull-up located on the far side when seen from the MCU. The debugger connects to the PCB using its ribbon cable (C2D, C2CK and ground connected).
The code that is executed before the main loop is the initialisation of the device registers for XBAR configuration, SPI, interrupts, and Timer0, plus setting a digital out to low (not being the RST pin). VDD reset is disable.
Iam using c8051f340 hid firmware template for making a hid device. I had modified my report descriptor values as per my requirement and even changed vid, pid values. But my device is not recognised by pc and showing me this message
"THE LAST USB DEVICE YOU CONNECTED TO THIS COMPUTER MALFUNCTIONED AND WINDOWS DOESNOT RECOGNISE IT" and "DEVICE DESCRIPTOR REQUEST FAILED".
At first I thought it was pc problem and tried various methods to solve it and tried a usb monitoring software to know where the problem exists...I found a packet in which the device sent IN packet with vid is 0000 and pid 0002. Iam doubting that it is problem in communication. I entered correct descriptor values and checked twice.how to know where I did mistake .Im not getting any idea what is the problem...anyone gone through this problem before
Hi, I'm trying to use ADC autoscan (as per AN919) on a system where I've previously used non-autoscan conversions successfully. My basic requirement is to convert P1.2 through P1.5 every 2 msec (triggered by timer 4) with the best accuracy I can. The first problem I'm having is that I'm getting an ADC interrupt but my XDATA doesn't change. The ADC0 output SFR shows something, but nothing gets written to XDATA RAM. Where do I look?
My other specific questions are:
1. How do I force the alignment of my RAM array in XDATA to be word aligned? I tried __align(2) but the compiler chokes.
2. Does the ADRPT still work as I've been accumulating eight 12 bit conversions for lowest noise.
3. What do I set ADC0ASCT to? Is it 0 for 1 scan, 3 for 4 channels, 31 for 4 channels times 8 accumulations or something else?
The latest updates to Windows 10 and Windows 7 have caused reported issues with Silicon Labs' Toolstick adapters, 8-bit debug adapters, and 32-bit debug adapters.
The reported behavior is that the debug adapters do not enumerate properly. Affected devices will not show up in the Windows Device Manager. Example bug reports are linked below.
If you are running into these issues you can try to roll back the above updates. However note that Microsoft places some restrictions on rolling back an update. For more information about rolling back a windows update and Microsoft's restrictions on uninstalling updates click the links below.
I'm wondering, if I power the MCU with +3.0V, and using the internal voltage reference of 2.4V, am I still able to sample signals from 2.4-3.0V? The datasheet says that using a (stable) power supply as external voltage reference "can provide the ADC with added dynamic range". By how much? I'll only be sampling at an 8 bit resolution.
I'm making a project where time is critical so I can't rely on timers because, depending of the instruction being interrupted, the number of cycles after interrupt may differ.
I made a small assembler routine that "wastes" time by executing MOVC A,@A+DPTR instruction in a loop. The reference guide states that it takes 6 cycles to execute this instruction at max speed (48 MHz) with prefetch, but it actually takes 5 cycles after branch, and 4/5 (I guess it's because prefetch is 2 bytes, and the instruction is 3 bytes so it sometimes takes an extra cycle) if it's executed consecutively. Also DJNZ takes 4 if the jump is taken, and not 5. I noticed it because the routine was executed faster than I expected. I saw in the guide that clock frequency could vary 1.5%, but this was much more than that (6%). So I used debugger with timer and it showed that the guide is wrong. When taken different timings into account, I got that 6% difference.
Forum
Introducing the new EFM8BB1 Low Cost Kit
The EFM8BB1 Low Cost Kit is an easy to use yet powerful evaluation tool and development starting point. It contains an integrated debugger and a simple USB micro connection to allow rapid prototyping. The board is fully supported in Simplicity Studio including code examples for every peripheral and demos to take advantage of the on board button and LED.
Kit Contents
Kit Features
Visit the EFM8BB1 Low Cost Kit page:
https://www.silabs.com/products/development-tools/mcu/8-bit/efm8bb1lck-efm8-busy-bee-low-cost-starter-kit
Have any questions about the kit? Leave your questions below in the comments.
Tips for troubleshooting and asking questions
Before posting a question
When posting a question, make sure to include the following:
For general community usage please refer to the Silicon Labs Community Guidelines.
Development for EFM8SB with IAR Workbench
Dear Sir,
I am new to Simplicity Studio and do not have any experience with the development on Simplicity Studio.
Can I develop my code on IAR Workbench and port my 8051 hex Code output onto EFM8SB Developer kit, will it work.
I wish to quickly learn working on to Simplicity Studio, Please advice suitable help for the same.
Please advice.
Connection Problem of USB Debug Adapter with Simplicity Studio
Hello,
When I connected a USB debug adapter to target and PC, I received an error message as below:
I used the version of Simplicity Studio is SV4.1.11.7. I paste it below:
The 8 bits MCU i used is C8051F563-A_IM. Can you let me know how to solve it?
Thanks,
Hao
Issues with resets and/or debugger when disabling weak pull-ups (external pull-up implemented)
I have a custom board equipped with a 8051F582-IM, the implemented circuit for the C2 and RST interface is attached.
With the weak pull-ups activated (XBR2 = 0x40) there are no issues with debugging over C2 using the USB Debug Adapter.
With the weak pull-ups disabled (XBR2 = 0xC0) I have the following behaviour:
- If I set a break-point before my main-loop it (almost every time) re-triggers the same break-point, or with multiple break-points it "jumps" backwards as if the device did a reset.
- If setting a break-point inside the main loop (or no break-point at all), everything works fine. As well pausing and continuing execution works. Have had a program running for 2-3 hours now without an issue.
- The debugger seems to have more communication faults as well. Forcing me to un-powered it, and restating Simplicity Studio in order to get the debugger up and running again.
The PCB track for the C2 interface is no more than 20-25 mm with the pull-up located on the far side when seen from the MCU. The debugger connects to the PCB using its ribbon cable (C2D, C2CK and ground connected).
The code that is executed before the main loop is the initialisation of the device registers for XBAR configuration, SPI, interrupts, and Timer0, plus setting a digital out to low (not being the RST pin). VDD reset is disable.
Any ideas?
Edit: Corrected device type
USB HID device using c8051f340 having a problem in enumeration of device
Hi everyone,
Iam using c8051f340 hid firmware template for making a hid device. I had modified my report descriptor values as per my requirement and even changed vid, pid values. But my device is not recognised by pc and showing me this message
"THE LAST USB DEVICE YOU CONNECTED TO THIS COMPUTER MALFUNCTIONED AND WINDOWS DOESNOT RECOGNISE IT" and "DEVICE DESCRIPTOR REQUEST FAILED".
At first I thought it was pc problem and tried various methods to solve it and tried a usb monitoring software to know where the problem exists...I found a packet in which the device sent IN packet with vid is 0000 and pid 0002. Iam doubting that it is problem in communication. I entered correct descriptor values and checked twice.how to know where I did mistake .Im not getting any idea what is the problem...anyone gone through this problem before
Please help me
Clock Stretching Between NACK and STOP Condition
I'm using EFM8LB12F32-B-QFN24
Slave : EFM8LB12F32-B-QFN24
Master : Raspberry Pi3
Clock : 400kHz
I know as NACK and Stop Condition are generated by MASTER Device.
Why does It occure the Clock Stretching between NACK and Stop Condition.
My ISR Code :
SI_INTERRUPT(SMBUS0_ISR, SMBUS0_IRQn)
{
static U8 SFRPAGE_save;
static U8 wr_check;
SFRPAGE_save = SFRPAGE;
SFRPAGE = 0x00;
if (SMB0CN0_ARBLOST == 0){
switch (SMB0CN0 & 0xF0){
case 0x20:
SMB0CN0_STA = 0;
i2c_ADD = SMB0DAT;
if(((i2c_ADD&0xFE) == 0xF0){
...... // if Read, Send Data
}else // NACK Recieved
{
SMB0CN0_ACK = 0;
SMB0CN0_SI = 0;
}
break;
...
EFM8LB laser bee ADC autoscan problems
Hi, I'm trying to use ADC autoscan (as per AN919) on a system where I've previously used non-autoscan conversions successfully. My basic requirement is to convert P1.2 through P1.5 every 2 msec (triggered by timer 4) with the best accuracy I can. The first problem I'm having is that I'm getting an ADC interrupt but my XDATA doesn't change. The ADC0 output SFR shows something, but nothing gets written to XDATA RAM. Where do I look?
My other specific questions are:
1. How do I force the alignment of my RAM array in XDATA to be word aligned? I tried __align(2) but the compiler chokes.
2. Does the ADRPT still work as I've been accumulating eight 12 bit conversions for lowest noise.
3. What do I set ADC0ASCT to? Is it 0 for 1 scan, 3 for 4 channels, 31 for 4 channels times 8 accumulations or something else?
Thanks in advance,
Oliver
Informational Thread: Toolstick and Debug Adapter Issues After Recent Win10 and Win7 Updates.
EDIT: See additional discussion in the Studio forum thread
https://www.silabs.com/community/software/simplicity-studio/forum.topic.html/informational_thread-kgyL
The latest updates to Windows 10 and Windows 7 have caused reported issues with Silicon Labs' Toolstick adapters, 8-bit debug adapters, and 32-bit debug adapters.
The updates in question are:
KB4487044 (Win10 ver 1809)
KB4487017 (Win10 ver 1803)
KB4486563 (Win7)
The reported behavior is that the debug adapters do not enumerate properly. Affected devices will not show up in the Windows Device Manager. Example bug reports are linked below.
1 2 3
If you are running into these issues you can try to roll back the above updates. However note that Microsoft places some restrictions on rolling back an update. For more information about rolling back a windows update and Microsoft's restrictions on uninstalling updates click the links below.
Windows Patching Information
Windows 10 Update FAQ
If you are able to roll back these updates but still experience issues, please submit a support ticket here.
Silicon Labs is in contact with Microsoft and we are working to resolve the issue. Updates will be posted here.
Connection Problem of USB Debug Adapter with Simplicity Studio
Hello,
When I connected a USB debug adapter to target and PC, I received an error message as below:
I used the version of Simplicity Studio is SV4.1.11.7. I paste it below:
The 8 bits MCU i used is C8051F563-A_IM. Can you let me know how to solve it?
Thanks,
Hao
Interrupt in interrupt excecution
Hi all,
I'm using a C8051F124.
Is it possible to call an interrupt while an interrupt routine is already running?
I mean, my TMR2 is running with a low priority. When I excecute the TMR2 routine, the TMR0 flag, with an Higher priority, is fired.
Is the TMR2 routine skipped to excecute the TMR0 or the TMR0 ISR is only excecuted when the TMR2 ISR is finished?
Best Regards.
F930 RAM usage ?
My project is using UART and large data stream is coming in which needs to store for further processing. I need an array size of 1k to store all data.
Array should be located in Xdata space so the array is assigned as: unsigned char xdata myarray[1000];
I can compile it with no errors but program just halts immediately and does nothing at all.
I tried something like large memory model but no change. I use IDE from Silabs and Keil compiler.
How can i use the full RAM space of F930?
Im a weekend programmer and this might sound as a crazy question... :/
-J
C8051F85x/86x internal ADC voltage reference?.
Hello,
I'm wondering, if I power the MCU with +3.0V, and using the internal voltage reference of 2.4V, am I still able to sample signals from 2.4-3.0V? The datasheet says that using a (stable) power supply as external voltage reference "can provide the ADC with added dynamic range". By how much? I'll only be sampling at an 8 bit resolution.
thanks
iosman
Mismatch in instruction duration efm8ub20
I'm making a project where time is critical so I can't rely on timers because, depending of the instruction being interrupted, the number of cycles after interrupt may differ.
I made a small assembler routine that "wastes" time by executing MOVC A,@A+DPTR instruction in a loop. The reference guide states that it takes 6 cycles to execute this instruction at max speed (48 MHz) with prefetch, but it actually takes 5 cycles after branch, and 4/5 (I guess it's because prefetch is 2 bytes, and the instruction is 3 bytes so it sometimes takes an extra cycle) if it's executed consecutively. Also DJNZ takes 4 if the jump is taken, and not 5. I noticed it because the routine was executed faster than I expected. I saw in the guide that clock frequency could vary 1.5%, but this was much more than that (6%). So I used debugger with timer and it showed that the guide is wrong. When taken different timings into account, I got that 6% difference.
Did someone else encounter this?
EFM8LB How can I configure SMBUS 400kHz?
Hi,
I try to configure SMBus SCL Freq 400kHz. (Master)
But, Timer Reload Overflow Period is Very Short.
I want to configure SMBus SCL Freq 400kHz And SCL Low Time(Timer Reload Overflow Period) > 1.3us.
How can I configure this?
My Timer Configuration as Bellow: