This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: how to test Redboot version/configuration from within ecos application
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "Neundorf, Alexander" <Alexander dot Neundorf at jenoptik dot com>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Thu, 3 Nov 2005 17:38:08 +0100
- Subject: Re: [ECOS] how to test Redboot version/configuration from within ecos application
- References: <5A8A17126B73AC4C83968F6C4505E3C502F1E85F@JO-EX01.JENOPTIK.NET>
On Thu, Nov 03, 2005 at 09:51:02AM +0100, Neundorf, Alexander wrote:
> Hi,
>
> in our device we did something not-really perfectly in redboot. Now
> we fixed this and have a slightly different version. We can work
> around this issue in the application, but we have to find out which
> of the two redboots is running on this board.
>
> Is there a way to check for the version or configuration of redboot,
> e.g. by using a virtual vector ? I didn't find a suitable one yet.
Why not use the VV call CYGACC_CALL_IF_MONITOR_VERSION_SET. This
returns the version string Redboot prints at startup. You can parse
this string to get the build data and time. You can then say that
anything built before 03/11/2005 is broken and anything after that
date might work until you find the next bug.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss