Hello,
I am writing a driver for SDIO communication for WM4 and WM6. I need to do 2 things
(1) stress the CPU and Memory so that only part of the resources are available to the driver. Pocet PC TestSuite allows this but it does not work on WM5 and WM6
(2) measure the resources taken up by my driver's thread/process
Can anyone please suggest me software/API calls with which i can achieve the above 2 things.
Hi,
use windows ce performance monitor from embedded visual studio 4.
Houser
Related
I use Visual Studio 6 and 2005 at work, and was wondering what development environment you use for writing applications etc, for the Exec. I installed WinCE C++ v4.0 yesturday and the .exe built for the ARM processor wouldn't run!
Dev env for WMobile 5
Visual Studio 2003 or 2005 work fine.
(you can get the "academic" version if you are a student for less than £50)
with 2003 you have to make smartdevice projects and write them in c#
in 2005 you should be able to do MFC and win32 in c++ as well
Thanks.
Which ever IDE you use, you need to download Pocket PC SDK from MS (it's free) for Window Mobile 5.
You can also use eVC 4, but you need to install SP 4 for it, and PPC SDK for Windows Mobile 2003 (it won't recognise WM5 SDK).
Sorry to be a pain but I have not written software targeted at WinCE/WM before.
I have installed eVC4, Microsoft Pocket PC 2003 SDK, SP3 and SP4. I can debug with the Pocket PC Emulator fine, but when I try to debug or install in release mode on the O2 Exec (which is connected) I get the following warning dialog: "CE platform pocket pc 2003 does not match remote os version 501". :?
I do not want to write software for the PPC using .NET (although I write in C# at work, as well as MFC/ATL C++), as in my opinion the PPC isn't fast enough for managed code. So how can I write apps' for the O2 Exec using eVC4 :?:
Hi VZ800!
You are right about .NET, those apps are more sluggish then native code.
Don't worry about the warning, just click yes, then you going to get another warning, something about CPU type, click yes on that one two.
The eVc *****es because it's not familiar with WM5 devices, but your program will run fine. In fact, I used eVc 3, to write programs for WM5 that were backwards compatible with WM 2002 and they worked fine (although eVc 3 can't connect to the device so I had to copy the exe manually).
The debugger should work as well, though I try to avoid it since it some times takes a long time to connect.
If all you need is some debug prints, no watches or brake points, you might be better off writing to a file with the old fopen, fprintf, funcs. which come in both ASCII and Unicode (wfprintf) versions.
Good luck!
Thanks, I'll give it another go tomorrow.
I have been learning to use visual studio 2005 and I am getting stuck on the output. My target device is a pocket pc 2003 device but the exe only will run on a wm2005 device. I have not installed the wm2005 sdk, i am using the sdk that comes with visual studio for wm2003 devices.
I have tried replacing the $(CEVER) in the preprocessor definitions that translates to 0x0420 with lower values like 0x0300 but that generates so many errors that can't be the solution. Dose wm2003se require a different sdk from the one that ships with visual studio?
Can anyone offer a solution?
I found the cause.
I was using mfc as a shared library. The version of that dll on my mini is different (same name) from that on my dopod. When I statically link It all works. But thats no good because it triples the size of the app.
the real question is how do i get my wm2003 app to use the new version of mfc. I want to use mfc80u.dll instead of the mfcce300.dll, how?
I'm from Mexico, I bough a HTC qtek 9100 with WM5, and I was dissapointed on somethings:
1.- the OBEX bluethooth file transfer used on 2003, Disappears!!!!!!
How can I surf in a bluetooth device like in a 2003 PPC?
Is a program for download on the web for make this happens?
2.- I can't assign more memory for programs or storage in ram! it sucks!
It seems that this Operative systems has made for IDIOTS!
3.- Texas instruments doesn't mix as well like arm's, nobody's learn for itself
mistakes?
4.- u know what? I'm still in love with my Strong arm xscale h2200 400 mhz processor and wm2003 se
see you soon... is there a program for OBEX file transfer?
"2.- I can't assign more memory for programs or storage in ram! it sucks!
It seems that this Operative systems has made for IDIOTS!"
to avoid hardresets clearing all data on the device they changed it so storage is placed in flash not in ram
if storage was used as ram with it's limited writes before it dies
and it's limited speed you would be likely to be much less happy
Is there currently a working emulator for either of these operating systems available for windows mobile 6?
I've tried searching all I can and have found no answers yet.
HAHAHAHAHahahahah.... ah, but seriously, no.
TylerC161 said:
Is there currently a working emulator for either of these operating systems available for windows mobile 6?
I've tried searching all I can and have found no answers yet.
Click to expand...
Click to collapse
Do you realize thats the equivalent of asking if my pc can emulate a cray mainframe? Running one windows 95 program would use up all the memory and cpu your entire phone has and then some.
Don't make the mistake of thinking a 200mhz arm processor = 200mhz pentium..the pentium is 1000 times faster and keep in mind the average phone has 20-30 meg of memory...the average pc...ok..even a dog old pentium 150 typically had 128 meg of ram available.
Now do you see why the first poster is laughing at you?
famewolf said:
Do you realize thats the equivalent of asking if my pc can emulate a cray mainframe? Running one windows 95 program would use up all the memory and cpu your entire phone has and then some.
Don't make the mistake of thinking a 200mhz arm processor = 200mhz pentium..the pentium is 1000 times faster and keep in mind the average phone has 20-30 meg of memory...the average pc...ok..even a dog old pentium 150 typically had 128 meg of ram available.
Now do you see why the first poster is laughing at you?
Click to expand...
Click to collapse
I had a pentium 90 with 16mb ram.
but anyway, I've seen someone running windows 95 on a pocket pc
http://www.pocketgamer.org/showthread.php?s=&threadid=3660
dont know if it works on wm6 but it looks like you need a large storage card, a lot of patience, a great cpu, lots of memory and a vga screen at least.
good luck
Its not so hard to believe is it?
I had it running on my PSP, so why not my ppc?
Okay, well in that case, whats the best software to access your PC through the internet on your ppc? I used to have this software that worked via wifi for my PSP that would let me operate my windows machine with the psp, but I cant remember its name, and thats not QUITE what im looking for. I want one that will work NON wifi as well
you can use pocketdos or dosbox with bochs plugin to make win95 work. Nevertheless you wont get any decent speed on it.
TylerC161 said:
Its not so hard to believe is it?
Okay, well in that case, whats the best software to access your PC through the internet on your ppc? I used to have this software that worked via wifi for my PSP that would let me operate my windows machine with the psp, but I cant remember its name, and thats not QUITE what im looking for. I want one that will work NON wifi as well
Click to expand...
Click to collapse
You are probably referring to VNC and there are plenty of clients that run on ppc.
LlamaV3 said:
I had a pentium 90 with 16mb ram.
but anyway, I've seen someone running windows 95 on a pocket pc
http://www.pocketgamer.org/showthread.php?s=&threadid=3660
dont know if it works on wm6 but it looks like you need a large storage card, a lot of patience, a great cpu, lots of memory and a vga screen at least.
good luck
Click to expand...
Click to collapse
Yep and your gonna trash the storage card in a short amount of time due to all the read/writes since it's basically using it as a huge swapfile.
there's the emulator of win32-x86 for win32-arm platform. it called wow86 and developed by GreateVK. it is not ready-to-use product yet. but it successfully run some (even simple) x86-applications without modifications.
p.s. wow86 and applications should be placed into the root folder of your device
famewolf said:
Don't make the mistake of thinking a 200mhz arm processor = 200mhz pentium..
Click to expand...
Click to collapse
the PSP has a lesser speed MIPS processor than some of the available ppc's today.
MIPS being the old one we don't use anymore.
and look at what IT can do, without anything but that to run it's games.
and take a look at the NEC MobilePro 900C.
it has an Intel PXA255 400MHz processor, and runs windows ce .net 4.2.
which basically has the same interface as windows xp with classic skins and does alot of the same things (e.g. the full desktop ms office apps).
i think we underestimate the possibility of today's pxa270 624mhz processors and the mobile graphics chips.
but yer, pocketdos and the likes have shown to run windows 95 and 98.
if they were more optimized it could be a possibility to run basic apps and find a way to convert the instruction set to run more complicated apps.
"(e.g. the full desktop ms office apps)."
maybe more full then the office mobile
but i doubt ms would ever compile a full office
nor a full windows for the arm based instructionset
the asm codes are not the same
all the software needs a full recompile to work
unless a full emulator is being used
the maintaince expenses for ms to make something like that
would be staggering
when ms first made windows CE all devices which had CE had the same GUI as NEC MobilePro 900C
but nobody was buying the devices people pref'd the palm way of operating their pda's
so ms made pocketpc series
this was not a step down it was a step besides
CE is not any closer to real windows then pocketpc series it's just different
it's the same core it's the same everything but imput and gui
chrismrulz said:
the PSP has a lesser speed MIPS processor than some of the available ppc's today.
MIPS being the old one we don't use anymore.
and look at what IT can do, without anything but that to run it's games.
and take a look at the NEC MobilePro 900C.
it has an Intel PXA255 400MHz processor, and runs windows ce .net 4.2.
which basically has the same interface as windows xp with classic skins and does alot of the same things (e.g. the full desktop ms office apps).
i think we underestimate the possibility of today's pxa270 624mhz processors and the mobile graphics chips.
but yer, pocketdos and the likes have shown to run windows 95 and 98.
if they were more optimized it could be a possibility to run basic apps and find a way to convert the instruction set to run more complicated apps.
Click to expand...
Click to collapse
All very true..but the person asking has a tmobile wing which is a 200 mhz arm chip. The low end of the spectrum (I should know as I have the MDA which is the same chip) and it's gonna run a PC emulator like that CRAPPY as all get out. It has a hard enough time emulating a gameboy. Also in the end would still be easier to "optimize" the code into a ppc version then to try to run bloated regular windows programs where they stopped caring about resources a long time ago.
Rudegar said:
"(e.g. the full desktop ms office apps)."
maybe more full then the office mobile
but i doubt ms would ever compile a full office
nor a full windows for the arm based instructionset
the asm codes are not the same
all the software needs a full recompile to work
unless a full emulator is being used
the maintaince expenses for ms to make something like that
would be staggering
when ms first made windows CE all devices which had CE had the same GUI as NEC MobilePro 900C
but nobody was buying the devices people pref'd the palm way of operating their pda's
so ms made pocketpc series
this was not a step down it was a step besides
CE is not any closer to real windows then pocketpc series it's just different
it's the same core it's the same everything but imput and gui
Click to expand...
Click to collapse
If you want the full version of MS Office, you can try porting Open Office (http://www.openoffice.org or http://porting.openoffice.org) to Windows Mobile. I'm sure a lot of us here at XDA-Developers would like to see that happen.
i guess that it would be easier to compile it for linux on our phones
being that i think the wm win32 stk is more limited then linux is terms
of which components are alowed
As I understand it, eMbedded VC++ can be used to write applications that will work in Windows Mobile 5/6. I'm curious as to what I would miss out on in terms of API. In other words, what's new and shiny in VS 2005 that would make it worth my money to purchase instead of just using eMbedded VC++?
Particularly, I'm interested in writing a Today Screen plugin (so the .Net features don't matter to me very much). Is there any API breakage between Pocket PC 2003 and Windows Mobile 5/6 regarding Today Screen .dll's?
Alternately, is there a way to use the Windows Mobile 5/6 SDK with eMbedded VC++?
embedded vc++ apps can run on wm6 devices because in most cases all arm wm apps can run on all wm devices
the beta2 of visual stuio 2008 is free and can also do what vs2005 can and more
Rudegar said:
embedded vc++ apps can run on wm6 devices because in most cases all arm wm apps can run on all wm devices
the beta2 of visual stuio 2008 is free and can also do what vs2005 can and more
Click to expand...
Click to collapse
I know eMbedded VC++ apps can run on WM6, my question was more about whether there are any differences in available library/API calls using the older development platform, any name mangling issues writing DLL's, etc. Can I just use eMbedded VC++ to compile against the newest SDK libraries?
You will miss the following:
1) 1GB+ of you hard drive wasted.
2) 5 minutes wasted every time you try to access built in help
3) A lot of time lost due to slow response of the IDE
4) Programs that are not backward compatible.
5) Spending lots of money unless you have "other" ways of acquiring VS which we do not condone.
I worked with VS 2005 and still prefer eVC 4.
API is just a matter of what libraries you link to. You can get all the shiny new bells and whistles (frankly I am not familiar with any critical API, and certainly there is nothing new for today plugins) in two ways:
1) Manually unpack WM 5 or 6 SDK and link to its libs.
(Project->Settings->Link)
2) Use LoadLibrary and GetProcAddress to dynamically gain access to the API.
Oh and if you want to write today plugin check out this article and the link to RegDisplay in my signature. It is a skeleton plugin project you can use as a base.
Oh and stay away from VS 2008 at least till it comes out of beta. VS 2005 beta was the worst nightmare I ever seen and I can bet MS track record has not improved.