How to remap /dev/ttyUSB* to a specific name to be called by my program.

How to map /dev/ttyUSB* to specific device.

ref: How can I match a ttyUSBX device to a usb serial device

ref: http://unix.stackexchange.com/questions/81754/how-can-i-match-a-ttyusbx-device-to-a-usb-serial-device

ref: http://ubuntuforums.org/showthread.php?t=168221and : http://unix.stackexchange.com/questions/64266/putty-can-access-serial-port-as-dev-ttyusb0-but-not-as-named-udev-device

Quickly Reference/Steps:

Brief Steps:

1. Command:

   >> lsusb

   This lists your usb devices and "067b:2303",for instance, as its ID

   or:

   >> ls -l /sys/bus/usb-serial/devices

   An other locations worth exploring are /sys/class/tty/

2. Write this to /etc/udev/rules.d/50-usb.rules

  ----

   SUBSYSTEM=="tty", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0031", SYMLINK+="ONDA"

   SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14ac", SYMLINK+="HUAWEI"

  ----

   Reboot.

   Now you can use /dev/ONDA to get to your ONDA device.

   If you want non-root users to be able to use these, then add

  ----

   , MODE="0666"

  ----

   to the end of each line.

3. To get enough information to distinguish the devices try something like this for all devices:

   Command:

   >>

    $ udevadm info --query all -name /dev/ttyUSB0 --attribute-walk

4. To start using these new rules, you need to run the command udevstart

   Command:

   >> sudo udevstart

   You can also restart udev using

   Command:

   >> sudo /etc/init.d/udev restart    #you may need to reboot if this doesn't work.

5. Command:

   >> 

Create your own udev rules to control removable devices

I'm sure many people who use removable devices have noticed that sometimes they don't appear where they were before.



You plug your USB drive in, and use fdisk to find the device node and then mount it. Sometimes the USB appears as /dev/sda1, sometimes /dev/sdb1. It can depend on what order you plug in your USB devices, and where you plug them in. This is a real pain if you
mount devices manually or if you are trying to customise your /etc/fstab.



udev allows the assignment of a persistant device node, /dev/..., based on a rule match defined by your specific hardware. In other words, if a device
is attached that matches certain criteria it is given it's own device node, rather than being assigned a dynamic one.



It's actually really easy to setup.

To start with you need to know the dynamic device node that is given to a device when attached for the first time. The way that I would do this is to use thetail command

tail -f /var/log/messages

When a device is plugged in, the screen will update with the newest messages, usually imparting some knowledge on the location of the new device. My USB flash disc for example, produced this output when plugged in.

The output shows that the USB device attached is assigned the device node
/dev/sdd. You may also want to determine the partition number using

sudo fdisk -l

For my USB flash disc, the partition is /dev/sdd1.



So next thing is to find out some unique information from the device, information that will be used in defining the udev rule, remembering a match is required to assign the persistant node. The next command I have used is from theWriting
udev rules link at the bottom of this HOWTO

udevinfo -a -p $(udevinfo -q path -n /dev/sdd)

This command outputs a lot information about the hardware associated with
/dev/sdd. I've left out a lot of the information, leaving only the section I think is most relevant. This section contains the more specific information about my USB flash disc.



Note the bolded text in the output. It is important that information used in a udev rule is contained in the one section.

udevinfo starts with the device the node belongs to and then walks up the

device chain, to print for every device found, all possibly useful attributes

in the udev key format.

Only attributes within one device section may be used together in one rule,

to match the device for which the node will be created.

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:02.0/usb1/1-3':

    BUS=="usb"

    ID=="1-3"

    DRIVER=="usb"

    SYSFS{bConfigurationValue}=="1"

    SYSFS{bDeviceClass}=="00"

    SYSFS{bDeviceProtocol}=="00"

    SYSFS{bDeviceSubClass}=="00"

    SYSFS{bMaxPower}=="100mA"

    SYSFS{bNumConfigurations}=="1"

    SYSFS{bNumInterfaces}==" 1"

    SYSFS{bcdDevice}=="0100"

    SYSFS{bmAttributes}=="80"

    SYSFS{configuration}==""

    SYSFS{devnum}=="6"

    SYSFS{idProduct}=="0005"

    SYSFS{idVendor}=="0c76"

    SYSFS{maxchild}=="0"

    SYSFS{product}=="TS128MJFLASHA"

    SYSFS{speed}=="12"

    SYSFS{version}==" 1.10"

The items that contain specific information regarding my USB disc have been coloured red. These are the two items of interest to me, the device is connected to theUSB bus, and the product is identified byTS128MJFLASHA

______



The next step is to create the udev rule concerning this device. I'll start by creating my own .rules file

sudo nano /etc/udev/rules.d/10-local.rules

By naming my set of rules 10-local.rules they should be looked at before the other rules set in this folder.



The rule I will use for the flash disc looks like this.

A quick explanation.



- The BUS==”usb” and SYSFS{product}==”TS128MJFLASHA” options are the same as those I picked out from theudevinfo output.



- The option KERNEL="sd?1" will only match locations like /dev/sda1, /dev/sdb1 and more importantly, it won't match nodes like /dev/sda, /dev/sdb, which can be fdisk'ed. The 'Writing udev rules' guide also mentions this.



- The options NAME="128FLASH" and
SYMLINK="usbdisc/128FLASH" will create the persistant node at /dev/transcend128mb and a symlink /dev/usbdisc/transcend128mb that points to the persistant node /dev/transcend128mb. The SYMLINK option is not required. The reason I have included it is so
that all my USB devices will have a symlink starting with /dev/usbdevices/...

I just think its neater.



There are other options that could be used to create udev rules, such as GROUP=”some_group”, if you want to assigned the group ownership of the device node to a specific group, and MODE=”0660”, which would give the owner/group read and write permissions, likechmod.



The Writing udev rules guide contains some more detailed information on these other options.



______



To start using these new rules, you need to run the command udevstart

sudo udevstart

You can also restart udev using

sudo /etc/init.d/udev restart    #you may need to reboot your linux system if this doesn't work.

This should work for later versions of udev, that don't appear to use the udevstart command



- thanks to ash211 for pointing this out



Now to quickly check that the new node for my example has been created.

user@ubuntu:~$ ls -l /dev/trans*

brw-r-----  1 root plugdev 8, 49 2006-04-30 16:37 /dev/transcend128mb

user@ubuntu:~$ ls -l /dev/usbdevices/

lrwxrwxrwx  1 root root 17 2006-04-30 16:37 transcend128mb -> ../transcend128mb

______



Finally the fstab can be edited to include the new persistant device node, but first we'll back it up

sudo cp /etc/fstab /etc/fstab_backup

sudo nano /etc/fstab

Then we can add an entry for the example USB device using either the device node
or the symlink (if used), so in my example I could either use the new device node

/dev/transcend128mb  /media/usb128mb  vfat  iocharset=utf8,umask=000   0   0

or the symlink to the node, which I prefer as all my USB devices have symlinks in /dev/usbdevices. I think makes the fstab look neater.

/dev/usbdevices/transcend128mb  /media/usb128mb vfat iocharset=utf8,umask=000  0  0

When the entry has been correctly entered, you can save the file (Ctrl+O) and exit (Ctrl+X), and then mount the device, in this example my USB disc using

sudo mount /media/usb128mb

or

sudo mount -a

Once this is all completed, the example USB drive will always appear at /dev/transcend128mb so the entry in the fstab can remain unchanged and will always find the device.





And you're all done!





Hope that helps some people, like it did me.



Please let me know if this works for you, and of course if there are any typos, errors or things that need clarifying.







The useful links I needed to get this working

Kernel.org - udev



Writing udev rules

Last edited by Sutekh; May 27th, 2006 at02:02 PM.

最新文章

1. mysql 5.7 的安装配置与 navicat premium for mysql 11 的破解使用
2. Java实现的二分查找算法
3. web学习之Django--安装
4. 保护眼睛，把常用软件的背景设置成Dark
5. 短信猫 TIdTCPServer TIdTCPClient
6. 【Django】如何自定义manage.py命令？ 达到启动后台进程的目的？
7. HDU 1166敌兵布阵+NOJv2 1025: Hkhv love spent money（线段树单点更新区间查询）
8. MySQL开启远程链接（2014.12.12）
9. Cocos2d-x 多分辨率适配完全解析
10. java基础系列--Exception异常处理
11. 【省选十连测之九】【DP】【组合计数去重】【欧拉函数】基本题
12. Lintcode85-Insert Node in a Binary Search Tree-Easy
13. 20165231 预备作业二：学习基础和C语言基础调查
14. 8. American Friendship 美国式的友谊
15. UINavigationController popToViewController用法
16. HashTable HashMap HashSet区别(java)
17. Ibatis框架之系统架构
18. mybatis mapper调用mysql存储过程
19. java 编写小工具 尝试 学习（四）
20. C++学习之路（六）：实现一个String类

热门文章

1. Video to SDI Tx Bridge模块video_data（SD-SDI）处理过程
2. Cygwin使用2-心得
3. url参数的转码和解码
4. ckeditor_4.5.10_full，ckfinder_aspnet_2.6.2，插件使用
5. 在centos7中安装nodejs(npm )
6. C++标准模板库（STL）介绍：string的基本用法
7. spring4.0之五：@Conditional在满足特定条件下，才会实例化对象
8. Java学习---流与文件
9. Java-Runoob-高级教程-实例-方法：14. Java 实例 – Varargs 可变参数使用
10. centos7 搭建DHCP服务器