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.

Topics - t0nyl2

Pages: [1]
1
Discussion - Hardware / FT313H Test mode vs Normal mode
« on: May 08, 2020, 03:54:33 PM »
To use the TESTMODE (50h) and TESTPMSET1/2 (70h/74h) on the FT313H, must the TESTEN pin be pulled up?

Is it acceptable to have the TESTEN pulled down externally for normal operation or should it be left floating?

2
Discussion - Hardware / FT313H ASYNC List hang
« on: May 08, 2020, 03:24:04 PM »
I am working on an embedded system trying to use of the FT313H Hi-Speed USB Host Controller. The system uses an ARM based SoC runnning an RTOS and a USB Host Stack from Micro-Digital (smxUSBH). Previous versions of the system used an ISP1761 USB HC. But, I am trying to replace this part with multiple FT313H parts (currently only 1 device is installed). Micro-Digital has provided me with an EHCI compliant Host Controller Driver. However, it must be modified to work with the FT313H.

Currently I am perfectly able to  communicate with the FT313 registers and can successfully access its internal memory via the MEMADDR, DATAPORT and DATASESSION registers.
I can detect insertion of a peripheral device, reset the port, and determine the speed of the peripheral from the registers. But, I am having trouble performing the device enumeration operation when a device is connected.

The driver creates the QH and QTD structures to perform the "Get Device Descriptor" operation, sets the ASYNCADDR register to point to the QH Head and then enables the Async list execution by setting the ASCH_EN (bit 5) of the USBCMD register. But, the device does not seem to complete the operation.

The ASYNCADDR does change to point to the second (terminating) QH. But I cannot tell if it attempted to perform the transfers in the linked QTDs.

I have a Beagle 480 USB Analyzer connected to the port and can not see any valid transfers. I would expect to see a SETUP, IN and OUT packets.

I've tried to use the TESTMODE and TESTPMSET1 registers to send the SETUP packet but I cannot figure how to accomplish this.

I would really appreciate any technical help anyone can provide. I can provide register and memory dumps. I feel that if I can get the first USB operation to complete, I should be able to everything else working.

3
New Member Introductions / Hello FTDI Community
« on: May 08, 2020, 02:55:00 PM »
Hello FTDI Community.
I am new to this forum. I am an EE whose has been in the field for over 30 years.
However, in this unusual time of COVID-19, it is the first time I've been working from home for any extended period.
I'm hoping to get assistance from the participants in the forum.
Thanks for allowing me to participate in your discussions!

Pages: [1]