• The MCUBoot bootloader (used by InfiniTime)
  
• The NRF Bootloader (used by Wasp-os)
  

• The possibility to force revert to the previous version of the firmware
  
• The possibility to install a recovery firmware from the external flash memory. This firmware can be useful if you installed a firmware that does not support OTA, for example.
  
• Simple UI
  
• The bootloader displays its own version and exports it to the application.
  

• The update procedure from a device coming out of factory (factory bootloader + InfiniTime 0.7.1) : First update the bootloader, then flash the recovery firmware, then use your PineTime
  
• The OTA procedure (update InfiniTime)
  
• The revert procedure
  
• The recovery procedure
  
• The switching procedure to/from InfiniTime and wasp-os
  

• testfw-random-dfu.zip : this firmware contains only random data instead of executable code. This could happen if the user applied a DFU file that is not intended to be run on a Pinetime. In this case, the bootloader will apply the upgrade, notice that it's not runnable and will automatically revert to the previously running firmware.
  
• testfw-no-validate-no-watchdog.zip : this firmware displays a yellow InfiniTime logo. It does not validate the firmware and does not refresh the watchdog. It simulates a firmware that crashes and that is not able to refresh the firmware. The watchdog will reset the device and MCUBoot will revert to the previously running firmware.
  
• testfw-validate-wdt-no-ota.zip : This firmware does refresh the watchdog AND automatically validate the version. It means that to the point of view of MCUBoot, the firmware is working fine! BUT... this bad firmware does not provide the OTA and the reset functionality. This is one of the worst degraded case : the bootloader cannot do anything! The only workaround is to wait for the battery to drain completely and then charge the PineTime again. This is reset the CPU and offer the possibility to force a firmware revert during the next boot.
  
• The worst of the worst degraded cases is one where the new firmware erase or overwrite the bootloader and/or the recovery firmware with invalid data. In this case, the device is totally bricked and can only be recovered using SWD (meaning the device must be opened).
  

(12-27-2020, 10:16 AM)wibble Wrote: I've not done anything with the PineTime in a while, so this is as good an excuse as any The Pi I was using for building and flashing has been repurposed since, so I might have a bit to do before I can test. Do you have links to the procedures you want testing, or did I miss something in the readme?

• Using SWD : flash bootloader.bin at offset 0x00, reset, done.
  
• Using OTA : use NRFConnect or gadgetbridge to OTA a specific firmware that upgrades the bootloader : reloader-mcuboot.zip. When the transfert is complete, your device will reset, the bootloader will be updated, the device will reset again on the new bootloader.
  

• OTA a new version of InfiniTime and validate it.
  
• Reset the PineTime (long push on the button).
  
• When you see a pinecone, press the button until the cone is drawn in blue.
  
• Wait for the revert to be applied
  
• and voilà, you're running the previous version of your firmware.
  

• Reset the PineTime (long push on the button).
  

• When you see a pinecone, press the button until the cone is drawn in red.
  
• Wait for the recovery firmware to be installed.
  
• Your Pinetime should reboot and display the InfiniTime logo. That's it, you're running the recovery firmware. You can try to OTA any version of InfiniTime you like (>= 0.7.1).
  

(12-28-2020, 08:37 AM)JF002 Wrote: Hi @koemdjiev and thanks for testing the update procedure!

This is an expected behavior : the application firmware (InfiniTime), the bootloader and the recovery firmware are 3 different softwares and they all have their own version.
In your case, before the update, you were running InfiniTime 0.8.3, the old bootloader (I can't remember its version), and no recovery software.

When you applied reloader-mcuboot.zip, it only upgraded the bootloader (old -> test version "1.2.3"). But it didn't upgrade the version of InfiniTime that was running on your device.
Then your applied pinetime-mcuboot-recovery-loader.zip. This tool flashes the recovery firmware into the SPI flash memory, but again, it didn't touch the version of InfiniTime you are currently running.
Now, you're still running InfiniTime 0.8.3, and you have the new bootloader (test version "1.2.3") and the new recovery firmware installed on your device.

So, now, if these 2 steps were successful (do you see the new screen of the bootloader when you reset the watch ?), you can update InfiniTime by using the DFU file from the release page (dfu-0.9.0.zip).
[url=https://github.com/JF002/Pinetime/releases/tag/0.9.0][/url]

(12-27-2020, 10:31 AM)JF002 Wrote:

(12-27-2020, 10:16 AM)wibble Wrote: I've not done anything with the PineTime in a while, so this is as good an excuse as any The Pi I was using for building and flashing has been repurposed since, so I might have a bit to do before I can test. Do you have links to the procedures you want testing, or did I miss something in the readme?

I'm happy to provide you with an excuse to work on your PineTime !

The installation procedure is in the release note.

To install the bootloader, you'll first need to run on InfiniTime (0.7.1 or 0.9.0, for example). Then, you have 2 options:

• Using SWD : flash bootloader.bin at offset 0x00, reset, done.
  
• Using OTA : use NRFConnect or gadgetbridge to OTA a specific firmware that upgrades the bootloader : reloader-mcuboot.zip. When the transfert is complete, your device will reset, the bootloader will be updated, the device will reset again on the new bootloader.
  

When the new bootloader is installed, you can install the recovery firmware by using pinetime-mcuboot-recovery-loader.zip. The procedure is the same : OTA this file, reset, let the tool run, reset again and it's done.

You can have a look at the video listed in the release note to have an overview of the procedure : https://video.codingfield.com/videos/watch/5b70cc41-2e14-49cc-a631-0aa466957169

From there, you can test the revert and recovery functionalities.
Revert :

• OTA a new version of InfiniTime and validate it.
  
• Reset the PineTime (long push on the button).
  
• When you see a pinecone, press the button until the cone is drawn in blue.
  
• Wait for the revert to be applied
  
• and voilà, you're running the previous version of your firmware.
  

Recovery:

• Reset the PineTime (long push on the button).
  

• When you see a pinecone, press the button until the cone is drawn in red.
  
• Wait for the recovery firmware to be installed.
  
• Your Pinetime should reboot and display the InfiniTime logo. That's it, you're running the recovery firmware. You can try to OTA any version of InfiniTime you like (>= 0.7.1).
  

(12-29-2020, 06:16 PM)wibble Wrote: Ok - using the Pi for the SWD updates and GadgetBridge 0.51.0 from F-Droid for the OTA. I've not tried OTA before. Note that the phone is somewhat knackered, and has been slightly glitchy with bluetooth recently. This appears unrelated to GadgetBridge and PineTIme.

First used Lup's pinetime-updater to get the PineTime into a known state - it's 'latest' bootloader and application, which is 0.7.1 at present.
Download the RC1 bootloader.bin and flash to 0x0000 using pinetime-updater's from downloaded file option. This gets me the new bootloader working v1.2.3 bootloader, still bringing me into 0.7.1
Download RC1 pinetime-mcuboot-recovery-loader.zip, connect GadgetBridge and use it to OTA. This failed on the first attempt soon after touching the screen to keep it from dimming, but worked on a second attempt when I didn't touch the screen. I don't know if that's an unexpected quirk of GadgetBridge, or just the glitchy bluetooth on this phone.
Download dfu-0.9.0.zip and use GadgetBridge to OTA that - I didn't touch the screen and it worked first time. I now have 0.9.0 and can validate it.
I now tried a few reboot cycles, both green to keep current version, and blue to swap between 0.7.1 and 0.9.0 - it seems smooth and reliable.
Long press to red during the bootloader gets me to the white InfiniTime logo. I then tried OTA to 0.9.0 again. The first time this failed with the progress bar just short of completion, and I had to long-press to reboot and try again. The second attempt failed at ~50% but the third succeeded, and I rebooted into 0.9.0 and validated. I suspect my iffy bluetooth again, but this also shows the process is robust - even with failures during OTA I could still eventually get a successful OTA and a working application without having to use the cable. Nice

I haven't tried the to/from wasp-os yet.

---

On a side note the combination of GadgetBridge and kdeconnect allowed the media controls in 0.9.0 to control the video in the desktop browser, but the scrolling of a title as long as 'WIP: bootloader improvements, factory firmware, OTA - Codingfield' is too fast for comfort.

Quote:I noticed the screen does not turn off when running the recovery firmware.

• Most of the time, resetting the watch and/or the phone and retrying works. To reboot the watch running InfiniTime, simply push the button for 5-10s, it'll reset and reboot.
  
• Do not run NRFConnect and Gadgetbridge at the same time. If one of them auto-connects to the PineTime, the other one won't be able to connect. Also, I noticed that disabling the CTS (current time service) into NRFConnect improves the situation with Gadgetbridge, even if you're not using NRFConnect...
  
• The proximity of other WIFI/BLE/USB-C(with low quality wires) devices might cause RF interferences and cause the transfer to fail.
  
• [EDIT] When using Gadgetbridge, the OTA fails if you receive a notification (gadgetbridge will formward it to InfiniTime and it'll conflict with the OTA process). This is a known bug. As a workaround, you can disconnect from the internet to stop receiving notifications.