From: Edgar Grimberg <edgar.grimberg@zylin.com>
To: wb ning <helloningwb@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Do anyone has at91sam7s - Redboot of RAM startup
Date: Tue, 29 Dec 2009 10:02:00 -0000 [thread overview]
Message-ID: <d0f570ed0912290202g2706a732pe2273864b2f62e74@mail.gmail.com> (raw)
In-Reply-To: <44185a820912290049v4bce5b07q6190a60cd30c6b1@mail.gmail.com>
On Tue, Dec 29, 2009 at 9:49 AM, wb ning <helloningwb@gmail.com> wrote:
> I just want to get a prebulit redboot of is RAM startup.
>
> Because i can't bulid a RAM startup redboot or a RAM startup
> application on at91sam7s. The rom startup redboot and application(such
> as hello world) is ok.
>
> The website http://ecos.sourceware.org/ecos/boards/at91sam7s.html
> claims that "Prebuilt binaries of RedBoot are available for download
> for both ROM and RAM startup." But i found it's a joke, i can only
> find ROM version there.
Maybe this will work:
http://ecos.sourceware.org/cgi-bin/cvsweb.cgi/ecos/images/arm/at91/?cvsroot=ecos
On the other hand, you should be able to build your own. If not, maybe
it's better to start understanding why you cannot build a RAM
application.
> Can somebody tell me how to get one? I do need RedBoot running in RAM,
> so i can use it to debug my application in ROM.
If you want to debug the application in ROM, you'd better start
looking for a JTAG debugger.
Edgar
--
Edgar Grimberg
System Developer
Zylin AS
ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html
Phone: (+47) 51 63 25 00
--
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:[~2009-12-29 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 8:50 wb ning
2009-12-29 10:02 ` Edgar Grimberg [this message]
2009-12-29 15:17 ` [ECOS] " John Dallaway
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=d0f570ed0912290202g2706a732pe2273864b2f62e74@mail.gmail.com \
--to=edgar.grimberg@zylin.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=helloningwb@gmail.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).