Part Number:TMS320F28379D
When debugging and loading to a launchpad, I'm getting a Device is held in reset error. When switching to a sample project, I can get a successful load, which would rule out hardware related issues. I copied the targetConfig file from the sample into unsuccessful project, and am also using the same debug configuration (by changing the program tab to the specific project).
During the unsuccesful debug/loading, it will get to the 'Finish" stage (>90% and past all the erasing flash/loading program calls), then eventually throws an error after hanging at the Finished state.
JTAG test connection is successful:
[Start: Texas Instruments XDS100v2 USB Debug Probe_0]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\a0226870\AppData\Local\TEXASI~1\
CCS\ccs901\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 'jioserdesusb.dll'.
The library build date was 'Mar 25 2019'.
The library build time was '17:36:26'.
The library package version is '8.1.0.00007'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
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 FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 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).
-----[The log-file for the JTAG TCLK output generated from the PLL]----------
There is no hardware for programming the JTAG TCLK frequency.
-----[Measure the source and frequency of the final JTAG TCLKR input]--------
There is no hardware for measuring the JTAG TCLK frequency.
-----[Perform the standard path-length test on the JTAG IR and DR]-----------
This path-length test uses blocks of 64 32-bit words.
The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 bits.
The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.
-----[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 XDS100v2 USB Debug Probe_0]
Console Output:
C28xx_CPU1: GEL Output:
Memory Map Initialization Complete
C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
C28xx_CPU1: Error: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.1.0.00007)
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Breakpoint Manager: Unable to remove requested AET job
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
or sometimes
C28xx_CPU1: Error: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.1.0.00007)
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
C28xx_CPU1: GEL: Error while executing OnTargetConnect(): Could not write 0x0005F412@Data: target is not connected
at *((int *) 0x5F412)=0x000F [f28377d_cpu1.gel:79]
at OnTargetConnect()
C28xx_CPU1: Error occurred during flash operation: Could not read 0x70204@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5FF00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x5FF00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005FC00@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005FC00@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x70268@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x700B0@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x70201@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070202@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070200@Data: target is not connected
C28xx_CPU1: Flash Programmer: Warning: The configured device (TMS320F28377D), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx_CPU1: Error occurred during flash operation: Could not write 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x5FF00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005FC00@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F002@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F002@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F004@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F01A@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F01C@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F01E@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F020@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F040@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F040@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F040@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F042@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F042@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F044@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F05A@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F05C@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F05E@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5F060@Program: target is not connected