[RAUC] RAUC with nanopi board

[RAUC] RAUC with nanopi board

[Mikhail]

[-- Attachment #1.1: Type: text/plain, Size: 929 bytes --]


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)?
 
Best regards,
Mikhail

[-- Attachment #1.2: Type: text/html, Size: 1074 bytes --]

[-- Attachment #2: Type: text/plain, Size: 66 bytes --]

_______________________________________________
RAUC mailing list

Re: [RAUC] RAUC with nanopi board

[Enrico Jörns]

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

Re: [RAUC] RAUC with nanopi board

[Arti Zirk]

On N, 2020-03-12 at 15:53 +0300, Mikhail wrote:
> The system (with Ubuntu 18) is installed on EMMC and it uses rockchip
> u-boot as bootloader
Have you looked into how Armbian has done support for this board? 
https://www.armbian.com/nanopi-neo4/


_______________________________________________
RAUC mailing list

Re: [RAUC] RAUC with nanopi board

[Mikhail]

[-- Attachment #1.1: Type: text/plain, Size: 2717 bytes --]


Hi,
Yes, I’ve seen the example script for boot selection. The problem is I don’t know where to integrate it. The image flashed on emmc has no boot partition which would usually be mounted at /boot and contain boot.scr script. Instead, bootloader, kernel image and other components are placed to separate raw partitions at the beginning of the emmc. Then go rootfs and data ext4 partitions. Here is the layout:
 
flash=mmc,1:loader:idb:0x8000,0x280000:idbloader.img;
flash=mmc,1:env:env:0x3F8000,0x8000;
flash=mmc,1:parm:parm:0x400000,0x0400000:param4sd.txt;
flash=mmc,1:uboot:raw:0x800000,0x0400000:uboot.img;
flash=mmc,1:trust:raw:0xC00000,0x0400000:trust.img;
flash=mmc,1:misc:raw:0x1000000,0x0400000;
flash=mmc,1:resc:raw:0x1400000,0x0C00000:resource.img;
flash=mmc,1:kern:raw:0x2000000,0x2000000:kernel.img;
flash=mmc,1:boot:raw:0x4000000,0x2000000:boot.img;
flash=mmc,1:rootfs:ext4:0x6000000,0x117800000:rootfs.img;
flash=mmc,1:userdata:ext4:0x11D800000,0x0:userdata.img;
 
Best regards,
Mikhail
  
>Среда, 18 марта 2020, 3:14 +03:00 от Enrico Jörns <ejo@pengutronix.de>:
> 
>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 | 
 
 
--
. .
 

[-- Attachment #1.2: Type: text/html, Size: 3666 bytes --]

[-- Attachment #2: Type: text/plain, Size: 66 bytes --]

_______________________________________________
RAUC mailing list

Re: [RAUC] RAUC with nanopi board

[Mikhail]

[-- Attachment #1.1: Type: text/plain, Size: 698 bytes --]


Hi Arti,
 
Yes, this page contains instruction from FrienlyArm on how to create flashing sd-card to create the image on emmc:
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO4
I’ve read it and that’s actually how I flash emmc now. But I did not find a way to customize boot script to integrate RAUC.
 
Best regards,
Mikhail
  
>Среда, 18 марта 2020, 21:01 +03:00 от Arti Zirk <arti.zirk@gmail.com>:
> 
>On N, 2020-03-12 at 15:53 +0300, Mikhail wrote:
>> The system (with Ubuntu 18) is installed on EMMC and it uses rockchip
>> u-boot as bootloader Have you looked into how Armbian has done support for this board?
>https://www.armbian.com/nanopi-neo4/
>  
 
 
--
. .
 

[-- Attachment #1.2: Type: text/html, Size: 1413 bytes --]

[-- Attachment #2: Type: text/plain, Size: 66 bytes --]

_______________________________________________
RAUC mailing list

Re: [RAUC] RAUC with nanopi board

[Mikhail]

[-- Attachment #1.1: Type: text/plain, Size: 548 bytes --]



Finally I’ve managed to to make it work on both SD card and eMMC. I used Yocto with the latest mainline U-boot instead of Friendlyarm approach to build the image.
 
Thanks,
Mikhail
  
>Среда, 18 марта 2020, 21:01 +03:00 от Arti Zirk <arti.zirk@gmail.com>:
> 
>On N, 2020-03-12 at 15:53 +0300, Mikhail wrote:
>> The system (with Ubuntu 18) is installed on EMMC and it uses rockchip
>> u-boot as bootloader Have you looked into how Armbian has done support for this board?
>https://www.armbian.com/nanopi-neo4/
>  
 
 
--
. .
 

[-- Attachment #1.2: Type: text/html, Size: 1153 bytes --]

[-- Attachment #2: Type: text/plain, Size: 66 bytes --]

_______________________________________________
RAUC mailing list