Hello Uwe,
thank you, this helped a lot. I can connect to the devices using this method.
Also it works multiple times without a problem.
I would say though the problem i had with reading the eeprom was actually more
a problem of the custom made ftdi device, because I now tested my previous
solution with a off-the-shelf ftdi product and it worked fine even multiple
times.
The new version is even nicer though :)
Thanks again.
Tim
Am 18.01.2011 um 15:19 schrieb Uwe Bonnes:
> Tim> Dear all, I am currently working on connecting a self build sensor
> Tim> with the HTC Desire running Android with hostmode enabled. I am
> Tim> using a FTDI Chip and libftdi for the task. Since it might be
> Tim> possible that I have multiple FTDI Devices connected, I cannot use
> Tim> the ftdi_usb_open API. Instead i'm using ftdi_usb_find_all
> Tim> afterwards ftdi_usb_open_dev. Then I read the
> Tim> eeprom(ftdi_read_eeprom_getsize & ftdi_eeprom_decode), to determine
> Tim> weather this is the sensor I'm looking for.
>
> Connect the device to a Linux PC. If "dmesg" reports something like
> [268963.174419] usb 1-3.3: New USB device found, idVendor=0403, idProduct=6010
> [268963.174426] usb 1-3.3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [268963.174432] usb 1-3.3: Product: LLBBC10
> [268963.174436] usb 1-3.3: Manufacturer: IKDA
> [268963.174440] usb 1-3.3: SerialNumber: 30
> You can run
> res = ftdi_usb_open_desc(ftdi_handle, 0x403, 0x6010, "LLBBC10", NULL);
> to open the first device with "Product: LLBBC10"
> or
> res = ftdi_usb_open_desc(ftdi_handle, 0x403, 0x6010, "LLBBC10", 30);
> for the exact device.
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
