CCS/TMDSDSK6713: Problem executing program on DSK6713

Hi,

In my experience, runtime errors when migrating projects usually stem either from small differences between the DSP/BIOS releases or some initialization that is done differently between the CCS releases (via different GEL files, for example).

Also, I am not sure which version of DSP/BIOS you were using before, but I suspect you already went through the steps mentioned in the post below:
e2e.ti.com/.../1025444

One important detail in the case above is that migrating to the newer DSP/BIOS requires explicitly calling CSL_Init() at main(). Another point is to carefully verify the heap and stack sizes to prevent overlapping (DSP/BIOS 4.9 did this some memory checking for you but not DSP/BIOS 5.x).

If you are using the device's internal memory and given you are able to run up to a certain point in your code by adjusting heap and stack, check carefully how the internal C6713 memory is being configured: if I recall correctly you can set part or all of it to cache - this was automatically done with DSP/BIOS 4.9 but I don't know for sure how this is done in DSP/BIOS 5.x.

At last, I would refer to the post below that contains some information and additional tips to perform this migration.
e2e.ti.com/.../47475

Hope this helps,
Rafael

I have changed my program. I simplified all tasks and reduced to basic instructions for debugging purpose. The zip file attached contains testing code. I think the problem is contained in for instruction at 217 - 245 lines.

Maybe there are some unreferenced libraries.

I'm waiting to hear from you and I would appreciate  any suggestions.

DSP_prova1_7.zip

Hi,

Thanks for sending the testcase; it was an application issue. I could see the sin() function was failing throughout the code execution, which was solved by increasing the stack.

I send attached the project with a few modifications to accommodate the code you sent.

The linker CMD file splits most sections across two memory regions (IRAM and L2RAM) to help overcome the increased memory usage. Some sections cannot be split (.stack, .sysmem, .cinit and .bss) but you can still leave the linker to choose where they will be allocated. (reference: here)

The memory region I used (L2RAM) sometimes is used as Cache for the external SDRAM, thus the debugger does not allow writing to it - to allow writing to this, simply go to menu below and select ClearMemoryMap. 

If you plan to use the cache in the future, then replace L2RAM with EMIFCE0 on all memory sections. 

I also fill the .stack memory section with a known value to allow monitoring stack usage (see picture below). This has the drawback of increasing the size of the .out file, but has no impact in runtime and can be turned off when you finish debugging. 

Hope this helps,

Rafael