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.

TMS320F2800135: RAM memory address starting after the BOOT section + 8 bytes to 0x00000130

Part Number: TMS320F2800135

Tool/software:

Hi Team,

My customer's team ran into some issues due to the misunderstanding that TI FOC SDK sets uninitialized features interface pointers to 0x00 RAM addresses when not in use. They wanted to expand RAM area into the bootloader section at the start of RAM, and without realizing my previous comment, set start of RAM to 0x00. Combined with the another team member leaving some code in from the example project with unused communication interfaces, they had comms interface code changing random RAM variables.

Their solution was to keep RAM memory address starting after the BOOT section + 8 bytes to 0x00000130. They are worried that this is risky since TI HAL code doesn't do null-pointer checks and uses a shift from the base 0x00 pointer while setting variables. Can you help to confirm if this is a correct fix and if there is any risk by setting registers in this configuration?

Can you advise the typical approach moving from TI FOC SDK example code to product code?

Thank you.

  • Hi Erika,

    I'm not familiar with the FOC SDK but am familiar with boot ROM issues. Can you provide more background information on the general flow of the code? Is there a bootloader using a comms peripheral? Why are there unused comms peripherals? That seems to be related to the cause of the issue.

    Thank you,

    Luke