• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 15 subscribers
  • Views 1456 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.

Strange XDS100 v3 driver behaviour

Henrik Sandaker Palm
Intellectual 975 points
Other Parts Discussed in Thread: CC1310

It's hard to describe exactly what I did before my two SmartRF06 boards stopped being recognized as debuggers, but I remember upgrading firmware in SmartRF Programmer v2 (I think this was on the CC1310 launchpad , though), and having several CC1310 in bootloader connected via FTDI vcp chip.

Status right now:
- Both SmartRF06 Evaulation boards only shows up as "USB Serial Converter" in device manager. If I tick "Load VCP" in its properties a virtual COM port also shows.
- No XDS100v3 debugger showing in Device Manager
- I actually had a CC1310 with FTDI vcp chip show up as Texas Instruments XDS110 debugger when connected via serial bootloader. How can this happen? 

But how do I restore my SmartRF06 evaluation boards?

  • 0
    Intellectual 975 points



    For some reason, if I wipe all drivers assigned to VID 0403 and PID 6015 and power cycle the SmartRF06 it shows up as two driverless FT231X USB UART converters. AFAIK the FT231x has nothing to do with the FT2232D that's on the SmartRF06? Anyway, FT231x is what I use on my own hardware, have I somehow tricked windows into thinking all FTDI should use these new drivers?

    It only shows up like in the image above for 5 seconds before windows goes about and re-installs the drivers I just uninstalled. After that the SmartRF06 appears as USB Serial Converter and USB Serial Port in device manager.

  • 0 in reply to Henrik Sandaker Palm
    Intellectual 975 points

    Finally I managed to solve this. Somehow I had managed to swap the Product ID of the FTDI controller to the default 0x6050 which made windows load the generic USB VCP drivers. On both Eval boards. This may have happened while developing another product using FT231x chip and lots of other FTDI tools installed.

    The text in SmartRF06 Eval Board manual SWRU321A tipped me: The TI XDS100v3 USB VID is 0x0403 and the PID is 0xA6D1. Using FTDI's programming tool FT_PROG I managed to swap it back to the TI product ID, and the correct drivers loaded.