How does one utilize the output of bootimage? It seems the load addresses are listed in a comment. Do I need to manually parse the output to get this info?
Could the author of the script make an update to do something like this:
int num_boot_sections = 3;
int array_addresses[3] = { _resetVecs, _text, _const };
int load_addresses[3] = {0x00000000, 0x8C7A0000, 0x8C826700};
That way the corresponding boot code could generically and programmatically determine how many sections, where they go, and where the data is located.
Background: In order to put up a splash screen early in the boot process on DM8148 we need to be able to load an executable to one of the Cortex M3 devices. Personally I'd like to use hex470 for that purpose but the --boot option still does not exist (SDSCM00038229) so it's out of the question. So now I'm trying to use bootimage. I've successfully generated the *.c and *.h files from this utility. However, I'm having a little difficulty figuring out how to use it. Here's a snippet from the output as an example:
output.c said:/*********************************************************
** _text[0x866fe]: paddr = 0x8c7a0000
**********************************************************/
const unsigned char _text[0x866fe] = {
0x03, 0x46, 0x16, 0xe0, 0x1a, 0x68, 0x42, 0xf0, 0x10, 0x02, 0x0e, 0xe0, 0x1a,
0x68, 0x42, 0xf0, 0x01, 0x02, 0x0a, 0xe0, 0x1a, 0x68, 0x42, 0xf0, 0x02, 0x02,
0x06, 0xe0, 0x1a, 0x68, 0x42, 0xf0, 0x08, 0x02, 0x02, 0xe0, 0x1a, 0x68, 0x42,
0xf0, 0x04, 0x02, 0x1a, 0x60, 0x0a, 0x68, 0x52, 0x1c, 0x0a, 0x60, 0x0a, 0x68,
0x12, 0x78, 0x20, 0x3a, 0xf4, 0xd0, 0xd2, 0x1e, 0xee, 0xd0, 0x08, 0x3a, 0xe8,
