public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Grant Edwards <grante@visi.com>
Cc: ecos-discuss@sources.redhat.com, Dave Airlie <airlied@parthus.com>
Subject: Re: [ECOS] PID ROM and eCos
Date: Wed, 24 Jan 2001 08:02:00 -0000	[thread overview]
Message-ID: <XFMail.20010124090159.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <20010124094608.A1646@visi.com>

On 24-Jan-2001 Grant Edwards wrote:
> On Wed, Jan 24, 2001 at 03:15:20PM +0000, Dave Airlie wrote:
> 
>> So my question is how feasible is to build eCos for RAM, and
>> build a small routine to link against it that boots up and
>> copies all of eCos into RAM and starts it ?
> 
> Piece of cake.
> 
>> Could I use something like redboot or anything like that for
>> this purpose or is a platform where this has been done ..
> 
> Sure, RedBoot would work great, but's it's overkill if all you
> want is to copy a single fixed image to RAM and execute it.
> That only takes 10-15 lines of assembly language.
> 
> You'll probably also want to re-map memory so that RAM is at
> address 0 instead of ROM (if possible). You can run eCos from
> RAM with ROM at 0, but it's a pain since you'll have to hack up
> the vectors.S file in hal/arm/arch/.

Look at the startup code for the Cirrus Logic EDB7xxx boards.  They
support this configuration where the image in ROM (FLASH or whatever)
is linked at an address different from where they are stored.  If
this case is detected, the ROM code simply gets copied to RAM at
startup time.  Look in the file:
  hal/arm/edb7xxx/current/include/hal_platform_setup.h

  reply	other threads:[~2001-01-24  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24  7:12 Dave Airlie
2001-01-24  7:27 ` Andrew Lunn
2001-01-24  7:42 ` Grant Edwards
2001-01-24  8:02   ` Gary Thomas [this message]
2001-01-24 11:08     ` Jonathan Larmour
2001-01-24 11:15       ` Dave Airlie
2001-01-24 11:20       ` Gary Thomas
2001-01-24 11:39         ` Jonathan Larmour
2001-01-25  9:53           ` Dave Airlie

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=XFMail.20010124090159.gthomas@cambridge.redhat.com \
    --to=gthomas@cambridge.redhat.com \
    --cc=airlied@parthus.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=grante@visi.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).