Re: Help! Confused by different processors



On Thu, 15 Jun 2006 16:35:33 +0100, "Keith Sheppard"
<keith.sheppard@xxxxxxxxx> wrote:

Although a seasoned programmer in most respects, I am a bit of a novice when
it comes to developing for mobile devices.

I have an application which I developed using eMbedded Visual C++ 4.0 and is
working OK on a small number of platforms. Someone just asked me to build a
version for a "2002 XDA". A bit of investigation reveals that this has (I
think) an SA-1110 processor. My eMbedded C++ development environment
doesn't admit to the existance of such a beastie.

I had a stroll around MSDN hoping to find a suitable SDK to download but
rapidly got lost. The only download which even mentioned the SA-1110 was
something called the BSP(?) which appears to be something to do with
building operating systems(?) and complete overkill.

Can anyone advise me exactly what I need to download, and where I can find
it, in order to rebuild my humble little application for this target
platform?

The word "platform" is the key. Each SDK targets a specific platform.
A "platform" is a combination of base operating system, plus and minus
some tweaks, plus a hardware specification. For more info, see:
http://www.opennetcf.org/Forums/topic.asp?TOPIC_ID=317
http://www.pocketpcfaq.com/wce/versions.htm
Also, any device that is officially (with Microsoft logo) a Pocket PC,
_will_ support code created with the corresponding SDK from Microsoft.
Your XDA is officially a Pocket PC 2002 Phone Edition (see
http://reviews.zdnet.co.uk/hardware/handhelds/0,39023880,10001359,00.htm).
So if you build with the Pocket PC 2002 SDK, you should be fine. You
would also probably succeed with the original Pocket PC SDK.


Each SDK supports a specified set of CPUs. Microsoft defines the specs
for the Pocket PC platforms (original, 2002, 2003, WM 5, ...), and has
decreed that only ARM-compatible CPUs are allowed. So Pocket PC SDKs
support only emulator and ARM-compatible CPU. I believe the SA-111 is
a StrongARM CPU. And I'm quite sure StrongARM CPUs are ARM-compatible.
So code built for ARM should be fine on an SA-111.

So far so good. Unfortunately, I don't think the Pocket PC 2002 SDK
will work with eVC 4, although I've never actually tried. I'm quite
sure apps built using eVC 4 and the Pocket PC 2003 SDK are likely to
have problems running on a Pocket PC 2002. So, I think you will need
to use eVC 3 and the Pocket PC 2002 SDK. Fortunately, eVC 3 is still
available, is free, and is very similar to eVC 4.




Regards
Keith


-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com
.



Relevant Pages

  • Re: debugging?
    ... In Platform Manager I can add a device under 'Windows CE Default ... no SDK that works with eVC supports WM 5. ... Studio and the SDK for WM 5 for Pocket PC. ...
    (microsoft.public.pocketpc.developer)
  • Re: Some questions; SHMenuBar, multilingual prog
    ... >>> applications that run on a Pocket PC 2003, but you will not be able to ... It worked under eVB, but not eVC. ... When I try to start EVC, it says something like "SDK not ... >>Emulator showed a 1024x768 environment, the OS looked like a handheld ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: How to make application work on Symbol MC3000?
    ... for SMDK V1.4 for eVC. ... For simple applications you don't need any Symbol SDK at all. ... Please see the install requirements for the Symbol Mobility ... Microsoft Pocket PC 2003 SDK." ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Some questions; SHMenuBar, multilingual prog
    ... >> applications that run on a Pocket PC 2003, but you will not be able to ... It worked under eVB, but not eVC. ... >> eVC 4 to use the Pocket PC 2003 SDK. ... >Emulator showed a 1024x768 environment, the OS looked like a handheld ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: sdk question
    ... or my firewall finaly woke up and allowed eVc to communicate with the WCE ... SURE THAT IT DOES NOT SAY ANYTHING ABOUT THE STANDARD SDK. ... Standard SDK installed and install another, specific device SDK, you'll get ... Emulator, if your device SDK has an emulator for the device. ...
    (microsoft.public.windowsce.embedded.vc)

Loading