>>>>> "Chaves," == Chaves, Kevin <kevin.chaves@xxxxxxxxxxxxxxxx> writes:
>> 0x80 0x00 0x00 sets all pins low, sets all as inputs. If what I'm
>> thinking makes since and I should go confirm this with my hardware
>> team. The reason why the CS start at dbus3 is that maybe in spi mode
>> the ftdi chip uses adbus 0-2 as miso/mosi/clk... 0xX8 would set dbus
>> 3 as anoutput only, while the libmpsse is using dbus 3-7 as outputs
>> 0xF8. Hmmm seems wrong otherwise the libmpsse is toggling all the
>> chip select lines.
Chaves,> So after talking to my hardware team, seems this makes a very
Chaves,> large difference. On the device that works we have a reset line
Chaves,> on dbus5 that is disconnected currently. On the one that
Chaves,> doesn't work we have a reset line on dbus5 that is
Chaves,> connected. So libFTDI is driving all the lines low and using
Chaves,> them as inputs.
Chaves,> Success!
Good!
Chaves,> I do have one more question, is it possible to use the MPSSE
Chaves,> commands using the virtual com port that opens up on windows?
I don't think so. Setting the MPSSE mode requires access to the USB control
endpoint. Probably while the VCP is open, no other program may talk to the
USB control point. And opening the VCP port probably sets the default mode,
switching away from MPSSE set before...
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
|
