Custom CC2650 PCB not recognized by programmers

DanielB

Other Parts Discussed in Thread: CC2650, UNIFLASH

Hi, I have designed a custom PCB with a CC2650 on it. It is based on the Sensortag an other reference designs, the CC2650 part is rather standard, except that I do not use a 32KHz crystal. This is the schematic:

The problem is that the CC2650 is not recognized by programmers. I tried using a XDS100V3 and the debug devpack from the sensortag, both give error 275: JTAG timed out. I checked the DCOUPL, VDDS and VDDR voltages, they are all as they should be. The current draw of the processor with no programmer attached is also 5-7mA, as it should be (probably the bootloader). Does anyone have a clue on what is going on?

Thanks,

Daniël

over 10 years ago

0 CHS over 10 years ago

TI__Mastermind 18780 points

Have you checked this wiki: processors.wiki.ti.com/.../CC26xx_HW_Troubleshooting

can you post a picture of the layout?

0 DanielB over 10 years ago in reply to CHS

Prodigy 90 points

Hi Charlotte, thank you for the reference, I had not found that one yet. I'm however afraid that it does not solve my issue, the steps described there are pretty much what I already checked.

0 DanielB over 10 years ago

Prodigy 90 points

0 Juan David Rios Ruiz over 10 years ago in reply to DanielB

Prodigy 20 points

How are you connecting the custom PCB to the programmer? Make sure this is the configuration you are using :

If you are using the connections of your PCB directly (via a 2x5 connector) in the JTAG interface of the debugger/programmer it won't work because it is not the expected one.

0 DanielB over 10 years ago in reply to Juan David Rios Ruiz

Prodigy 90 points

I am using a TC-2050 connector, so the pin numbering is indeed different than for a standard pin header (a pin header is per row, so: 1,2-3,4-etc, while the tag connect is on one side 1,2,3,4,5-6,7,8,9,10). You can check it in the schematic.

0 CHS over 10 years ago in reply to DanielB

TI__Mastermind 18780 points

sounds strange, your design looks fine. Have you tested more than one board?

0 DanielB over 10 years ago in reply to CHS

Prodigy 90 points

I have, they all show the same behaviour. I'm also out of ideas here. It will probably turn out to be something stupid, but I don't know what.

0 DanielB over 10 years ago in reply to DanielB

Prodigy 90 points

I researched this issue a bit further. Using the debug devpack (an XDS110 programmer) I now also connected the TDI and TDO lines. This works: the CC2650 on the PCB is recognised and can be read. With the XDS100V3 however, where the TDI and TDO are also connected, I still get the timed out error. I did some measurements with an oscilloscope, and on the XDS100 there is no data visible on the TDO line, the device does not send any data back. With the XDS110 there is data visible on the TDO line. What could be the problem here, how can I solve this? The XDS100 is a lot more convenient to use as a standalone programmer.

0 CHS over 10 years ago in reply to DanielB

TI__Mastermind 18780 points

I will check if our tools department can share some more insight on your observation.

0 TIABO over 10 years ago in reply to DanielB

TI__Genius 12900 points

Daniel,

What software are you using? What error message do you get?

If you are using IAR EWARM or CCS: Make sure you correctly configure the IDEs to use the correct emulator.

Br,
TIABO

0 DanielB over 10 years ago in reply to TIABO

Prodigy 90 points

Hi, I'm using flash programmer 2, which just says that the target isn't recognized, and CCS uniflash which gives the timed out error.

0 TIABO over 10 years ago in reply to DanielB

TI__Genius 12900 points

To get furhter, I need to know what error the XDS drivers give you. You can get it in CCS: Create a new Target connection file (XDS100v3 + CC2650) and run "Test connection". I'm interested in the error message you get.

0 DanielB over 10 years ago in reply to TIABO

Prodigy 90 points

The exact error I get is 275: JTAG timed out. I don't get any further hints on what the problem can be.

0 TIABO over 10 years ago in reply to DanielB

TI__Genius 12900 points

Hmm, does the XDS100v3 show up correctly in the Windows Device Manager?

The XDS100v3 works with other boards, just not with your PCB?

0 DanielB over 10 years ago in reply to TIABO

Prodigy 90 points

It shows up correctly. I don't know whether it works correctly with other boards, I only have this one.

0 TIABO over 10 years ago in reply to DanielB

TI__Genius 12900 points

Based on what you are saying, the device appears to be alive, but for some reason it's not detected by the emulators. I'm looking into what can give error 275. You said you have a CC Devpack -- do you have a SensorTag from TI that you can debug using the devpack?

0 Edward Fewell over 10 years ago in reply to TIABO

TI__Intellectual 2515 points

Error -275 on an XDS100v3 usually means that a command was issued to the device's ICEPick to add or remove a core from the scan chain, and the ICEPick failed to respond to the request within a certain retry count.

This is often when the configuration is wrong, or the TCK setting is too high, or the JTAG is otherwise not working reliably. The first thing to check would be to see what's the result from the Test Connection output in CCS. Do that and post the entire results here.

Bluetooth®︎

Bluetooth forum

Custom CC2650 PCB not recognized by programmers