Presumably, since the bootloader is a regular SDK program, it causes runtime_init() and all the other things that happen before main() is called to happen. So it seems to me that, rather than the bootloader calling the main application's regular entry point, which would cause runtime_init() to be called again, that the bootloader could call the main application's main(), avoiding a second redundant call to runtime_init(). Perhaps the main application's linker script could cause the address of main() to be output to some fixed address.
Statistics: Posted by alastairpatrick — Tue Apr 30, 2024 9:06 pm