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 ... 32
1
Hi,

We are pleased to hear it's working well now,

Best Regards, FTDI Community

2
Hello,

You are already in contact with our support team on this issue via email.
Please post any resolution here to help other customers

Best Regards,
FTDI Community

3
General Discussion / Re: FT230X Flow Control
« on: September 23, 2020, 04:40:29 PM »
Hello,

Flow control is handled by the application program.

For example, with terminal programs like PuTTY or Tera Term there are settings available in the application that allow you to select the type of flow control. These typically use the VCP drivers.

If you wanted to use the D2XX drivers that would involve creating your own application program that would allow you to configure flow control. You can take a look at some software examples here:

https://www.ftdichip.com/Support/SoftwareExamples/CodeExamples.htm

TN_153 Instructions on Including the D2XX Driver in a Visual Studio Express 2013 Project is also useful.

There is no handshaking prior to configuration in software.

Best Regards,
FTDI Community

4
Discussion - Drivers / Re: VCP driver on macOS 11
« on: September 22, 2020, 03:56:28 PM »
Hello,

We have a few products using the default FTDI vendor ID with our own PID (granted by FTDI some years back). Will our VID/PID combination also work in the upcoming .dext driver?

If your VID/PID combination is currently included in our macOS VCP driver's Info.plist file then yes it will be included in the .dext version of the driver.

Best Regards,
FTDI Community

5
Hi,

Could you send us a screenshot of your config tool window please,

You can post here or you can send to support1@ftdichip.com if you would prefer and we'll check it out,

Best Regards, FTDI Community

6
Discussion - Drivers / Re: VCP driver on macOS 11
« on: September 18, 2020, 10:45:48 AM »
Hello,

I see that your device is using the Product ID (PID): 0xEEEF with our default FTDI Vendor ID (VID): 0x0403.
This VID/PID combination is included in our VCP driver (FTDIUSBSerialDriver.kext), however it is not included in the inbuilt Apple VCP driver (AppleUSBTDI.dext).

Unfortunately at this time we do not have a .dext version driver available for macOS 11 Big Sur, but we hope to have this available shortly.

Best Regards,
FTDI Community

7
Discussion - Drivers / Re: VCP driver on macOS 11
« on: September 14, 2020, 03:43:59 PM »
Hello,

I am unfamiliar with the Microham USB Interface III, could you share its details from the hardware monitor similar to the attached screenshot?

Best Regards,
FTDI Community

8
Discussion - Drivers / Re: VCP driver on macOS 11
« on: September 11, 2020, 12:57:48 PM »
Hello,

We are currently working on a .dext version of the driver to be compatible with the newer versions of macOS.
 
However in macOS 10 Apple distributed a VCP driver built into the OS which works for all standard FTDI devices, this was called AppleUSBFTDI.kext pre-Catalina and AppleUSBFTDI.dext in Catalina. I haven’t had a chance to look at macOS 11 yet, but I believe the inbuilt apple driver should still be included.


Best Regards,
FTDI Community

9
Hello,

The data being clocked out of the FT2232H will be at 60Mhz, so a device clocked at 22Mhz would not be able to control this byte by byte. As long as you account for the clock mismatch in your buffering solution you should be able to use the RD# signal to pause the datastream whilst the target device reads from the buffer. I would suggest buying a development module to test your design.

Best Regards,
FTDI Community

10
Hello,

The signals used in the FT245 Sync FIFO mode are not traditional flow control signals, so I wouldn't be able to guarantee no data loss would occur. I am also curious about your proposed configuration, could you expand on what you mean by "attach another dual port FIFO for clock synchronisation and when the external FIFO is full to drive the RD# signal"?

Best Regards,
FTDI Community

11
Hello,

When in synchronous mode, data is transferred on every clock that RXF# and RD# are both low.
I wouldn't recommend using RD# as a flow control signal, but data will not be transferred if the RD# signal remains high.

When RXF# is low, there is data available in the FIFO which can be read by driving RD# low.

Best Regards,
FTDI Community

12
Discussion - Software / Re: Basic Question - Image overlap
« on: September 04, 2020, 04:31:37 PM »
Hello,

It looks like you have loaded both images into the same section of RAM_G:
Gpu_Hal_WrCmdBufFromFlash(phost, p, imgSize);

You need to load these concurrently into RAM_G.
I would suggest loading both images into RAM_G at the beginning of your code, then you can select the desired image to be displayed upon touch. this should mitigate any issues with loading times for the images to RAM_G.

Best Regards,
FTDI Community

13
General Discussion / Re: Regarding V2DIP2
« on: September 04, 2020, 04:22:15 PM »
Hello,

V2DIP2 is supplied with V2DAP firmware pre-programmed, but please check you have the latest version.
The latest version is supplied with the Vinculum-II Tools at the following location on the PC:

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

Please refer to the Vinculum Firmware User Manual for usage.
Also see AN_176 - Vinculum Comparison of VDAP and V2DAP, as V2DAP is a port of VDAP.

Also note that on the UART side you will also require to connect the flow control signals (CTS/RTS) and this should be set by the UART application.

You can only host 2 x FT232R which will allow you to read from either of them and use one of them at a time in data mode.
It will never bridge between them though.

The VNC2 is quite a mature product.
Hosting FT232 devices with these older Vinculum/Vinculum-II products can be unreliable.
It takes a lot of the MCUs resources to run the FT232 device code so there can be performance issues.
I wouldn’t recommend using these products for this application.

The latest MCU FT90x has similar features to VNC2 and is actively supported from R&D, so you might want to consider this product.

Take a look at FT90x UART to FT232 Host Bridge, there is already a software example which can host FTDI devices.
A video has been created which demonstrates this:

https://youtu.be/_vwOKFaOcJI

There are significant benefits of FT90x over VNC2:

-Eclipse based IDE
-Source code for API drivers is provided
-Significant performance improvement
-Firmware updates over USB DFU
-Improved documentation and examples

We provide a free FT9xx Toolchain and FT9xx Development Modules.

If you need local support see Contact Us.

Best Regards,
FTDI Community

14
Discussion - Hardware / Re: FT4232H_I2C connection
« on: September 04, 2020, 04:21:05 PM »
Hello,

Example code of bit bang/GPIO is shown in the documents linked in the previous post.

Best Regards,
FTDI Community

15
Discussion - Software / Re: FT800 Bitmap Colour Inversion
« on: September 04, 2020, 03:56:07 PM »
Hello,

Thanks for providing an example of the icons.
As these are quite basic two colour images you have a couple options to achieve the inverted image.

The first and simplest option would be to use a bitmap format that uses less bits per pixel for these icon, this should allow you to fit both the normal and inverted icons into RAM_G. For example if you were to use L4 bitmaps these would take up 1/4 of the space in RAM_G that a RG565 bitmap would occupy.

The following should be useful for you:
AN_314 FT800 Advanced Technologies - Working with Bitmaps

You could also look into using bitmap cells with L1/L4 bitmaps so that both the inverted and non inverted icon are loaded into RAM_G as one bitmap, please see the above Application Note.

The final option would be to use a bitmap format which supports the Alpha channel (such as ARGB2). This way you would create the icon with a transparent background, after which you can colour the arrow and background when placing the bitmap on your display.


Best Regards,
FTDI Community

Pages: [1] 2 3 ... 32