RSDK's --debs option isn't replacing the default kernel

Zero Series
1

Hello everyone,

I’m trying to build a custom image using RSDK and have run into an issue.

I have a custom kernel that I built from the BSP and packaged as a .deb file. This kernel package installs and works correctly on my board when I install it manually using dpkg .

However, when I try to include this custom kernel in a new image using RSDK with the --debs option, the final image is still built with the default kernel instead of my custom one.

Has anyone encountered a similar issue or have any idea why the --debs option might not be overwriting the default kernel?

2

Did you make sure the kernel deb file is placed in a debs directory under the root directory of rsdk? You can also save the output of rsdk using tee and confirm if the kernel deb package was tried to be installed but failed because of some reasons.

3

Thanks for the reply.
Yes, that’s correct. All the .deb files generated by the BSP are placed in the debs directory. My command is:

rsdk build --debs ./debs radxa-zero3 bookworm cli

is that correct?
I will try tee to capture the logs.

4

command is:

rsdk build --debs ./debs radxa-zero3 bookworm cli

is that correct?

It looks good to me.