Hello Logan,

Yes the following signals are all connected to the programmer module via CN7 which are then connected to PortB of the FT4232H on the UMFTPD2A, so I can see why there would be some contention on the SPI lines:

SPIS0_CLK/GPIO36
SPIS0_SS/GPIO37
SPIS0_MOSI/GPIO38
SPIS0_MISO/GPIO39

As I have mentioned in my emails, please check out the SPI master to SPI slave example in AN_360 FT9xx Example Applications which can be used as a reference.

Best Regards,
FTDI Community

Hello,

I assume you mean 3.1.2?
There is a new version slated for release by the end of the month, I believe this will resolve your issue.

Best Regards,
FTDI Community

Hello,

Thanks for sending a follow up to your question explaining the workaround, I'm sure this will be a good resource for the Community.

Many thanks,
FTDI Community

Hello,

I see that you have also contacted email support where we will deal with your issue and post an outcome here.

Regards,
FTDI Community

Hello,

I'm working with you via email on this.

Please post the solution here which will benefit other users.

Best Regards,

FTDI Community

Hello,

I will need to double check with the development team if it is possible to send host commands to a Cleo board in such a manner, as the FT900 on the Cleo is programmed with a custom firmware which expects Cleo.xxx() commands.

Best Regards,
FTDI Community

Hello,

Can you please try using Ft_Gpu_HostCommand(phost,0x43); and let me know how you get on?

Best Regards,
FTDI Community

Hello,

I’m not familiar with the product that you are using.  Since this is not one of our products, although it may utilise our device, It is difficult to offer any support on it as FTDI cannot control how the USB ICs are used and has no knowledge of the entire product.

Product Manufacturers are responsible for supporting end-users of their products, so you will need to contact the manufacturer directly.  Please see the following document for reference:
http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products.pdf.

With that said however, if they are using our default driver then you may want to try using our latest driver v2.12.28, which is available on our website here:

http://www.ftdichip.com/Drivers/D2XX.htm

You can download the setup executable by clicking on this link. Once installed you should be able to plug in your device and the driver will install. Have a look at our Installation guides here http://www.ftdichip.com/Support/Documents/InstallGuides.htm for further information.

I’m sorry I could not be of further assistance.

Regards,
FTDI Community