This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: GDB connection via TCP
- To: 'Gary Thomas' <gthomas at redhat dot com>
- Subject: RE: [ECOS] GDB connection via TCP
- From: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Date: Tue, 24 Oct 2000 12:34:42 -0700
- Cc: "Ecos-List (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
> -----Original Message-----
> From: Gary Thomas [mailto:gthomas@redhat.com]
> Subject: RE: [ECOS] GDB connection via TCP
>
> On 24-Oct-2000 Fabrice Gautier wrote:
> > I do not understand how this is handled with the assabet
> > board which have
> > basically the same scenario with the ethernet driver in Redboot.
> >
>
> The main difference is that in the other environments, RedBoot runs in
> ROM which turns on CYGSEM_HAL_ROM_MONITOR which in turn
> changes a number of internal behaviours.
As far as I can understand ARM assembly (which is not very far) it seems
that the VSR table entries are reinitialised by the RAM application (line
290 in vetors.S I think).
It seems that in fact Redboot never enable IRQs but the ethernet card is
still configured to generate those IRQ so that when the real application is
started and interrupts enabled we get those spurious interrupts.
Why this would not occur with other board or arch is still a mistery for me.
Is there a way for Redboot to initialise the ethernet driver so that it
would not trigger interrupts ?
Thanks
--
Fabrice Gautier
fabrice_gautier@sdesigns.com