Other Parts Discussed in Thread: SYSCONFIG
This thread is related to thread:
MCU-PLUS-SDK-AM263X: SDK Example using TCM - edma_multimem_transfer_am263x-cc_r5fss0-0_nortos_ti-arm-clang
and the FAQ:
The FAQ state that the way to define memory regions for adding code and data to TCM memory is "To create section in TCM edit the linker.cmd".
However, when I import an SDK example it seems like the Build (make) is what creates "linker.cmd".
Also, I see in SysConfig Memory Configurator memory regions as seen here:
These seem to corelate to the memory regions in "linker.cmd" seen here:
MEMORY
{
R5F_VECS : ORIGIN = 0x0 , LENGTH = 0x40
R5F_TCMA : ORIGIN = 0x40 , LENGTH = 0x7FC0
R5F_TCMB : ORIGIN = 0x80000 , LENGTH = 0x8000
SBL : ORIGIN = 0x70000000 , LENGTH = 0x40000
OCRAM : ORIGIN = 0x70040000 , LENGTH = 0x40000
USER_SHM_MEM : ORIGIN = 0x701D0000 , LENGTH = 0x4000
LOG_SHM_MEM : ORIGIN = 0x701D4000 , LENGTH = 0x4000
FLASH : ORIGIN = 0x60100000 , LENGTH = 0x80000
RTOS_NORTOS_IPC_SHM_MEM : ORIGIN = 0x72000000 , LENGTH = 0x3E80
MAILBOX_HSM : ORIGIN = 0x44000000 , LENGTH = 0x3CE
MAILBOX_R5F : ORIGIN = 0x44000400 , LENGTH = 0x3CE
/* For memory Regions not defined in this core but shared by other cores with the current core */
}
Is the FAQ still current, of should the TCM section be added through the SysConfig Memory Configurator?