This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM2634-Q1: can I allocate SBL to space > 0x70040000 (except .vector section)

Part Number: AM2634-Q1

Hi BU experts, 

 I am asking this question for customer- VMAX. 

There are one constraint for SBL, i.e. vector section should load at 0x70002000~0x70002100. And the rest sections of SBL are all allocated to the space of 0x70002100~0x70040000 by default in SBL example. But in customer application, they have one further customer boot, i.e. UDS boot. And they want to allocate the UDS boot into 0x70002100~0x70040000. So there is one question: can they allocate SBL to space > 0x70040000 (except .vector section)? Any problem to do so? 

Regards, 

Will 

  • Hi Will,

    There are one constraint for SBL, i.e. vector section should load at 0x70002000~0x70002100

    Yes. The reason for the same is this "Understanding Eclipse and SBL Image Creation Guide".

    But in customer application, they have one further customer boot, i.e. UDS boot. And they want to allocate the UDS boot into 0x70002100~0x70040000. So there is one question: can they allocate SBL to space > 0x70040000 (except .vector section)? Any problem to do so? 

    Can they consider UDS boot as an application (.appimage) and load it whenever required ? or they want this to be done by ROM ?

    SBL size can go from 0x70000000 to 0x700F0000 (960KiB).

    Best Regards,
    Aakash

  • Hi Aakash, 

    The reason they put UDS boot into 0x70002100~0x70040000 is that they don't want the UDS boot overlaps with APP image (UDS and APP should always be in the RAM at run-time, so that they can quickly change to UDS just by modifying the vector at 0x0 space). 

    SBL size can go from 0x70000000 to 0x700F0000 (960KiB)

    Got it, thanks for the confirmation. 

    Regards, 

    Will