Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 01 Oct 2003 09:37 AM by  skochan
Deploying from Visual Studio.Net 2003 via ActiveSync?
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
skochan
New Member
New Member
Posts:


--
25 Sep 2003 12:30 AM
    Anyone,

    I wish to start development wih VS.Net 2003 using ActiveSync to deploy. So far I have successfully created a Mobile Handheld device with the 12.1" display and graphical shell (release - no debug) - no problem. I've added the ActiveSync, KITL, and TCP/IP Transport features to the build. In addition, I've edited the lpd_LH7A400_USBF_beta_001.reg file to "StartRepllog"=dword:1. What appears to happen is that the Repllog crashes silently even when run manually from Platform Builder. On the desktop side, ActiveSync cannot find a device (even with unplugging the usb port several times. If I could fit the debug version into RAM, I'd be able to trace the contention (working on this).

    Does anyone have a good white paper describing configuring ActiveSync in Platform Builder that will work with VS.Net 2003?

    Does anyone have any tips for building the tiniest display device that will fit a debug image (I don't need the I-explorer components)?

    Cheers,
    Scott
    mikea@logicpd.com
    New Member
    New Member
    Posts:


    --
    26 Sep 2003 08:09 AM
    Scott,
    There are several components that are required for Active Sync on the CE device.
    -The Active Sync Application
    - TAPI
    - Dial Up Networking
    - Networking User Interface

    - A400 USB Function Driver

    Also, you will need the PC driver for this device. You can verify that it is installed correctly by plugging in the CE device and checking your Device Manager on your PC to see that it detects the device. (It shouldn't say unknown device)

    Thanks,
    Mike A.
    skochan
    New Member
    New Member
    Posts:


    --
    28 Sep 2003 04:31 PM
    Thanks Mike,

    I think my first step is to get the host side properly device drivered. I took a look at the wceusbh.inf file and edited the following:

    [Manufacturer]
    %LogicPD% = LogicPD

    [LogicPD]
    %USB\Vid_9753&Pid_4940.DeviceDesc% = Host_Inst, USB\Vid_9753&Pid_4940

    LogicPD = "LogicPD"
    USB\Vid_9753&Pid_4940.DeviceDesc = "LogicPD USB Sync"

    I have no idea what the vendor and product ID's should be, any ideas? I've scanned over 3000 files - you'd think it would be in an obvious device.h file. Perhaps I don't quite understand how plug and play works.

    Can anyone recomend an excellent USB bus analyzer?

    Cheers,
    Scott
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    29 Sep 2003 09:14 AM
    Skochan,

    The wceusbsh.inf file should be populated with the following settings:


    ; <VENDOR SECTION>
    ;
    ; 1 of 3.
    ; Add your manufacturer name here (and a string definition under [strings] below)
    ;
    ; e.g.
    ; %ACME%=ACME
    ;
    [Manufacturer]
    %Sharp% = Sharp

    ;
    ; <VENDOR SECTION>
    ;
    ; 2 of 3.
    ; Add your manufacturer section and device entry here.
    ; Use the hardware PnP ID of your device.
    ;
    ; e.g.
    ; [ACME]
    ; %USB\VID_xxxx&PID_yyyy.DeviceDesc% = Host_Inst, USB\VID_xxxx&PID_yyyy
    [Sharp]
    %USB\Vid_04E6&Pid_0000.DeviceDesc% = Host_Inst, USB\Vid_04E6&Pid_0000

    ;
    ; <VENDOR SECTION>
    ;
    ; 3 of 3.
    ; Define your strings here
    ;
    ; e.g.
    ; ACME = "ACME"
    ; USB\VID_xxxx&PID_yyyy.DeviceDesc = "ACME USB Sync"
    Sharp = "Sharp"
    USB\Vid_04E6&Pid_0000.DeviceDesc = "Sharp USB Sync"


    Since the USB function module is resident on the Sharp A400 processor, we are using Sharp-centric USB identifiers.

    Regards,
    --mikee

    P.S. I will be working on a more complete posting today. ActiveSync can be very frustrating. The good new is that once it works, it normally continues to work.
    skochan
    New Member
    New Member
    Posts:


    --
    01 Oct 2003 09:37 AM
    Thanks again Mike,

    The Vid and Pid worked fine. My desktop now recognizes the hardware as a WindowsCE USB Device from Sharp.

    Care must be taken not to plug in the USB port while the target isn't booted otherwise the desktop driver will fault.

    Now when I launch ActiveSync-3.7, it still doesn't find the target. On the target side, the PC connection dialog announces:

    "Connecting to Host"
    "Desktop @19200"

    This seems like an RS232-COM setting. Attempting to connect with VS03.Net results in deployment failure. I've noticed under the Device Tool properties it only has available:

    TCP Connection Transport
    and IrDA Transport

    Which confuses me, can you TCP over USB?

    Also it lists the Startup server as: ActiveSync Startup Provider (this seems relevant).

    Well I should have my USB books from Amazon today; perhaps I'll find an ActiveSync nugget. Thanks for your insight!

    Cheers,
    Scott
    You are not authorized to post a reply.