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.

PROCESSOR-SDK-AM62X: TCM accessing issue

Part Number: PROCESSOR-SDK-AM62X


Tool/software:

Dear TI team,

I am looking to maximize the usage of TCM A and TCM B on R5F and allocate specific application sections to TCM. I have faced two issues: 


1. Unable to access TCM A on R5F before jumping to application (before self reset of R5F). Accessing the TCM A to load either data or text causes exception. Referring to the TRM, it was mentioned that TCM A is disabled by default.


Could this be the cause of this issue ? If so, how to enable it?


2. Wanting to allocate memory sections to TCM B, I have updated the linker of application on R5F, instead of setting memory sections load origin TCM B and run origin TCM A, I set to load and run from TCM B . This causes the software to enter exception after jumping to application, which boots from TCM B. Is there a limitation to load and run from the same TCM ?

Regards

  • Hello Omar,

    Thanks for your query.

    I am looking to maximize the usage of TCM A and TCM B on R5F and allocate specific application sections to TCM. I have faced two issues: 

    Can you please tell which MCU+SDK are you using? 

    Unable to access TCM A on R5F before jumping to application (before self reset of R5F).

    The TCMA is not enabled by default. It is enabled as a part of _self_reset sequence for R5F core. So you will not be able to use TCMA memory to keep loadable sections.

    Regards,

    Tushar

  • Hello Tushar,

    Using MCU+SDK version 09.02.00.38.

    Is there a limitation to enable the TCMA before the self reset sequence ? 

    Regards,
    Omar


  • Dear TI team,

    Currently we are trying to allocate the main stack to TCM B in boot manager firmware on R5F before jumping to the application firmware on the R5F. Reallocating the stack section from external RAM to the TCM B causes exception. It was observed that the exception is caused by the self reset sequence of the R5F and it was fixed by increasing the size of the stack of the boot manager. Is it expected for the self reset sequence to use the previous firmware stack ? What could cause the need to increase the size of the stack by only reallocating the stack from External RAM to the TCM B ?  

    Opened inquires regarding the TCM topic: 

    1. Is there a limitation to enable the TCMA before the self reset sequence ? 
    2. Is there a limitation to load and run from the same TCM ?
    3. Is it expected for the self reset sequence to use the previous firmware stack ? What could cause the need to increase the size of the stack by only reallocating the stack from External RAM to the TCM B ?  


    Regards, 
    Omar