Zigbee stick not recognized

Software SW help
1

Hey all,

I would like to ask you for a help. I am already banging my keyboard for too long and have no idea what else to try.

I am running Home Assistant in LXC. Recently I have decided to upgrade my Zigbee coordinator with Slaesh’s CC2652RB. When it arrived I plugged it in, but Turris did not properly recognized it. I had this issue already with my previous coordinator, but if I remember correctly the solution was to use the front-facing USB port. I have tried both ports without success.

The device is recognized as plugged in, but I believe it should expose CDC_ACM device. The device is recognized currently as Vendor Specific Class.

root@turris ~# lsusb --tree
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M

There is no serial port exposed under /dev. I have installed all sort of serial drivers I could find:

root@turris ~# opkg list-installed | grep kmod-usb
kmod-usb-acm - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-core - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-ehci - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-ohci - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-serial - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-serial-ch341 - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-serial-ftdi - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-serial-qualcomm - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-serial-simple - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-serial-wwan - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-storage - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-storage-extras - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-storage-uas - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb-uhci - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb2 - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3
kmod-usb3 - 4.14.236-1-67f70e2f39f8e8859c56d42cced0b0b3

When I reconnect the coordinator not much is in dmesg:

root@turris ~ [0|1]# dmesg | grep usb
[422514.069278] usb 2-1: USB disconnect, device number 2
[422516.126011] usb 2-1: new full-speed USB device number 3 using xhci-hcd

Do you have any suggestions what to try please?

2

Hello,

I see that CC2652RB uses driver kmod-usb-serial-cp210x. Can you try to install it and let me know if it works? You can install it by running these two commands:

  1. opkg update
    This one will update lists of individual feeds with available packages
  2. opkg install kmod-usb-serial-cp210x.

Drivers need to be installed manually. This is default by OpenWrt because OpenWrt is minimalistic and we can not provide preinstalled all packages as we would simply run out of the available storage. There is also a way to add it into Updater Drivers, so recognized USB/PCIe devices would download the drivers automatically if the Internet connection is working.

3

Yey, you are right! Now it is recognized and there is /dev/ttyUSB0 device! Thanks a lot!

4

Since Turris OS 5.3, the driver will be automatically installed for your USB device, which you are using. More details:

1 Like
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.