• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 272 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TDA4VM: Why is MAIN MSRAM left out of device tree?

Vai Desai
Prodigy 240 points
Part Number: TDA4VM

Hi -

Looking at the mainline kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/ti/k3-j721e.dtsi, Main MSRAM (512KB) which corresponds to the TRM entry:

MSRAM16KX256E0_RAM 0x0003600000 0x000367FFFF 512 KB

 

is left out of the device tree. Why is that? Could you please provide tested device tree fragments/patch to use this memory? Specifically allocate all of it to MAIN R5F SS.

Thank you

Vai

  • 0
    TI__Guru**** 430295 points

    Hi Vai,

    Because it is not being currently used in the SDK.

    For its usage on R5F, please add entry in the MPU configuration and then you can directly use it. 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Prodigy 240 points

    I think we are ignoring the fact that remoteproc will fail to load to any section of memory not allocated correctly in the device tree to a specific core. For a baremetal application loaded externally, yes I agree. But my question was for the general case where we can use remoteproc for loading an R5F application.

    It'd be great if TI can patch this to the common SDK because it will help folks use available memory even when it is not used in the SDK.

    Regards

    Vai

  • 0 in reply to Vai Desai
    TI__Guru**** 430295 points

    True, but i really doubt that this memory is being used in the released firmware or not even in vision app firmware. Most of the firmwares either use TCM memory or DDR to store their sections.. SDK adds/enables the features that can be tested/validated on EVM with the released firmwares. I believe this is why it is not added. Please add in your device tree file if you would like to use it in your firmware. 

    Regards,

    Brijesh