From: "Jacob Avraham" <jacob@imagine-com.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] standalone Redboot configuration
Date: Thu, 03 May 2007 12:17:00 -0000 [thread overview]
Message-ID: <395D1D85A454F14CB58638B1AC60D7093EC55E@server.imagine-com.local> (raw)
In-Reply-To: <4639C257.8040904@mlbassoc.com>
> -----Original Message-----
> From: Gary Thomas [mailto:gary@mlbassoc.com]
> Sent: Thursday, May 03, 2007 2:07 PM
> To: Jacob Avraham
> Cc: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] standalone Redboot configuration
>
> Jacob Avraham wrote:
> > Hi,
> >
> > I'd like to run a standalone configuration of Redboot out of RAM,
using
> > a BDI debugger
> > to download it to memory. I tried redboot_RAM, but after some
> > instructions it trapped
> > into debug mode.
> > Is redboot_RAM capable of running standalone, or does it rely on
> > pre-existing setup
> > That perhaps redboot_ROM is doing?
> > How should I configure redboot to run standalone out of RAM?
>
> What's the platform? Most targets can run RedBoot from RAM,
> but some (in particular most ARM targets) cannot without some
> massaging.
>
The target is IXDP425
> --
> ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> ------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-05-03 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 6:54 Jacob Avraham
2007-05-03 11:07 ` Gary Thomas
2007-05-03 12:17 ` Jacob Avraham [this message]
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=395D1D85A454F14CB58638B1AC60D7093EC55E@server.imagine-com.local \
--to=jacob@imagine-com.com \
--cc=ecos-discuss@ecos.sourceware.org \
--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).