Reve,

Once I figured out (with the help of my engineer buddy) that you use the USB OTG connector and cable (The little itty bitty one next to the audio jacks) for ActiveSync instead of the type B connector (near the power jack) it worked fine.

A word about this in the readme for the usbf driver would have been nice, especially for folks like us who have been working with the PXA board for months.

Did the Windows host find new hardware when you plugged it in? Is it showing up in Device Manager? On my system it makes a new folder in Device Manager called 'Windows CE USB Devices'. And inside that the device is called 'Microsoft USB Sync'.

My first attempt at an OS image, ActiveSync seems to work, but neither the HID mouse and keyboard, nor the touchscreen work at all. I get a who mess of error messages about the PMIC driver in the debug output.

-Kevin

The device is detected when I use the type B connector - thanks. Yet, it isn't recognized as Windows CE device and Activesync doesn't see it.

An other idea ?

Quote:
The device is detected when I use the type B connector - thanks. Yet, it isn't recognized as Windows CE device and Activesync doesn't see it.

Reve,
Did you try the DEV image from LPD with the Mini connector?

I've been testing ActiveSync all morning. I have loaded the DEV image 10 times using the CF card and the non-Kitl command line params.

It successfully connected all 10 times when I booted first and then put in the USB cable.


Then I took my own OS image, and tried the same test. I booted my image 14 times; It connected twice. The other twelve times I get a message on the Windows XP host:

[color=blue:3ay177lq]USB Device Not Recognized
One of the USB devices attached to this computer has
malfunctioned, and Windows does not recognize it.
...

Also, I notice that when my image does connect (a rare event), I can pull the plug and re-insert it 10 times and it will connect every time. On my image, every time it connects (not very often) I get a debug message:


[color=green:3ay177lq]AUTORAS:: Dialer notifies: [1] [Dialer Start]
Posting WM_NETCONNECT(TRUE) message
AUTORAS:: Dialer notifies: [4] [Dialer Connected]


When I boot and it does not work, I get no WinCE debug messages at all in response to plugging in the USB cable.

-Kevin

Right, activesync works with the sample image. I haven't disable kitl.

I'll try with my OS image on monday.