FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  


Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support

New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Pages: [1] 2 3 ... 10
 on: August 03, 2022, 09:00:20 PM 
Started by CTENGR - Last Post by CTENGR
Hi All,

We're looking for someone who knows VNC2 coding to help us. We would happily pay for your services!

We are transitioning from VNC1L to V2DAP and see that the DRD command that allowed 50 ms polling in the VNC1L fails on the VNC2.  There is clearly some code in cmdusb.c that is responsible due to a 250ms wait state loop in unsigned char cmd_drd().

As a Hint we've seen this from FTDIs AN_176 (see attachment), but this is outside of our skills to develop a code fix.

Has anyone used or written code that resolves this?
Would anyone in the group like to help us write in a fix ($)? If so please contact me.

We just want DRD to be able to return valid data @ 50ms during a persons fast typing on a keyboard.

Thank you!

 on: August 01, 2022, 04:28:45 PM 
Started by zanovilla - Last Post by FTDI Community

Which version of the V2DPS firmware are you using?

Note that there is also an SP3 patch for the IDE available:


V2DPS firmware is provided with the IDE which allows customers to customise and debug the firmware:


So it might be worthwhile building the latest version of the code with the IDE and SP3 patch.

Otherwise the hub might not be compatible with the firmware or IC.
Also note that VNC2 only has USB Full Speed Controllers inside the IC.

Best Regards,
FTDI Community

 on: July 29, 2022, 05:08:22 PM 
Started by zanovilla - Last Post by zanovilla
Hello everyone,

I'm working on V2DPS with PORT1 as SLAVE connected to a PC and PORT2 with a BOMS ad all is OK.
Now I attach a USB HUB on PORT2 and QP2 command returns 0x80 correcly.
But when I attach a BOMS or any other device to the HUB, I see always 0x80 !!!!!
Any suggestion?

Thank you!

 on: July 18, 2022, 03:37:23 PM 
Started by ebone4 - Last Post by FTDI Community
OS X has included built-in partial support for some FTDI devices in VCP mode.  Starting with 10.11 (El Capitan), Apple’s own driver seems to be sufficiently comprehensive that many
customers will not need to install FTDI’s own VCP unless they wish to use its advanced features such as baud-rate aliasing and configurable latency times. 

If you have any additional issues or questions it would be better if you could contact your local support team via email.     

FTDI Community

 on: July 16, 2022, 03:18:47 AM 
Started by ebone4 - Last Post by ebone4
Anyone have any ideas?

 on: July 14, 2022, 09:13:24 AM 
Started by rascalito - Last Post by FTDI Community

This is the FTDI Community.

For EVE related questions please post on our Bridgetek Community:


Best Regards,
FTDI Community

 on: July 14, 2022, 08:14:04 AM 
Started by rascalito - Last Post by rascalito

Sorry, just replying to a part of my own post.
Compressing in ASTC format on Ubuntu:
1. Install by
sudo apt install astcenc
2. Run astcenc.
-> This will list a couple of examples which will be good to start before learning how
to tune the bitmaps for a given purpose.

Now the other questions remain: how to choose the right ASTC format.



 on: July 14, 2022, 07:20:48 AM 
Started by rascalito - Last Post by rascalito

I'm using Ubuntu 22.04.
I'm using a lot of bitmaps, and the easiest way to use bitmaps seems to be to compress
them to ASTC, and store them directly in flash.
As the process of adding a new bitmap is quite time consuming, I have made a php script
that takes one raw image and its associated json. It then creates a pair of .h / .c files
and adds a record in a bitmaplist.h / .cp. files.
Now the next step I would like is a way to directly compress my images on Linux.
It also creats in each .h / .cpp file a structure which contains the file name, data pointer, position
in flash, etc... and also spits out the percentage of flash that has been used. And beside this,
drawing a single image is done with a single command with 2 parameters, one being a rectangle,
and the other is this structure.
Rect R(x, y, w, h);
BitmapInfo * bmi = BitmapList->FindBMI("MyLogo");
if(bmi) SysLCD->DrawBitmap(R, bmi);
Is there a command-line tool that I can run from the terminal (and therefore from a php script)?

Next question:
How do I choose an encoding method?
I choosed ASTC8x8 at random and it works, but is there logical way to choose an encoding scheme?

Last one:
I have chosen ASTC8x8. When the bitmap dimensions are mutliple of 8, it's just fine. When not,
the size is rounded up to the next multiple of 8. In this case, what will the added image border
look like?



 on: July 11, 2022, 04:56:29 PM 
Started by cwryu - Last Post by FTDI Community

The location IDs on Linux are just an estimate of where the USB device is. it is not like windows where it is the exact location. there is no way to have it fixed. Although it shouldn't change when you reconnect, there is no guarantee that it won't. i would suggest that you would be better opening the device by description or serial number. Or you could even check where the device is on the USB tree before opening it.   

Best Regards

FTDI Community                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

 on: July 11, 2022, 10:22:46 AM 
Started by kalle - Last Post by patters
The software is EazyLink2, a serial file transfer utility for the Cambridge Z88 computer:

This software requires hardware flow control. It is a multiplatform application built on the Qt5 framework, and it uses the Qt5 Serial Port implementation.

I ended up giving up with the FTDI serial device and bought a Keyspan serial dongle. This works perfectly with EazyLink2. It allows for reliable bidirectional transfers with no errors, which means that the FTDI driver isn't functioning correctly. The money I spent on an FTDI dongle was wasted.

Pages: [1] 2 3 ... 10