Just updating everyone on my MCUBoot Bootloader progress:
(1) Yep it's possible to move the Standby Firmware Image to SPI Flash. Now testing this
(2) This solves a major showstopper with MCUBoot. We now allow application firmware images of up to 464 KB in size
(3) Now putting in a 5 second delay when MCUBoot starts up. If the watch button is pressed and held during the 5 seconds, MCUBoot will roll back the firmware to the previous one
(4) MCUBoot now displays a graphic image stored in SPI Flash while booting. This is needed because we have to show something during the 5 second delay. Also when MCUBoot swaps firmware during upgrade
(5) I have created a tool that loads a 240x240 PNG file into SPI Flash for display by MCUBoot: https://github.com/lupyuen/pinetime-graphic
So my job this weekend is to do more testing of MCUBoot with SPI Flash
And there shall be a new article to explains how all the above stuff works. So that someone can back me up on the MCUBoot development :-)
(1) Yep it's possible to move the Standby Firmware Image to SPI Flash. Now testing this
(2) This solves a major showstopper with MCUBoot. We now allow application firmware images of up to 464 KB in size
(3) Now putting in a 5 second delay when MCUBoot starts up. If the watch button is pressed and held during the 5 seconds, MCUBoot will roll back the firmware to the previous one
(4) MCUBoot now displays a graphic image stored in SPI Flash while booting. This is needed because we have to show something during the 5 second delay. Also when MCUBoot swaps firmware during upgrade
(5) I have created a tool that loads a 240x240 PNG file into SPI Flash for display by MCUBoot: https://github.com/lupyuen/pinetime-graphic
So my job this weekend is to do more testing of MCUBoot with SPI Flash
And there shall be a new article to explains how all the above stuff works. So that someone can back me up on the MCUBoot development :-)