Difference between revisions of "2253"
From Sensoray Technical Wiki
(Created page with "== Cross-compiling Linux driver for ARM == From sdk_2253_x.y.z_linux/driver: PATH=<path-to-cross-compiler/bin>:$PATH \ make -C <path-to-target-kernel-directory> SUBDIRS...") |
|||
| Line 10: | Line 10: | ||
For the demo application, modify the Makefile path to the cross compiler, then do "make demo_arm". | For the demo application, modify the Makefile path to the cross compiler, then do "make demo_arm". | ||
| + | |||
| + | == Connecting to USB 3.0 (SuperSpeed) ports on Linux == | ||
| + | |||
| + | When connecting the board to a port on a USB 3.0 hub, if the device does not work, check the dmesg log for these messages: | ||
| + | |||
| + | [ 378.352045] usb 9-1: new high-speed USB device number 19 using xhci_hcd | ||
| + | [ 378.369004] usb 9-1: device descriptor read/8, error -75 | ||
| + | [ 378.488958] usb 9-1: device descriptor read/8, error -75 | ||
| + | |||
| + | Reconnect the device to a USB 2.0 port, or contact support@sensoray.com for RMA. Boards manufactured after April 2013 have corrected this issue. (Windows is not affected.) | ||
Revision as of 10:42, 25 April 2013
Cross-compiling Linux driver for ARM
From sdk_2253_x.y.z_linux/driver:
PATH=<path-to-cross-compiler/bin>:$PATH \ make -C <path-to-target-kernel-directory> SUBDIRS=`pwd` \ CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm modules
Copy the s2253.ko file to the target's /lib/modules/`uname -r`/extra directory, and run "depmod -a".
For the demo application, modify the Makefile path to the cross compiler, then do "make demo_arm".
Connecting to USB 3.0 (SuperSpeed) ports on Linux
When connecting the board to a port on a USB 3.0 hub, if the device does not work, check the dmesg log for these messages:
[ 378.352045] usb 9-1: new high-speed USB device number 19 using xhci_hcd [ 378.369004] usb 9-1: device descriptor read/8, error -75 [ 378.488958] usb 9-1: device descriptor read/8, error -75
Reconnect the device to a USB 2.0 port, or contact support@sensoray.com for RMA. Boards manufactured after April 2013 have corrected this issue. (Windows is not affected.)