ARM .... ARM4 ....?

[Boris Nienke]

Hi,

when i create the CAB-Files i will get files for different processor
types...
MIPS and SH3 is pretty useless i think because PPC2002/2003 is running on
Arm-Processors only?

But i get TWO version for ARM
1.) ARM
2.) ARM4

What is "ARM4" and when will i need it?

thanks

Boris

 

[Rüdiger Kardel]

http://msdn.microsoft.com/mobility/prodtechinfo/devtools/netcf/FAQ/default.aspx#1.23

regards
Ruediger

 

[Boris Nienke]

well... thanks...
but now i have more questions than answeres

If the "ARM"-Version is for PPC2000/2002 then it will work on WM2003 too -
but what are the cons? Shouldn't i install an "ARM"-Cab to a CE.Net-Device?
Why? Slower?

If the "ARM4"-Version is for CE.NET then i should install it to all WM2003
Devices... and it won't work on PPC2000/2002 devices? What will happen?
Error?

thanks

Boris

 

[Boris Nienke]

http://msdn.microsoft.com/mobility/prodtechinfo/devtools/netcf/FAQ/default.aspx#1.23

oh... and:
"ARMv4T or ARMv4I for Windows CE.NET. This will run on Windows CE.NET
devices compiled with either the ARMv4T or ARMv4I kernels in Platform
builder. The cab that gets deployed to these devices has "armv4T" in the
name."

What devices are that?

Boris

 

[Neville Lang]

Boris,

Another way of viewing this is that the PPC 2002 operating system was
developed for WinCE 3.0 devices while the current WM2003 was developed for
WinCE4.2 and later.

So, it is best to use ARMV4 CAB files for WM2003 and ARM CAB files for
PPC2002 and PPC2000 where an ARM or XScale processor is used.

As an example, I originally purchased an iPAQ 3970 which had the PPC2002
loaded and so as I was building my app, I used the ARM CABS. When I upgraded
the os to WM2003, I began using the ARMV4 CABS of my app and noticed the
speed increase. In fact, just after I had installed the WM2003, I continued
to use the ARM CABS quite successfully and then switched over to the ARMV4
CABS without a problem, and the app ran better. The ARMV4-generated CABS use
the expanded instruction set of the XScale processors, as far as I know.

Since the current XScale processors now use the V5 instruction set, I assume
in the next upgrade of Visual Studio will be able to generate ARMV5 CABS but
may be limited to how the WM2003 os processes these expanded instructions.

Regards,
Neville Lang

 

[Boris Nienke]

hi Neville

So, it is best to use ARMV4 CAB files for WM2003 and ARM CAB files for
PPC2002 and PPC2000 where an ARM or XScale processor is used.
OK

As an example, I originally purchased an iPAQ 3970 which had the PPC2002
loaded and so as I was building my app, I used the ARM CABS. When I upgraded
the os to WM2003, I began using the ARMV4 CABS of my app and noticed the
speed increase. In fact, just after I had installed the WM2003, I continued
to use the ARM CABS quite successfully and then switched over to the ARMV4
CABS without a problem, and the app ran better. The ARMV4-generated CABS use
the expanded instruction set of the XScale processors, as far as I know.

Hm... that's interesting! can you "meter" it? what was faster or
"smoother"... the loops, array-lists, calculations or the GUI too?

BTW: when i compile my application i can see just one EXE file in the
\debug or \release directory. But when i build the CAB files i will get a
lot of CABs
How is that? I don't think the CAB-Builder will recompile the EXE... and as
far as i know, the EXE is just "intermediate code" - so where exactly is
the difference (now that i know where and how to use the CABs i like to
know how they are created and how the exe will know if it is for ARM or
ARMv4 you know?)

thanks

Boris