Connecting a PC (XP) to a WinCE5.0 device, I can get ASCII data xfer using HyperTerminal(PC,RS232 port COM1)-to-CEterminalprogram(USB host port) when the FTDI driver registry setting “InitialIndex” is set to COM0 (default) or another unused COM port – have verified ports 0,6,7.
Other FTDI registry settings are default. PC-side ActiveSync’s Connection Settings enable “Allow connections to … COM1″
Have added registry settings and ftdi_ser.dll to the BSP image, so they survive a reboot.

However, have not been able to open an ActiveSync connection. When the adapter cable is attached to the CE box, the blue LED on the cable flashes a couple times and a pop-up shows “USB Serial Status. Connecting to host”. The PC side continues to show “Not connected”.

Per another discussion thread, tried to configure a “direct connection” using “Network and Dial-up Connections” wizard on CE, but it will not show COM0,6,7 or in the dropdown, only “COM4:” and “Serial Cable on COM1:”, which are defined by other drivers on the device.

Have tried adding and changing other FTDI registry values per the FTDI readme file:

1) “ActiveSyncSetting”,0×00010001,256128
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

2)Persistant unplug/replug bit -
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Thanks.
Peter

I also got a working solution with two serial ports and only need to use Handera’s driver for the CN50 Vehicle dock. Possibly you have success with that too.

Next time you should provide more details. There is much background information missing. How many ports are already occupied, what does the registry show about active drivers etc, etc….

as you see, your comments will reach the board, but I have to approve all first time poster (due to avoid spammers).

Please go to http://www.ftdichip.com/Drivers/VCP.htm and download the driver from there (DLL file). Then go on and use the documentation and the inf posted here and at ftdichip.com to change it to your needs.

Although windows ce 6 may support another driver load dir, this depends on the decision of the OEM. There may be a syscache or other named dir in persistent storage area to provide additional drivers. Sorry, but you have to find it yourself (search the registry of the device).

regards

Josef

just load the patched driver and with a hex editor change the SER_ to COM_…

ftdi_ser.dll: SER_Close, SER:Deinit, SER_IOControl, SER_Init, SER_Open, SER_Powerup, SER_Read, SER_Seek and SER_Write

and then do the same within the inf file.

BTW: WinCE CabManager runs fine within Wine on my Ubuntu.

or use the newly attached file FTDI_driver_COM.cab

Do you have a copy of the patched driver that will still use COMx and not SERx?

I’m a linux guy trying to get something working on Win Mobile. The patched driver above seems like its working for my FTDI usb-> serial adapter on my pda – but the app i need to use doesn’t look for SERx – just COMx.

Ta!