This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: A safe way to print debug output in DSRs ?
- To: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Subject: Re: [ECOS] A safe way to print debug output in DSRs ?
- From: Grant Edwards <grante at visi dot com>
- Date: Tue, 29 Aug 2000 15:57:06 -0500
- Cc: Jonathan Larmour <jlarmour at redhat dot co dot uk>,"Ecos-List (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
- References: <8AE4B526B977D411841F00A0CC334020052C31@cuz-exchange.sdesigns.net>
On Tue, Aug 29, 2000 at 01:52:52PM -0700, Fabrice Gautier wrote:
> > -----Original Message-----
> > From: Grant Edwards [mailto:grante@visi.com]
> > Subject: Re: [ECOS] A safe way to print debug output in DSRs ?
> >
> > If diag_printf does a busy-wait on a UART (as it does on my
> > system in hal_diag_write_char()), it can have a pretty big
> > timing impact on the DSR. If it doesn't get called too often
> > and the messages fit into the UART FIFO, then this isn't too
> > much of a problem -- but it's important to keep in mind as you
> > sprinkle diag_printf() around in the code.
>
> Has someone considered to add parallel port debug support? This could
> improve the ti ming problems, and should be easier to do than ethernet
> support. USB could be great too
> (Just in case someone is not busy enought...)
The diag_printf routine uses the hal_diag_write_char() routine,
so you can define that to do whatever you want with the data.
Writing it to a parallel port should be pretty trivial.
If you're talking about supporting bi-direction communication
with gdb via parallel port, then that's a bit more work...
--
Grant Edwards
grante@visi.com