FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

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

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - FTDI Community

Pages: [1] 2 3 ... 22
1
Discussion - Hardware / Re: FT90x USB Connection Error
« on: October 22, 2019, 04:30:59 PM »
Hello,

It sounds like a problem with your custom hardware.

Also, VID_0000&PID_0002 doesn't match to what the FT905 is associated with.

What firmware is the FT905 running? Have you tried restoring the bootloader using the FT9xx Programming Utility found on your desktop as part of the FT9xx Toolchain?
Which silicon revision are you using? Rev B or the latest Rev C?

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

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

Best Regards,
FTDI Community

2
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

3
Discussion - Hardware / Re: FT232RQ revive
« on: October 15, 2019, 11:01:44 AM »
Hello,

Unfortunately it is not possible to access the EERPOM from the UART side of the IC.

Best Regards,
FTDI Community

4
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

5
Test and Review Area / Re: LibFT260 v1.1.2 Beta
« on: October 11, 2019, 11:33:14 AM »
Hi,

We also have a new example which uses LibFT260 in C#. It includes imports for the I2C functions to allow them to be used in managed code. You can also add the UART ones in a similar way if you require these. Here is a draft version of the document and a beta version of the code below.

AN_438 Draft

AN_438 Beta Code

Note that these are subject to change and provided as a draft version only until fully released to our website,

The example may help if you're looking to create your own C# GUI applications using the FT260 etc.

Remember our Shared Projects section on the forum if you would like to show any of your projects which you make with the FT260.

Best Regards, FTDI Community

6
Discussion - Software / Re: FT260 LibFT260 I2C Flags
« on: October 07, 2019, 04:35:14 PM »
Hello,

Please refer to AN_395 User Guide for LibFT260.

There are also software examples provided with LibFT260 download.

Best Regards,
FTDI Community

7
Discussion - Drivers / Re: FT_Write returning FT_OK but BytesWritten is 0
« on: October 07, 2019, 04:34:49 PM »
Hello,

What are the differences between the old and new CPU models?

The hub is part of the issue, you have mentioned resetting clears the problem.

Please test with our know good hardware. Links to these are in the previous post.

Best Regards,
FTDI Community

8
Discussion - Software / Re: Dual FT813 emulation
« on: October 07, 2019, 01:49:27 PM »
Hello,

Thanks for sharing!

Best Regards,
FTDI Community

9
General Discussion / Re: FT813 Custome Font Text
« on: October 07, 2019, 01:26:36 PM »
Hello,

I will pass this on to the development team so they can look into it.

Best Regards,
FTDI Community

10
Discussion - Drivers / Re: FT_Write returning FT_OK but BytesWritten is 0
« on: October 04, 2019, 03:31:03 PM »
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

11
Hello,

Please contact email support on support1@ftdichip.com

Regards,
FTDI Community

12
Discussion - Software / Re: Dual FT813 emulation
« on: October 04, 2019, 10:08:52 AM »
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:

Code: [Select]
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                            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

13
Discussion - Software / Re: Dual FT813 emulation
« on: October 02, 2019, 03:18:48 PM »
Hello,

Unfortunately it is not possible at this time to emulate two LCDs concurrently.
But I will pass this on to the development team for their consideration.

Best Regards,
FTDI Community.

14
Test and Review Area / Re: LibFT260 v1.1.2 Beta
« on: September 26, 2019, 03:58:19 PM »
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

15
Discussion - Drivers / Re: LibFT260.dll 64-bit
« on: September 26, 2019, 03:57:36 PM »
Hi,
We're pleased to hear it helped,

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

Pages: [1] 2 3 ... 22