• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 449 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.

CCS4 V4.2.5 Debug Session Initiation Causes OMAP-L138 Experimenter to Reset

Duncan Verrall24
Prodigy 105 points

Hi,

Just like community member   in his E2E post at CCS4 V4.2 Debug Session Initiation Causes OMAP-L138 Experimenter to Reset. I too cannot connect to the DSP side of the L138 using XDS100v1 from Code Composer v4.2.5 without causing a system reset to occur as soon as I attempt to start the debugging session.

I am trying to follow the TI DSPLike debugging example article to the letter and have used a target configuration without a GEL. Note I do not have the CCS v4.2.5 debugger option to reset on connect enabled.

 decided to roll-back to an earlier version of CCS (v4.1.3) in order to debug without the reset occurring. Is there something I can edit within the CCS v4.2.5 that could prevent the reset? Or is it a bug? If so is it better for me to downgrade as MikeH did, or move to CCSv5. To help you give the best advice my current project uses the OMAP L138 Experimenter from Logic PD using Arago/Open Embedded Linux 2.6 and  DSP/Bios 5. I wish to use DSPLink for IPC activities.

Thanks for any help you can provide.

Duncan.

  • 0
    TI__Guru**** 483671 points

    Hi Duncan,

    Duncan Verrall said:
    If so is it better for me to downgrade as MikeH did, or move to CCSv5.

    Could you try out CCSv5? Support for v4 is being deprecated. It could be a known bug you are hitting that was addressed only in v5.

    Thanks

    ki