From: "Gregg C Levine" <hansolofalcon@worldnet.att.net>
To: "'Gary Thomas'" <gary@mlbassoc.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] New problem with building eCos--see output
Date: Tue, 11 Nov 2003 16:56:00 -0000 [thread overview]
Message-ID: <004701c3a874$dd132d00$0100a8c0@who5> (raw)
In-Reply-To: <1068554645.9906.303.camel@hermes>
Hello (again) from Gregg C Levine
This is for an ordinary x86 based computer setup, something along the
lines of the unit that I used to build the binaries on. It's the I386
template.
-------------------
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke." Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )
> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com [mailto:ecos-discuss-
> owner@sources.redhat.com] On Behalf Of Gary Thomas
> Sent: Tuesday, November 11, 2003 7:44 AM
> To: Gregg C Levine
> Cc: ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] New problem with building eCos--see output
>
> On Mon, 2003-11-10 at 20:32, Gregg C Levine wrote:
> > Hello from Gregg C Levine
> > It seems I am forever having problems with eCos. This time during
the
> > building of Red Boot, the build process gets interrupted when it
needs
> > to decide if the board in question will have any flash memory. (It
> > will, I don't know how much.) That step stops it from continuing
from
> > building any form of Red Boot. Prior to the inclusion of the ECM
file
> > for building a redboot.bin binary, it worked and I could get a
> > redboot.elf file built. I've put the output from the whole process
> > below my signature. The usual rules apply.
>
> What platform is this for? How did you configure it?
>
> What I can see from the dump you sent is that somehow you've enabled
> the FLASH sub-system, but there are no FLASH drivers present. This
> is not supposed to happen, so I'd like to know the steps you took
> to get here.
>
> --
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
>
>
> --
> Before posting, please read the FAQ:
http://sources.redhat.com/fom/ecos
> and search the list archive:
http://sources.redhat.com/ml/ecos-discuss
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-11-11 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 3:31 Gregg C Levine
2003-11-11 12:44 ` Gary Thomas
2003-11-11 16:56 ` Gregg C Levine [this message]
2003-11-11 17:02 ` Gary Thomas
2003-11-11 17:17 ` Gregg C Levine
2003-11-11 17:19 ` Gary Thomas
2003-11-11 17:33 ` Gregg C Levine
2003-11-11 17:38 ` Gary Thomas
2003-11-11 17:59 ` Gregg C Levine
2003-11-11 18:06 ` Gary Thomas
2003-11-12 8:56 ` Roland Caßebohm
2003-11-12 12:18 ` Gary Thomas
2003-11-12 20:21 ` Gregg C Levine
2003-11-12 22:24 ` Gary Thomas
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='004701c3a874$dd132d00$0100a8c0@who5' \
--to=hansolofalcon@worldnet.att.net \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary@mlbassoc.com \
/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).