[yocto] Image not staring after upgrade from sumo to thud

Hi all, I have several platforms and I have upgrade Yocto from sumo to thud. Most of them works fine after the upgrade, but some of them are not starting. Basically after I install the image and I have chose my OS in grub, the system reboot. But if I create the image using sumo, the image is

[yocto] arm yocto-linux custom defconfig not working

Hi, I have to create a custom 4.14.49 linux kernel. In my recipe I have added my defconfig , but yocto it's not taking in consideration the

[yocto] fitImage kernel compression type

Hello everyone, I'm building an fitImage and I would like to set the kernel compression type. Yocto is automatically creating the linux.bin but I cannot find any variable to specify the kernel compression type. I would like to have a gzip compressed kernel. Is possible to specify the

Re: [yocto] fitImage: hangs at "Starting kernel ..."

ded proprietary ash script to U-Boot default env? Thank you, Zoran ___ On Wed, Apr 17, 2019 at 5:13 PM Pierluigi Greto wrote: Hi all, I'm trying to build an image for an arm platform with uboot. After the installation, when the system is starting it hangs at "Starting kernel ..."

[yocto] fitImage: hangs at "Starting kernel ..."

Hi all, I'm trying to build an image for an arm platform with uboot. After the installation, when the system is starting it hangs at "Starting kernel ...". In the log I can see that the kernel uncompressed image, the ramdisk subimage and  the Flat Device Tree are found. But the kernel