I first installed the ARM-USB-TINY-H under my Windows and it installed fine.
Now afterwards I run it in Ubuntu 16.04 and it seems the VID and PID are overwritten.
When I do a lsbusb I get:
Bus 006 Device 011: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
And with a lsusb -v I get:
Bus 006 Device 009: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0x6001 FT232 USB-Serial (UART) IC
bcdDevice 6.00
iManufacturer 1 FTDI
iProduct 2 TTL232R-3V3
iSerial 3 FT97MPM7
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 90mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 TTL232R-3V3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
Afterwards I plugged it back in my Windows system, and it seems that now there as well it is detected as a FTDI and not anymore with the Olimex VID and PID.
Is there a way to restore this to the Olimex VID and PID?
Under Linux mine shows as idVendor=15ba, idProduct=002a
Looks like Windows has reprogrammed it - kinda surprising if true!
John
No problem to restore this information. Page 22 of this documents gives details on the procedure: https://www.olimex.com/Products/ARM/JTAG/_resources/ARM-USB-TINY_and_TINY_H_manual.pdf
The VID and PID for each Olimex OpenOCD debugger might be found at the bottom of page 7.
Best regards,
Lub/OLIMEX
Any idea to how/why this could have happened?
See post #2
John