Re: Debugging: Am I a dreamer. . . ?

On Tue, 29 Apr 2008 16:45:34 -0700, Tomás Ó hÉilidhe wrote:

I've been programming in C for the best part of a decade now but it's
only within the last year that I've really started doing embedded
systems programming.

When I did C programming for a personal computer, I commonly debugged my
code simply by putting in printf statements around the place to check
variable values, and also by using the instrument that lets you check
the values of variables at runtime when you're stepping through the
code.

Anyway, when I was doing my embedded systems project this year for
college, I was kind of in the dark when my board's program started to
malfunction. If I'd been using a PC, I would have used the debugger to
single-step through code to check variables' values. What I eventually
did was take the offending code and move it across to a PC, and then I
used the PC to debug it.

Anyway, here's the dream I had in my head, which may or may not be a
pipe dream:
You know the PIC16F684 chip that costs less than a dollar, well
what if they brought out the debug version of it (that costs maybe 20
dollars). The debug version would fit perfectly into the normal chip
slot, except that it would have some sort of socket on the top of it for
hooking it to a PC for doing stuff like printf's, and also maybe for
running a full debugger that will let you check variables' values?

Many chips have in-circuit debugging features, including that one. Read
the fine manual. Few require the chip-and-socket approach -- that's more
of an 80's/90's thing.

For some applications you'll find that reserving a pin (or pins) for
debugging that you can twiddle with in software instead of a printf is
more valuable than gold. Given an oscilloscope, not only will it tell
you _that_ your code executes, but if you're careful it'll tell you when
and for how long.

--
Tim Wescott
Control systems and communications consulting
http://www.wescottdesign.com

Need to learn how to apply control theory in your embedded system?
"Applied Control Theory for Embedded Systems" by Tim Wescott
Elsevier/Newnes, http://www.wescottdesign.com/actfes/actfes.html
.

Relevant Pages

  • Re: Teaching Assembly Language Programming
    ... And, as I stated, real programmers don't use a debugger at all. ... whereas he does not respond to Rod Pemberton because Rod Pemberton ... I had intended to start a programming ... with you, but my wife, who is a university teacher, in psycho ...
    (alt.lang.asm)
  • Re: Debugging: Am I a dreamer. . . ?
    ... When I did C programming for a personal computer, ... If I'd been using a PC, I would have used the debugger to ... used the PC to debug it. ... You know the PIC16F684 chip that costs less than a dollar, ...
    (comp.arch.embedded)
  • Re: Help me about this question.
    ... documented Intel manual and not in their ability to solve programming ... advantages of the C and Pascal calling conventions. ... I had to use the debugger to follow the data ... Or that you are solving it again, in a diffrent way, under a diffrent sets of environment, with surrounding code that has a set of completely diffrent properties that the last time you solved a similar problem. ...
    (alt.lang.asm)
  • Re: Annoying Error with Salford FTN95 Supplied Debugger Plato3
    ... absence and the compiler I am using is Salford's FTN95. ... There is a debugger that comes with this called Plato3, ... honest I am a bit unused to debuggers as back when I was programming I ... EVERY line I try to set a breakpoint on, ...
    (comp.lang.fortran)
  • Re: What is a stack frame?
    ... this group claim that a good C programmer needs no debugger. ... structured code bases for which you are almost solely responsible for. ... mixture of C and C++ programming (yes, I know many here have longer ... Emacs is falling behind the curve unfortunately. ...
    (comp.lang.c)