TDA4VM: Memory map update for Linux dts/dtso

James Lee

Part Number: TDA4VM

Hello experts,

I'm trying to update memory map with PSDKRA/PSDKLA 6.2.

After running gen_linker_mem_map.py, I'm getting below comment:

/*
* IMPORTANT NOTE: Follow below instructions to apply the updated memory map to linux dts/dtso/dtsi files,
*
* 1. Copy the memory sections, from the generated dts file, to the file shown below under reserved_memory: reserved-memory { ... }
* ${LINUX_KERNEL_PATH}/arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi
*
* 2. In file ${LINUX_KERNEL_PATH}/arch/arm64/boot/dts/ti/k3-j721e-auto-common.dtso
* - Remove the fragment@xyz { ... } entries for xyz = 101 to 119
*
* 3. In file ${LINUX_KERNEL_PATH}/arch/arm64/boot/dts/ti/k3-j721e-vision-apps.dtso
* - Remove the &reserved_memory { ... } entry
*
* 4. The entries are removed since the same are updated in k3-j721e-som-p0.dtsi, hence we should not have duplicate outdated one's
*
* 5. Rebuild the dtb, dtbo and use the updated dtb, dtbo files
* - In PSDKLA install directory, doing below should build the dtb and dtbo
* make linux-dtbs
* - Copy the below updated dtb, dtbo files to "boot/" folder in your target linux SD card filesystem
* arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dtb
* arch/arm64/boot/dts/ti/k3-j721e-auto-common.dtbo
* arch/arm64/boot/dts/ti/k3-j721e-vision-apps.dtbo
*/

but I cannot find k3-j721e-auto-common.dtso in step 2.

~/ti-processor-sdk-linux-automotive-j7-evm-06_02_00/board-support/linux-4.19.94+gitAUTOINC+5a23bc00e0-g5a23bc00e0/arch/arm64/boot/dts/ti$ ll k3-j721e*.dtso
-rw-r--r-- 1 1898 Feb 17 18:35 k3-j721e-common-proc-board-infotainment-display-sharing.dtso
-rw-r--r-- 1 4654 Feb 17 18:35 k3-j721e-common-proc-board-infotainment.dtso
-rw-r--r-- 1 2312 Feb 17 18:35 k3-j721e-common-proc-board-jailhouse.dtso
-rw-r--r-- 1 675 Feb 17 18:35 k3-j721e-pcie-backplane.dtso
-rw-r--r-- 1 3143 Feb 17 18:35 k3-j721e-vision-apps.dtso

Could you let me know where I can find it?

Regards,

James

over 5 years ago

0 Brijesh Jadav over 5 years ago

TI__Guru**** 476595 points

Hi James,

I think we have removed one of the dtb file, as it is not required.

we have made changes in the memory map such that code sections resides in a specific memory region whereas all heaps are moved to different memory region. With these changes, if code section is not changes, you dont need to change dtb file. So could you please help me understand what changes are you are trying to make in memory map?

Regards,

Brijesh

0 James Lee over 5 years ago in reply to Brijesh Jadav

TI__Expert 3145 points

Hi Brijesh,

I'm trying to increase c66x_1_ddr_size/c66x_2_ddr_size to 32MB from 16MB. In gen_linker_mem_map.py:

# Note, C6x_2 IPC region is just before C6x_1 resource table to allow to set MAR bit for C6x_2 IPC region to non-cached
c66x_2_ddr_ipc_addr = mcu3_1_ddr_addr + mcu3_1_ddr_size;
c66x_1_ddr_resource_table_addr = c66x_2_ddr_ipc_addr + linux_ddr_ipc_size;
c66x_1_ddr_boot_addr = c66x_1_ddr_resource_table_addr + 1*MB;
c66x_1_ddr_boot_size = 1*KB;
c66x_1_ddr_addr = c66x_1_ddr_boot_addr + c66x_1_ddr_boot_size;
c66x_1_ddr_size = 32*MB - (c66x_1_ddr_addr-c66x_2_ddr_ipc_addr);

# Note, C6x_1 IPC region is just before C6x_2 resource table to allow to set MAR bit for C6x_1 IPC region to non-cached
c66x_1_ddr_ipc_addr = c66x_1_ddr_addr + c66x_1_ddr_size;
c66x_2_ddr_resource_table_addr = c66x_1_ddr_ipc_addr + linux_ddr_ipc_size;
c66x_2_ddr_boot_addr = c66x_2_ddr_resource_table_addr + 1*MB;
c66x_2_ddr_boot_size = 1*KB;
c66x_2_ddr_addr = c66x_2_ddr_boot_addr + c66x_2_ddr_boot_size;
c66x_2_ddr_size = 32*MB - (c66x_2_ddr_addr-c66x_1_ddr_ipc_addr);

to have some more buffers in this area.

Then can I change only k3-j721e-common-proc-board.dtb and k3-j721e-vision_apps.dtbo (except k3-j721e-auto-common.dtbo)?

Actually we have k3-j721e-auto-common.dtbo in the pre-built file system and the default uEnv.txt file is referring to this file:

dorprocboot=1
overlay_files=k3-j721e-auto-common.dtbo k3-j721e-vision-apps.dtbo

Should I keep this default .dtbo in the uEnv.txt?

Regards,

James

0 Brijesh Jadav over 5 years ago in reply to James Lee

TI__Guru**** 476595 points

Hi James,

But why do you need more than 16MB in code section?

We feel 16MB should be good enough for code section.. For any extra heap, you could allocate from the heap section.

Rgds,

Brijesh

0 Brijesh Jadav over 5 years ago in reply to Brijesh Jadav

TI__Guru**** 476595 points

Hi James,

Is this same question, that is being asked by KPIT?

Regards,

Brijesh

Processors

Processors forum

TDA4VM: Memory map update for Linux dts/dtso