轮子——ubuntu串口名称绑定

课题中需要使用一台迷你PC作为主控，通过串口与DJI SDK、UWB模块和无线数传电台通信。三个设备都需要一个USB转串口与电脑相连，但是不同的拔插顺序会造成他们在/dev下的名字不同。

为了减小设备开机后的准备工作量，决定将串口直接绑定固定的名字。

根据之前的经验，可以在/etc/udev/rules.d下建立规则文件，用不同串口的idVendor和idProduct区分并命名各个串口。

但是在lsusb查看USB上所连接的串口信息时，发现有两个串口的芯片型号相同，造成了他们具有相同的idVendor和idProduct。
查阅了一番资料，发现似乎只要用各个串口与其他串口不同的信息建立规则就可以。
用命令查询：

udevadm info --attribute-walk --name=/dev/USB2COM_UWB

得到

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/ttyUSB0/tty/ttyUSB0':
    KERNEL=="ttyUSB0"
    SUBSYSTEM=="tty"
    DRIVER==""

  looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/ttyUSB0':
    KERNELS=="ttyUSB0"
    SUBSYSTEMS=="usb-serial"
    DRIVERS=="ftdi_sio"
    ATTRS{port_number}=="0"
    ATTRS{latency_timer}=="16"

  looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0':
    KERNELS=="1-1:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="ftdi_sio"
    ATTRS{bInterfaceSubClass}=="ff"
    ATTRS{authorized}=="1"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bInterfaceProtocol}=="ff"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{supports_autosuspend}=="1"
    ATTRS{interface}=="FT232R USB UART"
    ATTRS{bNumEndpoints}=="02"
    ATTRS{bInterfaceClass}=="ff"

  looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-1':
    KERNELS=="1-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{removable}=="unknown"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bMaxPower}=="90mA"
    ATTRS{product}=="FT232R USB UART"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{manufacturer}=="FTDI"
    ATTRS{rx_lanes}=="1"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bmAttributes}=="a0"
    ATTRS{bcdDevice}=="0600"
    ATTRS{speed}=="12"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{tx_lanes}=="1"
    ATTRS{idVendor}=="0403"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{maxchild}=="0"
    ATTRS{version}==" 2.00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{ltm_capable}=="no"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{authorized}=="1"
    ATTRS{urbnum}=="16"
    ATTRS{devpath}=="1"
    ATTRS{devnum}=="2"
    ATTRS{quirks}=="0x0"
    ATTRS{serial}=="A987Z55T"
    ATTRS{idProduct}=="6001"
    ATTRS{configuration}==""
    ATTRS{busnum}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1':
    KERNELS=="usb1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{idVendor}=="1d6b"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{serial}=="0000:00:14.0"
    ATTRS{interface_authorized_default}=="1"
    ATTRS{quirks}=="0x0"
    ATTRS{ltm_capable}=="no"
    ATTRS{devnum}=="1"
    ATTRS{product}=="xHCI Host Controller"
    ATTRS{version}==" 2.00"
    ATTRS{authorized}=="1"
    ATTRS{devpath}=="0"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{urbnum}=="95"
    ATTRS{configuration}==""
    ATTRS{authorized_default}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{removable}=="unknown"
    ATTRS{manufacturer}=="Linux 5.4.0-37-generic xhci-hcd"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bMaxPower}=="0mA"
    ATTRS{maxchild}=="12"
    ATTRS{tx_lanes}=="1"
    ATTRS{rx_lanes}=="1"
    ATTRS{idProduct}=="0002"
    ATTRS{busnum}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bcdDevice}=="0504"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{speed}=="480"

  looking at parent device '/devices/pci0000:00/0000:00:14.0':
    KERNELS=="0000:00:14.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="xhci_hcd"
    ATTRS{device}=="0x9d2f"
    ATTRS{consistent_dma_mask_bits}=="64"
    ATTRS{numa_node}=="-1"
    ATTRS{msi_bus}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{vendor}=="0x8086"
    ATTRS{local_cpus}=="3"
    ATTRS{d3cold_allowed}=="1"
    ATTRS{subsystem_vendor}=="0x8086"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{ari_enabled}=="0"
    ATTRS{dbc}=="disabled"
    ATTRS{revision}=="0x21"
    ATTRS{class}=="0x0c0330"
    ATTRS{irq}=="124"
    ATTRS{dma_mask_bits}=="64"
    ATTRS{enable}=="1"
    ATTRS{driver_override}=="(null)"
    ATTRS{subsystem_device}=="0x7270"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

使用ATTRS{serial}=="A987Z55T"这个类似于序列号的信息进行区分，最终在/etc/udev/rules.d文件夹下建立规则文件usb2com.rules，内容如下：

KERNEL=="ttyUSB*",ATTRS{idVendor}=="1a86",ATTRS{idProduct}=="7523",GROUP:="dialout",SYMLINK+="USB2COM_DJI"
KERNEL=="ttyUSB*",ATTRS{serial}=="A600F4OZ",MODE:="0666",GROUP:="dialout",SYMLINK+="USB2COM_3DR"
KERNEL=="ttyUSB*",ATTRS{serial}=="A987Z55T",MODE:="0666",GROUP:="dialout",SYMLINK+="USB2COM_UWB"

而后重启电脑或者使用如下规则更新命令进行配置

service udev reload
service udev restart

最终得到

遗留疑问：
在使用udevadm命令进行查询的时候，发现有一个串口没有serial码，好在它的idVendor和idProduct跟其他两个串口不同，暂时不影响当前课题的进行。