Part Number: TMDSCNCD263P
Hello,
In the SDK documentation...
AM263Px MCU+ SDK: Understanding the bootflow and bootloaders
...it mentions...
"Currently, the region 0x70002000 to 0x70040000 is used by the SBL code, data, stack, etc."
So I reserved this area in my application's memory map.
However, the SBL example's (sbl_ospi_multicore_elf) memory regions occupy memory beyond 0x70040000:
name origin length used unused attr fill---------------------- -------- --------- -------- -------- ---- -------- R5F_VECS 00000000 00000100 00000040 000000c0 RWIX R5F_TCMA 00000100 00007f00 00000000 00007f00 RWIX R5F_TCMB0 00080000 00008000 00000000 00008000 RWIX MAILBOX_HSM 44000000 000003ce 00000340 0000008e RWIX MAILBOX_R5F 44000400 000003ce 00000340 0000008e RWIX FLASH_BOOTINFO_SECTOR 60080000 00001000 00000000 00001000 RWIX MSRAM_VECS 70002000 00000100 00000040 000000c0 RWIX MSRAM_0 70002100 0003ff00 00028a80 00017480 RWIX MSRAM_HSMRT 70042000 00040000 0000a6e4 0003591c RWIX BOOT_SECTOR_INFO 80080000 00001000 00000000 00001000 RWIX
The end address os MSRAM_0 is 0x70041FFF which encroaches on the application space.
Fortunately, the actual occupation end address is 0x7002AB80 so in practice the SBL is able to copy application code to 0x70040000 without shooting itself in the foot...for now at least.
<Request>
Please can you change the size of MSRAM_0 to 0x3DF00 in your example so that if the SBL size increases beyond this size that you will know that this will have an impact the application area.
<Question>
The HSM firmware image also occupies application memory starting at 0x70042000. Is it correct the HSM firmware is no longer needed (and can therefore be overwritten) when the SBL starts to copy the application to RAM?
Thank you.
