AutoLaunch for Compact 2013 (v320)

Rating:        Based on 2 ratings
Reviewed:  2 reviews
Downloads: 490
Released: Jan 22, 2015
Updated: May 26, 2015 by Samuelphung
Dev status: Stable Help Icon

Recommended Download

application, 4788K, uploaded May 26, 2015 - 490 downloads

Release Notes

What's New:

In this release, project codes for the Compact-2013 UDP IP address broadcast utility and UDP listener for the desktop are added.

The "UDP IP Address Broadcast" component is intended to support headless device. When included in the OS image, it's configured to launch Compact2013UDPClient.exe to broadcast the device's IP address via UDP, during startup.

To capture the device's IP address, which is needed to establish connectivity between the Visual Studio IDE and the target device to deploy application onto the device via CoreCon, you need to launch the companion app, Compact2013DesktopUDP_Listener.exe, from a desktop attach to the same LAN as the target device, prior to power on the device and wait for the UDP message from the device.

The companion app, Compact2013DesktopUDP_Listener.exe, is included in the package, under the following sub-folder:
- %WINCEROOT%\Autolaunchv310_Compact2013\Desktop UDP Listener

The Autolaunch.exe is released in source code (Win32) in the package, and compile during build process and should work for both ARM and x86 devices.

Both Compact2013UDPClient.exe and Compact2013DesktopUDPListener.exe are simple console application written in managed code using C#. The codes for these two apps are included in the \IPBroadcast.src folder.

Known problem:

There are conflicts between the CoreCon connectivity, to support Visual Studio application development, and KITL connectivity, which is needed to support Platform Builder remote tools.

To use Platform Builder remote tools with an OS image built with KITL enabled, exclude the "Autolaunch CoreCon" sub-component from the OS design.

Reviews for this release

postlink.bat changes required: set _CORECONPATH=%CommonProgramFiles(x86)%\Microsoft Shared\Embedded Tools\CoreCon\%VisualStudioVersion%\Target\wce%_WINCEOSVER%\%_TGTCPU% set _UDPCLIENTPATH=%_WINCEROOT%\3rdParty\AutoLaunch_v320_Compact2013 Can't seem to get this to work with CEPC BSP and Windows Virtual PC. What's the trick? Am running Compact2013_Desktop_UDP_Listener on Host PC and have included Compact2013UDPClient with AutoLaunch. Not seeing anything. VPC is using Loopback NIC, not real NIC with static IPs. Do I need to use a real NIC with static IPs on each side, host and VPC?
by DougMoore on May 18, 2015 at 12:02 AM
Wrong path in postscript, still linking to v310 instead of 320 making it fail when build. Otherwise good! :)
by vimo on Feb 19, 2015 at 8:27 AM