From: Jupiter <jupiter.hce@gmail.com>
To: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Any UBIFS volume image installation command with selective ECC (DTB) in Linux?
Date: Thu, 14 May 2020 21:37:20 +1000 [thread overview]
Message-ID: <CAA=hcWT7eQ5nXjqRyOG7jaH=K8OEa5w_AwbB_fTJ6JdM-=YDeg@mail.gmail.com> (raw)
Hi,
I used ubinize to build a UBIFS image ubi.img, the image has three
volumes, dtb-volume (imx6ulz.dtb), kernel-volume and rootfs-volume.
To install u-boot and root UBIFS image to iMX6ULL NAND, I used a
zImage-initramfs to install the u-boot to u-boot mtd partition first,
then to install ubi.img in UBIFS partition by running following
commands:
flash_erase /dev/mtd2 0 0
ubiformat /dev/mtd2 -f /tmp/ubi.img
It was all fine, but after the installation, it cannot run ubi part in u-boot:
ubi0 error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 3
83:0, read 64 bytes
ubi0 error: ubi_io_read: error -74 (ECC error) while reading 2048 bytes from PEB
383:2048, read 2048 bytes
The problem was that u-boot installation requires a higher bit ECC, so
that zImage-initramfs was started with imx6ulz-kobs.dtb, if I change
to start zImage-initramfs with a low bit ECC imx6ulz.dtb, that ECC
error gone away, but then I could not flash u-boot to NAND.
Are there any way or mtd / ubi command to flash ubi.img to NAND based
on a specific ECC / dtb?
Appreciate any your kind advice.
Thank you.
Kind regards,
- jupiter
--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-05-14 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 11:37 Jupiter [this message]
2020-05-15 1:16 ` Any UBIFS volume image installation command with selective ECC (DTB) in Linux? Jupiter
2020-05-15 6:59 ` Jupiter
2020-05-20 11:22 ` Alexander Dahl
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='CAA=hcWT7eQ5nXjqRyOG7jaH=K8OEa5w_AwbB_fTJ6JdM-=YDeg@mail.gmail.com' \
--to=jupiter.hce@gmail.com \
--cc=linux-mtd@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;
as well as URLs for NNTP newsgroup(s).