Author |
Topic |
|
KnowledgeBase
296 Posts |
Posted - 26 Feb 2002 : 12:27:00
|
Q: What development tools can I use for ADS Systems?
Development for CE 2.12 and CE 3.0 systems is done with Microsoft eMbedded Visual Tools:
http://msdn.microsoft.com/vstudio/device/faq.asp
Development for CE.NET can be done with eMbedded C++ 4.0 (available with Platform Builder 4.0) or Microsoft Visual Studio .NET
http://msdn.microsoft.com/vstudio/
------------------ ADS Knowledge Base |
|
timslater
6 Posts |
Posted - 06 Oct 2004 : 12:45:04
|
I have a BitsyX development system, running WinCE 4.10 I am using eMbedded Visual C 4.0 as my development environment.
We are developing a custom board and expect to access it via a memory map. What I can't figure out is how to get access to physical memory. I've seen some examples that use VirtualCopy(), but it does not seem to be included in the embedded Visual tools package. Is there another tool (PlatformBuilder?) that will allow access Physical memory from my WinCE application?
-tim
|
|
|
Susan
123 Posts |
Posted - 06 Oct 2004 : 12:53:15
|
I don't profess to be knowledgable on this topic, but we are using VirtualCopy in our application. (BitsyX, 4.10.36 image, ROM 1.10, eVC 4.0). Maybe what you are trying to do is completely different than what we are doing...
Topic 845 may provide an answer?
And Topic 964...? |
Edited by - Susan on 06 Oct 2004 13:07:20 |
|
|
timslater
6 Posts |
Posted - 06 Oct 2004 : 13:20:55
|
Sounds like your setup is like mine. Do you know if you installed some other SDK or something? (asked another way, where do you get VirtualCopy() from ? I've been rumaging the net and have seen references to grabbing pkfunks.h and ceddk.h from platform builder. Did you have to do any such thing ? |
|
|
ctacke
877 Posts |
Posted - 06 Oct 2004 : 13:37:32
|
Several of our sample use VirtualCopy. To use it, simply include the definition as an extern in your code (which is what I did in the samples). |
|
|
Susan
123 Posts |
Posted - 06 Oct 2004 : 13:42:19
|
Here goes (here shows my ignorance...how embarassing...)
For the device (release and debug mode) I am using the BitsyX SDK (Topic 678). Grabbing the pkfuncs.h - I think you want to stay away from that - can't give you details, though - but there's something amiss with that.
That's about it. Unless I've forgotten some ridiculous, esoteric item.
Our original use of the VirtualCopy() copy was implementing the ADSCF2 code, since we use the compact flash interface for our own purposes.
In addition, at one time we were toying with the idea of doing a field upgrade of the image (without distributing NK.BIN). So, I grabbed the sample code at Topic 964 as my starting point. Fortunately for everyone involved, we realized the foolishness of that idea.
May I ask what problem you are having with VirtualCopy()?
Looks like Chris's post and mine crossed paths. Yes, I do have the following included at the top of my source file... // VirtualCopy definition extern "C" BOOL VirtualCopy(LPVOID lpvDestMem, LPVOID lpvSrcMem, DWORD dwSizeInBytes, DWORD dwProtectFlag); |
Edited by - Susan on 06 Oct 2004 13:47:41 |
|
|
timslater
6 Posts |
Posted - 06 Oct 2004 : 14:28:47
|
Thank you both. You've been very helpful.
One last question... I am coming from a Win2K/XP environment where there is a clear distinction between applications and device drivers. (both in terms of what they are allowed to do and the development tools needed to accomplish the task.
As mentioned earlier, I have a need to talk to a custom board (thus the need for Physical memory access. In the regular windows world, I would not have been able to (allowed to) access physical memory from "the application".
If we decide I also need to service an interrupt from the board, can that also be accomplished using only embedded Visual C++ ?
Asked another way ... at what point would I *need* to write a device driver (need another development tool, like platform Builder, or WinDriver ...
Thanks again shedding light.
-Tim |
|
|
|
Topic |
|