20 Feb
2014
20 Feb
'14
2:40 p.m.
On Thu, Feb 20, 2014 at 12:23:22PM +0100, Wolfgang Denk wrote:
Dear Charles,
In message 201402201358.19495.manningc2@actrix.gen.nz you wrote:
I looked at doing a mkimage integration, but is this really the way to go in all cases?
...only where it fits, of course.
The signed image does not really apply a header as such. It mashes in a "header" at position 0x40 and then appends a checksum at the end, then pads the file out to 64k.
The final file is:
- 64 bytes of executable (interrupt vector table)
- "header"
- more code
*crc32 *padding with 0x00 to 64k.
Sounds exactly as if you were making an image, so yes, mkimage fits.
Right. This is like the omapimage case or similar where we take input, beat it around and add stuff, then have what the HW wants, but not a file we can further query with mkimage, and that's fine.
--
Tom