From: Andrew Lunn <andrew@lunn.ch>
To: John Mills <john.m.mills@alum.mit.edu>
Cc: ecos-discuss@ecos.sourceware.org, Andrew Lunn <andrew@lunn.ch>
Subject: [ECOS] Re: eCos configuration question (was Re: [ECOS] General Q ...)
Date: Thu, 31 May 2007 15:21:00 -0000 [thread overview]
Message-ID: <20070531151854.GM32489@lunn.ch> (raw)
In-Reply-To: <Pine.LNX.4.44.0705310930230.28807-100000@otter.localdomain>
On Thu, May 31, 2007 at 09:50:50AM -0500, John Mills wrote:
> Leaving aside my responses to Andrew cut in below:
>
> 1. How should I set or clear this switch in my *.ecc files? I don't
> recognize the entry in 'configtool'. Should I edit the *.ecc and
> regenerate the tree? Edit the affected 'hal.h'?
You should never need to edit a .h file. I personally never use the
gui tool. I find it much easier just to edit the ecos.ecc file and use
ecosconfig
> > Is CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE true?
> Yes:
> ../trapeze/ECOSBUILD/dist/install/include/pkgconf/hal.h:
> #define CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE 1
I would expect this to be true for your Redboot true, but false for
you application tree. Look at your application ecos.ecc. Does it get
the value from the default_value statement, or has it been set by the
user_value? That will tell you if somebody has deliberately changed
it, or it is derived from other configuration settings.
> > cdl_option CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE {
> > display "Initialize whole of virtual vector table"
> > default_value { CYG_HAL_STARTUP != "RAM" ||
> > !CYGSEM_HAL_USE_ROM_MONITOR }
>
> > do you have a RAM image?
>
> Not of RedBoot. Our eCos app is expanded into RAM for execution, but
> RedBoot lives in FLASH.
So for your RedBoot tree CYG_HAL_STARTUP == ROM and for your
application tree CYG_HAL_STARTUP == RAM
> > Is CYGSEM_HAL_USE_ROM_MONITOR true?
> Apparently not, if I 'grep'ed right.
I would expect this to be false for the RedBoot tree, but true for the
Application tree.
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
next prev parent reply other threads:[~2007-05-31 15:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 17:02 [ECOS] General Q: Calling RedBoot CLI function from eCos app John Mills
2007-05-30 17:12 ` Gary Thomas
2007-05-30 17:16 ` Andrew Lunn
2007-05-30 17:20 ` Andrew Lunn
2007-05-30 17:58 ` John Mills
2007-05-30 19:18 ` John Mills
2007-05-30 21:00 ` Andrew Lunn
2007-05-30 21:06 ` John Mills
2007-05-30 21:41 ` Andrew Lunn
2007-05-31 15:01 ` [ECOS] eCos configuration question (was Re: [ECOS] General Q ...) John Mills
2007-05-31 15:19 ` Gary Thomas
2007-05-31 15:21 ` John Mills
2007-05-31 15:21 ` Andrew Lunn [this message]
2007-05-31 16:41 ` [ECOS] " Grant Edwards
2007-05-31 17:09 ` [ECOS] Re: eCos configuration question Sergei Organov
2007-05-31 17:24 ` [ECOS] Re: eCos configuration question (was Re: [ECOS] General Q ...) Paul D. DeRocco
2007-05-31 17:30 ` Gary Thomas
2007-05-31 17:35 ` Grant Edwards
2007-05-31 19:01 ` Andrew Lunn
2007-05-31 17:18 ` [ECOS] " Sergei Gavrikov
2007-06-01 8:10 ` [ECOS] Re: eCos configuration question Daniel Néri
2007-06-01 9:04 ` Sergei Gavrikov
2007-06-01 14:23 ` Grant Edwards
2007-06-01 14:30 ` Gary Thomas
2007-06-01 14:37 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070531151854.GM32489@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john.m.mills@alum.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).