• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 274 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.

TMS320F28377S: Debug Error Problem

er_kolt
Prodigy 80 points
Part Number: TMS320F28377S
Other Parts Discussed in Thread: C2000WARE, CONTROLSUITE

Hi TI experts,

I use TMS320F28377S for my project. It suddenly crashes during debug. Code Composer Studio gives this error:

C28xx_CPU1: Error: (Error -1135 @ 0x828ED) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.27.9)
C28xx_CPU1: Trouble Halting Target CPU: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.27.9)
C28xx_CPU1: Error: (Error -1135 @ 0x828ED) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.27.9)
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

This error occurs at a random time after the debug starts.

I tried my project code and example code and I got an error in both cases.

I tried the microprocessor in get mode and wait mode. I got an error in both cases.

I tried lowering the debug speed. I got error again.

I use Code Composer Studio 9.0.0, My emulator is XDS110

i have no idea how to do next. please help. thanks.

  • 0
    TI__Guru 50440 points

    Hi,

    Are you using TI EVM or it is your custom board? You have tried the examples from C2000Ware Driverlib ?

    Can you open the target configuration and run "Test Connection" and send the log?

  • 0 in reply to Santosh Jha
    Prodigy 80 points

    I using custom board. The file location of the example I tried: C:\ti\controlSUITE\device_support\F2837xS\v210\F2837xS_examples_Cpu1

    I sharing test connection log:

    [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\erdogan\AppData\Local\TEXASI~1\ CCS\ccs900\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 'Mar 13 2019'. The library build time was '21:38:07'. The library package version is '8.1.0.00005'. 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]

  • 0 in reply to er_kolt
    TI__Guru 50440 points

    Hi,

    Thanks for sending the log, looks like target configuration is set correct.

    Is this new board and you are trying first time to connect? What is the boot mode you are using? Try to set in "Wait boot mode"?

    The error code '-1135' is explained in this page. This page also has links to some useful e2e thread which may help you in debugging.

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#c28x-the-debug-probe-reported-an-error

    Another thing to try:

    - Launch target configuration manually. Open the 'Target Configuration Window' (CCS menu View -> Target Configuration). Select the target configuration, right-click and launch.

    - Connect CPU1 now, do you get same error code?

    Is it possible to install latest CCS and emulator package?

  • 0 in reply to Santosh Jha
    Prodigy 80 points

    Hi,

    Yes it is a new board. I've been connecting for one week and I often encounter this error. I tried wait mode but it didn't solve my problem.

    Thank you for the link you shared. I will review.

    I tried launch target configuration manually. I encountered this situation. I could not connect.

    I can install latest CCS but I only have one type of emulator.

    Thanks for your replies.

  • 0 in reply to er_kolt
    TI__Guru 50440 points

    Hi,

    The PC (0x3FF16A)  is in BootROM and trying to boot.

    Can you try to put it in Wait-Boot mode, and then connect?

  • 0 in reply to Santosh Jha
    Prodigy 80 points

    Hi,

    I configurated gpio72 and gpio84 to be in wait mode according to the this table. I also measured these pins. I saw that GPIO72 is high and GPIO84 is low. The pull up and pull down resistors of these pins are 10k.

  • 0 in reply to er_kolt
    TI__Guru 50440 points

    Hi,

    After setting into "Wait Boot mode", the where is PC when you connect?

    I will recommend one more time to go through this page for debugging tips:

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#c28x-the-debug-probe-reported-an-error