From: "Jan Lübbe via RAUC" <rauc@pengutronix.de>
To: "Bapat, Nachiket" <Nachiket.Bapat@sensxpert.com>,
"rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] RAUC integration NAND flash: PEC error -74 on UBIFS
Date: Mon, 19 May 2025 10:21:57 +0200 [thread overview]
Message-ID: <21c11f09562c5987a980dc1489c1e9929569e317.camel@pengutronix.de> (raw)
In-Reply-To: <AS8P194MB1463B1E5F31790B9927838B98A93A@AS8P194MB1463.EURP194.PROD.OUTLOOK.COM>
Hi,
On Fri, 2025-05-16 at 14:34 +0000, Bapat, Nachiket via RAUC wrote:
> I will be using RAUC for integration with NAND flash.
>
> I have the exact same error as shown in the following post:
> Solved: Re: After writing ubifs and booting into Linux bad nodes are found -
> NXP Community
First, you need to make sure that your UBIFS image works with ubiupdatevol. If
that fails, you're likely using a wrong UBIFS NAND layout during image creation.
It needs to match the target's NAND configuration (mtdinfo -u) exactly.
When ubiupdatevol works on the target, RAUC bundles with that slot image should
work as well, it uses the same kernel API as ubiupdatevol.
> Unfortunately using the solution from this post will not help me .
> Reason being that RAUC requires a UBIFS to be written into the slot.
> According to this solution I need to reflash the ubi partition with the
> correct UBIFS image from either an SD-card of TFTPBOOT.
> Is there a way I can still integrate RAUC with the above solution ?
>
> If not is there a pre-execution script or a function which I can override to
> attach my custom script which copies data to the UBI partition?
Ifyour *UBI partition* NAND layout doesn't match the hardware and you have
separate UBI partitions, you could use a install hook:
https://rauc.readthedocs.io/en/latest/using.html#slot-hooks:~:text=The%20install%20hook%20will%20replace%20the%20entire%20default%20installation%20process%20for%20the%20target%20slot%20of%20the%20image%20it%20was%20specified%20for
In that hook, you could recreate the inactive UBI partition and volume, and then
use ubiupdatevol.
If you need to repair the layout of the currently running slot, you can do that
from a normal userspace service running after the update. After repairing the
layout, you can remove the hooks again.
If you only have only one UBI partition and no rescue slot, I don't see a way to
repair the layout while the partition is in use, so you probably have to reflash
from an external device.
Regards,
Jan
--
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 |
parent reply other threads:[~2025-05-19 8:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <AS8P194MB1463B1E5F31790B9927838B98A93A@AS8P194MB1463.EURP194.PROD.OUTLOOK.COM>]
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=21c11f09562c5987a980dc1489c1e9929569e317.camel@pengutronix.de \
--to=rauc@pengutronix.de \
--cc=Nachiket.Bapat@sensxpert.com \
--cc=jlu@pengutronix.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