Difference between revisions of "EFR32xG1x Bootloader"
(→Solution) |
|||
Line 6: | Line 6: | ||
==Solution== |
==Solution== |
||
+ | #Do not perform a chip erase. Basically a separate is not necessary as the J-Link software always performs an implicit erase prior programming if required. |
||
− | #Do not perform a chip erase |
||
#Program the bootloader (see '''Files''' below) as part of the application or in a separate step after programming the application |
#Program the bootloader (see '''Files''' below) as part of the application or in a separate step after programming the application |
||
+ | |||
==Files== |
==Files== |
||
* [[:File:Dummy_btl_efr32xg1x.mot|File: EFR32xG1x default bootloader]] |
* [[:File:Dummy_btl_efr32xg1x.mot|File: EFR32xG1x default bootloader]] |
Revision as of 12:36, 22 September 2017
Description
On EFR32xG1x series devices, a bootloader is executed after reset. The bootloader is stored in a separate section in the Information memory space of the device. The section is called Bootloader (BL) and located at memory address 0x0FE10000. The size depends on the device. Factory-fresh devices are pre-programmed with a simple bootloader which jumps to the start of the internal flash. However, customers are allowed to exchange the bootloader with a customized one which supports more complex tasks like SPI flash, crypto, etc... Therefore, the J-Link software supports erasing as well as programming of this section.
Problem
When issueing a chip erase, the bootloader section and therefore the bootloader will be erased as well. As a result, the device will no longer boot as no valid bootloader resides in the bootloader section.
Solution
- Do not perform a chip erase. Basically a separate is not necessary as the J-Link software always performs an implicit erase prior programming if required.
- Program the bootloader (see Files below) as part of the application or in a separate step after programming the application