Hi,

Thanks for your question. Please contact our email support via support1@ftdichip.com and we will assist you further.

Regards,
FTDI Community

Hello,

Sorry I ment to say "As previously mentioned the BT815/6 (like the previous FT80x) includes 1MByte of internal graphics RAM, and the same sized RAM_DL which will limit you to ~2000 instructions". I.e. that RAM_DL has not increased so the limit on instructions is the same.

Best Regards,
FTDI Community

Hello,

The FT232BL flow control is handled automatically when configured by the application software.

For example, if you use a terminal program like PuTTY you can set the flow control to RTS/CTS or DSR/DTR.
Once this is set by the application, the flow control signals are automatically controlled by the IC.

Also, FT232B is quite an old IC and not recommended for new designs.
You should consider FT232R or FT-X

Best Regards,
FTDI Community

Hello,

The ESD4 functions are currently only available for the display aspects of the application. At the moment, you would need to edit the code after exporting it in order to pass values from other external peripherals.

You can use the method shown in 'Add User Functions' in the ESD user guide or just edit the code directly after export.

One example of interaction between ESD and other MCU features is the Blink LED demo provided with the ESD4 software. This allows the GUI created to interact with GPIO on the FT900.

Regards, FTDI Community

Hello,

Please can you contact email support on support1@ftdichip.com and we will look into this, the outcome of which we will post here.

Regards,
FTDI Community

Hello,

I believe you also contacted email support with the same issue. Please continue to correspond via that support channel and we will post the resolution here.

Regards,
FTDI Community.

Hi,

After adding commands or data to the co-processor RAM_CMD you must manually write the REG_CMD_WRITE to update it to point to the end of your data. In general, your application writes REG_CMD_WRITE and the co-processor writes the register REG_CMD_READ. Your MCU must keep an accurate count of the number of bytes sent and take account of the wrap around at RAM_CMD + 4095 (effectively it maintains an equivalent count to what the EVE device is doing internally)

If an error occurs, you should follow the steps shown in section 5.6 below:
http://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/ICs/EVE/FT81X_Series_Programmer_Guide.pdf
What cases do you see the pointers remain un-equal? The section mentioned above has some examples where it may happen such as an invalid image format, corrupted image, image de-compress where there isn't enough RAM_G space  to put the resulting data, a blocking call (such as calibrate), a command with invalid parameters (e.g. non multiple of 4 bytes) or it could be an error in the amount by which the MCU increments REG_CMD_WRITE.

For the transparent image, please ensure that the original one displays correctly in a program such as GIMP as the original image may have some non-transparent pixels (e.g. slightly different shade from the transparent colour) where you had expected transparency.

Regards,
FTDI Community

Hello Carlos,

The LibFT4222 Linux Library is for i386, x86_64 and ARMv6-hf which implements the LibFT4222 API, with D2XX built-in.

Our standard Linux D2XX driver is 1.4.8 ARMv6 hard-float is suitable for Raspberry Pi.

So LibFT4222 should be suitable for RPi (ARMv6), though this has never been tested.

Best Regards,
FTDI Community