It turns out that there was a bug in both the bootloader and the app linker scripts, which allowed the app image to extend to the bootloader settings page, and hence erase the settings when programmed. This would only have been felt if the app firmware actually used this page, which until now hasn't happened. While this could be considered a BLAPI change, I'm considering it an implementation bug and not updating the BLAPI version number. After this fix, both the app linker script and bootloaders now enforce that the app doesn't extend into the last page.
|Failed to load latest commit information.|
|app_layer_v1||firmware: Add SYNC command|
|blapi||bootloaders / BLAPI: Bug in address map|
|blink||Added some logging and better error handling in device bootloader.|
|bootloader||bootloaders / BLAPI: Bug in address map|
|bootloader_common||bootloaders / BLAPI: Bug in address map|
|common||firmware: Thread-safety and cleanup|
|device_bootloader||bootloaders / BLAPI: Bug in address map|
|latency_tester||Initial implementation of device bootloader.|
|libadb||Fixed a bug with adb_file.|
|libbtstack||firmware: Upgrade btstack to r2027|
|libconn||firmware: Upgrade btstack to r2027|
|libusb||USB device descriptor: declare a 500mA draw.|
|microchip||Fix compilation in Linux|
This directory holds the firmware running on the IOIO board.