From: Ira W. Snyder <iws@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Is CCSRBAR relocation broken on P2020?
Date: Thu, 10 Nov 2011 08:54:48 -0800 [thread overview]
Message-ID: <20111110165447.GA1801@ovro.caltech.edu> (raw)
Hello Timur, Kumar, U-Boot List,
I'm working on porting U-Boot to the Freescale P2020 COM-Express board.
See the ML post from 2011-09-27 titled "[PATCH 0/2] mpc85xx: support for
Freescale COM Express P2020".
When it was posted, the port was working on the top of tree U-Boot. This
included relocation of the CCSRBAR from the power on location of
0xff700000 to 0xffe00000.
Today I updated U-Boot to top of tree to address the comments in the
initial mailing list posting. Upon attempting to boot the board, I get
no console output. I have traced this to commit 6ca88b0958
("powerpc/85xx: relocate CCSR before creating the initial RAM area").
Indeed, making sure that the code does not run by adding the following
to my board config file causes U-Boot to start correctly. Though the
CCSRBAR is not relocated, as expected.
#define CONFIG_SYS_CCSR_DO_NOT_RELOCATE
As an alternative, reverting the commit causes my board to work again.
The CCSRBAR is relocated correctly.
The P2020DS board is very similar to the board I am using. It performs
the same relocation of the CCSRBAR that I want to use as well. Does
anyone have a P2020DS that they can test with the current top of tree
U-Boot? Does it boot? Can you send the output of "md ffe00000 1"?
Thanks,
Ira
next reply other threads:[~2011-11-10 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 16:54 Ira W. Snyder [this message]
2011-11-10 17:12 ` [U-Boot] Is CCSRBAR relocation broken on P2020? Timur Tabi
2011-11-10 17:33 ` Ira W. Snyder
2011-11-10 17:47 ` Timur Tabi
2011-11-10 19:24 ` McClintock Matthew-B29882
2011-11-10 19:28 ` Timur Tabi
2011-11-10 19:46 ` Ira W. Snyder
2011-11-10 19:49 ` Timur Tabi
2011-11-10 19:59 ` Ira W. Snyder
[not found] <4EBC2D50.5070200@embedded-sol.com>
2011-11-10 20:07 ` Felix Radensky
2011-11-10 20:48 ` Ira W. Snyder
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=20111110165447.GA1801@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--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