Re: [RAUC] Private: Re: [yocto] #yocto update the kernel with a rauc bundle

["Enrico Jörns" <ejo@pengutronix.de>]

Hi Hans,

Am 18.02.20 um 15:06 schrieb Hans-Ulrich Schlieben:
> Hi Enrico,
> 
> I just answered your first mail on the website and thought that will automatically reply to all. Added all lists now, hope these are correct.

ah, I wasn't even aware that there is a website for this ;)

> Thanks to you I found the custom automount in the providers recipes. This mounts /dev/mmc0.0 to /mnt/mmc.

Ok, good that we clarified this. The script should not be required in a
modern barebox as it has a lot of built-in automounting magic on board.

> After the mount it seems that only when I install a new image the barebox mount /dev/mmc0.0 to /mnt/mmc0.0 works. 

This is the point that sounds a little strange, yes.

> Rauc / barebox seems something to change after a bundle update whereas mount /dev/mmc0.0 to /mnt/mmc0.0 fails and the files are only visible in /mnt/mmc.
> 
> /mnt/mmc works in both cases so I have now 
> /mnt/mmc/boot... for system0 and
> /mnt/mmc0.1/boot... for system1

Would be great to see a log of such a failed mount to get a more
concrete idea what 'failed' actually means.

Best regards, Enrico

> -----Original Message-----
> From: Enrico Jörns <ejo@pengutronix.de> 
> Sent: Tuesday, 18 February 2020 01:12
> To: Hans-Ulrich Schlieben <hu.schlieben@codewrights.de>
> Subject: Re: Private: Re: [yocto] #yocto update the kernel with a rauc bundle
> 
> Hi hu,
> 
> please keep at least any list in CC so that others can benefit from this discussion, too (Both RAUC and barebox ML would fit here). It also increases the range and thus potential people that may help here.
> 
> Am 17.02.20 um 13:58 schrieb Hans-Ulrich Schlieben:
>> Hi Enrico,
>>
>> thank you very much for your help with IMAGE_INSTALL_append = " 
>> kernel-image kernel-devicetree"
>> that did the trick.
>>
>> What i do not understand is how barebox handles the mount names for my 
>> two alternate boot partitions.
>> The boot on the first partition works only under /mnt/mmc/:
>>
>> global.bootm.image="/mnt/mmc/boot/zImage"
>> global.bootm.oftree="/mnt/mmc/boot/imx6q-phytec-ksp0663.dtb"
>> global.linux.bootargs.dyn.root="root=/dev/mmcblk0p1
>> rootflags='data=journal' wd=60 ipv6.disable=1"
>>
>> whereas the second works with /mnt/mmc1/:
>> global.bootm.image="/mnt/mmc0.1/boot/zImage"
>> global.bootm.oftree="/mnt/mmc0.1/boot/imx6q-phytec-ksp0663.dtb"
>> global.linux.bootargs.dyn.root="root=/dev/mmcblk0p2
>> rootflags='data=journal' wd=60 ipv6.disable=1"
>>
>> In barebox i see both root filesystems under /mnt/mmc0.0 and 
>> /mnt/mmc0.1/.
>>
>> When i try to have a symmetrical configuration and rename /mmc/ into 
>> /mmc0.0/ boot on mmc0.0 does not work because it still mounts the 
>> first partition ar /mnt/mmc/.
> 
> Which version of barebox?
> 
> It should be sufficient to either say
> 
>   boot mmc0.0
> 
> or
> 
>   boot mmc0.1
> 
> and barebox will automatically mount the partition, look for a bootspec file under /loader/entries and assemble the required boot options and kernel command line automatically.
> 
>> What tells barebox to mount during boot mmc and mmc0.1 instead of 
>> mmc0.0 and mmc0.1?
> 
> Is there any custom automount unit located in you built-in env probably?
> 
> 
> 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