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

[Colin Helliwell]

Hmmm, ok – maybe I should be baking beyond ‘core-image-minimal’?

 

As background:

Up until now I’ve just been manually copying/renaming/extracting the various items - rootfs,modules,kernel,dtb,MLO,uboot - from build/tmp/deploy/images/beaglebone into the necessary places on SD card. i.e. that bake *isn’t* putting the dtb into the rootfs tgz in that directory (though the kernel, together with a symlink ‘zImage’, *is* in the tgz).

Today I’ve started looking at using wic (based on info in https://lists.yoctoproject.org/pipermail/meta-ti/2014-July/004887.html ) to create a single SD image file. I have this successfully pulling everything into the image – automagically doing all the steps I’ve previously being doing manually. Except that the waiting dtb has the wrong name, as described. 

So I’m unsure of the best point of attack to amend this…

 

 

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?

 

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