• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 2869 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.

CCS/TMS320F28377S: C28xx_CPU1: Failed CPU Reset: (Error -1137 @ 0x6) Device is held in reset.

Nir Givon
Intellectual 345 points
Part Number: TMS320F28377S

Tool/software: Code Composer Studio

Hello,

I am trying to bring up boards from a new layout.

The new layout has no changes from the previews layout with regards to the CPU.

I have tested all the voltages on my board and it all looks fine. also the OSC is vibrating nicely.

For some reason I can't upload software to the Delfino.

I monitored the communication with the XSD100v2 USB debug probe and the Delfino and the communication looks exactly like in the old board.

the Reset signal behaves the same. and the CPU is replaying to the messages from the XSD100v2

Why do i get this error:

C28xx_CPU1: Failed CPU Reset: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.100.1)
C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.100.1)
C28xx_CPU1: GEL: Error while executing OnReset(1): Internal error while writing 0x0005FB00@Data
at *((int *) 0x5FB00)=0 [f28377s.gel:28]
at OnReset(1)
C28xx_CPU1: Trouble Writing Memory Block at 0x5fb00 on Page 0 of Length 0x2: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.100.1)
C28xx_CPU1: Error occurred during flash operation: Target failed to write 0x5FB00@Program
C28xx_CPU1: Trouble Writing Memory Block at 0x5f800 on Page 1 of Length 0x2: (Error -1137 @ 0x5F802) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.100.1)
C28xx_CPU1: Error occurred during flash operation: Target failed to write 0x0005F800@Data
C28xx_CPU1: Trouble Writing Memory Block at 0x5fb00 on Page 0 of Length 0x2: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.100.1)
C28xx_CPU1: Error occurred during flash operation: Target failed to write 0x5FB00@Program
C28xx_CPU1: Trouble Writing Memory Block at 0x5f800 on Page 1 of Length 0x2: (Error -1137 @ 0x5F802) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.100.1)
C28xx_CPU1: Error occurred during flash operation: Target failed to write 0x0005F800@Data
C28xx_CPU1: Failed CPU Reset: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.100.1)
C28xx_CPU1: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.100.1)
C28xx_CPU1: GEL: Error while executing OnReset(1): Internal error while writing 0x0005FB00@Data
at *((int *) 0x5FB00)=0 [f28377s.gel:28]
at OnReset(1)
C28xx_CPU1: 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.
C28xx_CPU1: File Loader: Verification failed: Values at address 0x82000@Program do not match Please verify target memory and memory map.
C28xx_CPU1: GEL: File: C:\Users\user\workspace_v7\TOPI_MC_nir\F2837x_FLASH\TOPI_MC_nir.out: a data verification error occurred, file load failed.

  • 0
    TI__Guru 55700 points
    Did you already try probing the XRSn pin? If so, what was your observation? Can you send us the snapshot?

    Also, what are your boot mode pins and how are they configured?

    Is your flash already programmed?

    Regards,
    Manoj
  • 0 in reply to Manoj Santha Mohan
    Intellectual 345 points
    Hi Manoj,
    Thanks for your replay!

    The XRS pin has a 2.2K res to 3.3V and a 100nF cap to GND.
    The value on the scope is a constant 200mv. even when trying to program.

    the device is new/programmed.
    Both Boot mode pins where connected with w PU (4.7K).
    after digging in the datasheet i noticed that this may be a problem with programmed devices. so I removed the UP res on PIN0 to get in to wait mode.
    Still cant program the device, same error.

    one more thing, running a connection test in CCS is successful.
    see result:


    [Start: Texas Instruments XDS100v2 USB Debug Probe]

    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\user\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 'jioserdesusb.dll'.
    The library build date was 'Dec 11 2017'.
    The library build time was '12:04:14'.
    The library package version is '7.0.100.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 '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 in reply to Nir Givon
    Intellectual 345 points
    OK, found the problem.

    The PU res on XRS and cap where swapped in assembly.

    Thus the XRS was pulled down...