From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] I can not read Linux image from my nand flash
Date: Mon, 30 Nov 2009 18:31:44 -0600 [thread overview]
Message-ID: <4B1463F0.1080505@freescale.com> (raw)
In-Reply-To: <48abf2c20911301627i3a9f2dc2uf54435c9857d3096@mail.gmail.com>
Peter Pan wrote:
> The previous u-boot version I use is U-boot 1.2.0, an ancient version.
> So I upgrade the u-boot to 2009-08.
> The platform is MPC8247.
That's a chip, not a platform. Which NAND controller driver? What
happens if you also use a non-ancient Linux? Have you compared the OOB
layout between U-Boot and Linux?
> About build warnings, some warnings in printf for not proper type, and
> yes, I get the 64-bit printf warning :
>
> nand_util.c:45:2: warning: #warning Please define
> CONFIG_SYS_64BIT_VSPRINTF for correct output!
>
> After I change the loff_t from long long to unsigned long, it works fine now.
I suggest doing as it says, and defining CONFIG_SYS_64BIT_VSPRINTF in
your board config file instead.
-Scott
next prev parent reply other threads:[~2009-12-01 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 12:14 [U-Boot] I can not read Linux image from my nand flash Peter Pan
2009-11-30 22:02 ` Scott Wood
2009-12-01 0:27 ` Peter Pan
2009-12-01 0:31 ` Scott Wood [this message]
2009-12-01 0:44 ` Peter Pan
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=4B1463F0.1080505@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