This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1310 & XDS100v3, can't get them to connect

Other Parts Discussed in Thread: CC1310, CC2538

Hello

I'm having some difficulties getting an XDS100v3 debugger and a custom board with a CC1310 to talk to each other. Currently I'm stuck at a point, where CCS will, upon trying "Test Connection" give me this error:

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

So far I have done these things:

- Board is a custom one, with a CC1310F32 on it, using its DC-DC converter.

- Debugger is an XDS100v3 from Embest

- Voltages are correct -> 1.27V on DCOUPL and 1.68V on VDDR

- Circuit is powered by 2xAA batteries (3V in total)

- Bootloader mode works, I can read and program the chip with a simple FT230XS breakout board

- Tried 2-wire cJTAG and 4-wire JTAG modes

- Checked with an oscilloscope, that the TMS and TCK lines have activity and are not stuck

My connections between the debugger and board are GND, 3v3/VTref, TMS, TCK (+ connected RTCK to TCK), I have connected TDIS to ground, and I have connected RESET_N on the chip to nTRST of the debugger. I have tried using nRESET on the debugger, but it does not toggle, it just stays high all the time.

I know the chip works (bootloader), I know the connections between the debugger and chip are solid, I am sure all the pins are soldered well, but it will just not work. Any ideas on what else to try? Unfortunately, I do not have another debugger or an official dev board to test with.

Kind regards,

Wilin

  • Hi,

    Could you test to program the cc1310 with the most up to date smartRF Flash programmer 2, to sort out whether the debugger is defected, or there some issues with CCS configuration (may be drivers).

    Also, you haven't mentioned the OS, is it linux, or windows (MAC????) ?
  • Hello

    Flash Programmer 2 (ver 1.7.2) gives these reults:

    Clicking on the debugger (XDS100 Ver 3.0, XDS-...) gives a popup with error "Selected device was not recognized - Name of the device not defined in device_info.xml: "XDS100 Ver 3.0"". Clicking on the "Unknown" name beneath it gives a "The selected device could not be identified." etc. error message.

    Following this thread: e2e.ti.com/.../425459 , I have modified the device_info.xml file to include my debugger. When I click on it now Flash Programmer 2 it shows a picture of a SmartRF06EB board. But I have no option to select my target chip, and clicking on "Unknown" gives the same error message as before ("The selected device could not be identified"). There is no activity on TMS and TCK when I click on "Unknown"

    Main OS is Windows 10 64-bit, plus Linux Ubuntu 14.04 32-bit for testing.

    Kind regards,
    Wilin
  • Who is the manufacturer of your XDS100v3?
  • Hello

    The manafucturer is Embest. Link to the product page: www.embest-tech.com/.../xds100v3-usb-jtag-emulator.html

    Kind regards,
    Wilin
  • I think it has no support for cortex M3 devices, nor the cJTAG (2 wire jtag)
    Do you have any other XDS100v3, or XDS200 to test with?
  • Hello

    It should support Cortex M3 devices, since Cortex M3 devices are supported by XDS100v2 and XDS100v3. XDS100v3 is also reccomended for cJTAG support. I tried with normal JTAG too, and that did not work either. I do not have access to another to another debugger.

    Kind regards,
    Wilin
  • I agree with Igor. You may try other XDS100v3 such as www.olimex.com/.../
  • Wilin said:
    It should support Cortex M3 devices, since Cortex M3 devices are supported by XDS100v2

    cc1310 is not supported by XDS100v2.

    Wilin said:
    XDS100v3 is also reccomended for cJTAG support

    Several XDS100v3 won't work with cc1310

    Wilin said:
    I tried with normal JTAG too, and that did not work either

    Do elaborate, what is this "normal JTAG"?

  • Igor Sherer said:

    Wilin
    It should support Cortex M3 devices, since Cortex M3 devices are supported by XDS100v2

    cc1310 is not supported by XDS100v2.

    Fair enough, though the original comment said Cortex M3, not CC1310 specifically.

    Igor Sherer said:
    Wilin
    XDS100v3 is also reccomended for cJTAG support

    Several XDS100v3 won't work with cc1310

    A link would be appreciated. If this is a common problem, it should be clearly written that not all XDS100v3's are supported.

    Igor Sherer said:
    Wilin
    I tried with normal JTAG too, and that did not work either

    Do elaborate, what is this "normal JTAG"?

    My mistake, I meant "Generate 1149.7 4-pin standard mode", as described in CCS.

  • Wilin said:
    A link would be appreciated. If this is a common problem, it should be clearly written that not all XDS100v3's are supported.

    I have no specific link, I'm telling you this from my own experience, I had two different XDS100v3 (can't recall brand names), for one I had to

    update the FW so it could recognize TI's cortex M3 devices (cc2538...), the other one was especially useful for elevating a bit my custom boards when I was programming cc2538 SoCs with smartRF06EB.

    Wilin said:
    My mistake, I meant "Generate 1149.7 4-pin standard mode", as described in CCS

    I strongly recommend you to purchase additional XDS100v3, see this link, and this one for more info

  • SUCCESS!

    Turns out, it was the XDS100v3 at fault, and an FPGA update fixed it. The XDS100v3 from Embest, that I have, does not use the Actel ProASIC3 A3P125 that is in the design files. Instead, it uses the newer A3PN125. That meant that upgrading the FPGA firmware was non-trivial, as the firmware supplied in the XDS100v3 design files is not compatible (xds100v3_progfpga.exe will complain with "Failed to verify IDCODE"). I went through the procedure to generate the file again (note, use Libero IDE 9.1, and not 9.2 because it won't work), selecting the newer A3PN125 FPGA in the process. After generating the update file, I used xds100v3_progfpga.exe to load it onto the FPGA. The process was not exactly smooth, with the tool complaining a few times with "Unable to program UROW". I suspect some FTDI weirdness, as the tool succeeded after I connected the debugger to my Linux VM and back again.

    Now debugging works in CCS, and SmartRF auto-detects and reads the CC1310.

    For anyone having problems with XDS100v3 and cJTAG or programming/debugging or connection problems with CC13xx and CC26xx chips, update the FPGA firmware. I have attached the file, necessary for the A3PN125 FPGA, and you can get the one for the "old" A3P125 FPGA in the design files.

    Kind regards,

    Wilin

    dtsa_a3PN125.zip

  • I have the same problem as you faced
    my xds100V3 is from olimex
    I will try your solution
  • I have a custom board I just built with an CC1310 on board. I am using the sensortag debug devpack www.ti.com/.../cc-devpack-debug
    $15! to flash and debug with no problems.
  • I have bought 2 TI debugger devpack to see if I would be luky
    but no it doesn't function
    error msg : with "subpath " problem
    but in the meantime I have solved the problem with the XDS100V3 : solution was not to upgrade the fpga from my olimex xds100V3 but to change from TI jtag 20 pins connector to the arm jtag 20 pins connector ( I can't find any explanation )

    we have also a smartrf06 on which our CC1310 custom circuit doesn't connect ( error msg concerning jumpers )

    Mark could you send me the connections of your board to the devpack ?

    in conclusion : with a custom cc1310 based circuit only 1 interface is ok on 3
  • This is the schematic at my 10pin JTAG connector. I think I have seen that subpath message before, I cant remember why now. I'll let you know if I see it again...

  • thanks for your post .it solved the problem with the devpack 

    pin 1 on the TI devpack schematic has no connection to VDDS 

    when I did it according your schematic it worked !

    next step is to understand the smartrf06 board problem

  • Igor, 

    Igor Sherer said:

    cc1310 is not supported by XDS100v2.

    Can you provide some more information on this? I'm working on a Senior Design project at my university, and we chose the XDS100v2 to use with our CC1310 because the v2 supports Cortex M3 devices. Is there any reason it shouldn't work with the CC1310? 

    Thanks,

    Matt

  • You can only use XDS100v3 or XDS110 to program or debug CC1310.