LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mohammad Sadegh Sadri <mamsadegh@hotmail.com>
To: Linux PPC Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Virtex-4 PPC405 first instruction after reset - ultracontroller vs regular designs
Date: Sun, 29 Apr 2007 21:31:40 +0000	[thread overview]
Message-ID: <BAY115-W165FAC9CE3C0CB258DAF3AB24D0@phx.gbl> (raw)


Hi all

may be not really related to linux but I hope some body can help me with th=
is

As you know PPC405 runs the instruction at 0xfffffffc address as it's first=
 instruction

when generating a base system for ML403 using XPS, one should certainly add=
 PLB BRAM controller , this module will reside on PLB and contains some BRA=
M instances. A Code called boot loop is located in these block memories. PP=
C405 runs boot loop until sysace makes linux elf ready.=20

Looking in the generated xparameters.h you see that the base address for PL=
B BRAM IF is 0xffff0000 and since the first instruction should be located a=
t 0xfffffffc , you have to define the size of this PLB BRAM IF equal to 64k=
 when generating your system in XPS.

Now looking at ultracontroller reference design one can see that PPC405 loo=
ks for 0xfffffffc address on its IS OCM bus , but in regular designs as you=
 see PPC405 looks for this address on PLB Instruction bus, I'm wondering ho=
w PPC understands to do so in each of these designs? Does PPC have a specia=
l input port which is assigned a fix value and indicates where should PPC l=
ook for 0xfffffffc address ( ISOCM or IS PLB )?

thanks.

_________________________________________________________________
Connect to the next generation of MSN Messenger=A0
http://imagine-msn.com/messenger/launch80/default.aspx?locale=3Den-us&sourc=
e=3Dwlmailtagline=

                 reply	other threads:[~2007-04-29 21:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BAY115-W165FAC9CE3C0CB258DAF3AB24D0@phx.gbl \
    --to=mamsadegh@hotmail.com \
    --cc=linuxppc-embedded@ozlabs.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