• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 372 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.

TMS320F28379D: Problems debugging a custom board

Leon Linder
Intellectual 450 points

Part Number: TMS320F28379D
Other Parts Discussed in Thread: LAUNCHXL-F28379D, C2000WARE

Hello all,
I tried to debug a board I created today and I got the following error message:

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 9.4.0.00129)
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_CPU2: 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 9.4.0.00129)
C28xx_CPU2: Error: (Error -1135 @ 0x3FEC52) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.4.0.00129)
C28xx_CPU2: Unable to determine target status after 20 attempts
C28xx_CPU2: 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


On the LaunchXL-f28379D the program works flawlessly and I also checked the JTAG connection via "verify" in the properties and via "Test connection" in the connection settings ccxml. There everything works perfectly. Does anyone have any idea what the error is?

best regards

Leon

  • 0
    Intellectual 450 points

    i found out that it is working on the SYS-CLK with maximum frequency via the line:
    ClkCfgRegs.SYSCLKDIVSEL.bit.PLLSYSCLKDIV = 0;
    must be the problem. The program is not executed on the board unlike the launchpad with the line.
    If I comment out the line I can "debug" the program via SCI output. But the JTAG connection breaks after starting the CPU1 after about 1 second.

  • 0 in reply to Leon Linder
    TI__Mastermind 29921 points

    Hi Leon,

    Leon Linder said:
    On the LaunchXL-f28379D the program works flawlessly and I also checked the JTAG connection via "verify" in the properties and via "Test connection" in the connection settings ccxml. There everything works perfectly.

    Are you saying the JTAG "verify" test works perfectly on your custom board?

    Leon Linder said:
    i found out that it is working on the SYS-CLK with maximum frequency via the line:
    ClkCfgRegs.SYSCLKDIVSEL.bit.PLLSYSCLKDIV = 0;
    must be the problem. The program is not executed on the board unlike the launchpad with the line.
    If I comment out the line I can "debug" the program via SCI output. But the JTAG connection breaks after starting the CPU1 after about 1 second.

    If I understand correctly, the JTAG connection, you feel, is ok, but it is this line of code that is somehow causing the problem? If so, please double check that the PLL configuration is not running the device outside datasheet specifications.

    I would recommend you try one of the C2000ware examples. Since it appears you do have access to the SCI port, you can try the sci_ex3_echoback example. Be sure to modify the DEVICE_SETCLOCK_CFG settings in device.h to match your custom board, i.e. PLL source (INTOSC vs. XTAL), PLL multipliers and dividers.