Thank You for your continued support and contributions!
new_paddedsize = PAD_TO_BOUNDARY(firmware_size + bootloader_size);
new_paddedsize = PAD_TO_BOUNDARY(firmware_size + bootloader_size) + 0x200;
As for the "prepared environment", I don't see why we wouldn't be able to do so, in the first or second "stage" of our bootloader
First stage bootloader[/b]The first stage would be located in the firmware block, after the used part (that is after the code and the variable initialization sections). It needs to be as small as possible to fit every possible OF files. If we find out that we can increase the firmware block size, then we are in luck. If not, we may need an alternative location for that. I assume that we will a) have enough space in the OF file without modification, or b) we will be able to increase the firmware block size.Its job is:Intercept a particular signal (a button or something), and if not set, boot back to the OF (its job end up here in this case)Find (or maybe it should already know) the second stage bootloaderCopy it from ROM to RAM
I expect fragile_matter to flash an extended firmware (by 0x200, then BOOTLOADER_STAGE2_SIZE) and tell us if he still can boot the OF and use it, and tell us the results.
Page created in 0.112 seconds with 21 queries.