Hello,

Since this is not one of our products, although it utilises our device, I am unable to support it.
Product Manufacturers are responsible for supporting end-users of their products, so you will need to contact μFR.
FTDI cannot control how the USB ICs are used and often has no knowledge of the entire product.
Please see the following document for reference:

http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products.pdf

It does sound though like the FTDI IC being used in this product is working correctly, as you are able to access and issue D2XX commands to the IC and they return without error.

Best Regards,
FTDI Community

Hello,

Perhaps due to unaligned read/write.

An aligned write is a write on the FIFO interface with all byte enables selected, i.e. on a 16-bit interface, an aligned write is 16-bits wide and on a 32-bit interface, an aligned write is 32-bits wide.
 
An unaligned write is a write on the FIFO interface that is not as wide as the interface, i.e. on a 16-bit interface, an unaligned write is a single byte write and on a 32-bit interface, an unaligned write is 1, 2, or 3 bytes.
 
An aligned read is a read from the FIFO interface when the slave asserts all byte enables. On a 16-bit interface, an aligned read is 16-bits wide and on a 32-bit interface, an aligned read is 32-bits wide
 
An unaligned read is a read from the FIFO interface that is not as wide as the interface, i.e. on a 16-bit interface, an unaligned read is a single byte read and on a 32-bit interface, an unaligned read is 1, 2, or 3 bytes. An unaligned read from the slave always signals that it is a short packet

Further details can be found in AN_421 - https://www.ftdichip.com/Support/Documents/AppNotes/AN_412_FT600_FT601%20USB%20Bridge%20chips%20Integration.pdf

Regards,
FTDI Community

Hello,

In 245 Synchronous FIFO mode the TXE_N is an output signal, Transmit FIFO Empty. It is active low and when active it indicates the Transmit FIFO has space and it is ready to receive data from the FIFO master. It indicates there is a minimum, or at least 1 byte of space available.

By the way if you contact support1@ftdichip.com we have a new driver I can provide to you.

Thanks,
FTDI Community

Hello,

Please refer to AN_395 User Guide for LibFT260.

There are also software examples provided with LibFT260 download.

Best Regards,
FTDI Community

Hello,

Thanks for sharing!

Best Regards,
FTDI Community

Hello, if you are using FIFO mode, please see the following Tech Note which should help:

TN_167 FTDI FIFO Basics

Flow control must be set to CTS_RTS in the application, even though these signals are not physically used. This will avoid any data loss.

Are you using Sync or Async FIFO mode?

Are you using known good hardware? Test with C232HD cables, UM232H-B, UM232H.

It's a custom implementation and uses an external hub so is difficult to support. Is the results the same when the USB hub is removed?

Best Regards,
FTDI Community

Hello,

So the development team have informed me that it is actually possible to emulate two screens at once.

They have provided the below initialization code:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                            BT8XXEMU_EmulatorParameters params;
                            BT8XXEMU_defaults(BT8XXEMU_VERSION_API, &params,
#if defined(BT815EMU_MODE)
                                            BT8XXEMU_EmulatorBT815
#elif defined(FT810EMU_MODE)
                                            BT8XXEMU_EmulatorFT810
#else
                                            BT8XXEMU_EmulatorFT801
#endif
                            );

                            params.Flags =
                                            BT8XXEMU_EmulatorEnableKeyboard
                                            | BT8XXEMU_EmulatorEnableMouse
                                            | BT8XXEMU_EmulatorEnableAudio
                                            | BT8XXEMU_EmulatorEnableDebugShortkeys
                                            | BT8XXEMU_EmulatorEnableCoprocessor
                                            | BT8XXEMU_EmulatorEnableGraphicsMultithread
                                            | BT8XXEMU_EmulatorEnableStdOut
                                            | BT8XXEMU_EmulatorEnableMainPerformance
                                            ;
                            params.UserContext = this;

#if defined(BT815EMU_MODE)
                            params.Flash = flash;
#endif

                            BT8XXEMU_run(BT8XXEMU_VERSION_API, &emulator, &params);
                           
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

     More code to implement the read/write EVE by passing the pointers of different instances:


                void swrbegin(size_t address)
                {
                                BT8XXEMU_chipSelect(emulator, 1);

                                BT8XXEMU_transfer(emulator, (2 << 6) | ((address >> 16) & 0x3F));
                                BT8XXEMU_transfer(emulator, (address >> 8) & 0xFF);
                                BT8XXEMU_transfer(emulator, address & 0xFF);
                                // BT8XXEMU_transfer(0x00);
                }

                void swr8(uint8_t value)
                {
                                BT8XXEMU_transfer(emulator, value);
                }

                void swr16(uint16_t value)
                {
                                BT8XXEMU_transfer(emulator, value & 0xFF);
                                BT8XXEMU_transfer(emulator, (value >> 8) & 0xFF);
                }

                void swr32(uint32_t value)
                {
                                BT8XXEMU_transfer(emulator, value & 0xFF);
                                BT8XXEMU_transfer(emulator, (value >> 8) & 0xFF);
                                BT8XXEMU_transfer(emulator, (value >> 16) & 0xFF);
                                BT8XXEMU_transfer(emulator, (value >> 24) & 0xFF);
                }

                void swrend()
                {
                                BT8XXEMU_chipSelect(emulator, 0);
                }

                void wr32(size_t address, uint32_t value)
                {
                                swrbegin(address);
                                swr32(value);
                                swrend();
                }

                uint32_t rd32(size_t address)
                {
                                BT8XXEMU_chipSelect(emulator, 1);

                                BT8XXEMU_transfer(emulator, (address >> 16) & 0x3F);
                                BT8XXEMU_transfer(emulator, (address >> 8) & 0xFF);
                                BT8XXEMU_transfer(emulator, address & 0xFF);
                                BT8XXEMU_transfer(emulator, 0x00);

                                uint32_t value;
                                value = BT8XXEMU_transfer(emulator, 0);
                                value |= BT8XXEMU_transfer(emulator, 0) << 8;
                                value |= BT8XXEMU_transfer(emulator, 0) << 16;
                                value |= BT8XXEMU_transfer(emulator, 0) << 24;

                                BT8XXEMU_chipSelect(emulator, 0);
                                return value;
                }                             

Best Regards,
FTDI Community

The new library 1.1.2 is now released and you can find it on the FT260 product page.
https://www.ftdichip.com/Products/ICs/FT260.html

Direct Link:
https://www.ftdichip.com/Support/SoftwareExamples/LibFT260-v1.1.2.zip

Best Regards, FTDI Community