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 24 Sep 2004 11:34 AM by  geneer_dan@hotmail.com
.NET Smart Device Application deployment Error
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
accelsys@vsnl.com
New Member
New Member
Posts:


--
24 Sep 2004 04:23 AM
    We are trying to deploy our vs .NET 2003 application on the WinCE 4.2 .NET platform on logic
    pd LH7A400-10 SDK system. The device connects successfully with active sync 3.5 and platform
    builder KITL. However, the .NET deployment is resulting an error

    ------ Deploy started: Project: SmartDeviceApplication1, Configuration: Release Windows CE ------

    Deploying to Windows CE .NET Device using TCP Connect Transport

    Error: Cannot establish a connection. Be sure the device is physically connected to the development computer.
    ---------------------- Done ----------------------

    Build: 1 succeeded, 0 failed, 0 skipped
    Deploy: 0 succeeded, 1 failed, 0 skipped

    We have tried the smart device authentication utility on the device side, it gives
    the IP address as 192.168.55.101. We have put this address in the smart device authentication utility
    on host end and it is returning an error

    Device IP address not found. Run the device component of this utility to find the IP addresses of the device

    The device shows that it is connected @ 19200.

    Our platform settings are as follows :

    BSP selected LoCE_A400_REL_101

    Configuration Custom

    Custom Device Device with shell and GUI

    Applications and services C libraries and run time
    C++ exception handling
    .NET Compact framework

    Applications Active Sync

    Communication services and networking
    Networking Wide area network, Dial up networking( RAS/PPP )
    TAPI 2.0

    Internet client services Internet explorer HTML/DHTML API

    Security Cryptography services

    User Interface Network user interface, Touch display

    Notification acknowledged

    The Losh bootscript was as follows :
    exec :A400_UART:dbg_enet:91C111:dbg_enet_base:0x70000000:dbg_enet_irq:0x00000007:rtc:rtc_a400_int:share_eth:1:disp_num:9
    geneer_dan@hotmail.com
    New Member
    New Member
    Posts:


    --
    24 Sep 2004 11:34 AM
    Hi Ganapati,

    I would check the following settings first:
    + in VS2003: Under Tools/Select Windows CE Device CPU, choose ARMV4T and restart VS2003.
    + in VS2003: Under Tools/Options/Device Tools/Devices/Configure button next to "Transport" dropdown, make sure the following settings are selected: Use fixed port unchecked, Obtain IP address using Activesync checked.

    You can test basic connectivity by pressing the Connect button in the Tools/Options window.

    I have heard of difficulties connecting VS 2003 over activesync when a ethernet based KITL connection was present. You might try running your nk.bin without KITL and see how that flies.

    You shouldn't need to run the smart device authentication utility unless you are debugging over ethernet with no activesync conn available. Visual Studio uses TCP over activesync, but no ethernet connection is necessary.

    Hope this helps.

    Regards,

    Dan


    Dan Weaver
    Software Engineer
    Logic Product Development
    You are not authorized to post a reply.