fix: align bootloader image validation limits
This commit is contained in:
@ -18,7 +18,7 @@ This guide explains the Universal Shifters single-slot bootloader update flow in
|
||||
## Image Requirements
|
||||
|
||||
- File extension must be `.bin`.
|
||||
- Image must be at least 8 bytes and no larger than `0x42000` bytes.
|
||||
- Image must be at least 8 bytes and no larger than `0x3F000` bytes (252 KiB).
|
||||
- Image bytes must start at application address `0x00030000`.
|
||||
- Initial stack pointer must be aligned and within `0x20000000..=0x20010000`.
|
||||
- Reset vector must have the Thumb bit set and point inside the image after the first two vector words.
|
||||
@ -40,7 +40,7 @@ This guide explains the Universal Shifters single-slot bootloader update flow in
|
||||
| Invalid stack pointer or reset vector | `.bin` is not a raw app image for `0x00030000` | Rebuild/export the application image from the correct linker layout. |
|
||||
| Could not connect to bootloader DFU mode | Phone did not find `US-DFU` after app reset | Move closer, retry, and verify the device is advertising `US-DFU`. |
|
||||
| Timed out waiting for bootloader DFU status | Status indication/read did not arrive | Reconnect to `US-DFU` and retry. |
|
||||
| Bootloader status `bounds error` | Image length or app start rejected | Use a valid app image no larger than `0x42000` bytes. |
|
||||
| Bootloader status `bounds error` | Image length or app start rejected | Use a valid app image no larger than `0x3F000` bytes (252 KiB). |
|
||||
| Bootloader status `CRC error` | Full-image CRC did not match flash contents | Re-export or re-download the `.bin`, then retry. |
|
||||
| Bootloader status `vector table error` | Bootloader rejected the written vector table | Rebuild firmware for app start `0x00030000`. |
|
||||
| Bootloader status `flash error` | Flash erase/write/read failed | Retry once; if repeated, service or externally reflash the device. |
|
||||
|
||||
Reference in New Issue
Block a user