• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 931 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.

MSPM0G3507: Unable to access Debug Properties in CCS Theia 1.4.0.12

Dave Lang
Prodigy 30 points

Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

I'm attempting to debug a bare-metal application on a MSPM0G3507 residing on a target board, via SWD using a SEGGER J-Link.  Am unable to use the XDS110 on my LaunchPad because the target board uses 1.8V signaling (LP supports 3.3V only).  The application's main() function consists of initialization code followed by a "superloop" which spends most of its time awaiting an interrupt via a WFI instruction.  The low power policy specified via SysConfig is SLEEP0.  When the MCU's program flash is blank, I'm able to successfully establish a debug connection to it using CCS Theia, and debug normally.  However, subsequent attempts to establish a debug connection fail with the message "Error connecting to the target: Could not connect to target."  I discovered that if I connect to the MCU via J-Link Commander and erase the MCU's flash, a subsequent attempt to establish a debug connection via CCS is successful.  Thinking that perhaps this connection issue was a consequence of the MCU being in low power mode, I reviewed the addenda in the MCU SDK's "Known Issues and FAQ" section.  None of the described scenarios matched exactly, but it seemed that configuring the J-Link to perform a hardware reset of the target before connecting was a reasonable step.  However, when I attempt to access Debug Properties in CCS in order to configure the reset, I get the message "Cannot read properties of undefined (reading 'name').  Interestingly, if I reconfigure the "Connection" to be XDS110 instead of J-Link, the Debug Properties screen comes up fine.  Any ideas?  Note that I am using the latest J-Link firmware.  Thanks

  • 0
    TI__Mastermind 31205 points

    Hi Dave,

    Please claim the details, I am not fully clear what error is.

    Dave Lang said:
    When the MCU's program flash is blank, I'm able to successfully establish a debug connection to it using CCS Theia, and debug normally.  However, subsequent attempts to establish a debug connection fail with the message "Error connecting to the target: Could not connect to target."

    Any error screenshot?

    what will happen if you only load an empty example project to the device?

    Dave Lang said:
    However, when I attempt to access Debug Properties in CCS in order to configure the reset, I get the message "Cannot read properties of undefined (reading 'name'). 

    Any error screenshot? Note that J-Link is not an TI device, so it might not support debug modification here.

    B.R.

    Sal

  • 0 in reply to Sal Ye
    Prodigy 30 points

    Hi Sal,

    Thanks for your reply.  Here's a screenshot of an attempt to debug my project, after having debugged (and flashed) it successfully once prior:

    The same result is seen when attempting to debug the "empty" project:

    And here is the error seen when attempting to access Debug Properties:

    If the answer is that the Debug Properties menu is not supported for non-TI devices, that's OK -- I just wanted to make sure that I wasn't missing anything.

    Thanks, Dave L.

  • 0 in reply to Dave Lang
    TI__Mastermind 31205 points

    Hi Dave,

    Let me download the latest CCS Thiea version and double check this message.

    B.R.

    Sal

  • 0 in reply to Sal Ye
    TI__Mastermind 31205 points

    Hi Dave,

    I got the same result as you mentioned.

    I will check internally to see whether this is support or not, maybe need manual steps I am not aware.

    Will feedback here when I got some progress. Thanks for your patience.

    B.R.

    Sal