Re: Debugging: Am I a dreamer. . . ?
- From: clubley@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (Simon Clubley)
- Date: 30 Apr 2008 08:35:50 -0500
In article <X0BDLJNJEFGIFAL8@xxxxxxxxxxxxxxxxxxxx>, Chris H <chris@xxxxxxxxxxxx> writes:
In message <48184695$0$23852$8404b019@xxxxxxxxxxxxxxx>, David Brown
<david@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> writes
What's wrong with debugging using printf? I don't mean specifically
"printf", which you should normally avoid in a small embedded system,
Well you have answered the question.
but the general idea of putting out extra information while the program
runs is a very useful debugging technique.
Yes but not the same as using printf.
Are you objecting to the use of the C function printf() within a embedded
environment for debugging or are you objecting to the use of serial port
output as a debugging tool ?
In AVR land, I don't use printf as it's bloated (by embedded standards),
but I do have my own interrupt based UART I/O routines that I use for
normal communication with other serial devices as well as debugging.
The routines implement a tty for the hardware UART as well as a Tx-only
software UART for debugging output. As both UART's are interrupt based,
and the output can be optionally buffered in an application specified
buffer, I see very little overhead in using the software UART for
outputting debug information.
Simon.
--
Simon Clubley, clubley@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Microsoft: Bringing you 1980's technology to a 21st century world
.
- Follow-Ups:
- Re: Debugging: Am I a dreamer. . . ?
- From: Chris H
- Re: Debugging: Am I a dreamer. . . ?
- References:
- Debugging: Am I a dreamer. . . ?
- From: Tomás Ó hÉilidhe
- Re: Debugging: Am I a dreamer. . . ?
- From: Chris H
- Debugging: Am I a dreamer. . . ?
- Prev by Date: Re: Debugging: Am I a dreamer. . . ?
- Next by Date: Re: Debugging: Am I a dreamer. . . ?
- Previous by thread: Re: Debugging: Am I a dreamer. . . ?
- Next by thread: Re: Debugging: Am I a dreamer. . . ?
- Index(es):
Relevant Pages
|