Windows Mobile: Install FTDI_SER serial to USB adapter
- Mobile Phones Deposit High quality Huawei Mate X 5G smart cell phone 8GB+512GB China Original Flexible Full Body Screen Huawei mobile phones $ 50.00.
- Smart phones serial terminal program. USB equipment using Silicon Laboratories CP210X, FTDI FT232 and Prolific PL2303, CDC/ACM UART to USB Bridge chips can be used to connect to your smart phone.
- How to unlock your phone for free? Software update v2.29.19 for Sigma box and Sigma key: Software update v2.29.18 for Sigma box and Sigma key: Software update v2.29.17 for Sigma box and Sigma key: Direct unlock for LG T-mobile / Metro PCS models using Z3X server credits: APPLE EFI - ISP adapter for HD Box: Octoplus update.
- ESP8266 and Relay Control Using Smartphone: This instruction describes ESP8266 microcontroller start-up to control by smartphone a relay connected to the ESP. In a separate instruction I will try to present a similar case, but instead of the ESP8266 microcontroller we will use Raspberry PI ve.
Sometime you may need additional serial connectors for your windows mobile device. Here is the odyssey I had with a FTDI adapter:
The FT311D system allows providers to enhance connectivity to the mobile ecosystem with the ability to create applications that capitalize on the Android platform's resources such as high-performance processing, accelerometers, and touchscreen interfaces.
How I installed a FTDI serial to USB adapter within ITC CN50 running Windows Mobile 6.1.
Although the USB to Serial adapters with FTDI chips can be installed with drivers from FTDI, these will not work out of the box with WM6.1.
Initial Test with CN50
First I copied the Armv4 driver files ftdi_ser.dll and FTDIPORT.INF to Windows on the device.
Inserted a Micro USB/B to USB A host connector (Digikey H11576-ND)
Inserted the USB2SER adapter “US232R-10 – Premium USB – RS232 Serial Converter Cable“
The device prompts for the driver name and I typed “ftdi_ser.dll” although it should not do so, as I copied the files previously. See also
Then I started to try to communicate using COM10 (verified with registry). But there was no communication possible. The VCP test application did not list any port to open, so I entered COM10: (or SER0 for patched driver) but without success.
I also tested without success using a Loopback adapter as described here http://www.airborn.com.au/serial/rs232.html:
Using the VCP PC drivers for WinXP the serial adapter worked fine, so the hardwware is not faulty.
I also tested on CN3 (WM6.1) at the dock connector without the micro-USB cable. But this did also not work.
Finally I tested on a WinCE5 device (CK61) and this worked OK. So I compared the registry of WinCE5 and WM6.1 after driver install and adapter connection. I found the following (red) keys are missing on the WM6.1 device and so I added them manually:
Using this registry changes and after reinserting the adapter, I was able to communicate using the patched driver, where all COM was replaced with SER. Maybe the original driver will work too, it uses COM10 as port, where the patched driver uses SER0.
VCP test tool
Although the VCP Test application is not the best in regards of error checking (you can enter whatever you want for port and it always makes you think it was able to open the port), I include it here only for completeness.
Original VCP test tool: http://www.ftdichip.com/Projects/CodeExamples/VC++/VCPTest_vcpp.zip
Patched Driver: FTDI driver install cab using the standard COM prefix and not SER (838 downloads) UPDATED 13.02.2021
Same driver as cab with COM instead of SER: FTDI (CE ARM) patched driver (1975 downloads) UPDATED 13.02.2021
Here is the source code of the modded VCP test tool: Modded VCP test tool (1190 downloads) UPDTAED 13.02.2021
Additional links
Link to Installation guides: http://www.ftdichip.com/Documents/InstallGuides.htm
The CE installation guide: http://www.ftdichip.com/Documents/InstallGuides/Windows_CE_Installation_Guide.pdf
Update 23. march 2011: Anyone looking for a two port solution? Try the drivers provided by Handera (SD50).
Table of Contents
You can only test ONE CABLE at a time
Plug in the cable into your computer (we will use Windows)
Go to the Device Manager (From the Start Menu, select Settings→Control Panel. Double click on System and select the Hardware tab. Then click on the Device Manager button)
When plugging in a USB cable, the window will refresh and you will see USB Serial Port (COMx)
If the new COM port doesn't show up, there is a problem with the cable
This is the end of your FTDI Cable
We added breakout wires to make it easy to measure voltages
Test voltage between black and red wires - it must be 5V
Test voltage between black and orange wires - it must be 3.3V (NOT 5V)
If test voltages are not 5V and 3.3V, the cable is bad
Download X-CTU: http://ftp1.digi.com/support/utilities/40002637_c.exe
Install software
Start up software
Select the COM port that says USB SERIAL PORT
Click on TERMINAL tab
Test TX is not shorted to RX
FTDI cable has nothing attached to it
Type text into terminal window. All text should be blue. If red text appears, the cable is bad.
When done, click Clear Screen
Test RX and TX
Connect 100 ohm resistor between orange and yellow wires
Type text into terminal window, all characters will appear in blue AND red
If red text does not appear, cable is bad
We will test the CTS pin. Connect 100 ohm resistor between brown and red wires
On terminal, CTS box is black. If it is not black, cable is bad.
Now connect 100 ohm resistor between brown and black wires
On terminal, CTS box is green. If it is not green, cable is bad.
RTS short test
FTDI cable has nothing attached to it
Look at window, make sure RTS box is clicked and CTS is BLACK. If CTS is green, cable is bad
RTS function test
Put 100 ohm resistor between Green and Brown wires
When RTS box is clicked, CTS box is GREEN
When RTS box is not clicked, CTS box is BLACK
Ftdi Mobile Phones & Portable Devices Driver Download For Windows 10 Pro
If CTS box does not change color from black to green , cable is bad