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 - cioma

Pages: [1] 2
1
I believe you can switch between UART and MPSSE (I2C/SPI/JTAG) modes in software using set_bit_mode USB control request but I don't know if it's exposed in FTDI drivers.

2
Discussion - Software / Re: FT2232H JTAG TCK Clock Speed
« on: April 19, 2024, 11:49:21 AM »
I've been working with FT2232H a lot but I don't use FTDI drivers, instead I work directly through libusb.

Quote
1. Does FT2232H support 30MHz at JTAG-TCK?

IIRC, yes, I think I measured it at some point.


Quote
2. Is it required for platform to provide 60MHz clock to FTDI or 12MHz crystal is sufficient? Or any other hardware change required?

12 MHz crystal is sufficient, nothing else is needed in HW.


Quote
3. Any reference driver/test to enable FT2232H JTAG TCK operating at 30MHz?

These are notes from my code:

Master clock is 60 MHz after /5 clock divider is disabled
required_clock = master_clock / (2 * (divider + 1))
divider = master_clock / required_clock / 2 - 1

If you set it to 30 MHz but actually measure 6 MHz then the /5 clock divider is enabled.


3
Indeed, it's only FT232H, FT2232H, FT4232H (and their variants with USB PD) that have MPSSE which IMHO is much more capable, flexible and controllable than fixed SPI/I2C engines in FT4222H.

4
Reversing (swapping) of UART RX and TX is not possible in the FT2232H

5
Discussion - Software / Re: Delay Between CLK and MOSI Operation
« on: July 22, 2021, 05:44:16 PM »
I don't think this timing is controllable as this is just a propagation delay between the edge of the clock signal and the change in the data signal synchronized by that clock.
And I don't think you need to control it in your design either.
What SPI device are you trying to communicate with?

6
FTDI News / Re: New Power Delivery High Speed USB Devices
« on: July 20, 2021, 12:00:36 PM »
Is there a document describing differences between the old FT232H/FT2232H/FT4232H and the new chips?
E.g. is the availability of Type-C/PD3.0 Controller is the only difference with all the rest being exactly the same?

7
So if we don't use FTDI drivers then there is no need for us to enable RTS_CTS flow control when using MPSSE, correct?

8
General Discussion / Re: Programming Altera Cyclone II using FT232H
« on: January 09, 2021, 11:11:56 AM »
Try UrJTAG

9
Discussion - Hardware / Re: Programming Altera Cyclone II using FT232H
« on: January 09, 2021, 11:08:02 AM »
Try UrJTAG

10
Discussion - Hardware / Re: FT230XS
« on: January 09, 2021, 10:37:59 AM »
It's a known phenomenon in electronics: unpowered chip gets powered trough its internal ESD protection diodes when its signals are driven high.
The right way to deal with it is to use buffers with so-called Ioff feature (e.g. TI SN74AUP1G34) or a dual-supply voltage translators (e.g. ON FXMA2102).
Using series high-value resistors is not ideal as it will make signal edges very slow.

11
Discussion - Hardware / Re: Future of FT232H, FT2232H, FT4232H?
« on: November 24, 2020, 11:27:36 AM »
Thanks for the information.

But what I really interested in is MPSSE engine so FT4222H is not suitable for my needs as I need JTAG, I2C, SPI, Microwire, MDIO interfaces.

12
Discussion - Hardware / Future of FT232H, FT2232H, FT4232H?
« on: October 24, 2020, 12:02:11 PM »
Could FTDI please let us know if they are going to release new devices similar to FT232H, FT2232H, FT4232H in the future?

My ideal devices would be:

- High-speed USB
- 1, 2, 4, 8 channel device variants
- UART, MPSSE, bit bang on every channel
- xDBUS[7:0] ports only, no need for xCBUS[7:0] ports
- At least 8 kByte RX FIFO buffer and 8 kByte TX FIFO buffer for each channel
- At least 100 MHz internal clock (vs the current 60 MHz)
- Each port pin shall be independently configurable as open-drain
- Support for all SPI modes
- Support for I2C clock stretching
- Support for I2C multi-master
- Small QFN package with 0.5 mm pin pitch

13
Discussion - Drivers / FT60x protocol documentation
« on: September 21, 2020, 12:22:04 PM »
Assuming FTDI is interested in selling more chips it would be great if they opened their FT60x protocol documentation (and the same for other chips too).
We know we can use FTDI drivers but many of us would like to write clean code in selected language using generic libraries (e.g. libusb).
Just a thought :)

14
Discussion - Hardware / Re: FT4232H_I2C connection
« on: September 03, 2020, 05:27:04 PM »
Pinouts for FT232H, FT2232H, FT4232H MPSSE

Pin        JTAG  SPI   I2C
D0, output TCK   SCK   SCL
D1, output TDI   MOSI  SDAO
D2, input  TDO   MISO  SDAI
D3, output TMS   SS#   no connection

15
If my FT231X CBUS[0:3] pins are configured as "GPIO" in MTP can I control them (configure as input or output, write and read pin values) from Java D2xx library for Android?

Pages: [1] 2