>>>>> "Chaves," == Chaves, Kevin <kevin.chaves@xxxxxxxxxxxxxxxx> writes:
Chaves,> So I’m having an incredibly strange problem using an ft2232h
Chaves,> device. We have two different boards each have the same
Chaves,> circuitry surrounding the ftdi device. For some reason on
Chaves,> linux I can’t toggle the chip select on one of them using
Chaves,> libftdi. Neither work using the libMPSSE/d2xx drivers provided
Chaves,> in linux. They work in windows using the libMPSSE/d2xx drivers,
Chaves,> which doesn’t help me much since they are bound for embedded
Chaves,> linux products. The strange part about this I original got it
Chaves,> to work with both using libMPSSE/d2xx. And worse all the
Chaves,> signals look perfect apart from the cs never being toggled.
Do the two boards perhaps have different EEPROMs? Is the chip or at least
the CS pin perhaps broken or bad soldered? Been there, done that ;-)
Chaves,> We moved to libftdi because it’s easier to produce arm
Chaves,> binaries. I borrowed code from
Chaves,> https://code.google.com/p/libftdispi/ . I’m still not quite
Chaves,> sure if I’m selected the right dbus for the chip enable. I’m
Chaves,> not quite sure how to do it using libftdi or the libftdispi I’m
Chaves,> using.
Chaves,> Any help would be much appreciated. I’m completely lost and
Chaves,> would be happy to share the source code we are using for
Chaves,> initializing and using the spi device. I’m about ready to
Chaves,> throw my PC out the window… I’m down to using a usb trace to
Chaves,> figure out the difference in signals being sent but so far it’s
Chaves,> kind of useless.
Come back for more hints if the hint above doesn't help. B.t.w. what pin
causes the headach?
Bye
--
Uwe Bonnes bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
