Windows Embedded Compact and Windows CE related
Windows Pads .. Windows 7, CPUs, Windows CE, Windows Embedded Standard 7
Read the rest of entry »
We've released the first version of the Stream Driver Wizard on Codeplex.
I've got a first version ready for release. Here is a decription of it.
I've been working on building Mike Hall's CEFileWiz and StreamDriverWiz for CE 6 and for Windows Embedded Compact 7.
I have had my first go with WEC7. Here are some brief initial comments:
It seems that PB (CE 6 in VS 2005) doesn’t like long path names.
I’ve come across this before.
It builds OK but then fails over in makeimage as above.
C:\WINCE600\OSDesigns\LPC3250-DK_BIN with solution file in this directory worked OK.
C:\WINCE600\3rdparty\PhyCore_LPC3250_BSP_EVAL_V1_0_3_Prerelease\OSDesigns\LPC3250-DK_BIN fails as above
I seem to remember that spaces can cause problems too.
It seems a path length issue here.
Thanks to Bruce Eitman:
... And Nicolas Besson seems to have blogged about the same problem jsut when I came accross it:
It says that you need VPC 2007 when you try to enable networking with the Arm emulator. But Win 7 has a later VPC.
But when installed (Win 7 version) the required networking isn’t installed.
This article seems to resolve the issue:
Its out of the bag..
Windows Embedded Compact 7 is available as a trial download under the Public Community Tech Preview program (Public CTP).
Download appears to be 8 Gig.
It requires Visual Studio 2008 SP1>
Note VS 2010 has no support for devices, except Windows Phone 7
Mustn’t have Windows CE (any version) installed.
Freescale i.MX27 ARMv5
Freescale i.MX31 ARMv6
NEC NE1TB ARMv6 Multiprocessor (MP)
Samsung SMDK6410 ARMv6
Texas Instruments 3530 EVM2 ARMv7
ARMv4i support is not available in this release
SH-4 is not supported in this release
Virtual CEPC (vCEPC) replaces Device Emulator in this release
· 3DS_iMX27: ARMv5
· CEPC: x86
Lets completely work through a Platform Invoke Example.
For simplicity I’ll use a Windows Mobile Emulator, but it would simply apply to an actual Windows Mobile Device/Windows CE device.
Visual Studio 2008 with a suitable Windows Mobile or Windows CE Emulator/SDK installed.
Using C# for the application and C++ for the native DLL.
I have also tried this on my Windows Mobile 6.53 Phone
Create a new C# Smart Device Project .. Ignore the .NET Version in the first step. Call it PInvoke.
Choose a suitable Target Platform, Set the .NET CF Version (I selected 2.0), Select Device Application (This creates a Windows Form App)
A Windows CE Target might be a suitable choice.
Complete the project creation, the Target Form will show.
Add a Button and Text Box
Double Click on the button add the code:
textBox1.Text = DateTime.Now.ToString();
Build and run the ...
Native and Managed Code
Native code is code written in C++ (or assembler) and compiled to produce a binary executable or .DLL. Native code applications are CPU specific and only require the executable and any other required native .DLLs. Native code applications and .DLLs do not produce MSIL code.
Managed code applications are written in C# or VB.NET using the .NET Compact Framework (CF). Unlike desktop .NET, C++ cannot be used to code .NET CF (Smart Device) applications. CF provides a rich library of functionality and is not compiled in a processor specific manner.
.Net CF is in the main, a subset of the desktop .NET Framework with some added features that make sense on a Windows CE/Windows Mobile device. It builds to the same MSIL code as the desktop .NET. As a simple test, build a simple CF windows form application and build it. Choose a non x86 platform such as Windows Mobile/Pocket PC. Build the application. Go to its build directory, on the development machine and run the application dir ...