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 ... 44
1
Discussion - Software / Re: FT602 change resolution
« on: October 06, 2021, 03:18:16 PM »
Hi

Sorry, the only way to change the camera resolution is through the FT602 configuration programmer utility.

Best regards

FTDI Community

2
General Discussion / Re: Ft260q-t instead of ft232r
« on: October 05, 2021, 04:44:38 PM »
Hello,
Link below is for our application note AN_184 - FTDI Device Input Output Pin States.  Page 38 details the FT260 part. 
https://www.ftdichip.com/Support/Documents/AppNotes/AN_184%20FTDI%20Device%20Input%20Output%20Pin%20States.pdf

Regards
FTDI Community

3
General Discussion / Re: Ft260q-t instead of ft232r
« on: October 04, 2021, 04:46:20 PM »
Hello,
Yes, both parts can be used as USB to RS232/RS422/RS485 Converters
https://ftdichip.com/compare-products/?product_cate=18&compare_pr%5B%5D=2074&compare_pr%5B%5D=3757

Regards
FTDI Community

4
Hello,

The SCK line should normally be a push-pull output on this device (unless your code switches the pin to input mode at any time)

What I/O voltage does your MCU use? Is it a 3v3 I/O

We would recommend to check with a scope or logic analyser with analog capability to see what the waveforms are doing,

Best Regards, FTDI Community




5
Hi

Have you made sure to change the EEPROM settings of the device so that it is in self-powered mode? the datasheet states the following:

" Note that in this set-up, the EEPROM should be configured for self-powered operation and the option
“suspend on DBUS7 low” selected in FT_PROG. Also this configuration uses the pin BCBUS7, so this
assumes that MPSSE mode is not selected."

FT_PROG can be downloaded here

Best regards

FTDI Community

6
Discussion - Drivers / Re: VCP driver on macOS 11
« on: September 27, 2021, 01:47:33 PM »
Hello,

That would be the last version of macOS to support .kext drivers, this would be 10.15, but there is an extra notarization step for .kext drivers required by Apple in 10.15, that is not noted in that document. As such it would be safe to assume these instructions work up for drivers up till macOS 10.14.

Best Regards,
FTDI Community

7
Hi

I see the multiplexer you are using has two output channels for each input. are you sure you have configured them correctly, for the clock signal to come out on 2B1? have you tried to see if the signal is on 2B2?

Best regards

FTDI community

8
Hi,

The FT2232H defaults to 2 x UART ports. Using the MPSSE for SPI requires additional commands from the application itself,

The FTDI chipsets are vendor class devices and so require a driver on the host, if you run Linux on the host computer/MCU please ensure the Linux build includes the FTDI driver.

The Linux build may include an sio driver which is part of many distributions. However, MPSSE (for SPI) will require you to load our D2xx drivers which can be obtained from our D2xx drivers page. We have these for various Linux platforms but it will also depend if the Kinetis uses one of our supported processor types,

Best Regards, FTDI Community

9
The simple example requires a hardware loopback so would need a UART device. FT245R is a FIFO device so a loopback is not possible. Here's a description of the example:

Simple example to open a maximum of 4 devices - write some data then read it back.
Shows one method of using list devices also.
Assumes the devices have a loopback connector on them and they also have a serial number.

FT_SetFlowControl is also used for UART devices for UART flow control.

If you are trying to use the FT245R device see TN_167 FTDI FIFO Basics which should help you.

10
Hi


Power Sequence

It is recommended that VCC, VCCIO and RESET# are set at the same time, I would suggest connecting RESET# and VCCIO to 3V3OUT as this will ensure these are set when VCC is powered.
 
Mixing a bus and self-powered design is not recommended.  VCCIO should be connected to either 5V or 3.3V in one of the following configurations:
 
•   Entirely bus powered, that is from the USB port (VCC and VCCIO pins).  In the case where 3.3V IO's are required a local 3.3V regulator is needed which can be supplied from the USB bus.  Alternatively, in some cases, where only a small amount of current is required (< 5mA), it may be possible to use the in-built regulator of the FTDI device (where available) to supply the 3.3V to VCCIO without any other components being required.  In this case, connect VCCIO to the 3V3OUT pin of the FTDI device.
•   Entirely self-powered, that is from the local supply on your board.  In the case where 3.3V IO's are required, you will need 5V and 3.3V to be available on your board.


Crystal Frequency

Section 6.3 of the FT2232H Datasheet gives an example of a 12MHz crystal being connected in the oscillator configuration.


Suspend State
 
You can read about USB Selective Suspend in AN_107 Advanced Driver Options.

We tell the system we're idle and the system puts us in a low power state.

If it is in selective suspend, the next request through the driver will bring it out of suspend.

For example, in a terminal emulator open port, no data for say 5 seconds will put the device into suspend. The next keystroke will generate a write request. When the driver receives that request, it will come out of suspend and send the data.

There is also an additional feature called remote wake-up which can be used to bring the device out of suspend mode:

RI# pin: Ring Indicator Control Input. When remote wake up is enabled in the internal EEPROM taking RI# low (20ms active low pulse) can be used to resume the PC USB host controller from suspend.

Suspend mode can be monitored via the SLEEP# pin.

please let us know f you have any other questions.

Best Regards

FTDI community

11
Discussion - Drivers / Re: VCP driver on macOS 11
« on: September 22, 2021, 03:41:41 PM »
Hello,

Unfortunately we currently only have instructions for the previous .kext version of the driver:
https://ftdichip.com/wp-content/uploads/2020/08/TN_105-Adding-Support-for-New-FTDI-Devices-to-Mac-Driver.pdf

The edits to the info.plist would remain the same in terms of the latency timer and inbuffersize attributes, however Apple stipulating a codeless .dext approach for modifying drivers in macOS 11. The driver team are currently looking into the best way to produce a codeless .dext.

Best Regards,
FTDI Community

12
Hi,
As per the installation guide, the VCP driver is part of the kernel in versions 10.9 and later so it is there by default   

Best Regards
FTDI Community

13
Hello,

Have you unloaded the VCP driver? You need to in order to use the D2xx drivers.
See the Mac OS X Installation Guide for more information.

Best Regards
FTDI Community

14
Hello,

You should try uninstalling the drivers using our CDM uninstaller utility. Then install our windows driver:

https://ftdichip.com/drivers/vcp-drivers/

However Device Descriptor Request Failed usually points to a hardware issue. Please contact your local support team and include your schematics:

https://ftdichip.com/technical-support/

Section 3.2.2 of the device datasheet describes the pin configuration to use the device asynchronous mode.

Best Regards,
FTDI Community

15
Discussion - Drivers / Re: VCP driver on macOS 11
« on: September 20, 2021, 02:12:53 PM »
Hello Scott,

Thank you for the details.
The Latency timer and buffer settings are the correct settings to alter in this case.

However as I'm sure you have noticed performance on different machines can vary, this is due to the inherent nature of USB.

USB products can’t reliably be used in real-time applications with time interval resolution guarantees.

Sometimes the behaviour of USB can be a problem and applications cannot be guaranteed throughput.
If there is more USB traffic then the OS and USB have to schedule the communication with each of the USB devices.
It’s highly dependent on the OS and USB Host and is out with our control.

You could take a look at the following App notes:

Data Throughput, Latency & Handshaking
Optimising D2XX Data Throughput

These apply to all of our USB products.

The latency timer can only be set to 1ms minimum for our High Speed USB products and nothing less, and 2ms for our Full Speed USB products (like FT232R inside the USB-RS485-WE cable).

Best Regards.
FTDI Community

Pages: [1] 2 3 ... 44