meshtastic
[Bug]: Update all bootloader of nRF52 devices to recent 0.9.2 version
Category
Hardware Compatibility
Hardware
T-Echo
Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?
- [ ] Meshtastic UI aka MUI colorTFT
- [ ] InkHUD ePaper
- [ ] OLED slide UI on any display
Firmware Version
bootloader
Description
Currently for example the t-echo have an outdated bootloader version. This outdated bootloader version is from the year 2021. I have the issue with it to not be able to factory reset it.
I installed from here https://meshtastic.org/docs/getting-started/flashing-firmware/nrf52/update-nrf52-bootloader/#method-1-using-the-uf2-file-recommended this file https://github.com/meshtastic/firmware/raw/master/bin/update-lilygo_techo_bootloader-0.6.1_nosd.uf2
then i download the current firmware release and used the file Meshtastic_nRF52_factory_erase_v3_S140_6.1.0.uf2 from it. It is not working as expected. It is not doing a factory reset. You can see the problem directly after first boot. The region should be shown at the first screen with UNSET. But the region is still set.
This and other issues are out there in combination with those unnecessary many bootloader versions. Would i have a Seeed Tracker 1000-E, i would need based on the description here https://meshtastic.org/docs/getting-started/flashing-firmware/nrf52/nrf52-erase/#nrf52 a factory erase file named Meshtastic_nRF52_factory_erase_v3_S140_9.2.0.uf2 . Because i would have followed the recommended bootloader update before with this file https://github.com/adafruit/Adafruit_nRF52_Bootloader/releases/download/0.9.2/update-t1000_e_bootloader-0.9.2_nosd.uf2 But there is no such factory erase file.
At the end there should be one bootloader version, version 0.9.2, for all nrf52 devices. And then there should be one factory erase file for this bootloader version. This would simplify much and also with a high chance fix the factory erase issue i have with the old bootloader version 6.1.0 on the t-echo.
After some further tests i figured out the broken factory reset is a regression of recent Meshtastic firmware version 2.7. Using 2.6.11 beta i was able to reset the device. If someone else needs to factory reset a nrf52 device, flash back to firmware 2.6.11, wait for reboot, after reboot, go again in the bootloader file transfer mode, use Meshtastic_nRF52_factory_erase_v3_S140_6.1.0.uf2, wait until it reboots. When it have reboot and you see UNSET, you can again flash to firmware version 2.7.
All the bootloader versions still need a update. This bootloader versions mixup is not beneficial. Lets have one bootloader version for all nrf52 device. Like there is always one Meshtastic version for all supported devices.
After some further tests i figured out the broken factory reset is a regression of recent Meshtastic firmware version 2.7. Using 2.6.11 beta i was able to reset the device. If someone else needs to factory reset a nrf52 device, flash back to firmware 2.6.11, wait for reboot, after reboot, go again in the bootloader file transfer mode, use Meshtastic_nRF52_factory_erase_v3_S140_6.1.0.uf2, wait until it reboots. When it have reboot and you see UNSET, you can again flash to firmware version 2.7.
All the bootloader versions still need a update. This bootloader versions mixup is not beneficial. Lets have one bootloader version for all nrf52 device. Like there is always one Meshtastic version for all supported devices.
After flashing the factory erase file and waiting a reboot, did you open a serial monitor to start the erase process?
I have one T1000-E, two sets of T114/T-Echo all running 2.7.x train but never had issue with factory erase on Web Flasher.
While it seems opening serial monitor(or anything that works as a serial terminal) is required to begin the erase. (btw, the output says press key to erase, but Web Flasher's serial monitor automagically takes care of it? i never pressed a single key after opening the monitor)
although, if there's no negative impact to unity the factory erase binary across all nRF52 devices, i think that's good thing to do, and might prevent issues in the future.
