I have moved a bit further in the diagnosis, I modified the vendor ID (to 0x500 as a test) of my cable, and I was able
to get a pre-built (very old) libftdi from the internet to work (version 0.18), with the driver installed from
libusb-win32-bin-1.2.6.0. The old pre-built libftdi came with a serial_read.exe, and it works (it prints
"read 0 bytes").
However, if I run my serial_test.exe -p 0x500 from my compilation of the 1.0RC and my own compiled libusb 1.0.9,
I get the error mentioned below ( "unable to open ftdi device").
So, I tried to link my 1.0RC to the precompiled libusb.a from libusb-win32-bin-1.2.6.0 instead of my libusb 1.0.9,
but the linking fails. nm -a reveals that the precompiled libusb.a from libusb-win32-bin-1.2.6.0 is missing many functions
like libusb_control_transfer.
At this stage, I'm very confused why the attempt with libftdi 1.0RC and libusb1.0.9 compiles fine on my Win 7 machine,
but generates the "unable to open ftdi device" if I execute serial_test.exe -p 0x500.
Should this work?
Thanks!
From: shabaz_yousaf@xxxxxxxxxxx
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Subject: New user, testing libftdi RC 1.0
Date: Wed, 2 Jan 2013 22:06:40 +0000
Hello,
Happy new year.
I'm new to libftdi, so my sincere apologies if I'm asking basic questions.
I'm running Windows 7 64-bit, and I decided to compile using MinGW.
I had quite a few issues with CMake (probably due to my unfamiliarity with it),
where it would keep picking up my Visual Studio compiler instead of the MinGW
GCC, no matter if I deleted the build tree and tried to express the correct
compilers in the command line.
Anyway, in the end I aborted with CMake (Sadly I'm no good at troubleshooting CMake!), and I
manually compiled the libftdi library and examples folder, and I suspect all is well
regarding the compile (GCC 4.6.2). (I had compiled libusb-1.0.9 too, which I linked in).
However, when I run the examples, I seem to get an error. For example, running
find_all.exe:
$ find_all.exe
Number of FTDI devices found: 1
Checking device: 0
ftdi_usb_get_strings failed: -4 (libusb_open() failed)
It may be my lack of understanding how to use it. I have plugged in a FTDI ready-made
cable (TTL-232RG, and I also tried TTL-232-3V3), and currently in my Device Manager
I see that it is using ftser2k.sys, serenum.sys, ftcserco.dll, ftserui2.dll, i.e. the FTDI
drivers. Is this correct, or should I be using a different driver? (I removed the inf file and also tried
libusb-win32-bin-1.2.6.0 inf-wizard too, but I still got the same error with find_all.exe, so I've now
reverted back to the FTDI drivers). I also tried running find_all.exe with administrator privileges,
but I had an identical error response.
Here is another example program:
$ serial_test.exe
unable to open ftdi device: -3 (device not found)
Any help would be appreciated, or any pointers on how I should troubleshoot. I've got some FTDI chips on
order (FT2232HL-R) so I will also attempt those at some stage, and I'm looking forward to playing with
the example code to create new examples.
Thanks,
S.
libftdi - see
http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to
libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
for details.
