Hi!
I have a CC2652RB Zigbee stick, which I cannot access via /dev/cuaU*,
despite attaching at ucom(4), at least according to dmesg. It is
initially recognized as uslcom(4):
- - - - - - - - - - %< - - - - - - - - - -
uslcom0 at uhub3 port 5 configuration 1 interface 0 "Silicon Labs slae.sh
cc2652rb stick - slaesh's iot stuff" rev 1.10/1.00 addr 2
ucom4 at uslcom0 portno 0: usb3.0.00005.0
- - - - - - - - - - %< - - - - - - - - - -
A Quectel EC25 is showing up properly at ucom{0,1,2,3} and can be
accessed via /dev/cuaU{0,1,2,3}:
- - - - - - - - - - %< - - - - - - - - - -
umsm0 at uhub1 port 1 configuration 1 interface 0 "Android Android" rev
2.00/3.18 addr 2
ucom0 at umsm0: usb1.0.00001.0
umsm1 at uhub1 port 1 configuration 1 interface 1 "Android Android" rev
2.00/3.18 addr 2
ucom1 at umsm1: usb1.0.00001.1
umsm2 at uhub1 port 1 configuration 1 interface 2 "Android Android" rev
2.00/3.18 addr 2
ucom2 at umsm2: usb1.0.00001.2
umsm3 at uhub1 port 1 configuration 1 interface 3 "Android Android" rev
2.00/3.18 addr 2
ucom3 at umsm3: usb1.0.00001.3
- - - - - - - - - - %< - - - - - - - - - -
FWIW I can access the stick via macOS Sequoia 15.4.1 - I flashed a
coordinator firmware via this machine on the stick. I'd be happy about a
solution to access the stick on OpenBSD - if needed, I can provide more
info...
--
Mit besten Wünschen /
With best wishes,
Manuel Kuklinski
