• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 2021 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 JTAG error, but dbgjtag passes?

Chris Newman
Prodigy 110 points

In what cases would dbgjtag pass and CCS give the following error when connecting?:

CPU_4: Error connecting to the target: (Error -1052 @ 0xDED3) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Release 5.0.333.0)

 

dbgjtag passes all of its tests (integrity, givendata, brokenpath, pathlength returns IR=32bits and DR=4bits).

TDI, TDO, TMS, TCLK, TRST all toggle on the board, and the timing looks reasonable. EMU0 and 1 are always high. I have tried clock frequencies of 100kHz, 1MHz, 5MHz, and 10MHz in CCS, and all give the same result. The DSK5416 evaluation board works fine using the same emulator.

Some more details:

CCS version: 4.2.3.00004
DSP: C5441
Emulator: XDS100v2

I would appreciate any ideas.

Thanks,
Chris

  • 0
    Prodigy 110 points

    Update:

    When I use a target configuration that is set up for a C5416 (instead of C5441 like what is on the board), the debugger connects without any errors, but when I attempt to load a program, I get a message "Data verification failed at address 0x00007F80 Please verify target memory and memory map.", and none of my manual changes to registers or memory values stick.

    What is the importance of which device I select in the Target Configuration? The only visible difference I see in the Debug window is the number of cores.

    The fact that the C5416 configuration connects without errors (and dbgjtag passes) seems to indicate that my hardware is correct, but there is a problem with the C5441 Target Configuration. Is anyone aware of any such problems?

    Chris

     

  • 0 in reply to Chris Newman
    Prodigy 110 points

    I found the answer. The processor CLKIN was not running. I didn't think it would be necessary for the JTAG to connect, so I didn't check it, but apparently it is. dbgjtag doesn't need it, but CCS does.

    Perhaps a future enhancement to dbgjtag could check for this somehow?

    Chris