public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Tom Deconinck" <t.deconinck@gmail.com>
To: "Alois Z." <alois@gmx.at>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RAM Images on AT91SAM7s256
Date: Tue, 29 Jan 2008 12:19:00 -0000	[thread overview]
Message-ID: <e37cb5250801290055p6e6ef815r8a11e9decffe50f1@mail.gmail.com> (raw)
In-Reply-To: <20080128171909.64340@gmx.net>

Hi,

As Andrew stated, you will have to alter the startup code for the RAM
image to do the memory remapping so the vectors are located at 0x0.
Look at the ROM startup for reference.
I've done something similar on a AT91SAM7SE512, I used a BDI2000 JTAG
probe to load in my image though.

Regards,

Tom

On Jan 28, 2008 6:19 PM, Alois Z. <alois@gmx.at> wrote:
>
> -
> > > > How are you going to get this image into RAM?
> > >
> > > I thought of useing sam-ba for loading and starting images.
> >
> > O.K. But you need to find out what RAM sam-ba uses so you can avoid
> > it.
> >
> > > > You also need to make sure that RAM is mapped to address 0x0 as well
> > > > as 0x00200000. I know ROM startup does this, but i think RAM startup
> > > > probably does not.
> > > Is this necessary for the vectors to be at the right place?
> >
> > Yes. Without this, all your interrupts are not going to work etc.
> >
> >      Andrew
>
> Thanks that realy helped. So much to learn;-)
> Alois
>
> --
> Psssst! Schon vom neuen GMX MultiMessenger gehört?
> Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
>
> --
>
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>

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

  reply	other threads:[~2008-01-29  8:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 16:08 Alois Z.
2008-01-28 16:47 ` Andrew Lunn
2008-01-28 17:06   ` Alois Z.
2008-01-28 17:10     ` Alois Z.
2008-01-28 17:19     ` Andrew Lunn
2008-01-28 18:36       ` Alois Z.
2008-01-29 12:19         ` Tom Deconinck [this message]
2008-04-02  1:48           ` airdelroy
2008-04-02  6:12             ` Tom Deconinck
2008-04-05  0:14               ` airdelroy

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=e37cb5250801290055p6e6ef815r8a11e9decffe50f1@mail.gmail.com \
    --to=t.deconinck@gmail.com \
    --cc=alois@gmx.at \
    --cc=ecos-discuss@sources.redhat.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).