public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Yuri Frolov <yfrolov-uboot@yandex.ru>
To: u-boot@lists.denx.de
Subject: [U-Boot] [powerpc NOR flash start address]
Date: Mon, 20 Jul 2015 16:54:47 +0300	[thread overview]
Message-ID: <382201437400487@web22h.yandex.ru> (raw)

Hello,

probably an obvious question, but nevertheless...

More than a year ago, u-boot binary size was incfreased for powerpc boards (commit e222b1f36fedb0363dbc21e0add7dc3848bae553 "powerpc/mpc85xx:Increase binary size for P, B & T series boards."), so CONFIG_SYS_TEXT_BASE changed from 0xeff80000 to 0xeff40000.

I've been using Freescale P2041RDB-PA, rev. A board with U-Boot 2011.09-00000-g2c02d1d flashed to NOR at 0xeff80000 and running properly.

I'd like to update u-boot (rcw, fmac microcode, etc) hence, I need to flash u-boot binary at 0xeff40000.

The question is: which way does hardware know from which NOR flash address to begin to start?
After reset, powerpc cpus start to execute code from the 0xfffffffc address, which is usually (or, to say better - almost always) the last word of NOR flash); there is 0x4bfff004 at that address, which means "jump to 0xfffff000", if I understand it correctly. What code resides here and what does it do?

And, more practical question, where (and how) the hardware is given to understand, that it should look for u-boot image at particular NOR address?
What (and where) should I fix to change hardware's understanding of u-boot image location from  0xeff80000 to 0xeff40000?

TIA,
Yuri

             reply	other threads:[~2015-07-20 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 13:54 Yuri Frolov [this message]
2015-07-20 14:25 ` [U-Boot] [powerpc NOR flash start address] Bin Meng

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=382201437400487@web22h.yandex.ru \
    --to=yfrolov-uboot@yandex.ru \
    --cc=u-boot@lists.denx.de \
    /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