xous-core
xous-core copied to clipboard
usb strangeness with openbsd host
trying to plug the precursor (0.9.14) on an openbsd (-current close to 7.4 these days) machine through USB, I get the following on the host machine kernel log: uhub1: device problem, disabling port 5
not sure what this means since I did not really investigate deeper right as traveling, does that ring a bell?
openbsd line in kernel: https://github.com/openbsd/src/blob/master/sys/dev/usb/uhub.c#L604
if not, I guess, I'll dig and/or recompile kernel with debug to track down what's happening.. in the following days..
Have you tried another cable? Is this in just regular mode on the precursor (not trying to do auto-type or anything?)?
On OpenBSD current I get the following when I connect the cable:
ugen0 at uhub0 port 2 "Foosn Precursor pvt2" rev 2.00/1.01 addr 2
And in "vault mode" I get:
uhidev0 at uhub0 port 2 configuration 1 interface 0 "Kosagi Precursor" rev 2.10/0.10 addr 2
uhidev0: iclass 3/0
fido0 at uhidev0: input=64, output=64, feature=0
uhidev1 at uhub0 port 2 configuration 1 interface 1 "Kosagi Precursor" rev 2.10/0.10 addr 2
uhidev1: iclass 3/1
ukbd0 at uhidev1: 128 variable keys, 0 key codes
which release of OpenBSD, which release of xous? I am running the latest stable xous (0.9.14) and OpenBSD 7.4 I triggered usb debug to be able to use the precursor updater on my precursor and face that strange behaviour when I plug it in. do you see it when you # usbdevs?
OpenBSD 7.4 hasn’t been released yet. As I said, I am on current. Latest FWs on the precursor.
if your showing 7.4 you are running snapshots (current).
Did you try a new cable? Perhaps your usb port isn’t supplying enough juice?
I triggered usb debug
I don’t know what you mean by this.
usbdevs -vv
when running Shellchat
:
addr 02: 1209:5bf0 Foosn, Precursor pvt2
full speed, power 100 mA, config 1, rev 1.01
driver: ugen0
in Vault
:
addr 02: 1209:3613 Kosagi, Precursor
full speed, power 100 mA, config 1, rev 0.10, iSerial 1a452a193ea85c
driver: uhidev0
driver: uhidev1
yeah i have none of those, just the device problem. I anticipated the release since the package and the src were in freeze and release process was on going, the last snapshot was most likely to be 7.4.
I triggered usb debug, as to connect and make updates to the precursor you need to put the device in usb debug in shellchat.