From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Eric Bénard" <eric@eukrea.com>
Cc: barebox@lists.infradead.org
Subject: Re: iMX nand BBT problem
Date: Tue, 2 Jul 2013 10:14:13 +0200 [thread overview]
Message-ID: <20130702081413.GE516@pengutronix.de> (raw)
In-Reply-To: <20130701181234.15305e43@e6520eb>
HI Eric,
On Mon, Jul 01, 2013 at 06:12:34PM +0200, Eric Bénard wrote:
> Hi,
>
> when upgrading from 2013.05.1 to 2013.06 on an i.MX35 I get the
> following log :
>
> - initial log :
> barebox 2013.05.1-00001-ga8e8785 #25 Mon Jul 1 17:12:14 CEST 2013
> Board: Eukrea CPUIMX35
> detected i.MX35 revision 2.1
> netconsole: registered as cs1
> nand: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V
> 8-bit), page size: 2048, OOB size: 64
> mdio_bus: miibus0: probed
> imx-ipu-fb imx-ipu-fb: i.MX Framebuffer driver
> imx-esdhc imx-esdhc0: registered as imx-esdhc0
> ehci ehci0: USB EHCI 1.00
> malloc space: 0x87700000 -> 0x87efffff (size 8 MiB)
> running /env/bin/init...
>
> --> upgrade barebox :
> barebox 2013.06.0-00001-gf355cf4 #26 Mon Jul 1 17:57:52 CEST 2013
> Board: Eukrea CPUIMX35
> detected i.MX35 revision 2.1
> netconsole: registered as cs1
> nand: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V
> 8-bit), page size: 2048, OOB size: 64
> nand: Bad block table not found for chip 0
> nand: Bad block table not found for chip 0
> imx_nand imx_nand: no BBT found. create one using the imx_nand_bbm
> command
> mdio_bus: miibus0: probed
> imx-ipu-fb imx-ipu-fb: i.MX Framebuffer driver
> imx-esdhc imx-esdhc0: registered as imx-esdhc0
> ehci ehci0: USB EHCI 1.00
> malloc space: 0x87700000 -> 0x87efffff (size 8 MiB)
> envfs: wrong magic on /dev/env0
> no valid environment found on /dev/env0. Using default environment
> running /env/bin/init...
> no MAC address set for eth0. please enter the one found on your board:
> 00:12:34:56:78:90 saving environment
>
> Once I reset the board I can see that the env was not saved and I get
> prompted again for the MAC address.
>
> Any idea of what can be wrong there ?
>
> This board is configured in external boot from a 2k NAND (and was
> already using flash BBT), and the kernel and rootfs still run without
> any visible problem.
Are you sure this happens between 2013.05.1 and 2013.06.0? The only
changes in the mtd stuff are:
ae6f751 nand_base: sync flash detection functions with linux 3.9's code
c8af035 Merge branch 'for-next/misc'
7c15fd1 NAND: imx: Fix memory leak
d8ee54f mtd: Nand: Use dev_add_param_bool for erasebad parameter
7c6c61f treewide: Use dev_add_param_int_ro where possible
973176d mtd: update NAND manufacturer names from the kernel
4c2bdc8 nand_base: detect more ONFI flash
So the only patches which seem to change something are from you ;)
Does the 'md' command still work and shows meaningful content in the
NAND?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-07-02 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 16:12 Eric Bénard
2013-07-02 8:14 ` Sascha Hauer [this message]
2013-07-02 8:24 ` Re[2]: " Alexander Shiyan
2013-07-02 8:26 ` Eric Bénard
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=20130702081413.GE516@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eric@eukrea.com \
/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