Relevant Details:
OS: Windows Embedded Compact 7
HW: TI AM3358 processor on TMDXEVM3358 Evaluation Module
BSP: Windows Embedded Compact 7 TI ARM-A8 BSP Version 02.30.00 From Adeneo Embedded
We recently changed our OS to make use of hardware UART4 driver which runs as "COM5:", but then our ActiveSync connection stopped working. I was able to find out through the following links that the USB Serial virtual COM port was configured to be COM5: as well:
http://e2e.ti.com/support/embedded/wince/f/353/t/213068.aspx
http://social.msdn.microsoft.com/Forums/en-US/winembplatdev/thread/b9d3d744-8f53-4478-b04f-d8327274bd46/
I followed the guidance in these posts and changed my C:\WINCE700\platform\SMART_EVM_AM33X_BSP\SRC\DRIVERS\USB\USBFN\usbfn.reg file such that the virtual USB Serial COM port would now be COM7:, but if I have my COM5: hardware port enabled in the system, ActiveSync will not connect. I have attached the usbfn.reg file to this post.
When I open the USB Serial connection under the "Network and Dial-up Connections" window in the Windows Embedded Compact 7 desktop, there is an error pop-up stating "Error from RasDial".
If I disable my COM5: UART driver, ActiveSync works and using the Remote Registry Viewer, I can see that COM7: is indeed Active as part of USB Function Serial, so my changes to the ActiveSync com port number do seem to taking effect.
However, am I missing something else? Has anyone got any ideas why I still might be having what I assume is a clash between using COM5: as a UART driver reference and the ActiveSync USB Serial driver?
