I am developing Qt application for Windows CE 5.0 device.
My setup is:
Qt 4.7.3 compiled with Visual Studio 2005 using Windows CE 5.0 Standard SDK.
Everything works OK on real device, though I would like to test software "locally" in an emulator.
Visual Studio 2005 provides Pocket PC 2003, Windows Mobile 6 emulator images but no Windows CE 5.0.
Windows Microsoft CE 5.0 Emulator does that, but its sample device is based on i486, so this doesn't work for me...
I found some kind "Plaftorm Builder" and "ARMV4i BSP for Windows CE 5.0", but I am not building device or it's SDK, and I am not interested in specific device at all. All i need is "generic" AMRv4 WinCE 5 image for basic testing...
So what is possible outcomes for me?
Microssoft stopped providing Windows CE OS images for the emulator after the x86 emulator was abandoned, and for good reason. Windows CE is a modular OS so it's not possible to create an Emulator OS image that matches what all devices are and my guess is that there were too many support calls and complaints about how the emulator either contained something unwanted or didn't contain something that was wanted. The point being that there is no "generic Windows CE device" so there's no way to create an emulator of one.
The response from Microsoft was to provide the ARM-based Device Emulator 3.0 (available as a Standalone Release) and a BSP for the emulator so developers can create their own OS images that match their actual target hardware OSes.
So your options are to either create an OS yourself or find an OEM that provides an emulator image for their device (I'm not aware of one offhand, but I very, very rarely use the emulators so I've never bothered to look).
Related
Related to this
I'm planning to develop an app for Android using Qt Quick Controls and an Android Emulator. The same set of components is said to work on Windows Phone. Thus I'd like to build the app for Windows Phone as well.
Unfortunately, Qt for Windows Phone is only available for Windows.
I don't own any Windows phone. I'm using a computer running Linux.
Is it possible to build the app for Windows Phone and test it in an Emulator without virtualizing/dual-booting Windows
Well there is Wine. This is what wikipedia says about it;
Wine (short for Wine Is Not an Emulator) is a free and open source compatibility layer software application that aims to allow applications designed for Microsoft Windows to run on Unix-like operating systems. Wine also provides a software library, known as Winelib, against which developers can compile Windows applications to help port them to Unix-like systems.
You can find more info about Wine here; https://www.winehq.org/
I haven't tried it before but since it says "allow applications designed for Microsoft Windows to run on Unix-like operating systems," I'm thinking it should work.
This is your only option. If it doesn't work, then i guess you should think about running windows on virtual machine or dual booting with windows. Good luck!
I'm trying to create windows CE OS that will run in my industrial CPU using Microsoft Studio 2005. All my tried was failed.
Im trying to build a Windows CE that have
Catalog items view
Storage
Primary disk/storage/master/slave
Secondary
CAB
CF card
Device Manager
Registry flush
Pci 1710
Internet explorer
.netframework
C++
Usb
Uno3072l
Display
Audio
And other basic utilities
I hope that someone will build the windows for me without any error. And share the link here so i can download.
Or, someone who can teach me how to solve the error. I am really stuck.
The Advantech 3072L is a simple x86-basd machine. You can likely use the x86 BSP that ships with Platform Builder, though Advantech may also have a platform specific BSP for any peripherals. Without more info on the version of Platform Builder you're using, what you've tried and the errors you're seeing we can't provide much more help than that.
I've Motorola Symbol Handheld Model MC3090 (from symbol MC3000 series), having Windows CE 5.0.
Is it possible that i can upgrade the Handheld OS from CE 5.0 to CE 6.0?
In Short - NO.
To be able to do so you need to have the BSP (board support package) to build an image for Windows CE. Each OS is built specifically for each device. When you say Windows CE 6 it means nothing since it is a componentizied OS and your OEM (Motorola) decides what to put inside.
According to device's specs I think it has Windows Mobile. A different beast than Windows CE, but based on Windows CE 5. There is no Windows Mobile based on Windows CE 6.
In any case you cannot change the OS version without the OEM.
I'm running Embedded Visual C++ 4 with service pack 4, to develop an application for a device running CE 5.0. I'm using the CE 5.0 SDK for this purpose, which works fine except for the fact that while it will target my device (i.e. an SH4 based PDA), it will not let me select anything other than the StandardSDK emulator for debugging. If I go to Tools / Configure Platform manager, I can connect to my device under Windows CE default Platform, but I cannot select it from the Build Toolbar for output and debugging purposes. Is there any work around for this. I've considered moving to VS2008 for this app, but it breaks a large amount of 3rd party code.
Embedded Visual C++ and "Platform Builder" are different tools. The "Windows CE" SDKs are designed to work with "Platform Builder" to make things like OSes and drivers. However, Applications generally use the "Windows Mobile" or "Pocket PC" SDKs.
So here are three different solutions:
Continue to use EVC++ 4.0
If you want to keep using Embedded Visual C++ 4.0 instead of one of the newer IDEs, you can use "SDK for Windows Mobile 2003-based Pocket PCs". Which I believe is the newest SDK for EVC++ 4.0.
Upgrade to VS2005+
This details how to migrate from EVC++ to VS2005 while still making native apps.
You can use the 5.0 SDK line of features in the "Windows Mobile 5.0 SDK for Pocket PC"
Use Windows CE SDK to make Applications with EVC++ 4.0
It actually is possible to make Applications using a CE SDK. This is used by OS developers to make applications for their OS.
You can develop an application using
Microsoft® eMbedded Visual C++®
together with Platform Builder. Before
you can develop an application, you
must use Microsoft Platform Builder to
create an OS design, build a run-time
image, and then download the run-time
image to the target device.
When you download a run-time image,
Platform Builder uses a download
service to copy the run-time image to
the target device. When the run-time
image runs, Platform Builder
communicates with the target device
over a kernel transport.
To develop an application, keep
Platform Builder connected to the
target device, and then run eMbedded
Visual C++. After you write, compile,
and run the application, eMbedded
Visual C++ uses the established
connection to run the application on
the target device.
Note The previously mentioned
process differs from the process used
to develop an application for a
run-time image not downloaded by
Platform Builder. When you do not use
Platform Builder, you manually connect
to the target device using the
application connectivity
communications framework of Platform
Manager. For more information about
application connectivity, see
Application Connectivity.
-- http://msdn.microsoft.com/en-us/library/ms859575.aspx
As i just need the hard RT capabilities, can I install and run Windows Embedded CE 6.0 on a regular PC ? (dell or so ?), and UDP out some data ?
You can install Windows CE in a PC, but you would need to create your own image. See this tutorial in MSDN. Also google for CEPC.
Finally visit Mike Hall's blog. I remember reading a related article there, but I can't find it now. Anyhow, this blog is a great resource for Windows Embedded.
(From working with Windows CE 5.0, so there may be some differences, YMMV.)
You should be able to run Windows CE both in an emulator and installed on the device itself as the host operating system.
In the first case all you need is an emulator, which is provided with the development kit and in a more expensive version of Visual Studio. This will run the OS fine, albeit a bit slow depending on the architecture you choose to build the Guest OS for.
In the second case you will actually need to find or write drivers for the hardware that you want to run on and use. This will require the Platform Builder application (I believe it's a plugin to Visual Studio now) and knowledge of the hardware that you are running on. Windows CE itself does support x86 processors, although I don't remember if it supports all x86 processors (instruction sets) or just 486's.
If you want to go down the second route you also may be able to get an Intel Atom or AMD Geode board support package (BSP) which will help you develop the drivers.