Re: how important is an emulator to an embedded engineer?

From: Bryan Hackney (bh.remove_at_bhconsult.com)
Date: 08/10/04


Date: Tue, 10 Aug 2004 05:56:53 GMT

Tom Taylor wrote:
> Bryan Hackney wrote:
>
>>
>> Now an interactive debugger is not an emulator, and neither is an ICE.
>> But to assume that
>> you will need one up front is to be pessimistic these days.
>>
>>
> I would disagree that an In Circuit Emulator is not an emulator.
>

It is. In-circuit is always called such.

> There seem to be some of you out there that are such good designers
> and coders that you anticipate nearly everything and don't make
> dumb mistakes that you don't see no matter how many times you
> look at the code. I envy you and applaud you. Unfortunately,

Pick your tools. My point was anticipating the need for an ICE was
pessimistic, although that was beyond the scope of the original question
(which was very vague, BTW). ICE was not a part of the question.

> I am not one of those people and I've never had the pleasure
> of working with one AFAIK. Unless the system is very simple,
> problems of my own or those of others will crop up and as the firmware
> author I am usually in the best position to find them. Therefore,
> I believe I am being practical, not pessimistic. I don't understand
> what "these days" implies, as my projects have to be done faster,

"These days" there is a high level of integration, meaning there is
presumably much less hardware debugging between components when those
components are all on-board (on-chip). Another view is that most designs
are based upon stable reference designs, and the argument is about the same.
One should not _rely_ on an emulator to diagnose software composition
errors. When debugging hardware errors, there is no limit to the amount of
firepower that I would recommend. But that too, is beyond the OP's simple
question.

The OP was about 80's technology, so I admit lack of experience, or the need
for nostalgia.

[...]

There are days - I think I've had two. You get up in the morning, and code
all day without once compiling, or even stopping for lunch. You write hundreds
of LOC, and in the early evening try a compile. Everything compiles the first
time. No warnings. Everthing runs the first time. You never have to revisit the
code.

I think I've had two. I keep poor notes.

-- 
------------------------------------------------------------
Creepy, Soulless Gigolo for President ? NOT !
---------------------------------------------
THK is one weird, weird something.


Relevant Pages

  • Re: Emulator is slow
    ... I find the emulator is slower at doing it, ... Again, if it's the same speed for debugging, and one is unreliable, why ... >>Ethernet, as any other option was unbearable. ... >>> real devices connected via Ethernet. ...
    (microsoft.public.pocketpc.developer)
  • Re: Emulator Performance
    ... Is there any chance you could try your debugging on a fresh machine? ... > my app initialization is heavy due to form caching and DB preparations. ... > As a note, I'm using referenced DLLs in the app, and my app uses about 8 ... >> rather than on the emulator, but this is beyond the point. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Object reference not set to an instance of an object
    ... The last student built an application called ICE ACCRETION using Micr ... Win32 Version: 2.0.50727.42 ... To enable just-in-time debugging, ... When JIT debugging is enabled, ...
    (microsoft.public.dotnet.framework.aspnet)
  • PPC Emulator Debugging
    ... most of the replies in the newsgroup as I've tried to figure out the ... When debugging Smart Device Application in VS.Net, ... the physical device, but still no debugging on the emulator ... - Installation of Windows CE Utilities ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Does Evc4 can download executable file to wm5 device or emulator for debug or something else?
    ... Emulator" Installed, and it can sync by using activesync. ... But it will definitely not allow direct debugging on a WM 5 ... These choices come from the Pocket PC 2003 SDK you installed. ... For the few problems that still require indirect debugging, ...
    (microsoft.public.windowsce.embedded.vc)