We are using yocto (warrior) with the poky kernel, which used to be 5.0.7 and u-boot and fitImage. This seems to have worked fine so far, but when I updated the kernel to 5.0.x, x < 7, the boot fails. Sadly, this happens right when the kernel takes over, hence, the last thing I see is
“Starting kernel …”
Since this is for me not quite enough to understand, where the kernel hangs, I need more possibilities how one can debug that. Further more, right now, on some builds, even 5.0.7 kernel hangs. I am pretty sure, it has nothing to do with the changes that happen in the kernel, since the kernel breaks before event the first printk happens.
The funny thing is, that when I compare the binaries of a working or not working kernel, they almost do not differ. The places, where they differ seem to me be places where the build time is mentioned…
Does anyone have any hints, how to debug this???
I guess, I am using the wrong addresses for loading? But then, why does it work for one, and fail for another? It seems a bit random…