From: Mihaita Ivascu <mihaita_ivascu@trimble.com>
To: barebox@lists.infradead.org
Subject: ECC nand 74 code error in barebox 2018.04.10
Date: Wed, 3 Apr 2019 17:31:09 +0200 [thread overview]
Message-ID: <CAEp+FuB1y=LgWF6ZDV2JhT+=Qch1H9f6zGqLPgb4Em4E0wriRw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
Hello,
I have the following situation:
I use imx6ul platforms.
kernel 4.9.11 from NXP
barebox 2018.04.10
I create and update an FIT image(*.itb) using
ubiformat/ubiattach/ubimkvol/ubiupdatevol commands
I also do this operation from Linux once the kernel was booted.
Everything worked for a while but at some point the FITIMAGE size
increased over 50 MB and I adapted the nand table in device tree
sources.
Now the image update from barebox is still working, I update, the
kernel loads and then at the next reboot the target boots correctly.
But if do the the FIt image update from linux, the update is
finished without warnings but at the next reboot, the barebox will
complained as listed in the attachment and the target won't boot from
nand anymore. Then i have to do the update again but only from
barebox.
nand partition table is the same in kernel and barebox dts.
But for images larger than 50 MB somehow if I update from linux, the
barebox will complain about ECC code 74.
I have enabled the other ECC options(software with/without BCH,
hardware) both in barebox and linux but no change.
I don't know if/how should I play with the PEB settings.
Does anybody know how could I get around this issue or how to
continue with my investigation?
Thanks in advance,
Mihaita Ivascu
[-- Attachment #2: NAND_ECC.txt --]
[-- Type: text/plain, Size: 2898 bytes --]
barebox 2018.04.0 #2 Wed Apr 3 07:55:40 PDT 2019
Board: Phytec phyCORE-i.MX6 Ultra Lite SOM
detected i.MX6 UltraLite revision 1.2
mdio_bus: miibus0: probed
eth0: got preset MAC address: 50:2d:f4:14:96:09
nand: ONFI flash detected
nand: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron MT29F4G08ABADAH4), 512MiB, page size: 2048, OOB size: 64
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
nand_bbt: ECC error in BBT at 0x00001ffe0005
nand_bbt: ECC error in BBT at 0x00001ffc0005
Scanning device for bad blocks
Bad block table written to 0x00001ffe0000, version 0x01
Bad block table written to 0x00001ffc0000, version 0x01
imx-usb 2184200.usb: USB EHCI 1.00
imx-esdhc 2190000.usdhc: registered as 2190000.usdhc
netconsole: registered as netconsole-1
phySOM-i.MX6: Using environment in NAND flash
malloc space: 0x8fe7d300 -> 0x9fcfa5ff (size 254.5 MiB)
running /env/bin/init...
Hit m for menu or any other key to stop autoboot: 1
booting 'nand'
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 0:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 1:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 2:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 3:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 4:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 5:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 6:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 7:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 8:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 9:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 10:0
nand0.fit1: error -74 (ECC error) while reading 64 bytes from PEB 11:0
....................................................................................................
ubi0: scanning is finished
nand0.fit1: error -74 (ECC error) while reading 22528 bytes from PEB 273:4096
nand0.fit1: error -74 (ECC error) while reading 22528 bytes from PEB 274:4096
ubi0 error: vtbl_check: bad CRC at record 2: 0xf116c36b, not 0x000000
Volume table record 2 dump:
reserved_pebs 0
alignment 0
data_pad 0
vol_type 0
upd_marker 0
name_len 0
name NULL
ubi0 error: vtbl_check: bad CRC at record 2: 0xf116c36b, not 0x000000
Volume table record 2 dump:
reserved_pebs 0
alignment 0
data_pad 0
vol_type 0
upd_marker 0
name_len 0
name NULL
ubi0 error: process_lvol: both volume tables are corrupted
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd0, error -22
[-- Attachment #3: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-04-03 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 15:31 Mihaita Ivascu [this message]
2019-04-04 19:51 ` Sascha Hauer
2019-04-05 16:23 ` Mihaita Ivascu
2019-04-08 6:29 ` Sascha Hauer
2019-04-08 6:51 ` Mihaita Ivascu
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='CAEp+FuB1y=LgWF6ZDV2JhT+=Qch1H9f6zGqLPgb4Em4E0wriRw@mail.gmail.com' \
--to=mihaita_ivascu@trimble.com \
--cc=barebox@lists.infradead.org \
/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