• State TI Thinks Resolved
  • Locked Locked
  • Replies 28 replies
  • Answers 4 answers
  • Subscribers 80 subscribers
  • Views 32241 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.

MSP432 Error Factory Reset

Christoph Marko
Expert 1450 points

hi guys,

I got really silly with my launchpad. I couldn't connect to my 2 MSP432 launchpads anymore. I tried the reset of the firmware with the xdsdfu tool that worked fine and also the test connection always succeeded. Than I want to run the factory reset with the file. The half of the time I couldn't connect to the dsap but when I plug off and plug in again its able to connect. But when I want to use the factory reset I got this message:

Register DP_RESET: (Error -1170 @ 0x2) Unable to access the DAP. 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.83.1)
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()

Does anybody know how to fix this?

  • 0
    TI__Mastermind 49692 points

    Hi Christoph,

    According to the Debugging JTAG Connectivity Problems wiki page, this error is caused by the inability of the JTAG debugger to access the DAP or one of its ARM subcores. This is usually caused by either a hardware failure on the board or invalid code on the subcore that causes it to reset itself continuously. If this error is originated in software, it can potentially be recovered by accessing the DAP directly and trying to either reset the offending core, lock it or erase its flash memory via a GEL script (some microcontrollers have pre-loaded routines to allow that).

    For detailed factory reset instructions, take a look at Section 8 in the Code Composer Studio 6.1 for MSP432 User's Guide. I've summarized these steps below. Are these the steps you've been following?

    1. Connect the failing LaunchPad/unit to your PC.
    2. Open CCS, assume you already have at least one MSP432 project open.
    3. Go to View > Target Configuration.
    4. Within Target Configuration navigate to your MSP432 project > the .ccxml file.
    5. Right Click > Launch Configuration
    6. Under Debug window you should now see some tree structure starting with the .ccmxl file being the root > something_CORTEX_M4_something (unknown)
    7. Right Click > Show all hidden cores.
    8. Connect only to the Non-Debuggable Devices > DAP.
    9. Go to Script > Factory Reset.
    10. Power cycle and try to restart debug.

    Another approach may be to perform the factory reset using an external debugger (e.g. XDS200), related to this thread.

    MSP432 LaunchPad: Debugging fails with 'Unable to connect to the target' error - MSP low-power microcontroller...

    e2e.ti.com
    Other Parts Discussed in Thread: UNIFLASH Hi I have a problem with the new MSP-EXP432P401R (hardware unchanged, out-of-the-box). It worked at the beginning

    Hope this helps!

    Regards,

    James

    MSP Customer Applications

  • 0 in reply to James Evans
    Expert 1450 points
    Hi James,
    i tried to follow exactly this 10 steps but when I want to connect only to the DAP, I got the error. (this was by 2 boards)
    Therefore I am unable to run the factory reset in the next step.
  • 0 in reply to Christoph Marko
    TI__Mastermind 49692 points

    Hi Christoph,

    Christoph Marko said:
    I got really silly with my launchpad. I couldn't connect to my 2 MSP432 launchpads anymore.

    Could you provide more details about any changes that you made before you encountered this issue? Did you perform any updates in CCS?

    In the meantime, can you take a look at this thread to see if it helps resolve your issue?

    CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not...

    e2e.ti.com
    Hi , I have a rather puzzling issue. I get the following error when trying to debug the MSP-EXP432P401R using the BlinkLED_MSP432P401R example: CORTEX_M4_0

    Regards,

    James

    MSP Customer Applications

  • 0 in reply to James Evans
    TI__Mastermind 25045 points
    Hi Christoph,

    Maybe, you accidentally reconfigured the JTAG pins (Port J), please take a look at this post:

    e2e.ti.com/.../1803236

    Hopefully this helps.

    David
  • 0 in reply to DavidL
    Expert 1450 points
    hi david,
    that could be.
    But is it possible to reset it without the jtag interface?
  • 0 in reply to Christoph Marko
    TI__Mastermind 25045 points

    Hi Christoph,

     Yes it is possible. You will have to use the Flash Mailbox, please take a look at section 3 of this document Configuring Security and Bootloader (BSL) on MSP432P4xx (Rev. A)

      Did you try the running the Factory Reset using the SWD interface (2-pin Serial Wire Debug)??

       Regards,

        David

  • 0 in reply to DavidL
    Expert 1450 points

    hi david,


    i tried to follow the instruction but I got the following error

     Error connecting to the target:
    (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.83.1)


  • 0 in reply to Christoph Marko
    Expert 1450 points
    and on the second board i got this error:
    Error connecting to the target:
    (Error -613 @ 0x0)
    The target indicates that it is busy. Either try the SWD request
    again, or abort the transaction.
    (Emulation package 6.0.83.1)
  • 0 in reply to DavidL
    Expert 1450 points

    hi david,

    I read the document but I don't know I should update the code, when the board isn't found by the CCS.

    I tested various methods (see posts above) but It wasn't possible to access to the board.

    Do you have some hints?

  • 0 in reply to Christoph Marko
    TI__Mastermind 25045 points

    Hi Christop,

    Could you please send me the code that you used to break/brick your Launchpad's??

    Thanks,

    David

  • 0 in reply to DavidL
    Expert 1450 points
    I used the msp432p401_pcm_02.c from the TI Ressource Explorer.
  • 0 in reply to Christoph Marko
    TI__Mastermind 25045 points
    Hi Christoph,

    Which version of MSPWare are you using?? Could you please send the whole project??

    Thanks again,

    David
  • 0 in reply to DavidL
    Expert 1450 points
    hi david,
    i would check the version, when I at home. Yesterday I made an update on the latest version and the project is that from the TI Ressource Explorer. I didn't change anything in the code.
    Greez,
  • 0 in reply to Christoph Marko
    Expert 1450 points

    hi david,

    i use the MSPWare Version 3.30.0.18.

    I tried it again to get a connection to the board and now I got this error :

    CS_DAP_0: Trouble Writing Register DP_RESET: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 6.0.83.1)
    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()

  • 0 in reply to Christoph Marko
    TI__Mastermind 49692 points

    Hi Christoph,

    For your board that's encountering "Error connecting to the target: Error -613", can you try the following steps? Using a project that intentionally bricked the MSP432 (thanks DavidL), I encountered this error but was able to successfully complete the Factory Reset.

    1. In CCS, configure .ccxml file for recovery.
      1. View -> Target Configurations -> User Defined -> NewTargetConfiguration.ccxml (I renamed this file) -> Basic tab (select XDS110 debugger, MSP432) -> Advanced tab -> Texas Instruments XDS110 USB Debug Probe_0
      2. Configure the Connection Properties.
        1. Board Data File: auto generate
        2. Debug Probe Selection: Only one XDS110 installed
        3. Fixed with user specified value: 2.5MHz
        4. JTAG/SWD/cJTAG Mode: SWD Mode - Aux COM port is target UART port
      3. Click "Save".

    2. Prepare to perform the Factory Reset.
      1. Right-click this .ccxml file, select "Launch Selected Configuration".
      2. In the Debug window, right-click Texas Instruments XDS110 USB Debug Probe_0, select "Show all cores", then right-click "Non Debuggable Devices", and select "Connect Target".
      3. You should encounter Error -613, as shown below.

      4. Before clicking anything, unplug the board, then plug it back into the PC.
      5. Click "Retry" and the board should successfully connect.

    3. Perform Factory Reset.
      1. Go to Scripts -> default -> MSP432_Factory_Reset (this should successfully reset the MSP432).

      2. As described directly above, terminate the debug session, power cycle the board, and restart the debug session (I just started debugging the blink LED example).
      3. Success!

    Please let me know if you have any questions about these instructions and if they help reset your boards.

    Regards,

    James

    MSP Customer Applications

  • 0 in reply to James Evans
    Expert 1450 points

    hi james,

    thank you for your advice.

    I tried it like you suggested, but it didn't work.

    I got this message:

    CS_DAP_0: Error connecting to the target: (Error -613 @ 0x0) The target indicates that it is busy.  Either try the SWD request  again, or abort the transaction. (Emulation package 6.0.83.1)

    When I executed the test connection or tried to update the firmware it was successful.

    But I couldn't run the factory reset ...

  • 0 in reply to Christoph Marko
    TI__Mastermind 49692 points

    Hi Christoph,

    Thanks for trying my recommendations and providing feedback.

    Since our factory reset process doesn't seem to be working for you so far, we'd like to know more about your setup and what may have caused the boards to become unresponsive (code, power, etc.). Could you please provide more background information?

    If we can figure out what may have caused the issue, it will help point us in the right direction and hopefully towards a solution for you.

    Regards,

    James
    MSP Customer Applications

  • 0 in reply to James Evans
    TI__Mastermind 49692 points
    Hi Christoph,

    Have you been able to resolve this issue? If not, we'd like to take a closer look at your code and board.

    Regards,

    James
    MSP Customer Applications
  • 0 in reply to James Evans
    TI__Mastermind 49692 points
    Hi Christoph,

    I'm closing this thread, but please feel free to reply back if you have further questions about this topic.

    Regards,

    James
    MSP Customer Applications
  • 0 in reply to James Evans
    Expert 1505 points
    Hi James,
    I don't know if this is the right place to post this, but I too have a similar problem with my Red MSP432 launchpad. I tried to program the clock to 48 MHz a number of times without the fast wait states. I think this is what originally bricked it. I tried to follow your procedure here, without any success. Now I'm getting this message in the console:

    CORTEX_M4_0: * WARNING *: The connected device is not MSP432P401R
    CORTEX_M4_0: GEL Output: Memory Map Initialization Complete
    CORTEX_M4_0: GEL Output: Halting Watchdog Timer
    CORTEX_M4_0: Flash Programmer: Reading device TLV failed.
    CORTEX_M4_0: Your XMS432P401R material is no longer supported. We recommend you moving to production-quality MSP432P401R/M silicon by ordering samples at www.ti.com/product/MSP432P401R.
    CORTEX_M4_0: Flash Programmer: Device not recognized
    CORTEX_M4_0: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.
    CORTEX_M4_0: File Loader: Verification failed: Values at address 0x000023CC do not match Please verify target memory and memory map.
    CORTEX_M4_0: GEL: File: /home/frohro/workspace_v7/Test/Debug/Test.out: a data verification error occurred, file load failed.

    Do you have any advice for me?

    Thanks,

    Rob
  • 0 in reply to Rob Frohne
    Expert 1505 points
    Hi James,

    Here is a link to a previous post that I tried to follow, but didn't seem to work for me. I think I originally got the 613 error, but now it doesn't seem to show up, just the stuff above in the console.

    Thanks,

    Rob
  • 0 in reply to Rob Frohne
    TI__Mastermind 49692 points
    According to your warnings, it looks like you're LaunchPad has the pre-production (XMS432) silicon. I'd recommend replacing the MSP432 with production-level (MSP432) silicon. The samples available now should all be production-level.

    Hope this helps!

    Regards,

    James

    MSP Customer Applications
  • 0 in reply to James Evans
    Expert 1505 points
    Thanks for your kind reply James. This one was purchased from Digikey in March of this year. It is at the office, and so I can't inspect the unit at the moment. Will it be correctly identified on the IC if I inspect it under the microscope? Also, I'd love to get a sample to replace this one, but TI no longer supplies samples to professors or students (or anyone else with a .edu email address). The people at university support don't reply to emails either. And there is no student design contest anymore. It was a nice motivation for my students. I'm glad you guys here still reply to my queries. The help I got here this quarter was very helpful as I was writing the software for my student's hardware designs (vector network analyzer booster packs for the MSP432). The red board I bricked was one we bought for a student, and he will be needing it soon. :-( I guess I'll probably have to order another from Digikey. I'm wondering if we need to inspect all the boards we purchased from Digikey, to see if they are all pre-production silicon too. The funny thing is that I have a black board that must have the pre-production silicon and it works just fine. I guess I didn't brick it though. :-)

    Thanks again,

    Rob
  • 0 in reply to Rob Frohne
    Expert 1505 points

    Hi James,

    It is very hard to read, but under the microscope I can tell it is  labeled as MSP432P401R Rev C.  I have one of the XMSP432's here to compare it to.  Is there a bug in the error messages?  Is this board just fried?  Did the chip recyclers put a relabeled XMSP432 on the board?  What is the story?  Here is my photo.

    Thanks,

    Rob

  • 0 in reply to Rob Frohne
    TI__Mastermind 25045 points
    Hello Rob,

    Which version of CCS are you using??

    This might be an issue with the IDE, please take a look at this link processors.wiki.ti.com/.../XMS432_Support (IDE Compatibility)

    Thanks,

    David
  • 0 in reply to DavidL
    Expert 1505 points

    Hi David,

    Thanks for the reply on this.  Reading the wiki above indicates that I need to purchase new launchpad boards for the black ones I am running.  The red one I have that says it is a Rev C device is still puzzling me.  Everything I read says the boards that are working should not, and the one that the one that is not working should.  :-)  I am using Code Composer Studio Version: 7.1.0.00016.

    Here is the console output when connected to the March 2017 red launchpad pictured above (that I bricked without the wait states).

    CORTEX_M4_0: * WARNING *: The connected device is not MSP432P401R
    CORTEX_M4_0: GEL Output: Memory Map Initialization Complete
    CORTEX_M4_0: GEL Output: Halting Watchdog Timer
    CORTEX_M4_0: Flash Programmer: Reading device TLV failed.
    CORTEX_M4_0: Your XMS432P401R material is no longer supported. We recommend you moving to production-quality MSP432P401R/M silicon by ordering samples at www.ti.com/product/MSP432P401R.
    CORTEX_M4_0: Flash Programmer: Device not recognized
    CORTEX_M4_0: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.
    CORTEX_M4_0: File Loader: Verification failed: Values at address 0x00001938 do not match Please verify target memory and memory map.
    CORTEX_M4_0: GEL: File: /home/frohro/workspace_v7/ADC14_BareMetal/Debug/ADC14_BareMetal.out: a data verification error occurred, file load failed.

    Thanks,

    Rob 

  • 0 in reply to Rob Frohne
    TI__Mastermind 25045 points
    Hello Rob,

    Please send me a private message with your contact information (you can click on my profile and send me a private message that way), I would like to get this board and I will send you a new one.

    Thanks,

    David
  • 0 in reply to DavidL
    Expert 1505 points
    Thanks Davd,
    I sent you a friend request, which allowed me to send you my email address.
    Rob

**Attention** This is a public forum