Hello,

Please have a look at the following Application Note:
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/AN_340_FT800_Optimising-screen-updates-with-Macro-and-Append.pdf

The methods described in this should be helpful for you.

Best Regards,
FTDI Community

Hello,

This is a 3rd party product.  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

Regards,
FTDI Community

Hello,

After programming in FT_Prog did you hit the Cycle Port button?

If you are still having problems can you confirm which of our devices that you are using please? i.e a cable or a development module?

Regards,
FTDI Community

Hello,

Please try with our beta version of LibMPSSE which can be downloaded here:

libMPSSE__0_6_Beta.zip

You may also want to try without the LibMPSSE library and use the D2XX drivers direct. This gives a little more control. Some examples exist here:

https://www.ftdichip.com/Support/SoftwareExamples/MPSSE.htm#SPI

However, this is most likely due to the nature of USB. If there is more USB traffic then the OS and USB have to schedule the communication with each of the USB devices.
It’s highly dependent on the OS and USB Host and is out with our control.
FT2232H use USB Bulk transfers and those are designed to transfer large amounts of data with error-free delivery, but with no guarantee of bandwidth.

Best Regards,
FTDI Community

Hello,

Unfortunately it would not be possible to produce a continuous Clock signal using MPSSE commands. At some point the MPSSE commands would be split across a USB packet, the timing of USB packets is not deterministic and this will result in a pause with your Clock signal. The MPSSE functionality was designed as a clocking engine for data and not to run continuously.


Best Regards,
FTDI Community 

Hi,

We normally recommend to fit the EEPROM and to program it with a string which represents the purpose of the device e.g. "Datalogging Interface" and "Programming Interface". This allows you to easily identify which chip you are opening as well as the port. Other methods relying on location ID or index could have dependency on which physical port the user plugs each chip into and which order they are connected in.

Opening by the description appended with an A or B for the respective port would allow you to easily find and open the correct port without any manual selection by the user.
ftStatus = myFtdiDevice.OpenByDescription("Datalogging Interface B");

Best Regards, FTDI Community

Hello,

Unfortunately these can't be set to particular start-up states in the device itself and so you would need to configure them from the terminal once the port is open. Many terminals have check boxes or menu options for this which can set/clear the lines manually but only once the port is open.

Best Regards, FTDI Community

Hello John,

Yes that would be correct a quick run of the maths for a RGB565 image on a 1366*732 screen works out to roughly 2M Bytes. Such a bitmap would be too large for the internal graphics RAM on the BT81x. The BT81X ICs include support for external flash memory which can be used to store/offload graphics elements such as bitmaps, custom fonts and widgets from the integrated RAM, using ASTC:
You can find out more info at the following page (see programmers guide):
http://brtchip.com/bt81x/

Is there a specific reason you are trying to use a full screen bitmap?

Best Regards,
FTDI Community