Hello,

FTDI’s Mac OS X10.15 and macOS 11/12 VCP driver can change the latency timer but you will need to edit the info.plist but this means that the driver would need to be resigned as driver signing is enforced on macOS:

https://ftdichip.com/drivers/vcp-drivers/

See TN_105 Adding Support for New FTDI Devices to Mac Driver.

Signing requires you to join the Apple Dev program and applying for a signing certificate.

The other alternative for MacOS is to use the D2XX drivers. See the Mac OS X Installation Guide and the D2XX Programmer’s Guide and the FT_SetLatencyTimer API.
Example d2xx code is provided with the d2xx driver download.

Best Regards,
FTDI Community

Hi,

Yes you can disable the timeout by setting it to 0.

the FT_SetDivisor function is no longer required because FT_SetBaudRate automatically calculates the divisor based on the baud rate set.

section 3 of this document https://ftdichip.com/wp-content/uploads/2020/08/AN_120_Aliasing_VCP_Baud_Rates.pdf shows how to calculate the divisor for non-standard baud rates.

Best Regards

FTDI Community

Hello,

There are no internal pullups or pulldowns on databus FIFO, RD,WR,OE and SIWU.

This is classed as an I/O pin as per the datasheet so should be pulled up to VCCIO.

I can see that the datasheet instructs to pull this pin up but our evaluation modules don't have such a pullup.

If you can please send an email to your local support office we will be able to contact our R&D team to find out more details about this:

https://ftdichip.com/technical-support/

Best Regards,
FTDI Community

Hello,

The Windows ARM64 driver is now available on our website:

CDM-v2.12.36.4-for-ARM64-Signed-Distributable.zip

You can find this on the VCP and D2xx driver pages under the ARM column.

This supports Windows 10 and Windows 11 only for ARM64 based Windows PCs.

It also works on Mac M1 running Parallels VM with Windows.

Please note that you need to manually install the driver through Device Manager --> Update Driver --> Browse my computer for drivers and point to the downloaded driver files.
Please refer to section 3.3 of the Windows 10/11 Installation Guide.
This has to be performed twice, once for the D2xx interface and then for the VCP interface (COM Port).
If the VCP interface does not appear after installing the D2XX interface, then either use Device Manager to “Scan for hardware changes” or unplug/replug the hardware.

If using Parallels VM on Mac M1 then please note the following:

The device driver files must be on Local disk (C:), as seen by Windows.
The desktop shown in the home window of Parallels is actually the same as the Mac desktop. Windows apps and files run from here, but the device driver files must be located on the “actual” PC.

Best Regards,
FTDI Community

Hi,

The FT232H CBUS Bit-Bang mode is very similar to that of the FT232R device. This mode is useful as it provides up to 4 additional I/O lines in addition to the UART interface. In the FT232H, the four lines associated with this mode are ACBUS9, 8, 6 and 5. The FT_Prog utility should be used to configure the EEPROM to set these CBUS lines to the I/O mode. In the application, FT_SetBitMode can then be used to set the pin directions and values to be written onto the four lines:
 
FT_SetBitMode(FThandle, CBUS, 0x20)

Where 'CBUS' is an 8-bit value. The upper 4 bits specify the directions of the four pins ACBUS 9/8/6/5 (value 1 sets the pin as output). The lower 4 bits specify the value to be written to any pins set as output. The third parameter 0x20 is setting the device to CBUS Bit-Bang mode.

When in CBUS Bit-Bang mode, FT_GetBitMode can also be used to read the values of the four lines:

FT_GetBitMode(FThandle, PIN_VALUES)

Where 'PIN_VALUES' is an 8-bit value returned by the device. Only the lower 4 bits are used - these contain the values read from ACBUS 9/8/6/5.

Note: The CBUS Bit-Bang mode can only be used with the D2xx drivers and is not available through VCP drivers.

For further details, see the following application note:

http://www.ftdichip.com/Support/Documents/AppNotes/AN_232R-01_Bit_Bang_Mode_Available_For_FT232R_and_Ft245R.pdf


we have a number of software examples for C++ and C#.


https://ftdichip.com/software-examples/code-examples/visual-c-examples/
https://ftdichip.com/software-examples/code-examples/csharp-examples/
https://ftdichip.com/software-examples/code-examples/c-builder/

also, here is the D2xx programmers guide:

https://ftdichip.com/wp-content/uploads/2020/08/D2XX_Programmers_GuideFT_000071.pdf

Best Regards,

FTDI Community

Hi,

The L2 format uses two bits per pixel, giving four levels of grayscale per pixel. The stride is the number of bytes which contain one row of the image.  44 bytes will have the data for 176 pixels as you get four pixels per byte.

In general, a font converted (for example by our Asset Builder) will have the characters arranged as a vertical bitmap (one character wide by four tall if you have four letters) if you were to view it as an image (the asset builder outputs a png of the converted font where you can see this).

When displaying the font, make sure to set your format to L2 so that EVE knows how to display it.
If you look through the data then each pixel will be two bits and so look at pairs of bits for each pixel.

What settings did you use in the Asset Builder to convert it and what code were you using to display it?

p.s. We have a new forum for EVE on our BRT Community and so we recommend to post any EVE questions there http://www.brtcommunity.com/index.php?board=7.0

Best Regards, FTDI Community

Hi
You can use the FT Prog utility to read/ program the serial for these parts
https://ftdichip.com/wp-content/uploads/2021/05/FT_Prog_v3.12.11.594%20Installer.zip

Regards
FTDI Community

Hi
I need to check with colleagues but i believe that URB would be accessing the device without/rather than the FTDI driver. 
Have you looked at the D2xx programmers guide to see if there is a relevant function within D2xx?
https://ftdichip.com/wp-content/uploads/2020/08/D2XX_Programmers_GuideFT_000071.pdf

Regards
FTDI Community