public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Chris Garry" <cgarry@sweeneydesign.co.uk>
To: "xie boyan" <xieboyan@hotmail.com>, <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Why the application run on redboot uncorrectly?
Date: Thu, 27 Nov 2003 10:55:00 -0000	[thread overview]
Message-ID: <010101c3b4d5$8c0557e0$500ba8c0@jasper> (raw)
In-Reply-To: <BAY1-F41nQAn77fcGuK00006ac4@hotmail.com>

----- Original Message ----- 
From: "xie boyan" <xieboyan@hotmail.com>
To: <ecos-discuss@sources.redhat.com>
Sent: Thursday, November 27, 2003 1:53 AM
Subject: Re: [ECOS] Why the application run on redboot uncorrectly?


> 
> > > > I download the hello elf file by using command:
> > > >     load -v -h MyHost -m tftp /tftpboot/hello
> > > > and it failed by displaying "Abort! Attempt to load ELF data to 
> address:
> > > > 0x00020000 which
> > > > is not  in RAM."
> > >
> > > A little logical thinking is required. "is not in RAM" probably means
> > > its trying to load it into ROM. So you have probably built a ROM
> > > app. Try building a RAM application.
> > >
> > >      Andrew
> >
> >But for the snds platform if nothing is changed 0x20000 is RAM. It should
> >be right.
> >
> >Maybe RedBoot is a RAM version?
> >
> >Roland
> 
> Hi, Roland
> 
> My RedBoot is exactly the ROM version and my application is definitely the 
> RAM version. I have read some earlier archives in mailing list, the same 
> issue occured but it seems not have a final answer.
> This especially seems to be a problem of snds eval board, mybe you can find 
> out some bugs in the redboot source in the package?
> 
> I've tried to enforce the base=0x300000 in the entry of function 
> load_elf_image() whithin the source file load.c in the redboot source 
> directory, and the command
>       RedBoot> load -v -h MyHost_IP -m tftp /tftpboot/hello
> works out. It looks all right because of the screen messages are OK, 
> especially the memory size which contain the downloaded elf codes exactly 
> equal to the original elf file size in host. I think this means that the 
> source of redboot has at least a load base address bug.
> 
> The first problem, i.e. the elf load, has been resolved by temporarily 
> enforcing base=0x300000, but another problem comes up. When I do "GO" 
> command, the application hello still does not say "Hello !".
> 

The "Abort! Attempt to load ELF data to address: 0x00020000 which
is not in RAM." message will also be seen when you try to load an
image into RAM that RedBoot is already using.

What RAM does RedBoot report as 'available' when it first runs?

Chris




-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  reply	other threads:[~2003-11-27 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27  1:53 xie boyan
2003-11-27 10:55 ` Chris Garry [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-26  2:23 xie boyan
2003-11-26  8:24 ` Andrew Lunn
2003-11-26  9:31   ` Roland Caßebohm
2003-11-25  1:38 xie boyan
2003-11-25  8:35 ` Andrew Lunn
2003-11-25 11:00   ` Nick Garnett

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='010101c3b4d5$8c0557e0$500ba8c0@jasper' \
    --to=cgarry@sweeneydesign.co.uk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=xieboyan@hotmail.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).