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.

AWR2944EVM: Debugging and evaluating code with CCS

Part Number: AWR2944EVM
Other Parts Discussed in Thread: UNIFLASH, AWR2944

Tool/software:

Hi,

I have a methodological question.

Based on your application (HECR) we want to develop now our own one.

We use TI CCS as IDE.

The code is compiled there and appimage is created and is burned at chips' ROM with subsequent loading via UART boot mode.

However, this methodology is very inefficient. Loading with UniFlash takes 1-2 minutes and requires changes in SOP jumpers from 001->101->001. So effective development this way is impossible.

I know that SOP jumpers permit a debug mode as well.

So, what is your debugging methodology? 

Where can I read how effectively to use it?

May it possible loading the code strait into internal SoC memory without first booting it from ROM

Cheers,

Arie

  • Hi Arie,

    Instead of flashing the demo application each time you rebuild, you can flash CCS debug appimage - "C:\ti\mmwave_mcuplus_sdk_04_07_01_03\mmwave_mcuplus_sdk_04_07_01_03\ti\utils\ccsdebug\awr2944_ccsdebug.appimage". CCS debug application just has a while(1) loop and the appimage is flashed to unhalt all the cores. This CCS debug application is loaded by SBL onto the RAM. 

    You can now connect to CCS, reset the cores by clicking on CPU reset and load the binaries onto the cores. The application will be loaded directly onto the RAM. 

    Refer to section Developer’s guide of AWR2944 OOB Object Over CAN Users Guide for proper description of each step.

    Regards,

    Samhitha