From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Nand flash R/W,saveenv issue..
Date: Wed, 23 May 2012 17:45:38 -0500 [thread overview]
Message-ID: <4FBD6892.8020704@freescale.com> (raw)
In-Reply-To: <1337752596.2378.37.camel@Manukumar>
On 05/23/2012 12:56 AM, Manukumar wrote:
>
> u-boot version: u-boot-2010.12
>
> My OR and BR register values(according to our memory map):
> BR0 0xFF800C21 OR0 0xFF800396
> BR1 0xE8000801 OR1 0xFFFF8074
> BR2 0xE8009001 OR2 0xFFFF8074
>
> after defining VERBOSE_DEBUG in drivers/mtd/nand/fsl_elbc_nand.c
> i gave sacveenv command, igot below logs.
> please go through that and resolve asap.
People on this list are generally happy to help as time is available,
but if you need "asap" either contact support at freescale.com (especially
when using Freescale-supplied U-Boot) or another official Freescale FAE
or support contact, or hire someone to look into it.
> skipping bad block =
> 0
I don't see this exact message in mainline U-Boot, even in old versions.
And zero being a bad block would be a bad thing -- I suspect things
have gone wrong before the output you provided.
> DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0,
> pes 14 ps 9
> fsl_elbc_run_command
> DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=4e000000
> fcr=70000000
> DEBUG: fsl_elbc_run_command: fbar=00000000 fpar=00000000 fbcr=00000001
> bank=0
> DEBUG: fsl_elbc_run_command: stat=40000001 mdr=00000000
> fmr=0000f020
This is showing a command timeout (LTESR[FCT]). What happened with the
NAND earlier in the boot sequence?
-Scott
prev parent reply other threads:[~2012-05-23 22:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1337677828.2382.30.camel@Manukumar>
2012-05-22 14:15 ` [U-Boot] Nand flash R/W,saveenv issue Marek Vasut
2012-05-22 17:56 ` Scott Wood
2012-05-23 5:56 ` Manukumar
2012-05-23 8:02 ` Wolfgang Denk
2012-05-23 8:30 ` Manukumar
2012-05-23 16:16 ` Scott Wood
2012-05-30 5:02 ` [U-Boot] problem while making kernel up Manukumar
2012-05-30 16:18 ` Scott Wood
2012-05-31 4:15 ` Manukumar
2012-05-31 16:21 ` Scott Wood
2012-06-01 3:58 ` Manukumar
2012-06-01 10:10 ` Manukumar
2012-06-01 17:15 ` Scott Wood
2012-06-06 8:13 ` Manukumar
2012-07-05 10:27 ` [U-Boot] USB detection Manukumar
2012-07-05 11:45 ` Albert ARIBAUD
2012-07-05 15:34 ` Marek Vasut
2012-07-09 8:47 ` Manukumar
2012-07-09 12:18 ` Albert ARIBAUD
2012-07-10 2:17 ` Marek Vasut
2012-07-12 6:10 ` Manukumar
2012-10-25 12:21 ` Manukumar
2012-10-25 13:26 ` RgC
2012-09-26 10:42 ` [U-Boot] bootm command in U-boot Manukumar
2012-09-26 14:14 ` Wolfgang Denk
2012-10-03 12:24 ` [U-Boot] Booting through nand flash with other address Manukumar
2012-10-03 15:22 ` Scott Wood
2012-10-04 10:18 ` Manukumar
2012-10-04 17:21 ` Scott Wood
2012-12-04 12:04 ` [U-Boot] access u-boot environment variables from kernel space Manukumar
2012-12-04 13:24 ` Yegor Yefremov
2012-12-04 16:26 ` Scott Wood
2012-12-04 16:35 ` Steve Strobel
2013-01-25 6:50 ` Manukumar
2013-01-25 9:22 ` Wolfgang Denk
2012-11-23 4:08 ` [U-Boot] Quer on JTAG Manukumar
2012-11-23 5:33 ` Wolfgang Denk
2012-09-11 12:47 ` [U-Boot] Nand Flash Programing and Board Bring Up Manukumar
2012-09-11 14:10 ` Marek Vasut
2012-05-23 22:45 ` Scott Wood [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=4FBD6892.8020704@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