From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] xilinx-u-boot:- NAND: no devices available
Date: Mon, 26 May 2014 12:27:13 +0200 [thread overview]
Message-ID: <53831701.5020509@monstr.eu> (raw)
In-Reply-To: <CAC=Acqcs8Gb3N6AGGvSwyOCrFY2_3ej78OpmwdGwP4hD2zopGg@mail.gmail.com>
On 05/26/2014 09:35 AM, Uzair Zaidi wrote:
> I am trying to run FALCON MODE on zynq-microzed board. I am following
> README-falcon.But when i run `nand read 82000000 kernel` command, i get
> this error..
>
> ****no devices available****
>
>
> And when i run u-boot it shows..
> **
>
> > NAND: zynq_nand_init: Unable detect NAND based on MIO settings ZYNQ
> > NAND init failed
>
> **
> **Here are messages from my u-boot.**
>
> U-Boot 2014.01 (May 26 2014 - 11:19:45)
>
> I2C: ready
> Memory: ECC disabled
> DRAM: 1 GiB
> **NAND: zynq_nand_init: Unable detect NAND based on MIO settings
There is no NAND driver for zynq in mainline u-boot that's why please
use xilinx forums for this type of questions.
But based on this message you can simple identify where the problem is.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140526/22e7fb8d/attachment.pgp>
prev parent reply other threads:[~2014-05-26 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 7:35 [U-Boot] xilinx-u-boot:- NAND: no devices available Uzair Zaidi
2014-05-26 8:55 ` [U-Boot] Fwd: " Uzair Zaidi
2014-05-26 10:27 ` Michal Simek [this message]
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=53831701.5020509@monstr.eu \
--to=monstr@monstr.eu \
--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