326
edits
Changes
Jump to navigation
Jump to search
replaced misleading advice with something _useful_
Line 5:
Line 5:
To code computer side usbgecko application you need : +* For Win32 : [http://www.ftdichip.com/Drivers/D2XX.htm API] [http://www.ftdichip.com/Documents/ProgramGuides/D2XXPG34.pdf DOC]+* For Linux : [http://www.intra2net.com/de/produkte/opensource/ftdi/ API] [http://www.intra2net.com/de/produkte/opensource/ftdi/documentation/group__libftdi.html DOC]+
See [[Gecko OS]] for the Hombrew application to launch a game and be able to debug it remotely using this device.
See [[Gecko OS]] for the Hombrew application to launch a game and be able to debug it remotely using this device.
−== Windows Side Application Programming ==
+For Win32 : [http://www.ftdichip.com/Drivers/D2XX.htm API] [http://www.ftdichip.com/Documents/ProgramGuides/D2XXPG34.pdf DOC]
−== Linux Side Application Programming ==
+The USB Gecko will usually be recognized as a USB to serial port converter and a device file of the form
+/dev/ttyUSB0
+will appear. Simply writing to and reading from this device file will send data across the USBGecko link.
−Failing that, userspace tools could use the libusb library and usb_bulk_write and usb_bulk_read functions. The USBGecko will appear as 0403:6001 in the lsusb output.
== Hardware ==
== Hardware ==