• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1504 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.

GUI bug in CCSV5 causes annoying debugger crashes

Thorsten Lorenzen
Genius 17101 points


Hi Team,

can you comment on this? In the meantime I'll get more details on what an event can be in particular.

DM8148:

When connecting and loading multiple cores, events occuring on one target causes the selected target to change. When this happens during the same time the user issues a command such as connect or load, the debugger often silently ends up in an unusable state, requiring complete platform reset. Already when using only two of the processors, this is highly disturbing. Having to connect 3-5 processors this way would be a nightmare.

Suggested actions: Clean up the GUI and introduce a more efficient way to launch the platform, connect the targets, resetting properly, and loading the software.

Thanks,

Thorsten

  • 0
    TI__Genius 17101 points

    Additional discription.

    1. Connect to all cores

    2. Load first program into ARM core and run to Main.

    3. While loading click on DSP core.

    4. Load program into DSP core and run to Main

    5. While loading program window for DSP is still open the ARM core holds at Main and a target switch accurred.

    6. Now the open menu (eg. load program for DSP) is action on the ARM core instead of the DSP core.

    Under windows, separation of context is not functional. In focus objects can be moved to other objects.

    Hence, the issues relates to Eclips programming

  • 0
    TI__Guru**** 469301 points

    Hello Thorsten

    More details on the event" would be helpful:

    Thorsten Lorenzen said:
    When connecting and loading multiple cores, events occuring on one target causes the selected target to change.

    I think they mean to say the events occurring in one core / debug context causes the currently selected debug context to change.

    Thorsten Lorenzen said:
    the debugger often silently ends up in an unusable state,

    Is it a hang?

    The best details they can provide is a "Debug Server Log". See here for details:

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#CCS_Diagnostic_Logs

    Thanks

    ki

  • 0 in reply to Thorsten Lorenzen
    TI__Guru**** 469301 points

    Thorsten Lorenzen said:

    1. Connect to all cores

    2. Load first program into ARM core and run to Main.

    3. While loading click on DSP core.

    4. Load program into DSP core and run to Main

    5. While loading program window for DSP is still open the ARM core holds at Main and a target switch accurred.

    6. Now the open menu (eg. load program for DSP) is action on the ARM core instead of the DSP core.

    I could see this being expected behavior but the stealing of focus is something that could be troublesome. Still, CCS should not hang

  • 0 in reply to Ki
    TI__Genius 17101 points

    Lee,

    I see the major issue in steeling focus.

    Thorsten