M52223EVB: USB and Intel 82801EB chipset

[slyy]

We are going to use CMX USB stack for MCF52222X.
While working with it, i've experienced following problem:
-----------------
When connecting the M52223EVB board with PC (IBM ThinkCentre desktop with Intel 82801EB chipset ) using USB, Windows XP SP2 detects new hardware, but couldn't install the driver. Just adds an "Unknown device" with VID_0000&PID_0000 seen from "Device Manager". Doesn't matter if running HID or CDC demo.
-----------------
Trying to solve the problem, researched the web about it a lot, then reinstalled the Windows XP SP2, updated BIOS, updated all drivers from IBM and Intel, tryed different USB ports - but nothing.
Failed also with other ThinkCentres with Windows 2000 SP4 (different models of ThinkCentre, but with Intel 82801EB). Using the same PC's with extra PCI-USB card (VIA chip) works fine.

The board and USB works fine with IBM ThinkCentre with 82801G chipset. So i guess the problem comes with 82801EB.
* 82801EB chipset works with other USB devices.
* CMX USB stack works with other chipsets.
Possible conflict sources:
* USB stack bug which appears only when using with 82801EB (timing e.g.)
* Evaluation board M52223EVB hardware and 82801EB chipset "handshaking".

Anyone knows a fix or workaround for it?

[J2MEJediMaster]

This is a scientific guess, based on Windows XP2 behavior. It may or may not work, but is worth a shot:

1) Unplug the USB cable and reboot.
2) Go to the Device Manager and uninstall the bogus driver (VID_0000&PID_0000).
3) Assuming you have the USB driver software for the cable interface you're using, install that now.
4) Reboot.
5) Now try plugging in the USB cable, and hopefully it will find the correct driver.

XP2 is pretty aggressive about installing a default Microsoft USB driver if it can't find driver software for the device. That driver isn't suitable for what you're doing. What happens is that people plug the USB device first, XP2 puts in a funky USB driver, and then you can't install or XP doesn't recognize the other driver (because it's already installed the bogus driver). You have to have the proper driver software installed before the first-time plug-in of the USB cable.

If that doesn't work, then it certainly looks like the chipset might be the culprit.

---Tom

[slyy]

I think i tried it. I even did reintall the windows.

For example on one clean PC, when connected the board - windows hanged ca 1 minute until windows gave up and didn't even say that it doesn't have driver.

The board doesn't have its own drivers for windows, it just has an inf-file; ; ; it uses usbser.sys std windows driver for CDC demo project. And std windows drivers for HID demo projects.

When i installed a PCI-USB card with VIA chipset to to my PC, where Intel failed, then the driveers for HID and CDC projects were automatically installed - so the problem is not in the windows usb drivers. But maybe in chipset drivers (chipset drivers and bios update didn't help.)