udev + bossa = failure to autorecover?

A Former User

could i ask @gtj0 and/or @wilriker to test the following on a non-raspberry / non-raspbian setup? (with any duet attached to usb)

#!/bin/bash
#test for Duets with working RRF vendor 1d50 product 60e?
for i in $(find -L  /sys/bus/usb/devices/ -maxdepth 2 -name "tty*"); do
  grep -i "v1d50p60e[c-e]" $i/../modalias &>/dev/null && echo /dev/$(ls $i) 
done

#test for SAM-BA vendor 03eb product 6124
for i in $(find -L  /sys/bus/usb/devices/ -maxdepth 2 -name "tty*"); do
  grep -i "v03ebp6124" $i/../modalias &>/dev/null && echo /dev/$(ls $i)
done

wilriker

@bearer said in udev + bossa = failure to autorecover?:

Of course I can

$ uname -a
Linux duet3-6HC 4.19.115-1-ARCH #1 SMP PREEMPT Fri Apr 24 14:53:41 UTC 2020 armv7l GNU/Linux

$ ./the-bear-needs-test-helpers.bash
/dev/ttyACM0

A Former User

Cool, seems to work. Thanks!
(asuming /dev/ttyACM0 is a duet in one form or another:P)

(goal is to avoid trying to flash a non duet that happens to occupy ttyACM0:)

@wilriker said in udev + bossa = failure to autorecover?:

./the-bear-needs-test-helpers.bash

wilriker

@bearer said in udev + bossa = failure to autorecover?:

(asuming /dev/ttyACM0 is a duet in one form or another:P)

Yes, that's a Duet 3 permanently attached to RPi4 that runs DSF.

./the-bear-needs-test-helpers.bash

I knew you'd like that. Also as I use fish I had to put it into a script.

BTW:

$ lsusb
Bus 001 Device 006: ID 1d50:60ec OpenMoko, Inc. (Duet 2 Wifi)
Bus 001 Device 006: ID 1d50:60ed OpenMoko, Inc. (Duet 2 Maestro)
Bus 001 Device 004: ID 1d50:60ee OpenMoko, Inc. (Duet 3)
Bus 001 Device 008: ID 03eb:6124 Atmel Corp. at91sam SAMBA bootloader

Did you hack your usb-ids or did you just add the values in parentheses yourself? I have submitted change requests to fix the names to usb-ids months ago but they do not accept them.

A Former User

...sounds fishy!)

@wilriker said in udev + bossa = failure to autorecover?:

Did you hack your usb-ids or did you just add the values in parentheses yourself?

just added them for my own pleasure, wasn't aware it made it to the forum.

wilriker

@bearer said in udev + bossa = failure to autorecover?:

...sounds fishy!)

You as a bear should like that, don't you?

A Former User

@wilriker said in udev + bossa = failure to autorecover?:

usb-ids

huh poking around i find (but oddly enough not all fields for the bossa bootloader with the correct usb-id). oh well, enough to identify the board before querying bossa for the cpu type.

echo $(cat $1/../../manufacturer): $(cat $1/../../product) $(cat $1/../../version) \($( cat $1/../../idVendor):$( cat $1/../../idProduct)\)
Duet3D: Duet 2.00 (1d50:60ec)

edit:

seems there has been an update to usb-ids as well

pi@raspberrypi:~ $ lsusb
Bus 001 Device 031: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 039: ID 1d50:60ec OpenMoko, Inc. Duet 3D Printer Controller
Bus 001 Device 005: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:~ $

gtj0

@bearer Here's my info from a Jetson Nano if you still need it...

duet3j /~# uname -a
Linux duet3j.f5.int 4.9.140-tegra-gtj8+ #5 SMP PREEMPT Sat Mar 14 08:58:08 MDT 2020 aarch64 aarch64 aarch64 GNU/Linux
duet3j /~# ./testudev.sh 
/dev/ttyACM0
duet3j /~#

A Former User

@gtj0 awesome! just wanted to check if i could derive the tty device from usb ids across different combinations, so far so good.

wilriker

@bearer said in udev + bossa = failure to autorecover?:

seems there has been an update to usb-ids as well
pi@raspberrypi:~ $ lsusb
Bus 001 Device 039: ID 1d50:60ec OpenMoko, Inc. Duet 3D Printer Controller

Not really. 1d50:60ec has been in there for a very long time already. I added 1d50:60ed for Maestro and 1d50:60ee for Duet 3. Already back in October last year. But it still didn't make it into the release.

A Former User

@wilriker said in udev + bossa = failure to autorecover?:

@bearer said in udev + bossa = failure to autorecover?:
seems there has been an update to usb-ids as well
pi@raspberrypi:~ $ lsusb
Bus 001 Device 039: ID 1d50:60ec OpenMoko, Inc. Duet 3D Printer Controller
Not really. 1d50:60ec has been in there for a very long time already. I added 1d50:60ed for Maestro and 1d50:60ee for Duet 3. Already back in October last year. But it still didn't make it into the release.

ah, not often i have a wifi/ethernet connected, come to think of it I might initially have ~~defered~~ derived(?) the pid as 60ec based on maestro and duet 3. my bad.