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

Attaching CCSv5 to running embedded process

Jay Gowdy81418
Intellectual 810 points

Other Parts Discussed in Thread: OMAP-L138, MSP430F5438A

I am running CCSv5 ( Version: 5.1.1.00031) attaching to a OMAP-L138 with a BlackHawk USB560M JTAG emulator.

I have an embedded processor which is wedged somehow (I believe on the ARM side), and I want to attach to it and see where it is wedged.

For the life of me, I cannot figure out how to do this.   All of the "Debug" file options seem to want to stop the processor and load in new code, and the "Connect" menu item on the Debug perspective is greyed out.

This mystifies me, and I must be missing something obvious, because the ability to attach to a crashed processor to do forensics on where the processor is running and what the registers are seems fundamental.   If someone can go through the "how-to-for-dummies" procedure for attaching to a crashed processor without disturbing it for CCSv5, I would greatly appreciate it.

  • 0
    TI__Guru**** 482361 points

    Hi Jay, 

    Can you send a screenshot of CCS where you see the menu item greyed out and also what your Debug view looks like? 

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 810 points

    Ki,

    Now I am sure I am missing something obvious.   My Debug view is completely empty.  The only way I know to "fill" it is by making a project active and hitting "Debug", which then calls up the default Target Configuration, initializes the Debug view, connects to the ARM, runs the GEL file, loads the code, and runs the code to main.

    I want to know how to apply a Target Configuration, initialize the Debug view, and connect to the ARM to see where the ARM is running and take a look at its memory and registers of the previously running code (presumably loaded from flash).

    Just for completeness, I've attached the Debug view.  It was all blank, so just for kicks I captured the result of right clicking where you see the "Connect Target" action is greyed out.

    Again, I am pretty sure I am missing something so obvious that it doesn't occur to anyone that I could possibly miss it.

      Jay

  • 0 in reply to Jay Gowdy81418
    TI__Guru**** 482361 points

    Jay,

    I don't think you've started a debug session. If you did, the debug view should be populated. Since you haven't started a debug session, you can't do too much with regards to debug actions

    Jay Gowdy81418 said:
    The only way I know to "fill" it is by making a project active and hitting "Debug", which then calls up the default Target Configuration, initializes the Debug view, connects to the ARM, runs the GEL file, loads the code, and runs the code to main.

    That is one way to do it

    Jay Gowdy81418 said:
    I want to know how to apply a Target Configuration, initialize the Debug view, and connect to the ARM to see where the ARM is running and take a look at its memory and registers of the previously running code (presumably loaded from flash).

    You want to start a 'project-less' debug session.

    See slides 79-81 of: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/workshops/CCSv5/C2000/CCSv5-Workshop(C2000)_2.pdf

    thanks

    ki

  • 0 in reply to Ki
    Intellectual 810 points

    Ki,

    That did it:  the key was I had no idea that the Target Configuration view existed, let alone what it did.  I've always gone straight from the Edit view to Debug view on a particular project.   I think I can get into my errant system now.

      Thanks,

         Jay

  • 0 in reply to Jay Gowdy81418
    Expert 1420 points

    I'm trying to do the same thing but on a msp430f5438a.   I have code running that I want to look at with the debugger as well as the EEM tools.

    But when I try to mess with Run -> Load -> Symbols, there is no such menu entry. 

    Is there a way to fire up a project-less debug session with CCS for msp430f5438a

    I'm running the latest CCSv5.

  • 0 in reply to Eric Decker
    TI__Guru**** 482361 points

    Eric - the use case is the same for MSP430. You should see the menu under 'Run -> Load -> Load Symbols'. Also make sure you are in the 'CCS Debug' perspective.

    Thanks

    ki