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.

C2000: Possible to Connect to Running Target?

Other Parts Discussed in Thread: TMS320F28069

I'm having some difficulty enabling the CSM on a TMS320F28069 controller. When running under the debugger (insecure mode) everything works fine, but the processor appears to hang when running standalone.

I would like to be able to connect the debugger to the MCU after it has already started up standalone, akin to the "Connect to running target" option often seen when debugging ARM Cortex chips. Is establishing a connection without flash download / reset / run-to-main possible with the C2000 family?

Thanks,
Dave

  • Hi Dave,

    Nope, that's not possible! Btw what do you mean processor hangs while in standalone mode?

    Regards,
    Gautam
  • When I run under the debugger (CSM unlocked) everything works fine - but when powering up without the debugger attached, code running from FLASH, the MCU is unresponsive.

    I have moved an LED blink forever-loop through the code to try to determine where the hang is occurring. It seems to happen as a result of running the ADC self-calibration routine, in ROM at 0x3D7C80.

    Thanks,
    Dave
  • David R. said:
    I would like to be able to connect the debugger to the MCU after it has already started up standalone, akin to the "Connect to running target" option often seen when debugging ARM Cortex chips. Is establishing a connection without flash download / reset / run-to-main possible with the C2000 family?

    Yes this is possible when real-time mode is enabled. Please see this post for how you can enable this in your debug configuration. Even though that thread talks about the C66x device, the same concept should work as real-time mode is supported on F28x devices as well.

  • Thank you AartiG-

    I enabled realtime mode and attempted to debug, but got an error dialog that reads:

    "Device blocked debug access because it is currently executing non-debuggable code. You may retry after the device has had time to enter debuggable code, or you my cancel, disable realtime mode, and then attempt to connect"

    I'm guessing that this is because the device is secured by the CSM and, without a flash download, the debugger is not performing the ECSL unlock to permit JTAG access.

    Is there a way to configure the debugger to perform the ECSL unlock (i.e. lower 64 bits to key register) without executing the full Password Match Flow and unlocking the device?

    Ultimately, I just need to see where the processor is ending up.

    Thanks,
    Dave

  • Dave,

    Sorry about the delayed reply. 

    To allow debug access in real-time mode, you can enable "rude" real-time mode, or in other words disable "polite" real-time mode. In menu Run->Debug Configurations->Target tab, under Auto Run and Launch options, uncheck the checkbox for "Enable polite mode".

    Also under Program tab, be sure to select "Load symbols only" instead of "Load program" else it will try to erase and program flash again instead of just connecting to the running target.

    Hope this helps.