Re: [ECOS] #error " no RESET_ENTRY" ??

[Jonathan Larmour <jlarmour@redhat.com>]

Grant Edwards wrote:
> 
> On Wed, Jan 10, 2001 at 12:36:26AM +0000, Jonathan Larmour wrote:
> 
> > > I'm trying to impliment virtual vector support in my HAL, but I
> > > can't get it to build.  I am getting the following error
> > >
> > > /opt/ecos/ecos-cvs/ecos/packages/hal/common/current/src/hal_if.c:143: #error " no RESET_ENTRY"
> > >
> > > The problem seems to be that my plf_stubs.h file only defines a
> > > reset entry point if CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS is
> > > defined (because that's what the edb7xxx HAL does it).
> >
> > It doesn't in current CVS. Perhaps your CVS tree predates virtual vectors
> > getting added for the edb7xxx (it was 5th July it got added).
> 
> Vitrual vector support is in my snapshot of the edb7xxx
> HAL (it's the one after which I'm modelling mine. My CVS tree
> is from about a month ago.  The last entry in the ChangeLog is
> 
> 2000-11-25  Jonathan Larmour  <jlarmour@redhat.com>
[snip]

That is recent enough. Perhaps you misread plf_stub.h? It's definitely
after the #endif:

#endif // ifdef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS

//----------------------------------------------------------------------------
// Reset.

// Try and force the board into a reset state.  Since this hardware
requires
// a "wakeup" signal, we can't just use a watchdog/reset approach.
externC void reset_platform(void);
#define HAL_STUB_PLATFORM_RESET() reset_platform()

#define HAL_STUB_PLATFORM_RESET_ENTRY 0xe0000000



Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine