I don't know how to further debug the issue. lsusb -v -s 1:3 also reports the correct information for the device. Stty runs on the file without errors (however the reported data is obviously invalid/arbitrary, due to the device being a USB device and not a serial device). However, opening the device with a serial terminal or even with the cat command, results in garbage being printed, whereas ASCII NMEA commands should be printed (this is confirmed to work on two other systems). I plugged the device and it correctly got enumerated by the USB driver with address 001:003, and assigned to the cdc_acm driver that created the /dev/ttyACM0 file. The system didn't come with cdc_acm, so I cross-compiled it, transferred & insmodded it, and it loaded successfully (confirmed by dmesg). I connected the device and it correctly got enumerated by the USB driver with address 001:003, and assigned to the cdcacm driver that created the /dev/ttyACM0 file. The system didnt come with cdcacm, so I cross-compiled it, transferred & insmodded it, and it loaded successfully (confirmed by dmesg). The device has a native CDC ACM USB interface. The device has a native CDC ACM USB interface. I'm trying to connect a u-Blox USB GPS device to an embedded (armel) Linux 2.6.32 system based on BusyBox.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |