Previous we have been bringing our software up using LAUNCHXL F280049C with DRV8323XR and the debugging from CCS has been rock solid.
Now we have our own PCB and we are using XD110 DEBUG PROBE.
The debugger connection is not reliable anymore.
Sometimes it works for 10 minutes, sometimes it fails in seconds, mostly it fails within a few minutes.
First symptom of the trouble is that we get:
IcePick_C_0: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.4.0.00129)
</code>
Then some more (it varies) :
<code>
IcePick_C_0: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.4.0.00129)
IcePick_C_0: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.4.0.00129)
</code>
And finally CCS gives up (and stops the target which is a pain when debugging hardware).
<code>
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
</code>
At this point clicking the cute little bug icon re-flashes the code and everything works until it fails again.
Due to space constraints in our setup we have extended the two JTAG flat cables to double the original length (as supplied with XDS110 DEBUG PROBE).
Could this be an issue?
Other than using the original cables is there any other way try to solve this?
Can the JTAG speed be reduced, if so, how?
wbr Kusti
