I'm trying to connect to a TI CC2650 mounted on the TI smartRF06 board. I've pulled the headers to put the board into external debug mode and I'm connecting with a 10-pin cable.
Running
JLinkExe -if jtag -device CC2650F128
I've managed to get it to work about 5 times in about 200 attempts. Below is the output from one of the successful ones and also the output from the most common failure. I've tried two JLinks, 2 cables, 2 different boards and 2 laptops and get the same results. I've tried in Windows and in OSX.
I've found that sometimes setting the speed to 10kHz, resetting the interface to jtag inside JLink and performing a reset with 'r' works, but that's also a very random process, mostly I get the same errors. I've found one test board works slightly more often than another but it's marginal.
Clearly this device is supported and does work but it seems very random and doesn't work way more often than it does. What else can I try here, are there other parameters I can specify to help this along?
This is the output from one of the very few working ones
JLinkExe -if jtag -device CC2650F128
SEGGER J-Link Commander V4.98 ('?' for help)
Compiled Mar 20 2015 18:38:32
Info: Device "CC2650F128" selected.
DLL version V4.98, compiled Mar 20 2015 18:38:24
Firmware: J-Link Lite-Cortex-M V8 compiled Jul 17 2014 11:40:12
Hardware: V8.00
S/N: xxxxxxxxxxx
Feature(s): GDB
VTarget = 3.313V
Info: TotalIRLen = 10, IRPrint = 0x0011
Info: Found Cortex-M3 r2p1, Little endian.
Info: FPUnit: 6 code (BP) slots and 2 literal slots
Info: CoreSight components:
Info: ROMTbl 0 @ E00FF000
Info: ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB000 SCS
Info: ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
Info: ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
Info: ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
Info: ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 003BB923 TPIU-Lite
Found 2 JTAG devices, Total IRLen = 10:
#0 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
#1 Id: 0x8B99A02F, IRLen: 06, IRPrint: 0x1, TI ICEPick
Cortex-M3 identified.
Target interface speed: 100 kHz
However most of the time I'm failing to connect - the most common sequence is something like this
JLinkExe -if jtag -device CC2650F128
SEGGER J-Link Commander V4.98 ('?' for help)
Compiled Mar 20 2015 18:38:32
Info: Device "CC2650F128" selected.
DLL version V4.98, compiled Mar 20 2015 18:38:24
Firmware: J-Link Lite-Cortex-M V8 compiled Jul 17 2014 11:40:12
Hardware: V8.00
S/N: xxxxxxxxxx
Feature(s): GDB
VTarget = 3.306V
****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
Can not connect to target.
Failed to identify target. Trying again with slow (4 kHz) speed.
****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
Can not connect to target.
No device found at all. Selecting JTAG as default target interface.
Running
JLinkExe -if jtag -device CC2650F128
I've managed to get it to work about 5 times in about 200 attempts. Below is the output from one of the successful ones and also the output from the most common failure. I've tried two JLinks, 2 cables, 2 different boards and 2 laptops and get the same results. I've tried in Windows and in OSX.
I've found that sometimes setting the speed to 10kHz, resetting the interface to jtag inside JLink and performing a reset with 'r' works, but that's also a very random process, mostly I get the same errors. I've found one test board works slightly more often than another but it's marginal.
Clearly this device is supported and does work but it seems very random and doesn't work way more often than it does. What else can I try here, are there other parameters I can specify to help this along?
This is the output from one of the very few working ones
JLinkExe -if jtag -device CC2650F128
SEGGER J-Link Commander V4.98 ('?' for help)
Compiled Mar 20 2015 18:38:32
Info: Device "CC2650F128" selected.
DLL version V4.98, compiled Mar 20 2015 18:38:24
Firmware: J-Link Lite-Cortex-M V8 compiled Jul 17 2014 11:40:12
Hardware: V8.00
S/N: xxxxxxxxxxx
Feature(s): GDB
VTarget = 3.313V
Info: TotalIRLen = 10, IRPrint = 0x0011
Info: Found Cortex-M3 r2p1, Little endian.
Info: FPUnit: 6 code (BP) slots and 2 literal slots
Info: CoreSight components:
Info: ROMTbl 0 @ E00FF000
Info: ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB000 SCS
Info: ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
Info: ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
Info: ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
Info: ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 003BB923 TPIU-Lite
Found 2 JTAG devices, Total IRLen = 10:
#0 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
#1 Id: 0x8B99A02F, IRLen: 06, IRPrint: 0x1, TI ICEPick
Cortex-M3 identified.
Target interface speed: 100 kHz
However most of the time I'm failing to connect - the most common sequence is something like this
JLinkExe -if jtag -device CC2650F128
SEGGER J-Link Commander V4.98 ('?' for help)
Compiled Mar 20 2015 18:38:32
Info: Device "CC2650F128" selected.
DLL version V4.98, compiled Mar 20 2015 18:38:24
Firmware: J-Link Lite-Cortex-M V8 compiled Jul 17 2014 11:40:12
Hardware: V8.00
S/N: xxxxxxxxxx
Feature(s): GDB
VTarget = 3.306V
****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
Can not connect to target.
Failed to identify target. Trying again with slow (4 kHz) speed.
****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
Can not connect to target.
No device found at all. Selecting JTAG as default target interface.