Sample Header Ad - 728x90

Failing to SSH into a DE1-SoC even though I seem to have all dependencies met

1 vote
1 answer
104 views
I'm following Altera's guide for running Linux on the DE1-SoC board, specifically section 5.3 - Installing the Driver. The instructions provided in the guide are for a Windows host, and I'm on a linux host (I don't currently have any Windows hosts available for permanent use). I'm following the instructions, but I can't get to ssh into the device, and I've exhausted all my efforts trying to troubleshoot it.
$ uname -r
5.15.0-124-generic
**To form a baseline, upon host startup, before ever connecting the board through usb:**
$ ls -al /lib/modules/"$(uname -r)"/kernel/drivers/usb/serial/usbserial.ko
-rw-r--r-- 1 root root 116161 Sep 27  2024 /lib/modules/5.15.0-124-generic/kernel/drivers/usb/serial/usbserial.ko
$ ls -al /lib/modules/"$(uname -r)"/kernel/drivers/usb/serial/cp210x.ko
-rw-r--r-- 1 root root 79865 Sep 27  2024 /lib/modules/5.15.0-124-generic/kernel/drivers/usb/serial/cp210x.ko

$ lsmod | grep cp210x
$ sudo modprobe usbserial
$ sudo modprobe cp210x
$ lsmod | grep cp210x
cp210x                 40960  0
usbserial              57344  1 cp210x
Meaning I've successfully loaded the driver.
$ dmesg | grep -i usb
...
[   30.186227] usb 2-3: current rate 16000 is different from the runtime rate 48000
[  124.301044] usbcore: registered new interface driver usbserial_generic
[  124.301067] usbserial: USB Serial support registered for generic
[  128.825043] usbcore: registered new interface driver cp210x
[  128.825069] usbserial: USB Serial support registered for cp210x
Corresponding to the loadings from above.
$ dmesg | grep -i tty
[    0.006788] ACPI: SSDT 0x0000000074487000 002357 (v02 ALASKA TbtTypeC 00000000 INTL 20200717)
[    0.117362] printk: console [tty0] enabled
[    0.401844] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
$ lsusb
...
$ ls /dev/tty*
...
$ lsusb brings up a bunch of devices and $ ls /dev/tty* lists a bunch of terminals. The board is not showing of course, it's disconnected as I'm currently forming the baseline. **I now connect the board and turn it on.**
$ dmesg | grep -i usb
...
[  128.825069] usbserial: USB Serial support registered for cp210x
[  244.712211] usb 1-1: new high-speed USB device number 5 using xhci_hcd
[  244.860515] usb 1-1: New USB device found, idVendor=09fb, idProduct=6810, bcdDevice= 0.01
[  244.860527] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
idVendor and idProduct are identified correctly.
$ dmesg | grep -i tty[    0.006788] ACPI: SSDT 0x0000000074487000 002357 (v02 ALASKA TbtTypeC 00000000 INTL 20200717)
[    0.117362] printk: console [tty0] enabled
[    0.401844] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nothing's changed.
$ lsusb
...
Bus 001 Device 005: ID 09fb:6810 Altera
This line is added. $ ls /dev/tty* Brings up exactly the same list - nothing's changed. As mentioned above, I'm out of ideas. I will appreciate any kind of help, so I can ssh to the board and start communicating between the ARM core and the FPGA.
Asked by barak (15 rep)
Mar 29, 2025, 05:46 PM
Last activity: Mar 30, 2025, 03:17 PM