• Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1832 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Debugger DEVPACK 1.2.0 JTAG and CC2650 Flash SPI Pin Issue

Xianlin Song
Prodigy 80 points
Other Parts Discussed in Thread: CC2650

You will run into the clash/issue if using 1.2.0 version of Debugger DevPack JTAG and try to debug your sensor tag running program communicating with SPI pin to external flash on the tag.

Explained here:

http://43oh.com/2015/08/a-warning-on-jtag-debugging-and-the-sensortag-flash-chip/

Any suggestions or walk around?

Change to use SMARTRF06EB board and hack the pin P408 on the board as some post suggested? The SmartRF06EB will NOT clash with SPI pin when debugging using JTAG?

Thanks

  • Guru 16361 points

    I don't have anything to suggest that will work right now, but I think the issue will go away once the XDS110 drivers are updated to support cJTAG (like the XDS100).

    That will allow programming and debugging with just the TCK/TMS lines, leaving DP8 free for use as the SPI SCLK.

  • in reply to Robert Cowsill
    Prodigy 80 points

    OK now I understand, if update the XDS110 firmware to support 2-pin C-JTAG standard then the SPI pin which is also a TDI pin used by 4-pin JTAG standard will be used ONLY by CC2650, not debug devpack anymore.

  • Prodigy 80 points

    While waiting for the fix of this debug issue, I have disabled the cc26xx-web-demo code to read/write to the flash so you can use DevPack USB to see the debug output.

    1. In cc26xx-web-demo.c comment out load_config() at 890 line number.
    2. In contiki/apps/mqtt/mqtt.h line 125, enable debug mode by change DEBUG_MQTT to 1.

    Compile and flash to the sensortag and open your Tera Term software to observe the MQTT debug information, Don’t forget to change your peer route IPv6 address to the current updated address(e.g. used by your PC) in your 6lbr router web config page.

    This way you can debug the code but NOT able to read/write flash memory.

  • Guru 16361 points

    Apparently this conflict has been fixed in the latest XDS110 firmware:

    Debug DevPack XDS110 firmware 2.3.0.1 fixes CC2650STK SPI (external flash / Watch DevPack) conflict

    I've not tried it myself yet, so I don't know whether 2-pin cJTAG is the default option or needs to be selected manually. Either way, when using 2-pig cJTAG the devpack no longer drives the TDO pin, which was causing the flash to be inaccessible.

    EDIT: I've updated the "TI Emulators" in CCS to 6.0.228.0, and debugging in cJTAG mode is the new default for XDS110. I've been able to debug and access the SPI flash without issues. I had some trouble with the UART backchannel dropping the data transmitted from the target, but that seems to have resolved itself for now.

  • in reply to Robert Cowsill
    Prodigy 90 points

    hey,

    I successfully updated my debugger to 2.3.0.1. but when I try to debug without TDI/TDO the error 254 occurs which says that a router subpath could not be accessed. do I have to change any other settings to make a 2pin jtag debugging work? (ti emulation package 6.0.228.0)