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

Zoran Stojsavljevic zoran.stojsavljevic at gmail.com
Wed Apr 17 23:57:01 PDT 2019


Hello PierLuigi,

I almost immediately read your attached log file. And this cot my eye:
*>>> U-Boot SPL 2012.10-gcbef171* (Mar 09 2016 - 17:01:14)

Seems, that you have U-Boot version from Y2012 (2012.10)???

For the starters, could you, please, update your FW to U-boot version
2019.01 at least! And try the same conditions again?

Thank you,
Zoran
_______

On Wed, Apr 17, 2019 at 9:06 PM Pierluigi Greto <pierluigi.greto at bisdn.de>
wrote:

> Hi Zoran,
>
> thank you for the reply.
> [1] In this you can find some information about the device (link
> <https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/platforms/delta/armel/arm-delta-ag6248c/arm-delta-ag6248c-poe/platform-config/r0/src/lib/arm-delta-ag6248c-poe-r0.yml>).
> In this patch the dts (link
> <https://github.com/opencomputeproject/OpenNetworkLinux/blob/663642e817c33d44d5e4dd1f98247addd68c9f5c/packages/base/any/kernels/3.2-lts/configs/arm-iproc-all/patches/platform-delta-ag6248c-device-drivers.patch>).
> The platform is an arm cortexa9.
> [2] This is how I install the image
>
> install_uimage() {    echo "Format Nand Flash region\n"    flash_erase /dev/mtd-open 0 0    nandwrite -p /dev/mtd-open fitImage-core-image-base-delta-ag6248c-poe.bin    sync; sync}hw_load() {    echo "nand read \$loadaddr open 0x1000000 && run fpboot && bootm"}
>
> I'll attach the log from when I install the image to when it the kernel
> hangs.
>
> Thank you,
> Pierluigi
> On 17/04/19 17:26, Zoran Stojsavljevic wrote:
>
> Hello PierLuigi,
>
> [1] Which arm platform (based upon which arm Open Sorce platform) you are using?
> [2] Please, can we see your added proprietary ash script to U-Boot default env?
>
> Thank you,
> Zoran
> _______
>
> On Wed, Apr 17, 2019 at 5:13 PM Pierluigi Greto<pierluigi.greto at bisdn.de> <pierluigi.greto at bisdn.de> 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
> ...". In the log I can see that the kernel uncompressed image, the
> ramdisk subimage and  the Flat Device Tree are found. But the kernel
> doesn't start.
> Any hints on how to check what it's wrong with the image? For example if
> the kernel is correctly compiled, the FTD is the right one ecc.
> The loaded kernel is shown as "uncompressed", there is some way to
> define the compression type in yocto (I have an image that works and the
> kernel is shown as "gzip compressed")? Could the compression type be a
> problem?
>
> Any hint is very welcome.
>
> Thank you,
> Pierluigi
>
> --
> _______________________________________________
> yocto mailing listyocto at yoctoproject.orghttps://lists.yoctoproject.org/listinfo/yocto
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20190418/675503e5/attachment.html>


More information about the yocto mailing list