[yocto] Debugging deployment of kernel image

[Westermann, Oliver]

Hey,

I'm currently in the process of updating our yocto (sumo) with a new kernel version from a supplier (NXP) and I'm having some issues, we somehow broke deployment of the linux kernel: I get the Image & symlink in my images folder, but it does not end up in my rootfs. It SHOULD end up at /boot. My system boots u-boot and searches for the kernel (and fails ofc). If I manually place my kernel, everything is fine.

I would like to find out where in my recipes this goes south:
I've checked build/<my conf>/tmp/work/<m< conf>-poky-linux/linux-imx/4.14.78-r0/deploy-linux-imx and the kernel and the expected kernel Image and symlink is there alongside the .dtb files. The dtb files get deployed as expected, but my kernel does not.

I've also checked build/<my conf>/tmp/work/<my conf>-poky-linux/linux-imx/4.14.78-r0/deploy-rpms/<my conf>/ , where I've got a kernel-image-image-4.14.78-<branch>+-4.14.78-r0.<my conf>.rpm, which contains the kernel and the symlink.
Which brings me into an area of yocto I'm not used to, since usually THAT part worked for me ;-)

So if a RPM is generated, but not properly installed, where do I continue my debugging efforts?
I've already checked the output of bitbake -e linux-imx, but I only used -e only to debug my recipes (how stuff expands), so this was more of a "random looking at stuff" to figure things out.

Any help appreciated.

- Olli

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20190531/cc023a73/attachment-0001.html>