Hello,

It sounds like your external EEPROM is not being recognised.

Please email your local support team with your schematics for review:

https://www.ftdichip.com/FTContact.htm

Add an external 93C46 (93C56 or 93C66) EEPROM is recommended.

The EEPROM must be a 16 bit wide configuration such as a Microchip 93LC46B or equivalent capable of a 1Mbit/s clock rate at VCC = +3.00V to 3.6V.
If no EEPROM is connected (or the EEPROM is blank), the FT4232H will default to serial ports, which is what is shown in your post.

Please see our Development Modules for reference:

FT4232H Mini-Module
FT4232H-56 Mini-Module

We have used a 93LC56B external EEPROM.

Please check compatibility of 93LC66D. It seems to have an ORG pin to select 8 or 16 bit wide configuration.
Also from Microchip website: Status: Not Recommended for new designs.

Best Regards,
FTDI Community

Hello,

Which error are you seeing in this case? If you use the GUI version below can you successfully scan the devices or do you get an error?

https://www.ftdichip.com/Support/Utilities/FT_Prog_v3.8.128.448%20Installer.exe

Best Regards, FTDI Community

Hello,

This sounds like a issue with your custom application rather than the FT9xx.
Maybe others in the community will be able to help with your issue, but please note there is a Bridgetek forum available for our MCU products. Please see the link at the top of the page.

Have you tried outputting debug on UART while not in debug mode to help resolve your issue?

Please see our software examples for reference for outputting debug text via the UART interface:

AN_360 FT9xx Example Applications

The difference between debug and release is that the debug build contains debug symbols used by the debugger.

Best Regards,
FTDI Community

Hello,

It is possible to use AC0-AC7 as GPIO but AC8/9 are not controllable in MPSSE mode.

You can use MPSSE bit-bang to implement I2C although it will be slower than the usual MPSSE-assisted I2C as it is entirely bit-banged.

We have a small example below which was originally for FT2232H/FT4232H where users wanted open-drain but as it uses MPSSE bit-bang it may be a starting point. it uses the default I2C pins but you could re-code the values so that it drives other pins instead. if using multiple sets of SDA and SCL you would need to implement the I/O writes as mask values so that using one set of pins does not affect to the others (or have a copy of the functions for each pair of I2C pins and just make all other lines an input in each function and call only one at a time). Note that this is just an unofficial example and is not guaranteed or fully evaluated,

BitBang Example

Alternatively, you can get I2C muxes which allow you to have more than one device of the same address, such as
http://www.ti.com/interface/i2c/switches-and-multiplexers/products.html

Hope one of these help,

Best Regards, FTDI Community

Hello,

Customers using macOS 10.15 Catalina have been experiencing signature issues with FTDI's VCP driver.
The following driver should resolve these issues:

FTDIUSBSerialDriver_v2_4_4.dmg

Please let us know if you have any feedback on this driver by either posting here or emailing us at support1@ftdichip.com


Best Regards,
FTDI Community

Hello,

Is there any news about Apple's re-signing of the driver?

Yes, actually we have just managed to re-sign and notarize our VCP driver package for macOS 10.15.
We still need to do a couple things before we can release this online, update release notes, etc.


Best Regards,
FTDI Community

Hello,

Each time you want to update the screen, you must also have a swap as the display list has two buffers. After writing the new list, you swap that one so that it becomes active and you can edit the other one and so on. Therefore, try adding a swap after your DISPLAY in your main loop at the bottom.


    wr32(RAM_DL + 0, CLEAR_COLOR_RGB(0,0,255)); //CLEAR_COLOR_RGB0,0,0
    wr32(RAM_DL + 4, CLEAR(1,1,1));
    wr32(RAM_DL + 8, DISPLAY);
    wr8(REG_DLSWAP,0x02); 


Best Regards, FTDI Community

Hello,

Glad you've managed to get it working!

Best Regards,
BRT Community.