Re: Problem with EVC4 SP4 and Active Synch
r_z_aret_at_pen_fact.com
Date: 02/23/05
- Next message: r_z_aret_at_pen_fact.com: "Re: EVC++ 3.0 to EVC++ 4.0..."
- Previous message: Paul G. Tobey [eMVP]: "Re: closesocket"
- In reply to: nzpcmad: "Re: Problem with EVC4 SP4 and Active Synch"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Feb 2005 15:53:39 -0500
Much clearer. More below.
On 22 Feb 2005 13:32:30 -0800, "nzpcmad" <nzpcmad@yahoo.co.uk> wrote:
>>> 1) you are using eVC 4 with the DT-X10 SDK
>
>Yes
>
>>> 2) you have chosen the DT-X10 as the target (within the eVC SDK)
>
>Yes
>
>>> 3) the compilation and link steps proceed without problem
>
>Yes
>
>>> 4) the IDE automatically downloads your executable
>
>No - it automatically starts the download and then gives the error
As I thought.
This is typically because the IDE detects a mismatch between the
target you've specified and the actual hardware. I can understand why
the IDE might be fussy about matches when trying to debug. I wish it
would at least provide an option to let me override for the download.
More below.
>
>>> 5) the problem shows up when you try to debug,
>
>Doesn't get this far.
>
>(NOTE. eVC is different to Visual Studio at this point. In Visual
>Studio, build and deploy are two steps. eVC seems to combine them?)
>
>Also, I have been discussing with Casio. They are telling me that this
>only works with eVC SP1 !!!!!.
Very disappointing. Casio is a big company that has supported Windows
CE from the beginning (yep, they sold some of the original HPCs
running version 1.0 of the operating system). Effectively something in
their SDK keeps the IDE from recognizing that the target you specified
matches the actual hardware. Sigh.
>
>In answer to your question, this has NEVER worked with eVC on my PC.
>
>So I guess I'm stuck with debugging on the emulator that they supply
>which does work.
That will work for preliminary testing. But you really need to build
for the actual hardware, copy your executable manually (use
ActiveSync->Explore) and run on the hardware. Here is where larding
(not just sprinkling) ASSERTs throughout your code will help. The
ASSERTs will help localize any problems that show only on the actual
hardware. You can then pore through your source code, step through
code in the emulator, and/or add message boxes to narrow the problem
further. Definitely not as nice as running in a debugger. But better
than nothing. Arm yourself with as much inner peace as you can find.
>
>Many thanks for your help.
You're welcome. And good luck.
-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
PenFact, Inc.
500 Harrison Ave., Suite 3R
Boston, MA 02118
www.penfact.com
- Next message: r_z_aret_at_pen_fact.com: "Re: EVC++ 3.0 to EVC++ 4.0..."
- Previous message: Paul G. Tobey [eMVP]: "Re: closesocket"
- In reply to: nzpcmad: "Re: Problem with EVC4 SP4 and Active Synch"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
