Tools to help in the recovery of misbehaving/bricked devices.
Caution
This is highly experimental, and should only be used as a last resort. Consult the manufacturer of your device before. Use at your own risk; no guarantee anything will work.
Depending on the state of your device, you may need to do some research into how to force the device into bootloader. Some adapters have a dedicated button, others require opening the casing.
If your device cannot even enter the bootloader, you will not be able to use the methods below.
Some methods to (usually) force into bootloader:
- Sonoff ZBDongle-E
- pressing the
BOOT
button (inside the casing), plugging it in, then releasingBOOT
after a few seconds.
- pressing the
- SMLight (SLZB-06 series)
- connecting
G
and0
(inside the casing) then plugging it in. More details
- connecting
- SMLight (SLZB-07 series)
- connecting
FLSH
with the metal part of the antenna (inside the casing). More details
- connecting
Tip
In some cases, universal-silabs-flasher or ember-zli might be able to do that for you without opening the casing (--bootloader-reset [yellow|ihost|slzb07|sonoff]
for the former, Force reset
for the latter).
You can try the following (non-exhaustive) software:
- universal-silabs-flasher (dedicated to Silabs products)
- ember-zli (dedicated to Silabs products)
- ExtraPuTTY (with XMODEM file transfer)
- SecureCRT (with XMODEM file transfer)
Clears the entire NVM3 section. Erases the non-volatile memory, including network configs, etc.. After flashing, you will need to restore or create a new network.
The file name format is as follow:
<CHIP_NAME>_<GBL_TYPE>_<FLASH_BASE>_<FLASH_SIZE>_<FLASH_PAGE_SIZE>_<BTL_APPLICATION_BASE>_<NVM3_DEFAULT_NVM_SIZE>.gbl
Important
Current builds are only intended for use with default project parameters (no customization to the bootloader or other relevant areas) used by silabs-firmware-builder
projects. Check in the relevant location (example) in the repository of your firmware provider for the NVM3_DEFAULT_NVM_SIZE
you should use.
- Sonoff ZBDongle-E NCP (
EFR32MG21A020F768IM32_nvm3_clear_0_786432_8192_16384_32768.gbl
)
Clears the entire section after the bootloader (including NVM3). Erases any firmware previously flashed. After flashing, only the bootloader will be available (automatically entered by the chip), and a new firmware will have to be flashed then run.
The file name format is as follow:
<CHIP_NAME>_<GBL_TYPE>_<FLASH_BASE>_<FLASH_SIZE>_<FLASH_PAGE_SIZE>_<BTL_APPLICATION_BASE>.gbl
Important
These are unusually big GBL files, flashing will take a lot longer than usual (~5 minutes for serial, 2-3 times that for TCP). Make sure your connection is solid and won't drop over the duration or you may have to start over.
- SMLight SLZB07mg24 (
EFR32MG24A020F1024IM40_app_clear_134217728_1048576_8192_134242304.gbl
) - TubesZB MGM24PA (
MGM240PA32VNN_app_clear_134217728_1572864_8192_134242304.gbl
)