Problems with starting new BSP

Fernando RUIZ CASAS (E-mail) fernando.ruiz at
Tue Jul 10 13:25:24 UTC 2001

> -----Mensaje original-----
> De: Radzislaw Galler [mailto:morib at]
> Enviado el: miércoles, 04 de julio de 2001 17:43
> Para: Joel Sherrill; Radzislaw Galler
> CC: rtems-users at; jmills at
> Asunto: Re: Problems with starting new BSP
> On Tuesday 03 July 2001 12:11, Joel Sherrill wrote:
> > When you say "reenabling interrupts", do you mean all
> potential interrupt
> > sources?  My gut instinct says that you have an
> uninitialized interrupt
> > source that is happening.  Do you have a spurious interrupt
> handler in
> > your BSP to report an unexpected interrupt?
> >
> > I don't know if there is a generic sh spurious interrupt
> handler like
> > there is for some other CPUs.  I think the m68k has a nice
> example of
> > one.
> >
> After I twiddled a bit with interrupts trying to catch the
> spurious ones the
> system started to work, but I don't know what helped, because
> when I tried to
> get back to the previous state (using old files) the system
> also worked.
> It could be that I lost couple of days seeking a nonexistent
> bug which only
> needed to touch sources and recompile the libraries  :)
> Anyway right now I'm quite suspicious about #pragma interrupt
> directive
> (although it works now).
The use of
#pragma interrupt
is forbbiden if you set the vectors with rtems directives.

Ralph has made a catch to place regular functions in the vector table.

Rebuid was ever a good trick in the worst case.

> Thanks
> Radek

home:correo at
work:fernando.ruiz at

More information about the users mailing list