USB to Serial connection on Windows CE 6 without ActiveSync RRS feed

  • Question

  • Hi,

    I am trying to use an usb serial connection between my WindowsXP/Linux host
    and my Windows CE 6.0 R3 board without ActiveSync support but I was unable
    to make it work.

    I'm using:
     - Hardware:
      - AT91SAM9261-EK development board with the free BSP provided by ATMEL
     - Software:
      - Windows XP Professional SP3
      - Platform Builder + VS 2005
      - Windows CE 6.0 R3

    On Platform Builder I checked:
     - Device Driver -> USB Function -> USB Function Clients -> Serial
     - 3° Party -> AT91SAM9261EK -> USB Function -> USB Function Driver -> USB Function Driver

    The device registry contains:

       "Manufacturer"="Atmel Manufactor"
     "FriendlyName"="USB Cable Connection"
      "Manufacturer"="Atmel Manufactor"
      "DefaultClientDriver"=- ; erase previous default 
    On the board I can open the "virtual" serial port (I see it as COM4) and read/write on it.
    I attached the usb cable to a Linux Host PC with:
     modprobe usbserial vendor=0x03EB product=0x6119

    I opened a terminal on Linux and everything seems to work fine.

    On Windows, I use the following .inf file:


    1="Windows Install CD"










    ATMEL="ATMEL Corp."
    USBtoSerialConverter="AT91 USB to Serial Converter"
    USBSer="USB Serial Driver"

    I plug the USB cable and Windows detects the device. Unfortunately Windows cannot initialize it
    (a ! appear in Control Panel - ERROR NUMBER 10 - Device cannot start).

    If I change the "DeviceArrayIndex"=dword:0 in [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class] with
    "DeviceArrayIndex"=dword:1 the device is detected (the ! disappear). When I try to use it with Putty an error
    messagge appears (Unable to open serial port!).

    English is not my native language; please excuse typing errors.

    Thanks for your attention.


    Thursday, December 9, 2010 4:03 PM

All replies

  • Hi,

    We are working with the AT91SAM9263-EK and the free BSP from Atmel/Adeneo.

    All BSPs for the SAM9 series are written and maintained by Adeneo. The USBFN driver code is basically the same for both BSPs.

    Though we did not test using the USBFN as SERIAL connection, we got the same Error Code 10 when trying to connect to our desktop systems using USB RNDIS.

    Finally we got a USB hardware logger and found that the driver somehow did not read the number of Bytes returned in a control request correctly.

    Our main problem was that the USBFN driver seemded to work on some of our older systems correctly but on newer machines having an ICore-7 or an AMD chip set, the driver would fail to initialize.

    In the end we had to consult a company specializing in USB drivers to help us re-write the driver.

    I am not allowed to share the code, but you should try reading the UDP Endpoint Control and Status Register more than once to retrieve the number of bytes received as part of a control request.




    Monday, December 13, 2010 10:50 AM
  • Hello,

    We have a similar issue with USB.  I tried re-reading the UDP_CSR register again, but It's not solving our issue.  Our device still cannot start.  Can you offer any more insight>?

    Friday, August 31, 2012 5:11 PM