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

Pages: [1]
1
Discussion - Drivers / FT4232H SN missing A/B/C/D
« on: April 29, 2021, 05:38:21 PM »
Dear FTDI community,
I worked on a project in a Windows 10 environment. I identify the four ports by their serialnumbers, e.g. GM5K3KQXA, GM5K3KQXB, GM5K3KQXC, GM5K3KQXD.
Now I migrated to a Raspberry, and the very same commands do not return the full serial number, but omit the A,B,C,D.
Does anyone have an explanation for this, and maybe an easy way out?
Thanks,
Johannes


This is what serial.tools.list_ports.comports() returns (after formatting):



DEBUG:programming.uartProgramming:Found the following ports with FT232R parts:
DEBUG:programming.uartProgramming:{
  "device": "/dev/ttyUSB4",
  "name": "ttyUSB4",
  "description": "USB <-> Serial Converter",
  "hwid": "USB VID:PID=0403:6011 SER=GM5K3KQX LOCATION=1-1.3:1.3",
  "vid": 1027,
  "pid": 24593,
  "serial_number": "GM5K3KQX",
  "location": "1-1.3:1.3",
  "manufacturer": "FTDI",
  "product": "USB <-> Serial Converter",
  "interface": null,
  "usb_device_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3",
  "device_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.3/ttyUSB4",
  "subsystem": "usb-serial",
  "usb_interface_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.3"
}
DEBUG:programming.uartProgramming:Found SN: GM5K3KQX
DEBUG:programming.uartProgramming:{
  "device": "/dev/ttyUSB3",
  "name": "ttyUSB3",
  "description": "USB <-> Serial Converter",
  "hwid": "USB VID:PID=0403:6011 SER=GM5K3KQX LOCATION=1-1.3:1.2",
  "vid": 1027,
  "pid": 24593,
  "serial_number": "GM5K3KQX",
  "location": "1-1.3:1.2",
  "manufacturer": "FTDI",
  "product": "USB <-> Serial Converter",
  "interface": null,
  "usb_device_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3",
  "device_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.2/ttyUSB3",
  "subsystem": "usb-serial",
  "usb_interface_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.2"
}
DEBUG:programming.uartProgramming:Found SN: GM5K3KQX
DEBUG:programming.uartProgramming:{
  "device": "/dev/ttyUSB2",
  "name": "ttyUSB2",
  "description": "USB <-> Serial Converter",
  "hwid": "USB VID:PID=0403:6011 SER=GM5K3KQX LOCATION=1-1.3:1.1",
  "vid": 1027,
  "pid": 24593,
  "serial_number": "GM5K3KQX",
  "location": "1-1.3:1.1",
  "manufacturer": "FTDI",
  "product": "USB <-> Serial Converter",
  "interface": null,
  "usb_device_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3",
  "device_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/ttyUSB2",
  "subsystem": "usb-serial",
  "usb_interface_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1"
}
DEBUG:programming.uartProgramming:Found SN: GM5K3KQX
DEBUG:programming.uartProgramming:{
  "device": "/dev/ttyUSB1",
  "name": "ttyUSB1",
  "description": "USB <-> Serial Converter",
  "hwid": "USB VID:PID=0403:6011 SER=GM5K3KQX LOCATION=1-1.3:1.0",
  "vid": 1027,
  "pid": 24593,
  "serial_number": "GM5K3KQX",
  "location": "1-1.3:1.0",
  "manufacturer": "FTDI",
  "product": "USB <-> Serial Converter",
  "interface": null,
  "usb_device_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3",
  "device_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/ttyUSB1",
  "subsystem": "usb-serial",
  "usb_interface_path": "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0"
}

2
Discussion - Hardware / FT4232H not enumerating
« on: February 11, 2021, 10:39:35 AM »
Dear FTDI community members,
this is my first time posting in the community, and I hope I have debugged my design with enough care to be eligible to ask for your support.
My background in PCB development is 5+ years.

I have uploaded a PDF showing the schematic, screenshots of the four PCB layers, the Altium PCB file, a photograph of the board, and the USB Treeview log.
Unfortunately the size restrictions for the attachments make it impossible to upload them all here. Please find them in this owndrive share with Password "ftdi":
https://uni-bonn.sciebo.de/s/lRxJRAeBovjzGSR

My goal is to build a USB-4x-UART bridge, and I believe I followed the datasheet section 6.1 in my implementation.
Please note:
(1.1) The circuit "USB power" is not populated since it could not work like that. Instead, VUSBPRE and VUSBSW are directly connected.
(1.2) The lines TX/RX 1...4 are open at the moment.

What I see is that the device is not enumerating. Please find the output of USB TreeView attached.

Things I verified
(2.1) 3.3V and 1.8V are present. No ringing or noise on the power lines, also not after the ferrites.
(2.2) Quartz is running with 12MHz.
(2.3) Resetn is high.
(2.4) At powerup current briefly goes up to around 70mA as expected, then drops to below 1mA.

Things I have tried
(3.1) Populate a second board with the same design. The result is the same. This leads me to believe that a hardware defect is unlikely, as I used new components.
(3.2) Changing cap sizes for the quartz, since I misinterpreted the unregular operation of the quartz for a defect (when in fact I probably just observed the FT4232 going to sleep after unsuccessful connetion to the host, and attempting re-enumeration).
(3.3) The circuit is self-powered, 3.3V are supplied from a TPS73801 throught the 5V USB supply. This part was working with a previous FT232X prototype. Still I have tried to supply 3.3V externaly with a lab supply, but the result is unchanged.
(3.4) Try different USB ports, also directly attached (without hub). Try differenct computer.
(3.5) Remove EEPROM and adjacent resistors (this is shown on the photograph). No change.
(3.6) Try different USB cables.
(3.7) Repeatedly plug in/out.
(3.8) Remove USB_SH from board GND (hence the scrateches aroudn the USB connector)

Things I suspect
(4.1) The clock traces in L2 right below the EECS and EECLK pads are certainly not ideal. Did I say 5+ years of experience? Well...

I am looking forward to any ideas you might have.

Thanks,
Johannes

3
New Member Introductions / Hello from Germany
« on: February 11, 2021, 10:33:27 AM »
Dear FTDI community,
I am Johannes from Germany, and I work on small projects for a US-based company in the health sector.
I use FTDI chips as UART bridge to program ARM microcontrollers. Today I signed up for the community after I met some challenges with a FT4232 design. My previous experience includes successful implementation and operation with FT232X and the UM232H board.
I am looking forward to discussions!
Thanks,
Johannes

Pages: [1]