From: Erik Christiansen <erik@dd.nec.com.au>
To: Judong Kim <jdkim@snssol.co.kr>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Is ecos 2.0 usable without redboot?
Date: Wed, 01 Jun 2005 01:58:00 -0000 [thread overview]
Message-ID: <20050601015634.GA1349@dd.nec.com.au> (raw)
In-Reply-To: <OFEPJEEHNEOHPACEGGNFIEBGCAAA.jdkim@snssol.co.kr>
On Wed, Jun 01, 2005 at 08:57:09AM +0900, Judong Kim wrote:
> And ported HAL, the same one in the ecos 1.3.1, to ecos 2.0.
While not yet well experienced with ecos, I'd guess that mixing
potentially incompatible versions of HAL and kernel is a pioneering act,
subject to adventures.
> The problem is ecos 2.0 application doesn't work. even there is no
> message at all. It just reboots again and again. It seems forever.
...
> Is there any another problems I should consider?
If I correctly understand your reference to porting the HAL, is it
possible that this is not complete. e.g. if
cyg_hal_invoke_constructors() is not called, you'll see things like
crash/reboot when the idle thread should run. (All other threads
blocking)
We're finishing off our first board port now, and find (as usual) that
there's no substitute for an ICE, even if only JTAG, so that reasoning
can be based on some hard evidence.
Incidentally, we're not using redboot, so the answer to the question
asked in the subject line is: Yes
Erik
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
parent reply other threads:[~2005-06-01 1:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <OFEPJEEHNEOHPACEGGNFIEBGCAAA.jdkim@snssol.co.kr>]
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=20050601015634.GA1349@dd.nec.com.au \
--to=erik@dd.nec.com.au \
--cc=ecos-discuss@sources.redhat.com \
--cc=jdkim@snssol.co.kr \
/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).