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.

AM263P4-Q1: Questions about MSRAM allocation in AM263Px SBL (OSPI) linker.cmd

Part Number: AM263P4-Q1

AM263Px MCU+SDK (mcu_plus_sdk_am263px_10_01_00_31) SBL (OSPI): Question about linker.cmd memory map intent

I would like to confirm the intent of the memory map in the linker script for the AM263Px MCU+SDK SBL (OSPI). I am referencing the following file:
...\examples\drivers\boot\sbl_ospi\am263px-lp\r5fss0-0_nortos\ti-arm-clang\generated\linker.cmd

Q1: MSRAM_VECS start address 0x70002000
In the linker script, MSRAM_VECS starts at 0x70002000.
Can the address range 0x70000000–0x70001FFF (the first 8KB) be used by the SBL?
If this region is reserved, what is it used for?

Q2: Reducing MSRAM_HSMRT size
From my side, it looks like MSRAM_HSMRT actual usage is only about ~26KB.
Is it safe to reduce the allocated size of MSRAM_HSMRT? If there is a minimum required size or any  constraint, could you please advise?

Requested response date: June 19, 2026

  • Hi Imaoka-San,

    Q1: MSRAM_VECS start address 0x70002000
    In the linker script, MSRAM_VECS starts at 0x70002000.
    Can the address range 0x70000000–0x70001FFF (the first 8KB) be used by the SBL?
    If this region is reserved, what is it used for?

    The region MSRAM_VECS contains the vectors of the SBL. This is required for the proper loading of SBL by ROM.

    On bootup ROM wakes up and it loads the .vectors section of SBL into 0x7000_2000 address in RAM.This address is mentioned as load address in the linker script.

    See that the run address is kept as 0x0 for the .vectors section.

    That is because when eclipsing happens the vectors get moved to 0x0 address and execution happens from there.

    Therefor this address should not be changes and should be intact.

    Can the address range 0x70000000–0x70001FFF (the first 8KB) be used by the SBL?
    If this region is reserved, what is it used for?

    This is the area used by ROM for execution. If the SBL uses this area then, when ROM loads SBL it will overwrite itself.

    But one thing to notice is that, you can configure the .bss section of SBL to use this area. This is because .bss is not loaded since it is uninitialized and hence there is no risk of overwriting.

    Q2: Reducing MSRAM_HSMRT size
    From my side, it looks like MSRAM_HSMRT actual usage is only about ~26KB.
    Is it safe to reduce the allocated size of MSRAM_HSMRT? If there is a minimum required size or any  constraint, could you please advise?

    You may reduce the size of MSRAM_HSMRT depending on your application.

    Thanks & Regards,

    Aswin