update rootfs partition and boot partition #1330
Replies: 7 comments 17 replies
-
@pritpalm-kuk If you define the slot as In your case it is just a kernel image, no file system image. Normally, file systems are not updated by just putting a single file in it. RAUC supports 'files-based' updates only by creating a tar archive which is then extracted in a newly formatted slot. I also wonder how you define where in the vfat the kernel image should be placed? Thus if you actually need a vfat there, either let yocto build a vfat image or a tar archive containing the kernel. |
Beta Was this translation helpful? Give feedback.
-
Hi @pritpalm-kuk have you figured out this problem? |
Beta Was this translation helpful? Give feedback.
-
Hi
Thanks for the update.
I did resolve the issue.
Basically I put the kernel and device tree in the rootfs partition.
Then change the uboot to boot the kernel from rootfs
I can share the implementation with you if you wish
Regards
Pritpal
…On Wed, 24 Apr 2024 at 08:35, anthonio9 ***@***.***> wrote:
Hi @pritpalm-kuk <https://github.com/pritpalm-kuk> have you figured out
this problem?
I've run into a similar kind of an issue, where my /boot does not get
updated at all. I do not want to update the bootloader, just the contents
of the /boot that is a part of the rootfs (or is it the same thing?).
—
Reply to this email directly, view it on GitHub
<#1330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANVR26H3E22MIFE6A3NSIUDY65OFJAVCNFSM6AAAAABB73GVM6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEMBZGQZDO>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
This e-mail is intended only for the person to whom it is addressed and may
contain confidential information. If an addressing or transmission error
has misdirected this e-mail, please notify the author by replying to this
e-mail. If you are not the intended recipient you must not use, disclose,
print or rely on the contents of this e-mail and should immediately and
permanently delete it.
Kenwood Limited is a company registered in England
with registered number 872044. The registered office of Kenwood Limited is
1 Kenwood Business Park, New Lane, Havant, Hampshire, PO9 2NH.
Kenwood
Limited may monitor outgoing and incoming e-mails and other
telecommunications on its e-mail and telecommunications systems for the
purpose of ensuring compliance with the law and with Kenwood Limited's
policies.
|
Beta Was this translation helpful? Give feedback.
-
in my local.conf i added the following to put the kernel in the rootfs Then i modified the uboot boot process to boot from ext4 and this worked for us |
Beta Was this translation helpful? Give feedback.
-
Hi
our yocto is from gatesgarth
i have attached the patch in this email for the uboot
Regards
Pritpal
…On Wed, 24 Apr 2024 at 11:29, anthonio9 ***@***.***> wrote:
one more question, the _append syntax is rather old, are you running a
dunfel yocto distribution?
—
Reply to this email directly, view it on GitHub
<#1330 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANVR26F6DTDIG7SP7LY7GZDY66CSPAVCNFSM6AAAAABB73GVM6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEMJRGUZDS>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
This e-mail is intended only for the person to whom it is addressed and may
contain confidential information. If an addressing or transmission error
has misdirected this e-mail, please notify the author by replying to this
e-mail. If you are not the intended recipient you must not use, disclose,
print or rely on the contents of this e-mail and should immediately and
permanently delete it.
Kenwood Limited is a company registered in England
with registered number 872044. The registered office of Kenwood Limited is
1 Kenwood Business Park, New Lane, Havant, Hampshire, PO9 2NH.
Kenwood
Limited may monitor outgoing and incoming e-mails and other
telecommunications on its e-mail and telecommunications systems for the
purpose of ensuring compliance with the law and with Kenwood Limited's
policies.
|
Beta Was this translation helpful? Give feedback.
-
Hi
Will do on Monday
Regards
Pritpal
…On Fri, 26 Apr 2024 at 11:10, anthonio9 ***@***.***> wrote:
Hi @pritpalm-kuk <https://github.com/pritpalm-kuk>, could you paste the
patch here in the comment?
—
Reply to this email directly, view it on GitHub
<#1330 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANVR26AZ26P2PQNE5YI2FZDY7IRYHAVCNFSM6AAAAABB73GVM6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEMZVGM4TI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
This e-mail is intended only for the person to whom it is addressed and may
contain confidential information. If an addressing or transmission error
has misdirected this e-mail, please notify the author by replying to this
e-mail. If you are not the intended recipient you must not use, disclose,
print or rely on the contents of this e-mail and should immediately and
permanently delete it.
Kenwood Limited is a company registered in England
with registered number 872044. The registered office of Kenwood Limited is
1 Kenwood Business Park, New Lane, Havant, Hampshire, PO9 2NH.
Kenwood
Limited may monitor outgoing and incoming e-mails and other
telecommunications on its e-mail and telecommunications systems for the
purpose of ensuring compliance with the law and with Kenwood Limited's
policies.
|
Beta Was this translation helpful? Give feedback.
-
Hi
I have attached my patched in this email
Regards
Pritpal
…On Fri, 26 Apr 2024 at 11:10, anthonio9 ***@***.***> wrote:
Hi @pritpalm-kuk <https://github.com/pritpalm-kuk>, could you paste the
patch here in the comment?
—
Reply to this email directly, view it on GitHub
<#1330 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANVR26AZ26P2PQNE5YI2FZDY7IRYHAVCNFSM6AAAAABB73GVM6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEMZVGM4TI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
This e-mail is intended only for the person to whom it is addressed and may
contain confidential information. If an addressing or transmission error
has misdirected this e-mail, please notify the author by replying to this
e-mail. If you are not the intended recipient you must not use, disclose,
print or rely on the contents of this e-mail and should immediately and
permanently delete it.
Kenwood Limited is a company registered in England
with registered number 872044. The registered office of Kenwood Limited is
1 Kenwood Business Park, New Lane, Havant, Hampshire, PO9 2NH.
Kenwood
Limited may monitor outgoing and incoming e-mails and other
telecommunications on its e-mail and telecommunications systems for the
purpose of ensuring compliance with the law and with Kenwood Limited's
policies.
|
Beta Was this translation helpful? Give feedback.
-
We are wanting to ota the rootfs partition and the boot partition that contains the kernel image and device trees.
The partitions we are using are shown below:
/dev/mmcblk2p1 == boot_a partition (that contains the kernel and device trees)
/dev/mmcblk2p2 == rootfs_a
/dev/mmcblk2p3 == rootfs_b
/dev/mmcblk2p7 == boot_b partition (that contains the kernel and device trees)
The rauc system.conf is shown below:
The rauc update-bundle.bb is shown below:
From the above when we perform an update; rauc updates the rootfs and update the corresponding boot slot with the kernel image.
But the boot partition that has been updated can not be mounted and and the kernel reports bad file system
Please can you tell us what we are doing wrong; or what we have missed.
We want to use rauc to update the entire rootfs and the entire corresponding boot partition
Beta Was this translation helpful? Give feedback.
All reactions