• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 6827 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/MSP432-DEBUGGERS: Encountering a Very Strange Issue. MSP432 Launchpad giving debug error on my desktop, with error msg: Can't Run Target CPU: (Error -2134 @ 0x0). Unable to control device execution state, but working fine on other desktops.

suraj H
Prodigy 210 points
Part Number: MSP432-DEBUGGERS

Tool/software: Code Composer Studio

Hi, 

I am getting a very strange issue on my desktop. While trying to debug any program, CCS is giving below error:

CORTEX_M4_0: Can't Run Target CPU: (Error -2134 @ 0x0) Unable to control device execution state. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.628.3)


CORTEX_M4_0: JTAG Communication Error: (Error -615 @ 0x0) The target failed to see a correctly formatted SWD header. The connection to the target may be unreliable. Try lowering the TCLK setting before trying again. (Emulation package 6.0.628.3).

My version of CCS is 7.2.0.00013. I tested the issue with a sample GPIO interrupt program by TI  and one of our own program. But the strange thing is, It is running fine on my colleague's system (with CCS 7.1....). 

Moreover, I had one more board (same MSP432 launchpad) which I was using on my desktop, but it suddenly stopped working one day with error msg: 

CCS/MSP432P401R: MSP432_Factory_Reset() cannot be evaluated. identifier not found: DP_RESET at DP_RESET=1 [msp432_factory_reset.gel:44] at MSP432_Factory_Reset()CS_DAP_0: Error connecting to the target: (Error -613 @ 0x0). 

I tried to factory reset it, as per the link (e2e.ti.com/.../1854733 . But it is giving below error:

CS_DAP_0: Trouble Writing Memory Block at 0xe0044000 on Page 0 of Length 0x4: (Error -613 @ 0xE0044000) The target indicates that it is busy.  Either try the SWD request  again, or abort the transaction. (Emulation package 6.0.628.3)

CS_DAP_0: GEL: Error while executing MSP432_Reboot_Reset(): Target failed to write 0xE0044000@System_View at *((unsigned int *) 0xE0044000)=0x0000695A [msp432_factory_reset.gel:75] at MSP432_Reboot_Reset().

So, in short two boards are not working from the same desktop. Please help me resolve this glitch Or should I take my desktop to an Exorcist ?  ; )  :D

Kind Regards

Suraj

 

 

  • 0
    TI__Mastermind 26380 points
    Hi,
    Thanks for posting to the forum.
    Just to make sure we are on the same page, can you tell me what Revision LaunchPad you are using?

    The Rev1.0 LPs are black & support pre-release devices.
    If you have the Rev2.0 LPs (Red), these should work as expected.

    -Priya
  • 0 in reply to Priya Thanigai
    Prodigy 210 points
    Hi Priya,

    Thanks for commenting. Both the boards are Rev2.0 LPs (Red).
  • 0 in reply to suraj H
    TI__Prodigy 475 points
    Hi Suraj,

    regarding the factory reset: Could you try once again with the description in SLAU575 (www.ti.com/.../SLAU575), chapter 8.1 and tell us if you could connect to the DAP core?

    If this doesn't work go back to your project explorer, open the project properties and click on "Verify" debugger connection in the popup window.

    If the verification does not work I recommend to uninstall all XDSD110 probes via the device manager (under "Texas Instruments debug probes") and unplug/replug your launch pad in order to install the driver again.

    Hope that helps.

    Regards,

    Thorsten
  • 0 in reply to Thorsten Stauber
    Prodigy 210 points
    Hello Thorsten,

    Thanks for your suggestion.

    I can connect to the DAP core, by following section 8.1. But after clicking on Factory Reset from Scripts, I get the below error.

    CS_DAP_0: Trouble Writing Register DP_RESET: (Error -613 @ 0x2) The target indicates that it is busy. Either try the SWD request again, or abort the transaction. (Emulation package 6.0.628.3) MSP432_Factory_Reset() cannot be evaluated.
    Target failed to write register DP_RESET at DP_RESET=1 [msp432_factory_reset.gel:44] at MSP432_Factory_Reset().

    Next, I also clicked on "Verify" from Project properties, and it also seems to connect successfully. See the message below:

    CCS\ti\0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioxds110.dll'.
    The library build date was 'May 23 2017'.
    The library build time was '19:37:36'.
    The library package version is '6.0.628.3'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '5' (0x00000005).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller to enter SWD mode.

    -----[Print the reset-command hardware log-file]-----------------------------

    This emulator does not create a reset log-file.

    -----[Perform the SWD Mode Integrity test]-----------------------------------

    This test will read the IDCODE register 100 times.

    The IDCODE register value is 0x2ba01477.

    The SWD Mode Integrity test has succeeded.

    [End]

    Apart from all this, I have uninstalled > installed XDS110 driver, (ti_emupack_setup_6.0.579.0_win_32.exe) in C:\ti\ccsv7, after reading post e2e.ti.com/.../398575. Earlier I tried the same step and installed XDS110 driver in C:\ti. But nothing's working.


    Kind Regard
    Suraj
  • 0 in reply to suraj H
    TI__Prodigy 475 points

    Hi Suraj,

    given that the boards work at your colleagues desk I assume the hardware is still ok.

    Could you please try the other two steps I've suggested above? (Verifying the debugger connection and if this is not working removing the device in the device manager)

    Sometimes, when a lot of switching between different launch pads has been done something gets mixed up in windows which would explain your error messages.

    Regards,

    Thorsten

  • 0 in reply to Thorsten Stauber
    Prodigy 210 points
    Hi Thorsten,

    I have checked the debugger connection. It returns me below message.

    CCS\ti\0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioxds110.dll'.
    The library build date was 'May 23 2017'.
    The library build time was '19:37:36'.
    The library package version is '6.0.628.3'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '5' (0x00000005).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller to enter SWD mode.

    -----[Print the reset-command hardware log-file]-----------------------------

    This emulator does not create a reset log-file.

    -----[Perform the SWD Mode Integrity test]-----------------------------------

    This test will read the IDCODE register 100 times.

    The IDCODE register value is 0x2ba01477.

    The SWD Mode Integrity test has succeeded.

    [End].

    I already uninstalled and installed new XDS110 drivers. But both the boards (Red) are not working on my system.

    Leave the one which is working on my colleague's system, as i am not planning to factory reset it. But the one which is completely dead, I will try resetting from some other desktop and let you know. I really want to find the root cause of this issue.

    Thankyou Thorsten, for your help and suggestions.

    Kind Regards
    Suraj
  • 0 in reply to suraj H
    TI__Mastermind 26380 points
    Suraj,
    It's quite possible you have a board with issues (or some combination of drivers + windows).
    I'd recommend getting a replacement Launchpad if possible.

    -Priya
  • 0 in reply to Priya Thanigai
    Prodigy 210 points
    Hi Priya,

    How can I get a replacement launchpad, please suggest?
  • 0 in reply to suraj H
    TI__Mastermind 26380 points
    This is most likely via a local distributor or Digikey. How was the original Launchpad purchased?

**Attention** This is a public forum