This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Serial port used by both RedBoot and a program
- To: 'Jesper Skov' <jskov at redhat dot com>
- Subject: RE: [ECOS] Serial port used by both RedBoot and a program
- From: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Date: Thu, 9 Nov 2000 10:23:28 -0800
- Cc: Andrew Lunn <andrew dot lunn at ascom dot ch>, "Ecos-List (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
> -----Original Message-----
> From: Jesper Skov [mailto:jskov@redhat.com]
> Subject: Re: [ECOS] Serial port used by both RedBoot and a program
>
>
> >>>>> "Fabrice" == Fabrice Gautier
> <Fabrice_Gautier@sdesigns.com> writes:
>
> Fabrice> How does that works exactly ? The corresponding entries in
> Fabrice> the vector table are disabled or something like that ?
>
> No. What happens is that the stubs enable serial receive interrupts,
> but do not change the vector. When a serial interrupt happens, it
> causes the cyg_hal_default_isr of the application to be run. This
> calls into the stub (via the virtual vectors) which determines if the
> received character was a 0x03. If so, a breakpoint is put at the PC
> where the interrupt happened.
Ok for the isr and the ctrl-C stuff, but what happens about diagnostic
output that are sent throught the vector table to the serial port ?
Thanks
--
Fabrice Gautier
fabrice_gautier@sdesigns.com