This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Tracing and Debug
- To: 'Jonathan Larmour' <jlarmour at redhat dot co dot uk>
- Subject: RE: [ECOS] Tracing and Debug
- From: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Date: Fri, 21 Jul 2000 17:47:13 -0700
- Cc: eCos discussion <ecos-discuss at sources dot redhat dot com>, Gary Thomas <gthomas at redhat dot com>, Jesper Skov <jskov at redhat dot com>
> From: Jonathan Larmour [mailto:jlarmour@redhat.co.uk]
> Subject: Re: [ECOS] Tracing and Debug
>
> [ Please remember to CC the list. I don't do one-to-one
> support for free
> :-) ]
[Oups! sorry...]
> Fabrice Gautier wrote:
> > Init device '/dev/ttydiag'
> > Init tty channel: 27E6C
> > Init device '/dev/haldiag'
> > HAL/diag SERIAL init
> > Init device '/dev/ser0'
> > Set output buffer - buf: 296C4 len: 512
> > Set input buffer - buf: 298C4 len: 512
> > ASSERT FAIL: <1>intr.cxx [ 426] void
> Cyg_Interrupt::attach()
> > Interrupt vector not free.
>
> And here is your problem. The serial drivers have been
> enabled, but this is
> conflicting with the external break support because both want to put
> interrupt handlers on the serial line. You cannot have both.
Hum...
So I shouldn't have HAL/diag serial device driver
enabled(CYGPKG_IO_SERIAL_HALDIAG) when i include the GDB stubs in HAL with
GDB external break support (CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS and
CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT) ?
But I don't see why the problem only occurs when I enable tracing? I seemed
to run fine before.
I'm not sure I get the whole picture about the way the GDB, the GDB stub and
ecos manage the serial port.
But I understand that if I remove the HAL/diag serial driver I can't use the
standard IO functions in the C lib (CYGPKG_LIBC_STDIO require
CYGPKG_IO_SERIAL_HALDIAG) . So it should not be possible to use the same
serial port for both the eCos diag output and GDB stuf ?? But in the default
configuration of the ARM PID BOARD the Diagnostic Serial Port and the GDB
Serial Port are both set to 0.
> Admittedly, it shouldn't have been possible to do this without the
> configuration whinging at you.
I'm not sure, it worked fine without tracing...
(I will check again for the other building problem - and perhaps will try
the cvs stuff once I found any good cvs tool for Windows)
Thanks
A+
--
Fabrice Gautier
fabrice_gautier@sdesigns.com