![]() ![]() ![]() FTDI chips will each have unique entries here. There is also a /dev/serial/by-id but there will only be one entry there for this device because it shows the last one connected. If you're using linux you can find each device under /dev/serial/by-path. First and easiest is the position of the device on the USB bus. I have been trying to find solutions for this problem. This is also a problem for the PL2303 type. There is no storage on the CH340 and family of UARTs where you could put a unique ID. Which is essentially useless, as I can't identify the given board attached (when I attach two, their details are the same). ![]() usb 2-1.2: ch341-uart converter now attached to ttyUSB0 usb 2-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 2-1.2: New USB device found, idVendor=1a86, idProduct=7523 Does anyone know of an alternative utility/where I can find information to do the same with this chip?Ĭurrently the device identifies itself with: usb 2-1.2: new full-speed USB device number 7 using ehci-pci I have a nano-style boad with a QinHeng Electronics HL-340 USB-Serial adapter, which clearly isn't an FTDI chip, and the FTDI programmer therefore doesn't work. Reading there appears to be a way to write out to a FTDI USB-Serial EEPROM to set a given SerialNumber, allowing you to identify a given nano/other arduino to handle it specifically in UDEV. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |