• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 81 subscribers
  • Views 4501 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.

MSP432P401R - Error -1063 @ 0x0

Alexey Orishko
Intellectual 670 points


Hi all,


I have MSP432P401R with a few booster packs and I had it running for a short period. After trying to load one of examples I got an error

Error connecting to the target:
(Error -1063 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver.
(Emulation package 6.0.83.1)

Spent some time searching through previous posts, but nothing helped.

Initially I got an error while working with CCS6.1.2.00015 on ubuntu, but later tried Windows version with the same result.

As was recommended somewhere, I tried to do Factory reset, but still can't load firmware.

In CCS I see that Cortex is constantly on reset (picture changes: running/reset every second or faster), see cortex state and log messages on the picture:

It this endless run/reset cycle terminated, then on the next attempt I get Error -1063 @ 0x0...

While I was working with MSP430, it was possible to erase any bad fw and reflash it right away. What might the way be to de-brick MSP432 dev kit?

Any suggestions are welcome.

  • 0
    Guru 74080 points

    Hi Alexey!

    Did you try this already?

    Dennis

  • 0 in reply to Dennis Eichmann
    Intellectual 670 points

    Dennis Eichmann said:

    Did you try this already?

    Hi Dennis,

    Well, it took me a while to open the same screen, but there is no need to do anything - it looks exactly as on your picture.

    So, first link - no help.

    For the second link you've provided I have a bit different picture with XDS110, see

    Dennis Eichmann said:

    Then attempt to do a Factory Erase

    Is it Factory RESET or ERASE? Coz script name is reset...

    However, based on the log after script execution, it looks like erase anyway:

    CS_DAP_0: GEL Output: Mass erase executed. Please terminate debug session, power-cycle and restart debug session.

    Then did "Terminate and disconnect all", created a new project and tried to load code.

    Stuck again in the run/reset after these messages in the log:

    CORTEX_M4_0: GEL Output: Memory Map Initialization Complete
    CORTEX_M4_0: GEL Output: Halting Watchdog Timer
    CORTEX_M4_0: Flash Programmer: Erasing main memory
    CORTEX_M4_0: Flash Programmer: Writing 10264 bytes to flash memory 0x00000000

    I don't get Error -1063 on the first attempt, but on the next ones.

    Just in case, initially connected board has green led on, and when trying to flash in run/reset state: red/green.

    Alexey

  • 0
    Prodigy 40 points
    I have the same error. I've made sure it has the factory reset in the target configuration and I tried setting the JTAG frequency to the minimum. I haven't been able to get anything to run on the board since I got it today. I have been able to reset the firmware with xdsdfu.exe and the test connection button doesn't give me any errors.
  • 0 in reply to Samuel LeBlanc
    Intellectual 670 points

    Samuel LeBlanc said:

     I have been able to reset the firmware with xdsdfu.exe and the test connection button doesn't give me any errors.

    Could you, please, provide a command line you've used and a link to firmware image (if any)?

    Alexey

  • 0 in reply to Alexey Orishko
    Prodigy 40 points

    Alexey Orishko said:

    Could you, please, provide a command line you've used and a link to firmware image (if any)?

    Alexey

    I followed the instructions in ti\ccsv6\ccs_base\common\uscif\xds110\ReadMe.txt

    xdsdfu -m
    xdsdfu -f firmware.bin -r

    I used the firmware.bin that came in that directory.  It says it's version 2.2.5.1.  Should I be using a different file?

  • 0 in reply to Alexey Orishko
    Prodigy 40 points

    I am also having the same issue. I'm simply trying to run the "Out of Box Experience" code w/o GUI. Running with GUI does not work. I've tried the above mentioned answers but they do not provide a successful solution.

    Also, does it matter which S101 pins are jumped together? I assume from the documentation they should all be connected for using the XDS110 USB Debug Probe. When I received the Launchpad the RTS and CTS were disconnected. I was still having the same problem.

    Also to add, the documentation says if your using the on board emulator, you should see XDS110-ET under targetConfigs. My CCS shows the following.

  • 0 in reply to Robert Pringle
    Prodigy 40 points
    An update was available his morning for CCS...

    Tried connecting to the device again using the "Blink LED" code. It said I needed a firmware update. I clicked the button to update. That lasted all of two seconds before the device power cycled itself, and then posted the same error as the thread title again. :(

    I also noticed the target configuration file advanced options changed, so you can no longer select "Use SWD with SWO Trace Disabled" which is fine, because that did not work previously.

    With only one option left, factory reset, I proceeded with that solution. After power cycling and reloading the debugger, I get the following in the console.

    CORTEX_M4_0: GEL Output: Memory Map Initialization Complete
    CORTEX_M4_0: GEL Output: Halting Watchdog Timer
    CORTEX_M4_0: Flash Programmer: Erasing main memory
    CORTEX_M4_0: Flash Programmer: Writing 4040 bytes to flash memory 0x00000000
    CORTEX_M4_0: Failed CPU Reset
    CORTEX_M4_0: Error occurred during flash operation: CPU Reset failed with error code 1
    CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0xE004300C
    CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0x4000480C
    CORTEX_M4_0: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.83.1)
    CORTEX_M4_0: JTAG Communication Error: (Error -1170 @ 0x0) 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)
  • 0 in reply to Robert Pringle
    Prodigy 30 points

    I am experiencing the exact same problem with a brand new Launchpad and CCS.  Out of the box the launchpad had the OutOfBox image loaded and functioning. I tried the OOB windows side software to change the LED color, and that worked fine.

    I then launched into CCS and opened the OutOfBox_MSP432P401R project.   Once compiled I hit 'Debug'.   CCS said I needed to upgrade the firmware on the unit, so I clicked upgrade.  A few seconds went by and the device appeared to be in a reset loop.

    Power off and power back on, and CCS gets the same -1063 Error (unable to connect).

    Following the 'Device Security' section of the CCS user guide I was able to perform a MSP_FactoryReset.

    CCS can then connect, and the same problem happens again.  As soon as I hit Debug on any code, the console window shows:  

    CORTEX_M4_0: Flash Programmer: Writing 10264 bytes to flash memory 0x00000000

    And the device gets into a loop of resetting.    (The Debug pane flashes between "In Reset" and "Running - A reset occurred on the target).

    Firmware on the XDS110 interface:

    C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -e

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...

    <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 with CMSIS-DAP
    Version: 2.2.5.1
    Manufacturer: Texas Instruments
    Serial Num: 12345678
    Mode: Runtime

    Found 1 device.

    Anyone else found a solution?  As an aside, this is running on a new Surfacebook running Windows 10.

    Jeff

  • 0 in reply to JEFF SPONAUGLE
    Prodigy 30 points

    A minor update:

    I tired several solutions from other similar threads, including lowering the JTAG clock down to 100kHz, as well as switching to SWD Mode.

    AT 100KHz

    CORTEX_M4_0: GEL Output: Memory Map Initialization Complete

    CORTEX_M4_0: GEL Output: Halting Watchdog Timer

    CORTEX_M4_0: Flash Programmer: Verbose output enabled

    CORTEX_M4_0: Flash Programmer: DLL Version 0.9.6.0

    CORTEX_M4_0: Flash Programmer: Hard reset

    CORTEX_M4_0: Writing Flash @ Address 0x00000000 of Length 0x00000fc8

    CORTEX_M4_0: Flash Programmer: Uploading RAM loader to device

    CORTEX_M4_0: Flash Programmer: Device init finished

    CORTEX_M4_0: Flash Programmer: Erasing main memory

    CORTEX_M4_0: Flash Programmer: Mass erase finished

    CORTEX_M4_0: Flash Programmer: Writing 4040 bytes to flash memory 0x00000000

    CORTEX_M4_0: Flash Programmer: Write speed 2.6 kB/sec

    CORTEX_M4_0: Flash Programmer: Hard reset

    CORTEX_M4_0: Failed CPU Reset

    CORTEX_M4_0: Error occurred during flash operation: CPU Reset failed with error code 1

    CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0xE004300C

    CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0x4000480C

    CORTEX_M4_0: Failed CPU Reset

    CORTEX_M4_0: Error occurred during flash operation: CPU Reset failed with error code 1

    CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0xE004300C

    CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0x4000480C

    CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0xE004300C

    CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0x4000480C

    CORTEX_M4_0: Flash Programmer: Release Watchdog timer

    CORTEX_M4_0: Failed System Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.83.1)

    CORTEX_M4_0: Breakpoint Manager: One or more breakpoints will not relocate to new symbolic locations until the target halts.

    CORTEX_M4_0: AutoRun: Target not run as breakpoint could not be set: Cannot enable hardware breakpoint while the target is held in reset. Halt the target and try again

    CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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)

    CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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)

    CORTEX_M4_0: JTAG Communication Error: (Error -1170 @ 0x0) 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)

    Apon Reconnect, Errir -1063 Error connecting to Target.

    Power off board,   Connect to DAP, Perform Scripts MSP432_Factory_Reset

    CS_DAP_0: GEL Output: Mass erase executed. Please terminate debug session, power-cycle and restart debug session.

    Terminate Debug Session

    Unplug and Replug board

    Switch from "JTAG (1149.1), SWD and cJTAG are disabled" to "SWD Mode - Aux COM port is target UART port"

    Test Connection report:

    [Start: Texas Instruments XDS110 USB Debug Probe]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]

    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\jeff\AppData\Local\TEXASI~1\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 'Dec  9 2015'.

    The library build time was '20:05:50'.

    The library package version is '6.0.83.1'.

    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: Texas Instruments XDS110 USB Debug Probe]

    I then again hit Debug in the Blink Project

    CORTEX_M4_0: GEL Output: Memory Map Initialization Complete

    CORTEX_M4_0: GEL Output: Halting Watchdog Timer

    CORTEX_M4_0: Flash Programmer: Verbose output enabled

    CORTEX_M4_0: Flash Programmer: DLL Version 0.9.6.0

    CORTEX_M4_0: Flash Programmer: Hard reset

    CORTEX_M4_0: Writing Flash @ Address 0x00000000 of Length 0x00000fc8

    CORTEX_M4_0: Flash Programmer: Uploading RAM loader to device

    CORTEX_M4_0: Flash Programmer: Device init finished

    CORTEX_M4_0: Flash Programmer: Erasing main memory

    CORTEX_M4_0: Flash Programmer: Mass erase finished

    CORTEX_M4_0: Flash Programmer: Writing 4040 bytes to flash memory 0x00000000

    CORTEX_M4_0: Flash Programmer: Write speed 2.6 kB/sec

    CORTEX_M4_0: Flash Programmer: Hard reset

    CORTEX_M4_0: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.83.1)

    CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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)

    CORTEX_M4_0: Error occurred during flash operation: CPU Reset failed with error code 1

    CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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)

    CORTEX_M4_0: Error occurred during flash operation: Could not read 0xE004300C: execution state prevented access

    CORTEX_M4_0: Error occurred during flash operation: Could not write 0xE004300C: execution state prevented access

    CORTEX_M4_0: Flash Programmer: Watchdog halt failed

    CORTEX_M4_0: Error occurred during flash operation: Could not read 0x4000480C: execution state prevented access

    I did another Factory_Reset, change the Target Configuration to "SWD Mode - Aux COM port is target TDO pin"

    That failed as follows:  

    CORTEX_M4_0: GEL Output: Memory Map Initialization Complete

    CORTEX_M4_0: GEL Output: Halting Watchdog Timer

    CORTEX_M4_0: Flash Programmer: Verbose output enabled

    CORTEX_M4_0: Flash Programmer: DLL Version 0.9.6.0

    CORTEX_M4_0: Flash Programmer: Hard reset

    CORTEX_M4_0: Writing Flash @ Address 0x00000000 of Length 0x00000fc8

    CORTEX_M4_0: Flash Programmer: Uploading RAM loader to device

    CORTEX_M4_0: Flash Programmer: Device init finished

    CORTEX_M4_0: Flash Programmer: Erasing main memory

    CORTEX_M4_0: Flash Programmer: Mass erase finished

    CORTEX_M4_0: Flash Programmer: Writing 4040 bytes to flash memory 0x00000000

    CORTEX_M4_0: Flash Programmer: Write speed 2.6 kB/sec

    CORTEX_M4_0: Flash Programmer: Hard reset

    CORTEX_M4_0: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.83.1)

    CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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)

    CORTEX_M4_0: Error occurred during flash operation: CPU Reset failed with error code 1

    CORTEX_M4_0: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.83.1)

    CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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)

    CORTEX_M4_0: Error occurred during flash operation: CPU Reset failed with error code 1

    CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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)

    CORTEX_M4_0: Error occurred during flash operation: Could not read 0xE004300C: execution state prevented access

    CORTEX_M4_0: Error occurred during flash operation: Could not write 0xE004300C: execution state prevented access

    CORTEX_M4_0: Flash Programmer: Watchdog halt failed

    CORTEX_M4_0: Error occurred during flash operation: Could not read 0x4000480C: execution state prevented access

    CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. 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)

    CORTEX_M4_0: Error occurred during flash operation: Could not read 0xE004300C: execution state prevented access

    CORTEX_M4_0: Error occurred during flash operation: Could not write 0xE004300C: execution state prevented access

    CORTEX_M4_0: Flash Programmer: Watchdog halt failed

    CORTEX_M4_0: Error occurred during flash operation: Could not read 0x4000480C: execution state prevented access

    CORTEX_M4_0: Error occurred during flash operation: Could not write 0x4000480C: execution state prevented access

    CORTEX_M4_0: Flash Programmer: Watchdog halt failed

    CORTEX_M4_0: Flash Programmer: Release Watchdog timer

    CORTEX_M4_0: GEL: Error while executing OnRestart( 0 ): Specified reset is not allowed at this time

    at GEL_AdvancedReset("System Reset", 1) [msp432p401r.gel:173]

    at OnRestart(0)

    I did another Factory Reset:

    CS_DAP_0: GEL Output: Mass erase executed. Please terminate debug session, power-cycle and restart debug session.

    I switch to 250KHz JTAG

    CORTEX_M4_0: GEL Output: Memory Map Initialization Complete

    CORTEX_M4_0: GEL Output: Halting Watchdog Timer

    CORTEX_M4_0: Flash Programmer: Verbose output enabled

    CORTEX_M4_0: Flash Programmer: DLL Version 0.9.6.0

    CORTEX_M4_0: Flash Programmer: Hard reset

    CORTEX_M4_0: Writing Flash @ Address 0x00000000 of Length 0x00000fc8

    CORTEX_M4_0: Flash Programmer: Uploading RAM loader to device

    CORTEX_M4_0: Flash Programmer: Device init finished

    CORTEX_M4_0: Flash Programmer: Erasing main memory

    CORTEX_M4_0: Flash Programmer: Mass erase finished

    CORTEX_M4_0: Flash Programmer: Writing 4040 bytes to flash memory 0x00000000

    CORTEX_M4_0: Flash Programmer: Write speed 4.6 kB/sec

    CORTEX_M4_0: Flash Programmer: Hard reset

    CORTEX_M4_0: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.83.1)

    CORTEX_M4_0: JTAG Communication Error: (Error -1170 @ 0x0) 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)

    Factory Reset again:

    CS_DAP_0: GEL Output: Mass erase executed. Please terminate debug session, power-cycle and restart debug session.

    Unplug/Replug

    Switch to the OutOfBox_ example, Hit Debug

    CORTEX_M4_0: GEL Output: Memory Map Initialization Complete

    CORTEX_M4_0: GEL Output: Halting Watchdog Timer

    CORTEX_M4_0: Flash Programmer: Erasing main memory

    CORTEX_M4_0: Flash Programmer: Writing 10264 bytes to flash memory 0x00000000

    Then it unit is stuck in a reset cycle.

    Jeff

**Attention** This is a public forum