[yocto] am335x-boneblack.dtb 'misnamed'? (Fido/BeagleBoneBlack)

[Colin Helliwell]

Ah, ok – I see what you mean now. ‘core-image-base’ puts the dtb and kernel (with symlinks) into /boot in the rootfs tarball.

Thanks for the pointer – that may get me moving onwards again now…

 

From: Christopher Larson [mailto:clarson at kergoth.com] 
Sent: 24 September 2015 15:27
To: colin.helliwell at ln-systems.com; yocto at yoctoproject.org
Subject: Re: [yocto] am335x-boneblack.dtb 'misnamed'? (Fido/BeagleBoneBlack)

 

It's installed into /boot on the rootfs with the zImage prefix, and update-alternatives creates a symlink to the correct path so uboot can find it. Not sure why this indirection exists, but it does work.

On Thu, Sep 24, 2015 at 4:52 AM Colin Helliwell <colin.helliwell at ln-systems.com> wrote:

This may just be ‘the way it is’, but the stock Fido/BeagleBoneBlack BSP [core-image-minimal] builds the am335x-boneblack dtb file, and creates in build/tmp/deploy/images/beaglebone a symlink named ‘zImage-am335x-boneblack.dtb’. However – and this is borne out by README.hardware – uboot is set up to look for ‘am335x-boneblack.dtb’.

I daresay I can do some sort of fixup, but I was curious why it’s like this?

 

--
_______________________________________________
yocto mailing list
yocto at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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