Hello,
I am working with a custom built board using the TI CC2650 SoC for my bachelor thesis and currently try to debug the firmware (based on TI-RTOS) using J-Link EDU V10.1 with IAR Embedded Workbench 8.10.1. Previously we worked with the TI XDS100v3 debugger wich mostly worked out but now, using the J-Link EDU, different errors occur while downloading and debugging the firmware.
They occur kind of randomly and it's not always the same error. Also, sometimes after power cycling the debugger and the board or after waiting a couple of time before restarting the debugging session, it will work out, only to fail again on the next attempt.
This are the different errors:
1.
Fatal error: Device specific connect: Can not find CPU TAP (IDCODE mismatch)
2.
Communication timed out: Requested 2 bytes, received 0 bytes !
Could not transfer JTAG data.
Device specific connect: Can not find CPU TAP (IDCODE mismatch)
3.
Communication timed out !
Could not read speed info.
Could not transfer JTAG data.
Device specific connect: Can not find CPU TAP (IDCODE mismatch)
4.
Communication timed out: Requested 8 bytes, received 0 bytes !
Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command:10) @ Off 0x5.
5.
Communication timed out !
Could not transfer JTAG data.
6.
Communication timed out !
Could not transfer JTAG data.
Device specific connect: Can not find CPU TAP (IDCODE mismatch)
Here are some more detailled debug logs:
Example for 4:
pastebin.com/Ve6AGjZm
Example for 5:
pastebin.com/2VFMySaf
Example for 6:
pastebin.com/6KLPXCaM
Working example:
pastebin.com/SK7UYV1d
What could be the reason for these errors? It seems to be a failure in the JTAG connection and/or the reset of the device.
I think the signal connections are all correct and the settings in IAR too.
Thank you for any help and have a nice day,
Enno Sievers
I am working with a custom built board using the TI CC2650 SoC for my bachelor thesis and currently try to debug the firmware (based on TI-RTOS) using J-Link EDU V10.1 with IAR Embedded Workbench 8.10.1. Previously we worked with the TI XDS100v3 debugger wich mostly worked out but now, using the J-Link EDU, different errors occur while downloading and debugging the firmware.
They occur kind of randomly and it's not always the same error. Also, sometimes after power cycling the debugger and the board or after waiting a couple of time before restarting the debugging session, it will work out, only to fail again on the next attempt.
This are the different errors:
1.
Fatal error: Device specific connect: Can not find CPU TAP (IDCODE mismatch)
2.
Communication timed out: Requested 2 bytes, received 0 bytes !
Could not transfer JTAG data.
Device specific connect: Can not find CPU TAP (IDCODE mismatch)
3.
Communication timed out !
Could not read speed info.
Could not transfer JTAG data.
Device specific connect: Can not find CPU TAP (IDCODE mismatch)
4.
Communication timed out: Requested 8 bytes, received 0 bytes !
Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command:10) @ Off 0x5.
5.
Communication timed out !
Could not transfer JTAG data.
6.
Communication timed out !
Could not transfer JTAG data.
Device specific connect: Can not find CPU TAP (IDCODE mismatch)
Here are some more detailled debug logs:
Example for 4:
pastebin.com/Ve6AGjZm
Example for 5:
pastebin.com/2VFMySaf
Example for 6:
pastebin.com/6KLPXCaM
Working example:
pastebin.com/SK7UYV1d
What could be the reason for these errors? It seems to be a failure in the JTAG connection and/or the reset of the device.
I think the signal connections are all correct and the settings in IAR too.
Thank you for any help and have a nice day,
Enno Sievers