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.

TMS320F28377S: ".cmd" configuration using DCL

Part Number: TMS320F28377S
Other Parts Discussed in Thread: SFRA

Hello Champs,

Customer is using DCL on F28377S(CCS version is v10.1.1, CGT version is v20.2.1.LTS).

As described in DCL user guide, if adding below configuration in ".cmd" file:

dclfuncs : > RAMGS15, PAGE = 0

After compiling and downloading the codes into flash, it can run well in debug window with emulator connected. But after powering up the F28377S board again to run standalone, the codes will run abnormally and cannot run into Main().

If adding below configuration instead (as in "gridconnectedinvlclfltr_flash_cpu1.cmd" ):

   GROUP

   {

       .TI.ramfunc

       {

       -l sfra_f32_tmu_eabi.lib

       }

       ramfuncs

       dclfuncs 

   }

After compiling and downloading the codes into flash, then power up again, the codes can run normally both with emulator connected and in standalone mode.

Would you please kindly help why the first kind of configuration will not work in standalone mode? What about the different impact for these two configurations?

Thanks! 

Best Regards,
Linda

  • The first loads dclfuncs to RAM, but since RAM doesn't keep is value through the power cycle, the code will not be present when running standalone, likely leading to illegal instruction errors when one of the functions is called.

    The second puts the dclfuncs in .TI.ramfunc which is typically loaded to Flash but then copied to RAM for execution. Since Flash retains its value, the code is not lost during the power cycle.

    Whitney