From: "alysson brito" <alysson.alysson@gmail.com>
To: ecos-discuss@ecos.sourceware.org, "Adam Yergovich" <ayergo@jkmicro.com>
Subject: Re: [ECOS] Re: Trash when running RAM image
Date: Thu, 03 May 2007 11:35:00 -0000 [thread overview]
Message-ID: <876437dd0705030435p1f891falfa3e256a1e495c3e@mail.gmail.com> (raw)
In-Reply-To: <4638C9B6.4020504@jkmicro.com>
Hi Adam and all
On 5/2/07, Adam Yergovich <ayergo@jkmicro.com> wrote:
> Hi Alysson,
>
> alysson brito wrote:
>
> > Thanks Gary!
> >
> > I really should have payed more attention.
> >
> > Actually, the result was [almost] the same though :(
> >
> > RedBoot> load -m xm redboot_RAM.srec
> > CCEntry point: 0x00020040, address range: 0x00020000-0x00046d5c
> > xyzModem - CRC mode, 3574(SOH)/0(STX)/0(CAN) packets, 5 retries
> > RedBoot> go
> > $T050f:54000200;0d:ec0ffd03;#e3
> >
> > I have also tryed to up load the .bin image (using the -r) but it did
> > not work out either:
> >
> > RedBoot> load -r -m xm -b 0x00020040 redboot_RAM.bin
> > CCRaw file loaded 0x00020040-0x00046d9b, assumed entry at 0x00020040
> > xyzModem - CRC mode, 1243(SOH)/0(STX)/0(CAN) packets, 2 retries
> > RedBoot> go
> > $T0a0f:0002014c;0d:ec0ffd03;#3e
> >
> > I guess i am almost out of options ... Any other idea of what is still
> > wrong ?
> >
>
> In my experience, that is the kind of output you get when you try to
> execute something that is not executable or is not properly setup (i.e.
> turning on the MMU before executing a kernel).
>
> Perhaps I have just never done it, but I don't thinnk one usually
> executes a ramdisk. I might suggest you take your known good ramdisk in
> rom and try to load it the same way to see what happens.
>
> -Adam
>
>
> --
> Adam Yergovich
> Engineer
> JK Microsystems
>
> 1403 Fifth St. Suite D
> Davis, CA 95616
>
> Tel:(530) 297-6073
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>
Thanks for the reply! Actually I am trying to run an RAM image of
redboot, not a ramdisk, I might have written something wrong, sorry.
The problem still persists, I have seen that Gary wrote today on "Re:
[ECOS] standalone Redboot configuration" that some ARM have to get
some massage to runging RAM images, I do not know whether this is a
case, since xscale is arm based.
If some one can help me out really I'd really apreciated some more tips.
-- Alysson
--
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-03 11:35 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
2007-05-02 17:17 ` alysson brito
2007-05-02 17:26 ` Adam Yergovich
2007-05-03 11:35 ` alysson brito [this message]
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=876437dd0705030435p1f891falfa3e256a1e495c3e@mail.gmail.com \
--to=alysson.alysson@gmail.com \
--cc=ayergo@jkmicro.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).