AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Linux kernel gps driver cp21029/23/2023 ![]() ![]() # Automatically hot add/remove USB GPS devices via gpsdctl # They need to be read/writeable, either by user gpsd or the group dialout.ĭEVICES="/dev/serial/by-id/usb-u-blox_AG_-_ # Other options you want to pass to gpsd # Devices gpsd should collect to at boot time. Otherwise, if you are using GPS ensure you are explicitly specifying the GPS device you are using and disable USB hot add/remove of devices in the /etc/default/gpsd file. A solution to this would be either turn the gps daemon off if one is not using GPS. I shut off the GPS daemon and I was able to access the ttyUSB port. An losf command searching for ttyUSB informed me that GPS daemon took control of the device. Furthermore rigctl under debug was giving me device/resource busy errors. Looking closely at the dmesg logs it looked like the USB-UART Bridge was being detected as a PPS (pulse per second device i.e. ![]() usb 1-1.3.2: cp210x converter now attached to ttyUSB0 usb 1-1.3.2: Product: CP2102N USB to UART Bridge Controller usb 1-1.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.3.2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 usb 1-1.3.2: new full-speed USB device number 17 using xhci_hcd usb 1-1.3.1: Manufacturer: C-Media Electronics Inc. usb 1-1.3.1: Product: USB PnP Sound Device usb 1-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.3.1: New USB device found, idVendor=0d8c, idProduct=013c, bcdDevice= 1.00 usb 1-1.3.1: new full-speed USB device number 16 using xhci_hcd usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 usb 1-1.3: New USB device found, idVendor=0424, idProduct=2412, bcdDevice= b.b2 Do you have any tips/advice in order to get it working?ģ9741.315955] usb 1-1.3: new high-speed USB device number 15 using xhci_hcd It appears to be detected by the kernel via dmesg however I cannot it to work in rigctl or flrig. It appears the driver is maintained in the kernel per silicon labs. However I've been trying to get this to work on (serial port, audio works fine) on linux, specifically raspberry pi OS. I love the device and it works great on windows using the latest drivers. I purchased a digirig along with Yaesu cables about a month ago. Received email from Rocco today, posting with the solution in hopes it is useful for somebody in the same situation ![]()
0 Comments
Read More
Leave a Reply. |