Obtaining PID, VID
Fujmon
Posts: 4
Just installed MacBS2 on my PowerBook, but initially could not find the BOE Rev B (USB) board. I dug around, and found a work-around that involves installing an older version of FTDIUSBSerialDriver. After installing, system recognizes a new network port, but MacBS2 cannot access it.
So, i am logging into root to /Library/StartupItems/FTDIReEnumerate to edit the FTDIReEnumerate file, but need to reassign the vendorID (VID) and productID (PID). Where do I find this information? Will that information be in hex, or must i convert the dec number into hex before insertion into the line of text within aforementioned file?
gary
So, i am logging into root to /Library/StartupItems/FTDIReEnumerate to edit the FTDIReEnumerate file, but need to reassign the vendorID (VID) and productID (PID). Where do I find this information? Will that information be in hex, or must i convert the dec number into hex before insertion into the line of text within aforementioned file?
gary
Comments
For your reference, here's the contents of my FTDIReEnumerate:
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
OS-X: because making Unix user-friendly was easier than debugging Windows
System Preferences discovered the new network connection, but the Network Status dropdown shows that usbserial-181 "is configured, but is not connected"
The documentation that comes with MacBS2 identifies the problem, and offeres the modification of the FTDIReEnumerate file. I just need to know what my BOE Rev B (that has a BS2 Rev G chip) board's PID and VID numbers are...
gary
I'm not 100% sure the PID/VID is the issue. I'm successfully using both my Parallax USB/Serial adapter and the built-in USB port on my Professional Development Board with the PID and VID I posted earlier.
Here are a couple other things to look for:
If you go to System Preferences -> Network and select Show: Network Port Configurations you shouldn't have the usbserial-XXXX driver checked.
Run terminal and go to the /dev directory. Enter the command "ls cu.*". Do you see an entry for cu.usbserial-XXXX? There should also be a "tty.usbserial-XXXX" if you enter the command "ls tty.*".
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
OS-X: because making Unix user-friendly was easier than debugging Windows