Rev 3331 Rev 3332
1 i2c-tiny-usb test application - http://www.harbaum.org/till/i2c_tiny_usb 1 i2c-tiny-usb test application - http://www.harbaum.org/till/i2c_tiny_usb
2 ------------------------------------------------------------------------ 2 ------------------------------------------------------------------------
3   3  
4 This simple test application is meant to demonstrate libusb 4 This simple test application is meant to demonstrate libusb
5 interfacing to the i2c-tiny-usb interface. 5 interfacing to the i2c-tiny-usb interface.
6   6  
7 This is no useful application, if you are only interesting in 7 This is no useful application, if you are only interesting in
8 using the i2c-tiny-usb interface in your linux box please 8 using the i2c-tiny-usb interface in your linux box please
9 use the kernel driver. 9 use the kernel driver.
10   10  
11 Linux 11 Linux
12 ----- 12 -----
13   13  
14 This demo application has been developed under and for linux. Just 14 This demo application has been developed under and for linux. Just
15 make sure you have libusb installed. To use this program just 15 make sure you have libusb installed. To use this program just
16 compile by typing "make" and run the resulting i2c_usb. 16 compile by typing "make" and run the resulting i2c_usb.
17   17  
18 Be sure that the i2c-tiny-usb kernel driver is not loaded while 18 Be sure that the i2c-tiny-usb kernel driver is not loaded while
19 running the test application. Otherwise the test application will 19 running the test application. Otherwise the test application will
20 fail with the follwing error message: 20 fail with the follwing error message:
21   21  
22 USB error: could not claim interface 0: Device or resource busy 22 USB error: could not claim interface 0: Device or resource busy
23   23  
24 This is due to the fact that no two drivers may access the interface 24 This is due to the fact that no two drivers may access the interface
25 at the same time. 25 at the same time.
26   26  
27 Windows 27 Windows
28 ------- 28 -------
29   29  
30 This program can be compiled for windows. This has been tested 30 This program can be compiled for windows. This has been tested
31 under Linux using xmingw and the windows port of libusb 31 under Linux using xmingw and the windows port of libusb
32 (see http://libusb-win32.sourceforge.net). To install the 32 (see http://libusb-win32.sourceforge.net). To install the
33 driver plug the device in and install the driver from 33 driver plug the device in and install the driver from
34 the win directory. Then run testapp/i2c_usb.exe 34 the win directory. Then run testapp/i2c_usb.exe
35   35  
36 This program may also be compiled under windows using cygwin or 36 This program may also be compiled under windows using cygwin or
37 mingw (which is part of cygwin). In order to use cygwin simply 37 mingw (which is part of cygwin). In order to use cygwin simply
38 copy usb.h win32-linusb to /cygwin/usr/include and libusb.a to 38 copy usb.h win32-linusb to /cygwin/usr/include and libusb.a to
39 /cygwin/lib and do a "make -f Makefile.cygwin". Don't forget to 39 /cygwin/lib and do a "make -f Makefile.cygwin". Don't forget to
40 distribute /cygwin/bin/cygwin1.dll with your file to allow it to 40 distribute /cygwin/bin/cygwin1.dll with your file to allow it to
41 run in non-cygwin environments as well. No dll is required when using 41 run in non-cygwin environments as well. No dll is required when using
42 mingw. In that case copy usb.h to /cygwin/usr/include/mingw and 42 mingw. In that case copy usb.h to /cygwin/usr/include/mingw and
43 libusb.a to /cygwin/lib/mingw. Finally do a "make -f Makefile.mingw". 43 libusb.a to /cygwin/lib/mingw. Finally do a "make -f Makefile.mingw".
44   44  
45 MacOS X 45 MacOS X
46 ------- 46 -------
47   47  
48 The program can be compiled under MacOS as well. The fink version 48 The program can be compiled under MacOS as well. The fink version
49 of linusb has to be installed and a simple "make -f Makefile.macos" 49 of linusb has to be installed and a simple "make -f Makefile.macos"
50 will build the native MacOS X version. 50 will build the native MacOS X version.