• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 212 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS Debug

Daniel
Prodigy 205 points
Other Parts Discussed in Thread: IWRL6432BOOST, UNIFLASH

I am using SDK 05.03.00.02 and CCS 12.5.

I found that whether the IWRL6432Boost EVM is set in flashing mode or functional mode, the CCS debug functionality are available for execution after launching target configuration. Additionally, regardless of whether empty.debug.appimage/empty.release.appimage is flashed into meta image 1 by Uniflash or even if the entire flash memory is erased, the CCS debug functionality is still available. Is this normal?

  • +1
    TI__Mastermind 21461 points

    Hello, 

    Please clarify what you mean by "CCS debug functionality are available for execution" do you just mean that you are able to connect to the Cortex_M4? If so, this is expected. 

    If the device is set to flashing mode then you will still be able to connect to the M4 but should get an error upon trying to load a .out file. 

    If the device is set to functional mode and the empty image is not loaded to flash memory, you will still be able to connect to the M4 and load .out files. However with this method, you will only be able to debug examples which are not using the RF functionality of the device (hello world, driver examples, etc..). 

    To be able to debug the Out-of-Box example projects, such as motion and presence detection or mmWave demo, functional mode with the empty image flashed is recommended. This is because the front-end rf code (which is compiled and included with the empty project) must be present in the correct memory location or these examples will produce an error. 

    Also between, empty.debug.appimage and empty.release.appimage, either can be used. 

    Best Regards,

    Josh