Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: linux-mtd@lists.infradead.org
Cc: Yocto discussion list <yocto@yoctoproject.org>,
	Jupiter <jupiter.hce@gmail.com>
Subject: Re: Install Yocto image and backup
Date: Mon, 02 Nov 2020 09:40:43 +0100	[thread overview]
Message-ID: <2234110.ZDGxJVC3CD@ada> (raw)
In-Reply-To: <CAA=hcWQnJ1yRTwPF+9kubSt6FQPxwCRYFwXcYR8RnVLs4LMb7A@mail.gmail.com>

Hei hei,

Am Montag, 2. November 2020, 02:02:09 CET schrieb Jupiter:
> I built Yocto Linux kernel and installed Yocto image to MTD NAND
> storage in an iMAX6 device, because we designed RO for the kernel and
> root file system, RW for applications, we can update applications OTA
> but we cannot update kernel and root file system OTA. My supervisor
> asked if we need to have a dual NAND storage to backup the kernel and
> root file image, if the NAND bad sector occurred in the primary image,
> it can be booted from the secondary backup image. I understand where
> the concerns come from, but I am not clear if it is necessary or if it
> is a common practice to perform NAND backup storage, appreciate your
> insight advice.

In my opinion two things are common practice: 

1) Using a layer on top of raw NAND, like UBI/UBIFS nowadays, so bad blocks 
can be handled properly in a layer below your rootfs.

2) Using an A/B scheme for updating and using a well tested framework for that 
(instead of self written shell scripts).  You don't need another NAND chip for 
that, just multiple partitions.  You can still have your kernel/rootfs read-
only at runtime.

Greets
Alex




______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-11-02  8:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  1:02 Install Yocto image and backup Jupiter
2020-11-02  8:40 ` Alexander Dahl [this message]
2020-11-02  9:16   ` Jupiter
2020-11-03  8:16     ` Alexander Dahl
2020-11-03  9:17       ` Jupiter
2020-11-03  9:48         ` [yocto] " Richard Weinberger

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=2234110.ZDGxJVC3CD@ada \
    --to=ada@thorsis.com \
    --cc=jupiter.hce@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=yocto@yoctoproject.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