-
The RCP device shows up as USB ACM device. Depending on plug in order, or a device USB reset this devioce name is not always defined to be ttyACM0. This udev rules helps us to keep the device name stable with a symlink that links back to the original ttyACM? device. For now we support two types of RCP devies in there (the only ones we have been working with in Oniro). An OpenThread bare metal firmware flashed on the Makerdiary USB dongle and the Zephyr + OpenThread based RCP firmware on the Arduino Nano 33 BLE. Signed-off-by:Stefan Schmidt <stefan.schmidt@huawei.com>
The RCP device shows up as USB ACM device. Depending on plug in order, or a device USB reset this devioce name is not always defined to be ttyACM0. This udev rules helps us to keep the device name stable with a symlink that links back to the original ttyACM? device. For now we support two types of RCP devies in there (the only ones we have been working with in Oniro). An OpenThread bare metal firmware flashed on the Makerdiary USB dongle and the Zephyr + OpenThread based RCP firmware on the Arduino Nano 33 BLE. Signed-off-by:Stefan Schmidt <stefan.schmidt@huawei.com>
Loading