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.
Tool/software: TI C/C++ Compiler
Hello everyone,
when I program the TMS320F2802PZA-60 for the first time I get the following message (I use XDS110 USB Debug Probe and CCS Version: 9.3.0.00012):
C28xx: Failed CPU Reset: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.4.0.00006)
C28xx: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.4.0.00006)
C28xx: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.4.0.00006)
C28xx: GEL: Error while executing OnReset(-1): Target failed to read register ST1
at (ST1&~(0x0100)) [f2802.gel:257]
at C28x_Mode() [f2802.gel:38]
at OnReset(-(1))
C28xx: GEL: Error while executing OnTargetConnect(): Reset failed: retcode=-1
at GEL_Reset() [f2802.gel:91]
at OnTargetConnect()
C28xx: Flash Programmer: Warning: The configured device (TMS320F2802), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx: Failed CPU Reset: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.4.0.00006)
C28xx: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.4.0.00006)
C28xx: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.4.0.00006)
C28xx: GEL: Error while executing OnReset(-1): Target failed to read register ST1
at (ST1&~(0x0100)) [f2802.gel:257]
at C28x_Mode() [f2802.gel:38]
at OnReset(-(1))
C28xx: GEL: Error calling OnPreFileLoaded(): Reset failed: retcode=-1
but the DSP is correctly programmed and works well. Subsequent programming no longer shows this message.
Does anyone know why?
Hi Giovanni,
Could be a JTAG / Debug Probe issue. Is your target configuration file setup correctly and pass when tested? See JTAG debug guide for more information:
Best,
Kevin
Hi Kevin,
target configuration file should be setup correctly because the test connection does not return errors:
[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\giovanni\AppData\Local\TEXASI~1\
CCS\ccs930\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 'Nov 25 2019'.
The library build time was '16:55:29'.
The library package version is '8.4.0.00006'.
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]
Best regards,
Giovanni
Hi Giovanni,
OK, target config looks right then.
Does this issue only occur the very first time you program the device? or every time after erasing and re-programming?
I believe the errors you're getting are typically related to power not being supplied properly or the boot mode pins configuration. Can you check your boot mode selection?
Best,
Kevin
Hi Kevin,
yes, this issue only occur the very first time I program the device, not after erasing and re-programming.
I have BOOT to FLASH configuration, with GPIO18=GPIO29=GPIO34=1 by 10K pull-up resistors.
Best regards.
Giovanni
Hi Giovanni,
Giovanni Sanna said:yes, this issue only occur the very first time I program the device, not after erasing and re-programming.
OK, and by very first time you mean a brand new device, or has it been programmed for production (or by someone else)? On-chip flash comes in an erased state on a new device.
Giovanni Sanna said:I have BOOT to FLASH configuration, with GPIO18=GPIO29=GPIO34=1 by 10K pull-up resistors.
Does this same issue occur if not in FLASH boot mode?
Best,
Kevin
Hi Kevin,
by very first time I mean a brand new device. I program it because we are currently under development.
Instead, to test another configuration more than FLASH boot I need others pcb with unprogrammed DSP. At the moment I don't have any. I'll let you know as soon as I will get someone.
Best regards,
Giovanni.
Hi Giovanni,
Giovanni Sanna said:Instead, to test another configuration more than FLASH boot I need others pcb with unprogrammed DSP. At the moment I don't have any. I'll let you know as soon as I will get someone.
OK. If you're able to change the pull-up/down state of the BOOT mode pins you can use the board and device you have. You are able to erase and re-program the F2802 device as you see fit. Let us know how testing different boot modes works out.
Best,
Kevin