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 ... 54
1
Hello,

This version of the library has now been released on the website: https://ftdichip.com/software-examples/mpsse-projects/.

The changes and improvements made in this version are shown in the release notes text file in the library download.

FTDI Community

2
Hello,

Please post any new or replies on the BRT Community as Bridgetek support EVE products:

http://www.brtcommunity.com/

Best Regards,
FTDI Community

3
General Discussion / Re: FT813 bin compression algorithm documented?
« on: January 30, 2023, 09:44:57 AM »
Hello,

Please post your question of the BRT Community as Bridgetek support EVE products:

http://www.brtcommunity.com/

Best Regards,
FTDI Community

4
Discussion - Hardware / Re: Start problem on V2DIP1-32
« on: January 20, 2023, 02:49:04 PM »
Hi,

This is likely an issue with your custom firmware, you could try using one of our precompiled firmware like V2DAP, to see if you are seeing the same degradation. You could also use VNC2 tools to debug and analyse. There are some code analysis tools built in. 

you could also try applying the SP3 patch to the VNC2 toolchain, and then rebuild. If you email into support1@ftdichip.com we can give you the details on how to access the patch.

Best Regards

FTDI Community

5
Hi Yvonne,

The only examples can be found here:

C:\Users\Username\Documents\FTDI\Firmware\Samples\V2.0.2-SP2

I'm not sure if there is a HID report ID example, but if there is it will be in that directory. You can also create your own firmware for this purpose. See Vinculum II User Guide.

Best Regards
FTDI Community

6
Hello,

FTDI FIFO Basics has a fully tested example that is compatible with all FTDI devices using FIFO mode. You should try to get this example running first. 

The following documents should help you too:

AN_130 FT2232H Used in an FT245 Style Synchronous FIFO Mode
AN_165 Establishing Synchronous 245 FIFO Communications using a Morph-IC-II
Optimizing D2xx Data Throughput
AN232B-04 Data Throughput, Latency and Handshaking



Best regards,
FTDI Community

7
Hi,

You can reference the example found in C:\Users\Username\Documents\FTDI\Firmware\Samples\V2.0.2-SP2\USBHost\USBHostHID2. This example has been tested with a barcode scanner.

You should also have a look at Vinculum II User Guide. This details the full VNC2 API. See page 270 for the return codes.

Best Regards

FTDI Community

8
Hi,

Try setting the latency timer to 1ms, the default is 16ms.

The 245 FIFO interface should only be written to when the TXE# pin is logic 0.
 
The TXE# pin will go to logic 1 and back to logic 0 for every byte latched in.
 
If the application on the PC never reads any data the buffer on the PC (64kbytes) and the buffer on the chip will become full.
 
When these buffers are full the TXE# line should remain at logic 1 until the application on the PC does a read to free up some space.
 
Some users report TXE# goes back to logic 0 after a brief period (actually matches latency timer).
 
This can result in data loss due to overrun.
 
To prevent this from happening the application on the PC should have set flow control for RTS_CTS flow control.
 
Although the hardware does not have RTS/CTS pins the driver does not know this, but it is now forced to monitor certain status bits, which allows the TXE# pin to be kept at logic 1 until space is made available.
 
Best Regards

FTDI Community

9
Hello,

you should refer to FTDI FIFO Basics. Also, what operating system are you using?

Best Regards,

FTDI Community

10
Hello,

Please refer to our software examples here:

https://ftdichip.com/software-examples/ft600-601-software-examples/

There are Data Loopback and Data Streamer examples available in C# and C++.

Best Regards,
FTDI Community

11
Hello,

This is the correct example to use:

C:\Users\Username\Documents\FTDI\Firmware\Samples\V2.0.2-SP2\General\FirmwareUpdate

Also refer to AN_159 Vinculum-II Firmware Flash Programming for more information.

Please note the restriction in the example readme:

Fragmented ROM files not supported. Do "CHKDSK <filename>" from command line to check.

This has been tested by FTDI and is working.

There may be other FTDI Community users who can help you further.

Best Regards,
FTDI Community

12
Discussion - Software / Re: FT260 changing Baud rate
« on: December 01, 2022, 03:43:28 PM »
Hi,

i tested this for you and i am able to receive the full string at a Baud rate of 9600. See the attached capture. This is what my write looks like:

 // Write data
    ftStatus = FT260_UART_Write(handle, buffer, 10, 10, &dwRealAccessData);
    if (FT260_OK != ftStatus)
    {
        printf("UART Write NG : %d\n", ftStatus);
    }

Best Regards
FTDI Community


13
Discussion - Hardware / Re: VNC2 à la place de VNC1L
« on: December 01, 2022, 10:09:36 AM »
Hello,

You can have a look at VNC2 UART to USB Memory Bridge. This project uses V2DAP firmware and also provides sample code. You can change the Baud rate using FT_PROG. This is shown on page 7 of the pdf.

VNC2 does work differently from VNC1L. Vinculum II User Guide will be able to help you with using the command set. It provides descriptions and examples of the different commands you can use.

Best Regards
FTDI Community




14
Hi,

You can have a look at Establishing Synchronous 245 FIFO Communications using a Morph-IC-II. This gives an example utility you can try, along with some sample code. The sample code can be found here: https://ftdichip.com/wp-content/uploads/2020/12/Synchronous%20245%20Morph-IC-II%20Application.zip.

Best Regards
FTDI Community

15
Discussion - Hardware / Re: FT231X vs. USB-C - doesn't work!
« on: November 29, 2022, 05:00:18 PM »
Hello,

Please see TN_181 Type-C USB Connectors with FTDI Products which should help you.

You are missing 5K1 resistors on the CC1 (A5) and CC2 (B5) lines which are required.

You may have got these mixed up with A8 and B8.

Also there should be 27ohm an 47pF on the USB data lines. I can see 22ohm in your design which is incorrect.
See AN_146 USB Hardware Design Guidelines for FTDI ICs for more details.

Best Regards,
FTDI Community

Pages: [1] 2 3 ... 54