Re: debugging?
- From: r_z_aret@xxxxxxxxxxxx
- Date: Fri, 13 Oct 2006 09:54:06 -0500
On 13 Oct 2006 01:07:22 -0700, "Warren" <warren@xxxxxxxxxxxx> wrote:
Hi All
I am sure this is a stupid question, but I cannot seem to figure it
out.
I have MS's eMbedded Visual C++ and the Standard_SDK installed. I am
using an iPaq 6915. I can compile a program and run it on the Emulator.
Changing the CPU and manually copying the file to the ipaq, it will
also run. But I need to debug the program on the ipaq, and this is
where I am struggling.
In Platform Manager I can add a device under 'Windows CE Default
Platform' and select active sync. The test is OK. But how do I till
vc++ to use this device. The 'Set Default device' does not show this
new device, it only shows the options that are added under STANDARDSDK
in the Platform manager, and they do not seem to offer active sync
options.
How do I select an active sync device? Am I on the wrong track
altogether?
The eVC IDE is very fussy about mismatches between target platform and
actual platform. In this case, you specified a "Standard" device as
the target, but the actual device is running WM 5 for Pocket PC (I
used Google to find this info). You can generally debug directly only
when you install and use the SDK that goes with the actual device.
Unfortunately, no SDK that works with eVC supports WM 5. So if you
really want to debug directly, you will need to switch to Visual
Studio and the SDK for WM 5 for Pocket PC. And you will need to switch
to one of the Visual Studio versions that costs money.
With a little effort, you can stick with eVC. I infer from your use of
the STANDARD_SDK that you are using eVC 4 (eVC 3 has no such SDK). So
you should get and install the Pocket PC 2003 SDK. You can then do
much of your development and testing using the Pocket PC 2003
emulator. But you need to know that the emulator is not a very good
mimic (even for Pocket PC 2003 devices), so you should absolutely not
rely on it. If you sprinkle ASSERTs liberally through your code, they
will trap errors when you run on your iPAQ. With a bit of patience,
you can add enough ASSERTs to spot relevant source code quickly. When
an ASSERT does trigger, you can add MessageBoxes to narrow down the
list of suspect source lines. Such debugging can be tedious,
especially with new code. But it is possible.
The "standard" SDK is rarely useful.
Help will be very appreciated.
Warren
-----------------------------------------
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
.
- References:
- debugging?
- From: Warren
- debugging?
- Prev by Date: Re: Can I disable standy of PocketPC in my Application?
- Next by Date: Re: Bluetooth communication between WinCE and WinXP...
- Previous by thread: debugging?
- Next by thread: Re: debugging?
- Index(es):
Relevant Pages
|
Loading
