From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] problem with mpc837x start.S
Date: Mon, 8 Aug 2011 15:42:38 -0500 [thread overview]
Message-ID: <4E404A3E.8060006@freescale.com> (raw)
In-Reply-To: <SNT115-W322547F2BEA1B95D78CEB0D23D0@phx.gbl>
On 08/04/2011 06:37 AM, shawn Bai wrote:
> When enlarging Nor Flash to 4GiB, the AM in OR0 is 0x0000_0, where the number of zero is 17.
>
> According to what is said in datasheet, if the bit value of some bit in address mask is 0,
> then the corresponding bit in address will be masked.
>
> So, the higher 17 bits in address will be masked, is it right ?
>
> If so, the range accessed in flash is just 32KBytes from the BA in BR0.
> Is that right ? But Not the same with what you mean.
The address mask applies only to matching a chip select. Once it's been
matched, the full address goes to the device -- minus the bits that the
device does not implement. An bit whose address mask is zero is treated
the same as the least-significant 15 bits.
> And from what you replied before in this question, may I say the 32KBytes will repeat through 4GiB address space ? not 8MBytes ?
No.
> then, what is the effect of CONFIG_SYS_MONITOR_BASE in this ABSOLUTE branch as uboot comment indicates ?
The effect is that the program counter contains "CONFIG_SYS_MONITOR_BASE
+ in_flash", so that when the code later shrinks the chipselect it will
still be executing from flash.
-Scott
next prev parent reply other threads:[~2011-08-08 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.8996.1311744830.8190.u-boot@lists.denx.de>
2011-07-27 6:21 ` [U-Boot] problem with mpc837x start.S shawn Bai
2011-08-01 18:48 ` Scott Wood
2011-08-02 4:11 ` shawn Bai
2011-08-02 15:21 ` Scott Wood
2011-08-03 0:48 ` shawn Bai
2011-08-03 15:48 ` Scott Wood
2011-08-04 11:37 ` shawn Bai
2011-08-08 8:29 ` shawn Bai
2011-08-08 20:42 ` Scott Wood [this message]
2011-08-09 13:36 ` shawn Bai
[not found] <mailman.9047.1311929345.8190.u-boot@lists.denx.de>
2011-07-29 12:42 ` shawn Bai
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=4E404A3E.8060006@freescale.com \
--to=scottwood@freescale.com \
--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