> It's a nightmare to guess the serial port and have to
> pass it to your software every time you start it up. My system goes up
> to ttyACM5 and ttyUSB12.
[...]
> Enumeration with FTDI is very easy, you just locate your VID/PID and if
> there are two or more devices of such, you'll let user choose one.
I also think that USB serial port enumeration is not such a big deal. As an
alternative to coding some VID/PID search logic in your client tool, the user
can always write a small UDEV rule file so that a link to his particular device
always gets created with the same filename. For example, this is an excerpt
from some doc I recently wrote:
---------8<---------8<---------8<---------
In order to get a fixed /dev/jtagdue1 device name, create a new file called
/etc/udev/rules.d/47-JtagDue.rules (as root) with the following content:
SUBSYSTEM=="tty" ATTRS{idVendor}=="2341" ATTRS{idProduct}=="1234"
ATTRS{serial}=="JtagDue1" MODE="0666" SYMLINK+="jtagdue1"
---------8<---------8<---------8<---------
I haven't found yet a nice and easy GUI to do that, but writing the small file
by hand should not take long.
Regards,
rdiez
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
