Hello,
I would need to check the fw image uploaded to xmos device before flashing it (using xmodem).
Is there some doc reg image created by the xflash? - I could not find any...
I just need to get version and size - from looking into the image file seems like the info is there.
thanks in advance.
wbr
malo
flash image header format Topic is solved
-
malo
- Active Member
- Posts: 33
- Joined: Fri Sep 16, 2016 9:03 pm
-
colin
- Experienced Member
- Posts: 74
- Joined: Mon Dec 16, 2013 12:14 pm
Hi Malo,
The following table describes the image headers used in flash. You can find the offsets for the image size and version numbers here. Note there are two image size/length fields so take care to use the correct one for your purpose.
Best wishes
Colin
The following table describes the image headers used in flash. You can find the offsets for the image size and version numbers here. Note there are two image size/length fields so take care to use the correct one for your purpose.
| Offset | Field | Description |
| 0 | Image Tag | 0x1a551e5 for tools versions Tools12 and below; 0x0FF51DE for tools version Tools13 and above |
| 1 | Page CRC | CRC value for 256 bytes (64 words) from offset 3 of the Image Header Table |
| 2 | Image CRC | CRC value for the full image from offset 3 of the Image Header Table |
| 3 | Image Features (TOOLS 13) | See image features field below |
| 4 | Image Size | Size value the user requested with option --factory or --upgrade (Otherwise same as Image length) |
| 5 | Image Version | Version as specified when using option --upgrade (0 for --factory image) |
| 6 | Image Length | The actual size of the image from offset 0 of the Image Header table to then end of the Application data (or Overlay data if used) |
| 7 | Num Core Images | The number of core tables found within this image |
| 8 | Boot Image Address (TOOLS 13) | The address in RAM where the boot image address is to be stored (symbol __boot_image_address required in application) |
| 9 | Overlay Address (TOOLS 13) | The address in RAM where the overlay data is to be stored (-foverlay=flash / -foverlay=quadflash) |
| 10 | Overlay offset (TOOLS 13) | Offset in vytes from the start of the image of where the overlay data is located |
| 11 | Switch Setup Header offset (NEW TOOLS 13.2) | Offset in bytes from the start of the image of where the network setup table is located |
| 12 | Core Entry Header offset (NEW TOOLS 13.2) | Offset in bytes from the start of the image of where the first core application table is located |
Colin