Hi all, So, on Friday I had a whoopsie moment with the Olimex XDS100v3 clone JTAG probe I was using -- and managed to blow it up (let's say, the FPGA it uses is not 24V-tolerant on its GPIO pins), and needed to quickly replace it with something.
The XDS100v3 probes were out of stock everywhere, but a quick Google search for "XDS110" brought up these: https://au.mouser.com/ProductDetail/Texas-Instruments/CC-DEBUGGER?qs=O3wcJz4o8Id%2FMa87rj4LcA%3D%3D&mgh=1&vip=1&gclid=EAIaIQobChMI7u3gqKGH_AIVVH8rCh3dCwzoEAQYASABEgI_jvD_BwE In stock, and not expensive. Plus, the debugger itself was "encased" meaning it was likely safe from future +24V accidents. Thinking I was buying XDS110s, I bought two (the XDS100v3 belongs to work). Turns out, no, these are not XDS110s. TI's Uniflash refuses to look at them too. Question is though, has anyone successfully used one of these probes with OpenOCD, and if so, what config does one use? Identification when plugged in (super-imaginative Mfr/Product/SerialNumber): > [1065747.591030] usb 1-7: new full-speed USB device number 100 using xhci_hcd > [1065747.920375] usb 1-7: New USB device found, idVendor=0451, > idProduct=16a2, bcdDevice= 4.86 > [1065747.920385] usb 1-7: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [1065747.920389] usb 1-7: Product: CC Debugger > [1065747.920392] usb 1-7: Manufacturer: Texas Instruments > [1065747.920395] usb 1-7: SerialNumber: 00010486 > [1065748.325115] usb 1-7: USB disconnect, device number 100 It looks as if the device has full schematics, so maybe flashing its microcontroller (CC2511) with alternate firmware is not out of the question. The end game here is debugging and flashing TI CC2538 chips -- and this is basically done exclusively under Linux. (I can wrustle up a Windows 7 box to temporarily update something, but will not be using Windows in any capacity in day-to-day operations.) Regards, -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
