Cannot init. the m_boot_settings in S110 7.0 bootloader

[ericyy]

I'm using the S110 v7 SD, I want to amend the bootloader app such that I can merge it with my APP together with the SD to a single .HEX... To do so I'm taught to init. the m_boot_settings[] in bootloader_util_arm.c...

However, after I change the line from uint8_t m_boot_settings[CODE_PAGE_SIZE] attribute((at(BOOTLOADER_SETTINGS_ADDRESS))) attribute((used)); to uint8_t m_boot_settings[CODE_PAGE_SIZE] attribute((at(BOOTLOADER_SETTINGS_ADDRESS))) attribute((used)) = {BANK_VALID_APP};

The followings error occurs: ._build\bootloader.axf: Error: L6220E: Load region LR_IROM1 size (16624 bytes) exceeds limit (16384 bytes). Region contains 2701 bytes of padding and 0 bytes of veneers (total 2701 bytes of linker generated content). Target not created

My IROM1 setting is Start on 0x3c000, sized 0x4000

Anything goes wrong?

Thanks!

[John]

I think you need for the IROM1 size to be 0x3C00 rather than 0x4000. Alternatively depending on how big your bootloader is you may need IROM1 start to be 0x3BC00 with a size of 0x4000.

[ericyy]

May I know why should I set the size to 0x3c00 instead of 0x4000?

[ericyy]

Eventually I found that the array m_boot_settings[] lay on the very final 1024B of the segment (start from 0x3fc00 to 0x3ffff)... My Keil work just fine if there's no init. value on it... However if I add a init. value to it, somehow Keil "think" that the m_boot_settings[] use 240B more (1024+240B), which over the size of 0x4000...

I have no idea on why it need 240B more and nothing hint come from the .MAP file...

The only way I can do is relocate the m_boot_settings[] to 0x3f800 so that it has room for the extra 240B, and now it compile successfully...

Maybe sort of linker bug?

[Petter Myhre]

I'm not sure what is causing the error, but in this question I explain one way to do it.

Please vote if you think the question and/or answer is good.

Why should I vote?

[Nikita]

Try it like this:

UPD:

Though maybe IROM2 is unnecessary, it works if you just change IROM1 size to 0x3C00 (=0x4000-0x400 that is bootloader settings region).

UPD:

No, it's still would be correct to specify a region of memory used with IROM2.