From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] need help for SPL-NAND boot
Date: Thu, 29 Aug 2013 14:21:34 -0400 [thread overview]
Message-ID: <521F912E.50301@ti.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EA08093@DBDE04.ent.ti.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/29/2013 02:14 PM, Gupta, Pekon wrote:
> Hi,
>
> Need a help in debugging the spl boot via NAND.
>
> NAND Device is flashed with valid 'MLO' and 'u-boot.img'.
> Also it boots via MMC/SD perfectly using same images.
> But is NAND-SPL boot gets stuck under following condition..
>
> CONFIG_SPL_OS_BOOT (falcon mode) is enable by default for am33xx..
> #ifdef CONFIG_SPL_OS_BOOT
> if(valid_linux_image_header)
> loads_and_boots_linux
> else
> U-boot_hangs
> #else
> shows_serial_terminal with 'ccccc'
>
> #endif
>
> I have been debugging this flow by analyzing code in
> $U-BOOT/common/spl/spl.c
> $U-BOOT/common/spl/spl_nand.c: spl_nand_load_image()
> But, I'm getting stuck & lost ..
> Any pointers in this regard would be helpful.
So, when I was testing out falcon mode with NAND on am335x, what I found
was that the kernel was up and dying, unless I was using a much older
one that had NAND support in it, if I threw in earlyprintk.
> Also, I'm not seeing following CONFIGS being used anywhere..
> #define CONFIG_SYS_NAND_U_BOOT_START
> #define CONFIG_SYS_NAND_U_BOOT_SIZE
> #define CONFIG_SYS_NAND_U_BOOT_DST
> Have these been deprecated ?
They aren't used by CONFIG_SPL_FRAMEWORK drivers, no.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSH5EuAAoJENk4IS6UOR1WU/cP/jkIbJLCch2mC6cdvIYMmx9M
adpmZLztZDWVby2rE0NZj66AaBrmJKdf+F2q+liqMY3Mf7yqll2NaAXrTzzly45t
ZNjn42Fdg6WTkxSiTzsnkwm1DB4frusHhrfVLZqXaPU+hQUM+AhByzzaSk+e/C3a
Ou+Fwf22KEISKm9gl1BvxavMr/dUf0qpGGscTGbakbnD39UDEkQSbVpD4y1N3i2z
vAYiURUtMeadiz0BiqpwSYdEy5tH8ApAKxa74ngH/6vTWGOtL5LqEY5qrvyW1Iqb
6oG8EXAlUhO5MtPbs2WKzAUE+bShGl9IcPeAW7xudqEmHYydDJyg653hMrpaCA0R
79chfO9/NX0XTBMoAoTMAASagoPsTnm1WxbU9VuBwtMsRTYR0MqFVAmdYcuCn6SA
oKm4pvIYXYOlF7u7ApxzZi+eMczTlS+hrrWEEz1ZmTl64Aw+f0kVYRUF4aopzMr+
yE676D0h5RSm2WU6Svwn9ooh4JuuqH4SUX0J4zEqcQIz2hPYEJDZ8SGbiCNBLiaJ
JmpZ0++Zl3t/LWTRPlra0nW2hRKfA0wyv0KXQtVK3aIcyWbwliZBkRtVqPi3WsH+
cmf5TzWwIurwywHv59QSV1F4pc1bEAeWP4KMZagUa32W2YSBwgF+qh/l3g6LSp8v
VZk6iRk88uvPDGeEl7cH
=FZ3r
-----END PGP SIGNATURE-----
parent reply other threads:[~2013-08-29 18:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20980858CB6D3A4BAE95CA194937D5E73EA08093@DBDE04.ent.ti.com>]
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=521F912E.50301@ti.com \
--to=trini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.