[SOLVED] Unable to flash a TI LaunchPad CC2652R1FRGZ

This is a follow up to [SOLVED] LAUNCHXL CC26X2R1 + Code Composer + JLINK EDU MINI unfortunately the thread is closed and I would like to ask the OP how he managed to flash the board, using a JLink. I've removed all jumpers that where not necessary to provide power to the board and connected my J-Trace (using latest SW version V6.72b). JLinkExe just gave similar error messages (trying to reset the board):

Device "CC2652R1F" selected.




Connecting to target via SWD
InitTarget: Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0x3FFFFFFF
InitTarget: Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0x3FFFFFFF
InitTarget: Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0x3FFFFFFF
InitTarget: Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0x3FFFFFFF
InitTarget: Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0x3FFFFFFF
InitTarget: Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0x3FFFFFFF
InitTarget: Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0x3FFFFFFF
InitTarget: Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0x3FFFFFFF


****** Error: InitTarget(): PCode returned with error code -1

I've attached a logic analyzer and at least saw traffic on the SWDIO and SWDCLK lines. Finally, I gave up and installed the TI software to operate the on board debugger, with which is was possible to install firmware on the board, without any problems (after putting the pulled jumpers back in place). I tried the JTrace after using the TI software once more, but without success.

Any idea, what could be wrong here?

Best regards,
Torsten

Hi Fabian,
please find attached a picture from the setup I've used yesterday. I've checked the 3.3V on the connector at the lower left side of the board, I attached the logic analyzer to the TMS and TCK pins on the left connector side.

best regards,
Torsten

Hi Fabian,
looks like this would have been the solution. Haven't tried to flash the firmware, but the JLinkExe is reporting correctly the CoreSights components of the controller. Thank you very much for further looking into this!

best regards,
Torsten