meta-rauc-nxp support add to Kirkstone branch

[Hassin10760]

Dear Community,

Thanks for this meta-layer . I am working with Toradex verdin imx8mp SoM . For a Specific package version support I have to work with Kirkstone . Will there be any support added for nxp to the kirkstone branch like the meta-rauc-nxp available at the master branch ?

Thank you

[jluebbe]

The layer was added by @AtanasBunchev in #46 and extended by @leon-anavi.

I suspect that they don't have plans to backport it to kirkstone, but maybe they would review such a backport as a PR contribution?

[Hassin10760]

@jluebbe thanks for the reply . is it possible to create a new sub-layer following let's say meta-rauc-beaglebone as example / reference for an imx8mp board ? is there any guideline on how to do this ? So far I have understood that I need to create a new Layer which will have configurations to do the below

• choose u-boot as bootloader
• create kernel configs to enable squashfs in the kernel
• create partitions in the eMMC
• u-boot related customization (1) write bootloader script which will be called by u-boot (2) change boot.cmd.in
• certificate, keyring generation and integration

A tutorial on how to port in yocto , can be also very helpful

Thank you

[leon-anavi]

@jluebbe thanks for the reply . is it possible to create a new sub-layer following let's say meta-rauc-beaglebone as example / reference for an imx8mp board ?

The BeagleBone Black integration exists and it is available in sub-layer meta-rauc-beaglebone. As a reference for i.MX8 you can have a look at Olimex iMX8MP-SOM-4GB-IND / iMX8MP-SOM-EVB-IND from meta-rauc-nxp, although Toradex Verdin i.MX8 uses different BSP layers.

I am working with Toradex verdin imx8mp SoM . For a Specific package version support I have to work with Kirkstone . Will there be any support added for nxp to the kirkstone branch like the meta-rauc-nxp available at the master branch ?

I don't have a Toradex verdin imx8mp SoM anymore therefore as of the moment I have no plan to add support for it in meta-rauc-community. As the name of the layer suggests, community contributions are always welcome. Preferable new boards should go in the main branch first (if the BSP supports its) and after that to be backported to LTS releases like Scarthgap or even Kirkstone.

Best regards, Leon

[Hassin10760]

@leon-anavi Thanks for your kind suggestion and directing me to Olimex . I have just finished watching one of your videos (It helped me a lot understanding the concepts ) . Now going through RAUC documentations to understand how to do the Porting for a new board. I guess there is no straight step by step guide.

Toradex has said they do not support RAUC for this BSP at Kirkstone ref: https://community.toradex.com/t/rauc-support-for-verdin-imx8mp-kirkstone/26636 . In this case is it still possible to port RAUC for this SoM ? I guess it will be hard , first I have to follow Olimex out of the master branch , test out of a recent yocto version other than kirkstone and then backport to kirkstone

Thanks for your reply

[leon-anavi]

Why do you want to use Kirkstone? There is no major difference in the approach but for new integration Scarthgap makes more sense.

[Hassin10760]

@leon-anavi That's a very legitimate question . Actually the project is dependent on a Software Package which is only supported to Kirkstone. For that particular package the yocto version is locked to kirkstone :(

[leon-anavi]

@leon-anavi That's a very legitimate question . Actually the project is dependent on a Software Package which is only supported to Kirkstone. For that particular package the yocto version is locked to kirkstone :(

If I were you I would consider updating whatever this software package it to Scarthgap. Kirkstone will reach end of life at Apr. 2026 so it is not highly recommended for new development.