From: Vignesh R <vigneshr@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] QSPI XIP boot on am437x
Date: Tue, 10 Nov 2015 14:29:54 +0530 [thread overview]
Message-ID: <5641B20A.4080207@ti.com> (raw)
Hi,
With commit 7ae8350f67eea("ti: armv7: Move SPL SDRAM init to the right
place, drop unused CONFIG_SPL_STACK") QSPI XIP boot appears to be broken
on AM437x SK EVM.
Following UART initialization code (as indicated by TODO) causes the XIP
boot failure.
In arch/arm/cpu/armv7/am33xx/board.c:
@@ -275,9 +275,9 @@ void s_init(void)
#if defined(CONFIG_NOR_BOOT) || defined(CONFIG_QSPI_BOOT)
/* TODO: This does not work, gd is not available yet */
gd->baudrate = CONFIG_BAUDRATE;
serial_init();
gd->have_console = 1;
#endif
I was able to boot successfully from QSPI by commenting out the above code.
But, could you suggest me what needs to be done as part of TODO in order
to get QSPI XIP boot working?
Thanks!
--
Regards
Vignesh
next reply other threads:[~2015-11-10 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 8:59 Vignesh R [this message]
2015-11-10 12:14 ` [U-Boot] QSPI XIP boot on am437x Albert ARIBAUD
2015-11-11 6:12 ` R, Vignesh
2015-11-11 7:15 ` Albert ARIBAUD
2015-11-11 9:03 ` Albert ARIBAUD
2015-11-13 5:52 ` Vignesh R
2015-11-13 6:28 ` Albert ARIBAUD
2015-11-16 10:30 ` Vignesh R
2015-11-16 11:46 ` Albert ARIBAUD
2015-11-16 11:48 ` Vignesh R
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=5641B20A.4080207@ti.com \
--to=vigneshr@ti.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