Fresh, Out of the box and bag, New LP...
1st Attempt to Load "Blink LED" (Out of Box Program GUI worked properly).
Upon Debug, Error pops up stating to update firmware.
CS_DAP_0: Error connecting to the target: (Error -1040 @ 0x0) A firmware update is required for the debug probe. Click the "Update" button to update the firmware and connect to the debug target. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 6.0.83.1)
I click Update and receive the following:
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)
2nd Attempt. Retrying "Blink LED".
Power Cycled the board.
Started to debug.
I receive the following:
CORTEX_M4_0: 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)
I confirm Device and Debug Probe are correct in "Properties for BlinkLED_MSP432P401R".
Processor: MSP432P401R
Connection: Texas Instruments XDS110 USB Debug Probe [Default]
Compiler Version TI v5.2.6
Output Format eabi (ELF)
I then proceed to try updating the device driver.
The driver software appears to be up to date (according to Windows).
Driver version 1.6.0.0 Dated 11/25/2014 for XDS110 Class Debug Probe and XDS110 Class Data Port.
I then proceed to lower the TCLK Frequency to a "more reliable" setting of 500 kHz.
I test the connection, and receive the following:
[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\Robert\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.
This utility has successfully reset the controller.
-----[Print the reset-command hardware log-file]-----------------------------
The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).
-----[Perform the Integrity scan-test on the JTAG IR]------------------------
This test will use blocks of 64 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG IR Integrity scan-test has succeeded.
-----[Perform the Integrity scan-test on the JTAG DR]------------------------
This test will use blocks of 64 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG DR Integrity scan-test has succeeded.
[End: Texas Instruments XDS110 USB Debug Probe]
I restart the Debug, and receive the following:
CORTEX_M4_0: 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)
I assume since the update failed, I will need to do a factory reset. I follow the steps in slau575b, section 7 and receive the following:
CS_DAP_0: GEL Output: Mass erase executed. Please terminate debug session, power-cycle and restart debug session.
I noticed in the progress window that "Launching Blink_LEDMSP432P401R was still running. I tried cancelling. Still running. So at this point I restart CCS and power cycle the board. Upon re-openning I erase the project from the workspace and re-import it. I then change the TCLK speed back to 500 kHz. I build the blink LED project and launch the debugger. I receive the following:
CS_DAP_0: Error connecting to the target: (Error -302 @ 0x0) The requested TCLK PLL frequency option is invalid. The utility or debugger has requested a selection of the JTAG PLL frequency or clock source that is invalid. The value of USCIF.TCLK_FREQUENCY is probably bad. (Emulation package 6.0.83.1)
Fair enough. I go back to the target config and change it back to 2.5MHz. I then re-launch the debugger. I receive the following:
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: (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)
The device then hangs in the loading program state and I have to Cancel and Terminate the Debug session. The process is still running in the Progress window, and trying to cancel it from there still does not work. I restart CCS and power cycle the board again. I try a factory reset from that state.
CS_DAP_0: GEL Output: Mass erase executed. Please terminate debug session, power-cycle and restart debug session.
I terminate, and re-cycle the board, then attempt to launch debug for the blink LED program. I receive the following:
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: (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)
CCS hangs in launch mode again. Exact same as the previous attempt. I noticed this time that LED1 did blink however. I'm not sure if it did previously. I figure try factory reset once more and pay close attention to see if the LED blinks more than once. Rinse and repeat if you will. I restart CCS and perform another factory reset. Then I attempt to Launch the Blink LED debug session. I get the same errors, and I confirm that LED1 only Blinks once.
From here I do some digging to find some reliable JTAG TCLK settings that won't trip an error -302 again. I cannot find recommended settings in the documentation. I try resetting one more time and rerunning the debugger with default settings. Same story again.
I try setting the JTAG TCLK to 1 MHz, and performing a factory reset, then launching the debugger for the Blink LED program. This time I get some more info 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)
I try Factory reset another time with the new JTAG TCLK setting of 1 MHz. This time I get less info:
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: (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)
Tried several times to keep erasing at 1.0MHz. Still giving same errors. I figured as a last resort before posting this thread I would try the lowest setting. 100kHz.
I performed the factory reset at 100kHz JTAG setting and then launched the debugger for the Blink LED program. Same Errors. At this point I'm thinking JTAG TCLK settings aren't the issue. I've heard you have to perform factory reset more than once, so I keep trying...
I get the same errors on subsequent attempt, however this time, the program doesn't hang. So I try factory reset one more time, and I get this:
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
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: 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
Looks like some new information! So I'm interested again, The debugger is still not hanging, and I perform another factory reset.
Now it opens up boot.asm in the debugger. Also shows "no source available for 0x100056c." Console reads the following:
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
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: Failed System Reset
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)
I rinse and repeat.
This time it hangs again.
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: (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)
I figure one more time and I'll call it a night. I reset CCS due to hanging. Rinse, Repeat.
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
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: 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: AutoRun: Target not run as breakpoint could not be set: Error enabling this function: Target Access Failed
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)
I try again and this time boot.asmopens again. I note the line it shows being caught on:
Line 149 MOVW r1, #cpacr & 0xFFFF
I try again. boot.asm opens again. Same line 149.
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
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: Failed System Reset
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)
I tried several more times.
Same Story. :(
Nothing is working. Looks like I'm going to have to downgrade to the MSP430 until I can get this running. I now have two MSP432 bricks with this same issue. Please advise.
Thank you,
Robert