Hello,

There are plenty of examples available with the IDE.

Take a look at V2DAP:

C:\Users\Username\Documents\FTDI\Firmware\Samples\V2.0.2-SP2\VNC1L\V2DAP

This would allow a BOMs class device on Port 2 and HID class device on Port1.
You could customise the firmware to meet your needs or create your own custom firmware.

Also refer to the following documents:

Vinculum Firmware User Manual
AN_176 - Vinculum Comparison of VDAP and V2DAP

There may be other users on the forum who could help you further.

Best Regards,
FTDI Community

Hello,

Unfortunately I did not have a chance to before the UK (where I am based) went into lockdown due to the COVID-19 pandemic.
As such I cannot get into the office to acquire the correct EVE board to try this on.

Can you try taking logic captures of the SPI lines? you can decode these and see if the correct data is getting sent to the EVE IC for the second larger font example.

Best Regards,
BRT Community

Hi,

could you reproduce the error? Any news regarding this issue?

Thanks,
Santiago

Hello,

Thanks for you insight, I will pass this on to the development team for their consideration.

Best Regards,
BRT Community

Hello,

OK we have received your email.

You can post any resolution here to help other customers.

Thanks,
FTDI Community

Hello,

Please see AN_428 D2XX EEPROM Programming Examples for some useful information.

Also refer to the D2XX Programmer's Guide.

FT_EEPROM_Read and FT_EEPROM_Program must be used with the FT_X Series.

If you send us an email I can send a simple code example. This forum is limited to 20000 characters so couldn't post it here.

Best Regards,
FTDI Community

Hello,

We cannot support any virtual type system. There can be all sorts of problems that are out of our control.

You can find our supported drivers here:

http://www.ftdichip.com/FTDrivers.htm

If your target OS is Windows or Linux, please use it directly on that OS without any virtual machine.

Error 4 is FT_IO_ERROR.
Error 18 is FT_OTHER_ERROR.

Best Regards,
FTDI Community

Hello,

It is also best to have your application regularly checking the queue status and reading the data from the driver buffer into your own application buffer for processing.

If the driver buffers keep filling up, you will eventually reach a point where either data is lost (if you don't use handshaking lines)     or where the chip is unable to take more data from the attached serial device and de-asserts the flow control (if you use handshaking which we strongly recommend). This would be CTS or DSR for UART and would be TxE for FIFO. In this latter case your serial/FIFO device would need to pause sending and buffer up any data.

We therefore recommend to have your application check the queue status, read however many bytes are reported available if > 0 and then repeat this etc.

Best Regards, FTDI Community

Hello,

Section 6 of the following has an example of using customer fonts:
FT81X Simple PIC Library Examples

Can you show me the section of code where you assign the bitmap properties to your custom font?

Best Regards,
FTDI Community