From: nprasad3@gmu.edu
To: Gary Thomas <gary@mlbassoc.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] MPC860 eCos application
Date: Fri, 12 Dec 2003 15:07:00 -0000 [thread overview]
Message-ID: <8f0858fa6a.8fa6a8f085@gmu.edu> (raw)
Gary,
I started with a clean build for libTarget (setup startup configuration as RAM) but it seems to be always picking up the <variant>_rom.ldi file (<variant>_ram.ldi looks a bit different and has no rom section). I have verified my .cdl file several times but for some strange reason during build the wrong .ldi file is included.
The configtool gui shows that it will use <variant>_ram.ldi but still <variant>_rom.ldi contents show up in target.ld
Thanks in advance
Nirmal
----- Original Message -----
From: Gary Thomas <gary@mlbassoc.com>
Date: Thursday, December 11, 2003 11:08 pm
Subject: Re: [ECOS] MPC860 eCos application
> On Thu, 2003-12-11 at 18:55, nprasad3@gmu.edu wrote:
> > Hi,
> >
> > I have redboot working and i'm trying to write a simple
> application (just prints Hello eCos World!) but I seem to be
> missing something as redboot fails to load default .srec with the
> following message:
> >
> > *** Abort! Attempt to load S-record to address: 0xfff00000,
> which is not in RAM
> >
> > 1. Built libtarget.a (Work with ROM Monitor, Startup Mode : RAM)
> - target.ld still has references to rom.
> > STARTUP(vectors.o)
> > ENTRY(__exception_reset)
> > INPUT(extras.o)
> > GROUP(libtarget.a libgcc.a libsupc++.a)
> > MEMORY
> > {
> > ram : ORIGIN = 0x00001000, LENGTH = 0x1FFF000
> > rom : ORIGIN = 0xfff00000, LENGTH = 0x800000
> > }
> >
> > SECTIONS
> > {
> > .vectors 0xfff00000 : { . = .; KEEP(*(.vectors)) } > rom
> > .. etc (bunch of references to rom)
> > }
> >
> > 2. I modified the target.ld to change rom references to ram,
> [0xfff0000 -> 0x00007050] as redboot message is as [RAM:
> 0x00001000-0x02000000, 0x00007050-0x01fff000 available] and
> redboot loads the .srec file but my application does not run
> (*probably* its just the wrong printf i.e. target.ld is producing
> a copy of the printf whose state is different from the one redboot
> is using).
> >
> > How can I make my application refer to code that's in ROM
> (redboot has the printf which is working) but run from RAM?
>
> Try generating a whole new build tree just for this. Trying to adjust
> one from ROM to RAM mode is error-prone.
>
> --
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
>
>
> --
> Before posting, please read the FAQ:
> http://sources.redhat.com/fom/ecosand search the list archive:
> http://sources.redhat.com/ml/ecos-discuss
>
>
>
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-12-12 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 15:07 nprasad3 [this message]
2003-12-12 15:08 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2003-12-12 3:24 nprasad3
2003-12-12 9:20 ` 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=8f0858fa6a.8fa6a8f085@gmu.edu \
--to=nprasad3@gmu.edu \
--cc=ecos-discuss@sources.redhat.com \
--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).