Hello,
I am testing dev_lowlevel from the pico sdk. I have successfully compiled the firmware without modifications and uploaded to my pico.
On Ubuntu 24, the python code provided with the example can successfully interface with the pico, and I get the "hello world" as expected.
However, on an old Linux kernel (2.6.18), the device appears to enumerate, and I can see it in lsusb.
usb 2-2: new full speed USB device using ohci_hcd and address 23
usb 2-2: configuration #1 chosen from 1 choice
However, running the test program results in the below:
usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usb_client rqt 128 rq 8 len 1 ret -110
Likewise, if I create a simple program in C will also cause this error when I run libusb_open_device_with_vid_pid.
My test machine is a CentOS 5.2 box running 2.6.18-92.1.6.el5. Running on a newer kernel is not possible - this is for a proprietary arcade game whose developer is long out of business. I also do not have access to the original arcade game source, so the changes must happen in the pico firmware.
Any thoughts of how I can modify the firmware code to accommodate would be much appreciated.
I am testing dev_lowlevel from the pico sdk. I have successfully compiled the firmware without modifications and uploaded to my pico.
On Ubuntu 24, the python code provided with the example can successfully interface with the pico, and I get the "hello world" as expected.
However, on an old Linux kernel (2.6.18), the device appears to enumerate, and I can see it in lsusb.
usb 2-2: new full speed USB device using ohci_hcd and address 23
usb 2-2: configuration #1 chosen from 1 choice
However, running the test program results in the below:
usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usb_client rqt 128 rq 8 len 1 ret -110
Likewise, if I create a simple program in C will also cause this error when I run libusb_open_device_with_vid_pid.
My test machine is a CentOS 5.2 box running 2.6.18-92.1.6.el5. Running on a newer kernel is not possible - this is for a proprietary arcade game whose developer is long out of business. I also do not have access to the original arcade game source, so the changes must happen in the pico firmware.
Any thoughts of how I can modify the firmware code to accommodate would be much appreciated.
Statistics: Posted by therizzler — Mon Feb 09, 2026 7:11 pm — Replies 0 — Views 11