From: "Ali Sina" <replay688@hotmail.com>
To: gary@mlbassoc.com
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Redboot vs GDB application download (ARM E7T)
Date: Thu, 16 Jun 2005 20:46:00 -0000 [thread overview]
Message-ID: <BAY108-F29617AEB2392D0A7C65586EAF50@phx.gbl> (raw)
Hello,
is there any difference between loading an application to RAM and running it
there via Redboot as opposed to via GDB?
On the E7T with a ROM Redboot I observe the following:
- loading the app to RAM via GDB and starting it (continue) works fine.
Application has not crashed in months.
- loading the same code to RAM via Redboot (load -m xmodem) and starting it
(go) will start the application but the systems hangs after a few seconds.
Anyone a clue as to why this could be happening?
Thanks,
AS
>From: Gary Thomas <gary@mlbassoc.com>
>To: Ali Sina <replay688@hotmail.com>
>CC: eCos Discussion <ecos-discuss@ecos.sourceware.org>
>Subject: Re: [ECOS] E7T ROMRAM startup anyone? Alternatives?
>Date: Wed, 15 Jun 2005 13:48:35 -0600
>
>On Wed, 2005-06-15 at 19:39 +0000, Ali Sina wrote:
> > Hello all,
> >
> > another E7T question -
> > has anyone succeeded at implementing a ROMRAM startup for the ARM E7T?
> >
> > Or what other options are there for having an app. stored in ROM (see my
> > previous posts) and have it run from RAM?
> >
> > Can I somehow use Redboot "mcopy" in an automated way (i.e. upon
>startup) to
> > copy it from ROM to RAM and start it from RAM? (assuming the app was
> > compiled to run from RAM, of course)
> >
> > Any other ideas of how to achieve ROMRAM type of behavior?
>
>ROMRAM startup mode is really only for *the* monitor program, e.g.
>RedBoot. It's purpose is to take a program which has to run from
>FLASH/ROM from the start (e.g. the system initialization code) and
>allow it to run from RAM after some suitable minimal setup.
>
>RedBoot has FIS (FLASH Image System) which can store images. These
>can be programs or data. You simply put your RAM program into a
>FIS image then load and execute it at boot time.
>
>Sadly, I think the E7T has such little FLASH &/or RAM that these
>features are normally left turned off.
>
>--
>------------------------------------------------------------
>Gary Thomas | Consulting for the
>MLB Associates | Embedded world
>------------------------------------------------------------
>
_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee®
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
--
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 reply other threads:[~2005-06-16 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 20:46 Ali Sina [this message]
2005-06-17 19:34 ` Mark Salter
2005-06-18 6:46 ` Ali Sina
2005-06-18 7:15 ` Ali Sina
2005-06-20 15:24 ` Ali Sina
-- strict thread matches above, loose matches on Subject: below --
2005-06-17 19:22 Ali Sina
2005-06-15 19:48 [ECOS] E7T ROMRAM startup anyone? Alternatives? Gary Thomas
2005-06-17 10:18 ` [ECOS] Redboot vs GDB application download (ARM E7T) Ali Sina
2005-06-17 17:38 ` Paul D. DeRocco
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=BAY108-F29617AEB2392D0A7C65586EAF50@phx.gbl \
--to=replay688@hotmail.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).