• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 891 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/TMS320C28346: Code Composer V7.1 Debug Perspective problems

DanGr
Prodigy 50 points
Part Number: TMS320C28346


Tool/software: Code Composer Studio

There are two issues with trying to debug in version 7.1

1.  I need to update the GEL file to set the configuration for debugging, but when I got the the Tools menu, in the debug perspective, the GEL Files menu option isn't available.  Because I can't update the GEL file the debug command fails so I can't load my program. The image below shows what I get for the Tools menu. (The specific issue is that there is code to be loaded into external memory so I need to configure the GPIO for XINTF6). 


Potential workarounds to this are simply to edit the gel file outside the context of CCS and/or configure the GPIOs manually in the register interface.  Even if those work, I would still like to know what the underlying issue is that causes the Tools menu not to include the GEL Files and other debug related selections.

2.  I will be customizing the GEL file for this project and want it to be committed as part of the project file.  I presume that I will need to modify the debug configuration to do that.  When I select Run->Debug Configurations it either does nothing or gives a java null pointer exception.  (Similar to e2e.ti.com/.../606397).

The two issues seem related, but if they're not I will spit this up into two posts or move issue # 2 to existing post.

  • 0
    Prodigy 50 points
    One more thing. I forgot to mention that I have already tried the options of resetting the debug perspective and cleaning the project as suggested in processors.wiki.ti.com/.../Troubleshooting_CCSv7 and that did not resolve the problem.
  • 0
    TI__Guru**** 474391 points

    Hello,

    DanGr said:
    but when I got the the Tools menu, in the debug perspective, the GEL Files menu option isn't available

    Note that this menu item (along with the other debugger options) are not available until a debug session has started. You don't have to be connected to the target, but you need to have started a debug session successfully.

    DanGr said:
    The image below shows what I get for the Tools menu.

    The screenshot didn't come through but if you didn't start a debug session, then that would explain why the option is missing. If you did start a debug session, please repost the screenshot

    DanGr said:
    2.  I will be customizing the GEL file for this project and want it to be committed as part of the project file.  I presume that I will need to modify the debug configuration to do that. 

    Actually, the GEL file is referenced by the target configuration ccxml file

    DanGr said:
    When I select Run->Debug Configurations it either does nothing or gives a java null pointer exception.  (Similar to e2e.ti.com/.../606397).

    That message is a very generic message, basically akin to "something went wrong". It can apply to a myriad of cases (the link you referenced is unrated - it is regarding the TI-RTOS CFG file). What does it look like when you use the dropdown menu next to the debug button? Do you see some existing configurations listed? What happens when you press the "Debug Configurations" menu item there?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 50 points

    Hello Ki,

    Thanks for the reply

    1.  Ki:  "Note that this menu item (along with the other debugger options) are not available until a debug session has started. You don't have to be connected to the target, but you need to have started a debug session successfully."

    Dan:  Yeah I had concluded as much.  This creates a bit of a paradox.  I attempted to start a debug session but it failed because the GEL file had an error hence the need to get to the GEL menu item.  I worked around this by accessing the GEL file directly in an editor, but was able to do so only because I had apriori knowledge of the correct GEL file.  Had I not had that knowledge then I would have been stuck.

    2.  Here is another attempt at picture:

    V71ToolsNoGelOption.docx

    3.  Ki:  "Actually, the GEL file is referenced by the target configuration ccxml file"

    Dan  OK.  I'll figure out to specify it

    4.  Ki:  "That message is a very generic message, basically akin to "something went wrong". It can apply to a myriad of cases (the link you referenced is unrated - it is regarding the TI-RTOS CFG file). What does it look like when you use the dropdown menu next to the debug button? Do you see some existing configurations listed? What happens when you press the "Debug Configurations" menu item there?"

    When I select Debug Configurations from this menu I get the same problem (nothing happens or I get null point exception).  Here is the screen shot.

    V71DebugMenu.docx

    Having implemented the workaround so that Debug finishes, I still get nothing when selecting Debug Configurations.