Skip to content

Bootloader

Nerivec edited this page Jan 4, 2025 · 15 revisions

Interact with the Gecko bootloader in the adapter.

As of v2.2.0, the bootloader can be entered from either NCP or RCP firmware.

Tip

If your adapter refuses to enter the bootloader when using this command, you may need to use the dedicated button (if any) to force it. The 'Force Reset' option (prompt only available for supported adapters) can also force the adapter to enter the bootloader.

Get info

Print the Gecko Bootloader information.

Example:

Gecko Bootloader v1.12.00.

Update firmware

Update the adapter's firmware. Both upgrade and downgrade are supported.

You will be asked to provide a GBL update file when entering this menu. This may be from the pre-defined list (based on the adapter model you previously selected), a URL, or a file in the data folder.

Tip

You can also upgrade the bootloader itself with this menu, if you have a proper GBL file for it.

Clear NVM3

Clear the entire NVM3 of the adapter.

See https://github.com/Nerivec/silabs-firmware-recovery?tab=readme-ov-file#nvm3-clear for more details.

Caution

Read the above link first! This will erase any network (and associated configuration) present in the adapter. It is recommended you do a backup first, clear the NVM3, then restore your backup, unless you really want to clear everything for good (to create a brand new network for example).

Clear APP

Clear the entire APP of the adapter. This effectively erases the entire firmware. Should only be used to try to recover bricked adapters.

See https://github.com/Nerivec/silabs-firmware-recovery?tab=readme-ov-file#app-clear for more details.

Caution

Read the above link first! This will erase any network (and associated configuration) present in the adapter. It will take a lot longer than flashing a regular firmware, make sure you have a stable connection before starting.

Important

You MUST flash a new firmware afterwards. The adapter will remain in bootloader until you do.

Exit bootloader

Exit the bootloader and let the EmberZNet stack run.

Clone this wiki locally