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.

TMS320F28075: Debug configurations

Part Number: TMS320F28075
Other Parts Discussed in Thread: C2000WARE

Hello Team,

I want to understand the meaning of line CPU1_DEBUG, CPU1_RELEASE CPU1_FLASH and CPU1_RAM configurations.

and what is the difference between all of them.

When i tried CPU1_DEBUG configuration i am able to debug code on target device but once debugger is removed and try to run the application then code remains in reset state maybe.

When i tried CPU1_Release configuration i am unable to debug code on target device but once debugger is removed and try to run the application then code runs properly.

Above is my observation. 

When i tried CPU1_FLASH and CPU1_RAM configuration i am able to debug code on target device but once debugger is removed and try to run the application then code remains in reset state maybe.

Also at a time each project shows only 2 configs CPU1_Debug and CPU1_Release or CPU1_Flash and CPU1_ram why all configurations are not available for one project 

Need some clarifications on above things what is the purpose of above configurations and how to use them. 

Regards,

Sandeep

  • Sandeep,

    The configurations that you are referencing, are these for examples in C2000Ware?

    Generally, the CPU1_FLASH and CPU1_RAM configurations are desinged to run the application from either FLASH or RAM. See the device_support examples in C2000Ware for more infomration.

    The DEBUG and RELEASE options are more focused on the optimization of the compiled code. DEBUG code is typically the lowest optimization and is used for debugging code. RELEASE configurations have higher optimization (-o2) and are meant for applications.

    Let me know if you still have questions about the differences.

    Regards,

    Ozino