From: Gary Thomas <gary@mlbassoc.com>
To: alysson brito <alysson.alysson@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: Trash when running RAM image
Date: Wed, 02 May 2007 15:10:00 -0000 [thread overview]
Message-ID: <4638A9E0.2000909@mlbassoc.com> (raw)
In-Reply-To: <876437dd0705020802p3aa1463dud27d963ed09fa5eb@mail.gmail.com>
alysson brito wrote:
> Hi
> I am newbie on RedBoot. I am using redboot on an intel board.
> I am [trying] to load and run a RAM image, since I do not want to mess
> up the currently [runnable] image that is on the rom memory and is
> working.
> But the image I got from intel and the image I built from the sources
> are showing up some trash on the console when i execute them
> [for instance: $T0a0f:0c002000;0d:ec0ffd03;#39]. This pattern goes on
> an on for each key I press.
> I am loading the file redboot_RAM.srec [load -v -r -m xmodem -b
> 0x00200000 redboot_RAM.srec] [I also tried via tftp, same result...]
> and shooting "go" ro make it run, but all the time I get this output.
> Would any know what might be wrong ? I'd guess I am executing a some
> memory position that has nothing there ... But I do not know how to go
> on. Any help would be really appreciated.
>
> I also tryed "go redboot_RAM.srec" but it did not work either...
The options you are using for the download is causing the problem.
Try this:
RedBoot> lo -m xm redboot_RAM.srec
RedBoot> go
Your options do two things wrong:
-r: downloads the image raw, which means you've loaded ASCII S-records
into memory - these are not executable instructions
-b: eCos programs are not relocatable, hence they must be loaded at
their native address. 0x200000 is probably not the correct address.
--
------------------------------------------------------------
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
next prev parent reply other threads:[~2007-05-02 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <876437dd0705020801t68d84716s9a8c1c8be3dfa2a3@mail.gmail.com>
2007-05-02 15:02 ` alysson brito
2007-05-02 15:10 ` Gary Thomas [this message]
2007-05-02 17:17 ` alysson brito
2007-05-02 17:26 ` Adam Yergovich
2007-05-03 11:35 ` alysson brito
2007-05-03 11:57 ` Chris Zimman
2007-05-03 12:54 ` alysson brito
2007-05-04 11:43 ` alysson brito
2007-05-04 11:48 ` 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=4638A9E0.2000909@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=alysson.alysson@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).