linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: atul.sabharwal@exgate.tek.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: kernel startup
Date: Sat, 11 Feb 2006 02:20:27 +0100	[thread overview]
Message-ID: <20060211012027.DD9C8353B42@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 10 Feb 2006 16:28:28 PST." <4A062D477D842B4C8FC48EA5AF2D41F201BA2089@us-bv-m23.global.tektronix.net>

In message <4A062D477D842B4C8FC48EA5AF2D41F201BA2089@us-bv-m23.global.tektronix.net> you wrote:
> 
> Not much choice with IMMR as it can be 0x0 or 0x00f00000 or 0xFF000000
> Or 0xFFF00000.  

Initially. But you can change it.

> Flash is from 0xfe000000 thru 0xffffffff.  Now on POR,
> Processor goes to offset 0x100 on CS0.  So, if IMMR is overlapping with
> flash, it might not boot.

Just fix your memory map.

> On 870, it seems that reset value for BR0/OR0 is undefined.

Please RTFM. The steps how the processor  comes  up  from  reset  are
documented  in  great  detail.  Especially  the  handling of the boot
device chip select.

> Data fetch goes on CS0 and then in cpu_init_f BR0 & OR0
> Are remapped.  So, I could put flash at a non-standard address like
> 0xDE000000 and move IMMR to 0xFF000000.

There is no such thing as a "non-standard" address, as  there  is  no
"standard" address either.

> The problem this creates is that I can set IIP to 0 or 1. So, exception
> Vector prefix can be 0 or 0xfff.  Since no flash at 0xfff00000 base 
> Address I cannot have any exceptions in my code till the u-boot code
> has relocated to RAM.  Which should be acceptable as what can I do
> if there is exception so early in the system. 

In most cases it is useful to configure a system for low-boot, i.  e.
let  it  start  at  0x0100.  Then  just set up your memory map as you
like...

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
You don't need a weatherman to know which way the wind blows.
                                                          - Bob Dylan

  parent reply	other threads:[~2006-02-11  1:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11  0:28 kernel startup atul.sabharwal
2006-02-11  0:23 ` Kumar Gala
2006-02-11  1:20 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-11  2:10 atul.sabharwal
2006-02-11  2:03 atul.sabharwal
2006-02-11  1:47 atul.sabharwal
2006-02-11 12:59 ` Wolfgang Denk
2006-02-11  1:40 atul.sabharwal
2006-02-11  0:19 atul.sabharwal
2006-02-11  0:10 atul.sabharwal
2006-02-11  0:03 ` Kumar Gala
2006-02-11  1:13   ` Wolfgang Denk
2006-02-11  1:12 ` Wolfgang Denk
2006-02-11  0:02 atul.sabharwal
2006-02-11  0:12 ` Wolfgang Denk
2006-02-10 23:53 atul.sabharwal
2006-02-10 23:46 ` Kumar Gala
2006-02-11  0:08 ` Wolfgang Denk
2006-02-10 23:33 dibacco
2006-02-10 23:32 ` Kumar Gala
2006-02-11  0:06   ` Wolfgang Denk

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=20060211012027.DD9C8353B42@atlas.denx.de \
    --to=wd@denx.de \
    --cc=atul.sabharwal@exgate.tek.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;
as well as URLs for NNTP newsgroup(s).