• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 303 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28388S: Debug error(C28xx_CPU1: Error: (Error -1044 @ 0x0)

Jay
Prodigy 50 points
Part Number: TMS320F28388S


Tool/software:

C28xx_CPU1: Error: (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 12.7.0.00105)

C28xx_CPU1: Trouble Halting Target CPU: (Error -1135 @ 0xC7BA) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 12.7.0.00105)

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

What’s strange is that debugging works fine for about 1 minute, and then this issue occurs.
If the debugger failed immediately, I might have suspected a hardware issue, but since it runs fine for a while, that seems less likely.

Additional context:

I’ve been using the same board and XDS110 probe without any problems for over a week.

To isolate the cause, I even tested with an empty main() function, but the same issue still occurs after 50–60 seconds.

I’m using RAM-based .cmd linker file, not Flash.

I'm only using CPU1, not CPU2 or the CM core.

Debug connection shows only C28xx_CPU1 (Running); the other cores are disconnected, by design.


Could this be caused by a misconfiguration or missing setting (e.g., JTAG pin conflict, watchdog, or clock settings)?
Are there any known issues or debug timeout settings that might cause this behavior?

Any guidance or suggestions would be appreciated.

Thank you!

  • 0
    TI__Mastermind 36526 points

    Hi,

    Could you please see this app note? https://www.ti.com/lit/pdf/spracf0

    My recommendations:

    1. Power cycle the MCU

    2. Follow the steps for manual launch (found in app note) to connect to the MCU without loading any code

    3. Does the issue still occur? 

    Thanks,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 50 points

    Hello.
    Even though I tried all the suggested procedures, it still fails.
    However, I replaced the PCB and confirmed that it works normally.
    There is no problem with the power or OSC of the PCB. I don't think the 28388S chip can suddenly fail.
    Is there a possibility that the problem occurs because the wrong ROM is loaded into the FLASH?
    If so, please tell me how to initialize this 28388S Chip.

  • 0 in reply to Jay
    TI__Mastermind 36526 points

    Hi,

    So you have already flashed this 28388S chip? In that case, please try to repeat the above steps, but put the device in wait-boot mode.

    You can certainly flash the chip in a way that will prevent JTAG connections while executing the flashed program. Putting the device in wait-boot mode will prevent it from running the flashed program and will generally allow for a connection to be established.

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 50 points

    Thanks for the answer.
    But this wasn't the cause either.
    I tested the PCB in various ways and the disconnection time is different, so I think it's a difference in HW.
    There was no problem with the clock waveform. Is there a required current specification?
    I use the 7 pins below by connecting them separately to the XDS110.
    Is there anything I need to improve?

    3.3V
    JTAG_TMS
    JTAG_TCK
    JTAG_TDO
    JTAG_TDI
    JTAG_TRSTN
    GND

  • 0 in reply to Jay
    TI__Mastermind 36526 points

    Hi,

    Did you make sure that the flash is erased? 

    Are there any sources of noise?

    Thanks,

    Ben Collier