See if this help:

https://www.silabs.com/documents/public/application-notes/AN282.pdf

https://www.silabs.com/documents/public/example-code/AN282SW.zip

Hi Walter,

Thank you for your inquiry regarding modifying your project to use the LFRCO instead of the LFXO.  I have a few comments and questions:

1) Please note that there are certain accuracy requirements for Bluetooth applications which, if not met, can cause connection problems.  Section 4.1.2 on page 13 of UG136: Silicon Labs Bluetooth ® C Application Developer's Guide for SDK v2.x states (regarding the LFCLK):

"The accuracy of this clock depends on the operating mode of the device. When advertising or scanning, accuracy is not that important,
but when a connection is open the accuracy must be at least ±500 ppm. This clock can be driven either by LFXO, PLFRCO
(EFR32xG13 or xGM13), or LFRCO (EFR32xG2x or xGM2x), depending on the accuracy requirements. If applications only require advertising
or scanning, LFRCO can be used as the clock source. However, if Bluetooth connections are required, the clock source must
be either LFXO, PLFRCO (EFR32xG13 or xGM13) or LFRCO with High Precision Mode (EFR32xG22 or xGM22). When using
PLFRCO or LFRCO, the accuracy of the clock must be configured to ±500 ppm."

and 

"If none of LFXO, PLFRCO or LFRCO with High Precision Mode is connected but Bluetooth connections are required in the design,
sleep has to be explicitly disabled from the application. As mentioned in section 4.2.4 Sleep, if the LFCLK is not accurate enough, then
the sleep modes have to be disabled for Bluetooth connections to operate correctly."

Note that the EFR32BG21 device does not have a PLFRCO or an LFRCO with High Precision Mode.  Thus, you must use an external LFXTAL with the LFXO if your device will go into sleep mode.

2) At what point exactly after the call to  gecko_stack_init() does your program hang?

Thank you, and please let me know if you have any questions.  

Regards,

Mitch

Hi EMBgangsta,

Thank you for your inquiry regarding the EFM32GG280 (Series 0 EFM32 device).  Unfortunately, I think the information someone gave you is incorrect, as there are no level shifters in the EFM32GG280, not any other EFM32 device.  This device has power supply pins VREGVDD (internal digital voltage regulator supply), AVDD (analog supply), and IOVDD (I/O supply), and these all must be equal in voltage in the range [1.98 V, 3.8 V].  Additionally, the input and output low and high voltages (V_IOIL, V_IOIH, V_IOOL, V_IOOH) are all relative to this VDD voltage, and can be seen in Table 4.7 GPIO on page 70 of the EFM32GG datasheet.

If you need to interface I/O with a device outside of this range and require level shifting capability, you will have to utilize external level shifting devices.  I hope this helps!  Let me know if you have any questions.

Regards,

Mitch

Hi EMBgangsta,

Thank you for your inquiry regarding the EFM32GG280 (Series 0 EFM32 device).  Unfortunately, I think the information someone gave you is incorrect, as there are no level shifters in the EFM32GG280, not any other EFM32 device.  This device has power supply pins VREGVDD (internal digital voltage regulator supply), AVDD (analog supply), and IOVDD (I/O supply), and these all must be equal in voltage in the range [1.98 V, 3.8 V].  Additionally, the input and output low and high voltages (V_IOIL, V_IOIH, V_IOOL, V_IOOH) are all relative to this VDD voltage, and can be seen in Table 4.7 GPIO on page 70 of the EFM32GG datasheet.

If you need to interface I/O with a device outside of this range and require level shifting capability, you will have to utilize external level shifting devices.  I hope this helps!  Let me know if you have any questions.

Regards,

Mitch

Hi tejas75,

Thank you for your inquiry about using the Precision32 IDE for development with the SiM3i1xx devices.  Please forgive the relative lack of information and users of this device, as it is not as popular as our EFM32/EFR32 series devices.  

I am not sure exactly what you are asking how to do in this query - are you looking for an assembly listing file, a map file showing the memory location of all variables and segments, or a representation of the machine code/hex file?  Not that you can add a post-build step as described in this knowledge base article (https://www.silabs.com/community/mcu/32-bit/knowledge-base.entry.html/2012/02/06/how_can_i_generateh-YwQ8) to generate a hex file with the build.  This will allow you to see the hex file generated (in the build artifacts folder), which you can view with a text editor like Notepad++ or a hex file viewer.  The post-bild command to generate a hex file is:
 

arm-none-eabi-objcopy -O ihex '${BuildArtifactFileName}' '${BuildArtifactFileBaseName}.hex';

Additionally, you can add another post-build command to generate a mixed C/Assembly listing file <project>.lst which will also appear in your build artifacts directory.  The steps to do this for Simplicity Studio are described in this knowledge base article (https://www.silabs.com/community/mcu/32-bit/knowledge-base.entry.html/2016/02/05/generating_a_listing-D1ES), but the steps are the same for Precision32.  The command to generate a listing file in your build artifacts directory is:

arm-none-eabi-objdump -d -t -S ${ProjName}.axf > ${ProjName}.lst

I hope this helps.  Please let me know if you have any questions.

Regards,

Mitch

Hi tejas75,

Thank you for your inquiry about using the Precision32 IDE for development with the SiM3i1xx devices.  Please forgive the relative lack of information and users of this device, as it is not as popular as our EFM32/EFR32 series devices.  

I am not sure exactly what you are asking how to do in this query - are you looking for an assembly listing file, a map file showing the memory location of all variables and segments, or a representation of the machine code/hex file?  Not that you can add a post-build step as described in this knowledge base article (https://www.silabs.com/community/mcu/32-bit/knowledge-base.entry.html/2012/02/06/how_can_i_generateh-YwQ8) to generate a hex file with the build.  This will allow you to see the hex file generated (in the build artifacts folder), which you can view with a text editor like Notepad++ or a hex file viewer.  The post-bild command to generate a hex file is:
 

arm-none-eabi-objcopy -O ihex '${BuildArtifactFileName}' '${BuildArtifactFileBaseName}.hex';

Additionally, you can add another post-build command to generate a mixed C/Assembly listing file <project>.lst which will also appear in your build artifacts directory.  The steps to do this for Simplicity Studio are described in this knowledge base article (https://www.silabs.com/community/mcu/32-bit/knowledge-base.entry.html/2016/02/05/generating_a_listing-D1ES), but the steps are the same for Precision32.  The command to generate a listing file in your build artifacts directory is:

arm-none-eabi-objdump -d -t -S ${ProjName}.axf > ${ProjName}.lst

I hope this helps.  Please let me know if you have any questions.

Regards,

Mitch

Hi Hitesh Rohila,

In addition to Nam's comments and recommendation to pull up RSTb to VDD instead of VBUS, I also wanted to comment that it is not necessary to connect SUSPENDb to GND with a pulldown resistor.  The SUSPENDb pin is a digital output pin that is logi low when the device is in USB Suspend mode.

When your devices become unresponsive and no longer transmit/receive data after a period of time, what are the voltages on VBUS, VDD, RSTb, SUSPEND, and SUSPENDb?

Please let me know of your observations after taking into account Nam's and my suggestions.  Thank you!

Regards,

Mitch

Hi Jenishkumar,

Thank you for your inquiry about using the Gecko Bootloader with EFR2FG12.  In addition to delu's request for a detailed series of steps to reproduce and a detailed description of how you generate your gbl file (i.e. commands used), I have the following questions:

1) Can you please confirm that you are using the Application Bootloader - Internal Storage Bootloader (single image on 1 MB device)?  Are you using the default version of this from Simpliticy Studio, or have you made modifications (if so, what)?

2) Please confirm that you are acquiring the GBL upgrade image using your main application, which you have written to accept a GBL image and using UART XMODEM protocol and write it to a storage slot located at memory location 0x84000?

3) In order for a bootloader upgrade to take place the GBL must contain a GBL Bootloader tab, which should be added by Simplicity Commander during the GBL file creation process.  Thi is one reason why we are asking for your steps and commander commands used to make the GBL file.

4) How are you managing the version number of your bootloader upgrade image?  Note the following from UG266, section 4.2, page 20: "On Series 1 devices, the first stage bootloader verifies the CRC of the bootloader upgrade present in the bootloader upgrade location in internal flash, and copies the bootloader upgrade over the main bootloader if the version number of the upgrade is higher than the version number of the existing main bootloader."

Thank you!

Regards,

Mitch

Hi Tom,

Thank you for your inquiry regarding GPIO control of the CP2110 device from a MacOSX host platform.  GPIO and other CP2110 device functions are controlled with the use of a device interface library that is available for Windows, Linux, and Mac platforms.  To access this, please download the USBXpressHostSDK for MAC:

https://www.silabs.com/documents/public/software/USBXpressHostSDK-Mac.zip

In this package you can find the AN433: CP2110/4 HID-to-UART API Specification in the [Documentation/Application Notes] folder.  This document describes the use of the CP2110 Interface library.  The library itself and some python scripts demonstrating its use are found in the [/lib] folder.  Additionally, you can find the example application 'HidUARTExample' in the[/Examples] folder.

This example should also show in the source code how to read and write port latch (i.e. GPIO) values on the device using the API functions HidUart_ReadLatch() and HidUart_WriteLatch().

I hope this helps!  

Regards,

Mitch

Doh!  Please excuse me for not reading closely enough and noticing that this discussion concerns the EFM8BB1LCK and NOT the EFM8BB1 STK!  Sorry for the misdirection/irrelevant information.  Also thank you to the others who provided answers on this thread.

Yes, the debug chip (CF326-SX0261GM) on the EFM8BB1LCK can program the EFM8BB3/EFM8LB1 (any EFM8).

Additionally, though you will probably have to remove or disable the EFM8BB1 on the LCK in order to program an external target, you should be able to do it by connecting your external target C2CK, C2D, GND, and VDD signals to the corresponding signals connecting to the EFM8BB1 target device on the LCK, as delu mentions.

Please be aware, however, that these debug signals correspond to pins 1 (C2CK) and 28 (C2D) of the debug device (CF326), however pins 9 and 10 do not correspond to the the target MCU debug/programming pins and using these connections will not work for programming a target device.

On the board, this means that the test points labeled '1' and '2' correspond to "DBG_C2CK" and "DBG_C2D," respectively and are the correct connection points to use for device programming using the onboard debugger (please refer to the illustration below).  Note that the board test points labeled "C2D" and "C2CK" are debug signals associated with the debug device, not the target device, and can NOT be used to program the EFM8BB1 onboard target or an external target (please refer to the illustration below).

Additionally, here are a couple other posts/threads with related information:

https://www.silabs.com/community/mcu/8-bit/forum.topic.html/how_to_debug_externalboardbyefm8bb1lowcostki-CvVi

https://www.silabs.com/community/mcu/8-bit/forum.topic.html/unable_to_use_usbdebuggeradapter8bitonefm8bb-6bG2

I hope this helps.  Let me know if you have any questions.

Regards,

Mitch