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.
Visit the EFM8BB1 Low Cost Kit page:
Have any questions about the kit? Leave your questions below in the comments.
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.
在用EFM8SB1做这个触摸检测的时候，发现调节触发的灵敏度没有效果。调节的三个参数为Average Touch Delta ,Active Threshold和Inactive threshold
Hi. I designed many small embedded devices 7 yers ago. I was use Atmel AVR, Freescale S08 and few other chip. But now I return to this work and see ARM 32 bit in all segments. What you think about it? Thank You 192.168.0.1
I am using EFM8LB12.
The question is about SPI.
23K256 memory from MicroChip.
I write to her byte. In response from the memory on the oscillograph screen, everything is beautiful and correct.
writeSPI (0x03) // Read command
writeSPI (0x00) // Address
writeSPI (0xFF) // dummy byte
byte = SPI0DAT
As a result, I get byte = 0xFF
I am currently developing some firmware for a battery charger that uses the EFM8BB31F64I-C-5QFN32 and the EFM8 USB Type-C Library (ver 1.1.1) which is available as part of the 4.1.7 SDK.
We have had reasonable success utilising the library and are at the stage where we are making final modifications ready for production.
Unfortunately in our latest design iteration we have hit a problem. One of our requirements was to have a serial interface, and we wanted to keep the option of utilising the built in bootloader available through UART0. I have been able to get the UART and PD library working independently but seem to be able to get them to work alongside each other. And believe the problem is due to changes in the pin allocation made to accommodate the UART0 pins.
It is my understanding that the SPI module is used by the library to enable comms on the USB CC lines. And has its signals rerouted from the pins assigned by crossbar (physically not connected to anything) to the pins that are physically connected to these lines. Looking at the pin configuration I could see that the SPI module should be allocated pins P0.3, P0.5 and P0.6.
To accompany the UART0 interface I shifted the pins to P0.2, P0.3 and P0.6 (since UART0 required P0.4 and P0.5).
I believe the problem is that the MISO signal that is originally assigned to P0.5. Looking at the registers I can see that the other SPI signals (Clk and MOSI) are routed via the configurable logic units, and confirmed that the library still works when only the clk pin is changes (P0.3 changed to P0.2) but as soon as I try and change P0.5 to P0.3 the library stops working and looking at the PD messages using an analyser it looks as though incomplete responses are being sent back by the charger/library during PD negotiations (backing up the theory the problem is caused by the MISO pin being changed).
Due to not being able to see anything in the register settings that shows how the MISO signal (P0.5) is being redirected, I'm assuming that the library must be manually referring to the pin directly. Which would explain why it is unable to cope with the pin assignment changing for that specific signal.
Could you please confirm if this is the case and if there is a way of getting both UART0 and the PD library to work alongside one another.
Does anyone know how it is calculated checksum, when programming through "Download code to flash memory" button in keil uVision IDE?
Flash Image Update Complete.
Flash Program Done: 92 bytes programmed.
Flash Verify Done: 92 bytes verified.
Flash Load finished at 23:19:03
Since 3 weeks now, I have issue debugging my own PCB based on EMF8SB1 part with the SLSTK2010A hardware tool with Simplicity Studio 4.
I have ONLY connected 4 pins on the device (GND, VCC, C2K, C2DATA)
The debugg mode is ''OUT mode'' and the error message he got is:
J-Link V6.10g Error
''EFM (C2): Connect failed and connected J-Link (S/N 440046811) does not support fallback method (firmware too old). Please get in touch with SEGGER''
Please see the ''erreurj-link mode OUT'' image attached.
Any help will be appreciate
Can anyone help me out, i m getting a problem on Windows8 PC not able to install drivers for C8051F340
I have 32 bit drivers and sample example which is working fine on Windows 32 Bit PC
Where can i find the 64bit drivers and sample application for C8051F340
I am working with Simplicity Studio 4 with the Keil compiler to develop for an EFM8SB2. I have been using Timer 2 with no trouble. I can't get Timer 3 to be recognized.
I have set up Timer 3 to run, with the low byte disabled to fire every 10 milliseconds, and with the interrupt enabled at low priority. When I try to write the code for the interrupt, I get the message "Symbol 'TMR3CN0_TF3H' could not be resolved. See below.
I have checked that all of the entries relevant to Timer 3 are present in SI_EFM8SB2_Register_Enums.h.
I have checked the .hwconfig file and initdevice.c to confirm that the code is present and matches my chosen configurations.
Can anyone please shed some light on why things like TMR3CN0_TF3H are not accessible.
Thanks in advance,
I use Simplicity-Studio and built a board using the 8 bit controller: EFM8UB20F64G-A_QFP48.
I configured Timer 4 for a counter that has to do an interrupt each 1mS and count time (until few minutes).
I tried to configure the counter by the Simplicity-Studio Configurator and also handy.
It is always do the interrupt after about half of the time (0.56 mS) and it doesn't matter what numbers I insert to the " Target Overflow Frequency" (although I have changed it from 0 to 65000) and also have change the clock source to Sysclk or sysclk/12). I am also configured Disable low byte interrupt and 16 bit auto-reload.
I have done that also without the configurator and got the same. I don't succeed to change the Timer4 interrupt timing!!
it is always interrupt after 0.56 mS without any change - doesn't matter all my different configurations!
I also tried to put the following in the beginning of Timer4 interrupt function:
TMR4H = 0xRR; //I have changed RR to a lot of numbers
TMR4L =0xRR; //I have changed RR to a lot of numbers.
But it didn't change anything.
Please help me understand it and have the ability to change toe interrupt timing.
I am facing problem in configuring RTC as interrupt in C8051 - F930 MCU. Can anyone help with the list of registers I need to configure.
I am using Development Board : 4355-LED-868 (4355-PRXB868B) for the same. Please share if any example code available.
I want to remove MCU EBID (C8051F981 - GM) from 4355-LED-868 (4355 - PRXB868B) development board. Please help with the same.