From: Jesper Skov <jskov@cambridge.redhat.com>
To: "Chris C." <phchang@programmer.net>
Cc: jskov@cambridge.redhat.com, ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] RedBoot Problems!
Date: Wed, 25 Jul 2001 03:21:00 -0000 [thread overview]
Message-ID: <15198.40354.41089.873599@zoftcorp.adsl.dk> (raw)
In-Reply-To: <20010725100727.3411.qmail@mail.com>
>>>>> "Chris" == Chris C <phchang@programmer.net> writes:
Chris> 1. I have updated the latest version of repository and selected
Chris> the redboot template (PID platform) to build the redboot but
Chris> some errors occured. I haven''t change anything.
>> Did you import the redboot_R[AO]M.ecm file?
Chris> Why need to import the redboot_R[AO]M.ecm file? I found that
Chris> there are two files, so which file I need to import or import
Chris> both of them?
For RAM startup import _RAM.ecm, for ROM startup import _ROM.ecm. They
set some additional parameters not set by the template.
Chris> 3. I knew that redhat will release a platform HAL for AT91EB40,
Chris> shall I modifiy the sources in the redboot package so that it
Chris> can port to the AT91EB40?
>> No, that will already have been done.
Chris> If I want to port the reboot to the AT91EB40, do I need to
Chris> write the ecm files [ram and rom] for AT91EB40?
Yes - but as I said, have patience: there'll be released a RedBoot
port for AT91EB40 in a week or so.
Chris> If I select another template [not redboot], do I need to write
Chris> the ecm files?
No.
Chris> I don't know how to write the ecm file, where can I find some
Chris> reference materials.
.ecm files are just configuration settings. They are created using the
ecosconfig export option (and similar, if existant, in the graphical
configuration tool).
Chris> If I want to download a testing program to the target board via
Chris> gdb stub [rom startup], do I need the flash programmming tool?
Don't know if it's needed to put RedBoot in flash, or if there's
already a board monitor there. Wait for the RedBoot release - it'll
have documentation for getting started.
Jesper
next prev parent reply other threads:[~2001-07-25 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 3:07 Chris C.
2001-07-25 3:21 ` Jesper Skov [this message]
2001-07-25 5:29 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2001-07-30 7:10 Chris C.
2001-07-30 7:20 ` Gary Thomas
2001-07-24 22:12 Chris C.
2001-07-25 1:14 ` Jesper Skov
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=15198.40354.41089.873599@zoftcorp.adsl.dk \
--to=jskov@cambridge.redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=phchang@programmer.net \
/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).