SEGGER J-Link VersionIf you are using the SEGGER J-Link driver and/or tools, please ensure you are using the latest version to avoid problems. This is taken care of in Simplicity Studio, but if you are using other tools please ensure that you are using a recent release fromFirmware Upgrade Instructions 1.
Download Simplicity StudioIf you don't have Simplicity Studio 3 installed already, download it from.If you are unsure of which version you currently have installed, see.Simplicity Studio is available for Windows, Linux and Mac OS X.If you already have Simplicity Studio 3 installed, proceed to step 3. Install Simplicity StudioInstall using the downloaded file and start Simplicity Studio. When asked about which features to install, select EFM32:3. Upgrade Simplicity StudioMake sure you have installed the most recent updates by clicking the 'Update Software' button, as indicated with '1.' In the image below.
Upgrade the FirmwareConnect your kit, and find it in the list of detected hardware. You might need to refresh the list manually. Select the kit you want to upgrade the firmware on.
If a new firmware revision is available, click the 'download' link to download the upgrade file to your computer.After the download finishes, click the 'install' link to install the new firmware on your kit.After the upgrade completes, the kit should show up as a USB drive with the same name as your kit.
Are you looking for a CLI or GUI utility to upload programs to EFM32 microcontrollers through the factory-programmed bootloader? Look no further.A great feature of EFM32 microcontrollers, by Silicons Labs, is the factory-programmed UART bootloader that may be used to upload programs into the microcontroller instead of using a commercial programmer. The bootloader uses the protocol to transfer data and, as referred on the application note, TeraTerm, which supports that kind of data transfers, may be used. However, if you want the capability of uploading a program through your own application a command-line utility is what you need. Look no further, you have efm32loader which can run in CLI or GUI mode (if any arguments are provided).CLI mode usage: UART: efm32loader.exe uart USB: efm32loader.exe usbRegarding hardware, all you need is a USB-to-UART converter connected to your computer.
Connections are as follows: TX - BOOTRX (E11)RX - BOOTTX (E10)DTR - BOOTEN (DBGSWCLK)RTS - RESETPlease be aware that, in order to prevent the bootloader from being overwritten, the linker script must be modified as described on application note AN0003.The source code is available on Github:And there’s also a Windows executable, available here:Bugs report? Suggestions or feature requests? Please use the Github or the comment section bellow.Update : added support for USB bootloader. Ah that’s it!According to the application note:“Bootloader communication is initialized either by transmitting an uppercase “U” on the physical UART interface (which starts the autobaud algorithm), or by enumeration of the USB CDC virtual UART device. Whichever happens first will govern the rest of the bootloader operation.”So, when the USB bootloader is used the “i” character is sent in order to detect it, as you previously suggested.You can download the latest release here:Let me know if this works!You must still ensure that the bootloader is enabled by pulling-up the DBGSWCLK pin and reseting the chip, as in this case the efm32loader won’t do that for you.Like.