This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: General Q: Calling RedBoot CLI function from eCos app
- From: John Mills <johnmills at speakeasy dot net>
- To: ecos-discuss at ecos dot sourceware dot org
- Cc: Andrew Lunn <andrew at lunn dot ch>
- Date: Wed, 30 May 2007 16:03:14 -0500 (EST)
- Subject: Re: [ECOS] General Q: Calling RedBoot CLI function from eCos app
- Reply-to: John Mills <john dot m dot mills at alum dot mit dot edu>
Andrew -
Thanks for the reply.
On Wed, 30 May 2007, Andrew Lunn wrote:
> On Wed, May 30, 2007 at 02:11:43PM -0500, John Mills wrote:
> > Andrew -
> >
> > Thanks for the lead, but in my eCos app that macro just expands to NULL.
> > The same code line works perfectly in RedBoot's 'main.c', however.
>
> What is the value of CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_VERSION in you
> application? See hal/common/current/src/hal_if.c
I find in my package configuration:
/home/jmills/depot/trapeze/ECOSBUILD/dist/install/include/pkgconf/hal.h:
#define CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_VERSION 1
If I understand your track here, that would activate the following lines
in 'hal_if.c':
#ifdef CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_VERSION
CYGACC_CALL_IF_MONITOR_VERSION_SET(0);
#endif
which, I suppose, would in turn cause
CYGACC_CALL_IF_MONITOR_VERSION() to resolve as '0', or NULL.
Hence my <null> print string.
Is that sensible?
- John
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss