From: "Enrico Jörns" <ejo@pengutronix.de>
To: Mikhail <mp_kenga@mail.ru>
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] RAUC with nanopi board
Date: Wed, 18 Mar 2020 01:14:19 +0100 [thread overview]
Message-ID: <52895440-7b10-b1f8-694d-59547ecfec50@pengutronix.de> (raw)
In-Reply-To: <1584017610.667742517@f160.i.mail.ru>
Hi Mikhail,
Am 12.03.20 um 13:53 schrieb Mikhail:
> Hi,
>
> I need to implement a solution for rootfs/app update with nanopi neo4
> board. The system (with Ubuntu 18) is installed on EMMC and it uses
> rockchip u-boot as bootloader. This board seems to use special approach
> for defining partitions: the command line defining mtd partitions is
> hard-coded at specific block address on EMMC, and it also tells which
> partition is the rootfs (e.g. "root=/dev/mmcblk1p7 … mtdparts=…"). Since
> it looks hard-coded, I don’t know how to change rootfs partition by
> using u-boot environment variables. So even though I’ve managed to setup
> RAUC and successfully used it to update roofs in an inactive partition,
> I can’t make my board switch to the new rootfs partition after reboot.
>
> Since I’m new to the topic, maybe I’m missing something. I’d be grateful
> for any advice.
> Are there any success stories of using RAUC with nanopi boards
> (especially Neo4)?
an example script for implementing boot device selection with u-boot can
be found here:
https://github.com/rauc/rauc/blob/master/contrib/uboot.sh
A more detailed guide on how to integrate this we have in the documentation:
https://rauc.readthedocs.io/en/latest/integration.html#id4
Does this help already?
Best regards, Enrico
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2020-03-18 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 12:53 Mikhail
2020-03-18 0:14 ` Enrico Jörns [this message]
2020-03-19 9:56 ` Mikhail
2020-03-18 18:01 ` Arti Zirk
2020-03-20 8:35 ` Mikhail
2020-04-01 9:22 ` Mikhail
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=52895440-7b10-b1f8-694d-59547ecfec50@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=mp_kenga@mail.ru \
--cc=rauc@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