I want to boot a small customized program from EEPROM 0x50 (like POST) to configure some peripherals, such as SRIO, for 2nd stage booting.
However problem is encountered when I convert my app.out to a BIN file using post_romparse.bat in the POST project.
Error info can found as follows.
BTW, I just rename app.out to post_evm6678l.out and put it into tools\post\evmc6678l\bin and run the batch file.
Can anyone give some advice anything goes wrong?
Is it because my app.out is too big and can not fit into EEPROM 0x50?
Translating to ASCII-Hex format... "post_evm6678l.out" ==> vecs (BOOT LOAD) "post_evm6678l.out" ==> .text (BOOT LOAD)warning: boot table falls in unconfigured memory at 010400h "post_evm6678l.out" ==> .cinit (BOOT LOAD)warning: boot table falls in unconfigured memory at 010400h "post_evm6678l.out" ==> .const (BOOT LOAD)warning: boot table falls in unconfigured memory at 010400h..\..\..\boot_loader\ibl\src\util\bconvert\bconvert64x: Unspecified error, line 667Generating I2C ROM data ...
Thanks.
Boll
Boll,
I think you may need to link your application with the linker command file similar to what POST has, before trying to build the .bin file similar to POST. Have you tried building your application with the linker command file that POST has? (\mcsdk_2_00_##_##\tools\post\evmc6678l\post.cmd)?
-Aravind
Dear Aravind,
Thanks for the reply.
The reason is figured out.
When I change "ROM1: org = 0x0400, length = 0x10000, romwidth = 32, ..." to "ROM1: org = 0x0400, length = 0x20000, romwidth = 32...", the generation will be OK.
And the generated bin file size is bigger than 64 KB.
So it means my application out file is too big.