Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork841
Description
I have triedmake miniterm in 05 andmake chainboot in 06 and neither detects the USB serial device. I have two different USB serial devices and an RPi3 and an RPi4. I usedminiterm in python3 andscip to test that both USB serial devices and both RPis will boot the kernel for 05, so I'm happy that everythingshould work.
I started with 05. I know nothing about Ruby so I resorted to the traditional approach of adding some print lines to see where it gets to. I added aputs line, here:
loop do sleep(1) puts '...serial still not connected' break if serial_connected?endBelow, is my output. First, I ran thels -l command and you can see that the USB Serial device is not plugged in/detected. Then I ranmake miniterm and, after five loops, I plugged in the USB device . It's not detected. I cancel miniterm and re-run thels -l and you can see the USB device is available on the host.
$ ls -l /dev/ttyUSB0ls: cannot access '/dev/ttyUSB0': No such file or directory$ make minitermDOCKER_MINITERM is docker run -t --rm -v /home/simgar/rust-projects/rust-raspberrypi-OS-tutorials/05_drivers_gpio_uart:/work/tutorial -w /work/tutorial -i --privileged -v /dev:/dev -v /home/simgar/rust-projects/rust-raspberrypi-OS-tutorials/05_drivers_gpio_uart/../common:/work/common rustembedded/osdev-utils:2021.12Miniterm 1.0Running...[MT] ⏳ Waiting for /dev/ttyUSB0...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected <---- USB Serial plugged in here...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected...serial still not connected^C[MT] Bye 👋$ ls -l /dev/ttyUSB0crw-rw---- 1 root dialout 188, 0 Dec 28 19:52 /dev/ttyUSB0So, I wondered if it's possible to check if the USB device is available in the docker container session. [I figured I needed a different docker command line. I don't know anything about Docker ormake, so I did a bit of trail-and-error.] To themakefile, after the section where you assemble the DOCKER_* command line components, I added:
$(info DOCKER_MINITERM is $(DOCKER_MINITERM))so that I could see the command line, and
DOCKER_LS_USB = ls -l /dev/ttyUSB0and then after theminiterm: section, I added:
##------------------------------------------------------------------------------## Connect to the target's serial##------------------------------------------------------------------------------ttyusb: @$(DOCKER_MINITERM) $(DOCKER_LS_USB)When I runmake ttyusb, having left the USB Serial device plugged in from the previous tests, I get:
ls: cannot access '/dev/ttyUSB0': No such file or directorymake: *** [Makefile:200: ttyusb] Error 2If I change it to:
DOCKER_LS_USB = ls -l /dev/ttyUSB*I get
ls: cannot access '/dev/ttyUSB0': No such file or directorymake: *** [Makefile:200: ttyusb] Error 2which is odd because I haven't told it to look for/dev/ttuUSB0.
Note: previously, the200 has been189 (and possibly other values).
When I run the same command on the host, I get:
crw-rw---- 1 root dialout 188, 0 Dec 30 11:05 /dev/ttyUSB0To confirm this, I also added to themakefile:
DOCKER_DMESG_TAIL = dmesg -w | grep ttyand:
ttydmesg: @$(DOCKER_MINITERM) $(DOCKER_DMESG_TAIL)and when I runmake ttydmesg, I get:
[ 0.000000] Command line: init=/init loglevel=1 root=/dev/vdb rootfstype=erofs ro vsyscall=emulate panic=0 eth0.dhcp eth1.dhcp linuxkit.unified_cgroup_hierarchy=1 vpnkit.connect=tcp+connect://192.168.65.2:34845 console=ttyS0[ 0.052173] Kernel command line: init=/init loglevel=1 root=/dev/vdb rootfstype=erofs ro vsyscall=emulate panic=0 eth0.dhcp eth1.dhcp linuxkit.unified_cgroup_hierarchy=1 vpnkit.connect=tcp+connect://192.168.65.2:34845 console=ttyS0[ 0.127565] printk: legacy console [ttyS0] enabled[ 0.500669] 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550AThen I plug in the USB Serial device and there are no updates. At the same time, I was runningsudo dmesg -w | grep tty in another terminal on the host and could see the USB device registering:
[13761.981312] usb 2-1: pl2303 converter now attached to ttyUSB0As mentioned above, I have two different USB Serial devices (one USB, one USB-C) so I try the other one. I see no change on the container output but the host output shows:
[13901.182734] usb 6-1: cp210x converter now attached to ttyUSB0Can you think of anything I can try?
I'm running Ubuntu VERSION="24.04.1 LTS (Noble Numbat)" on the host.