: colin.helliw...@ln-systems.com; yocto@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.
No
Sent: 24 September 2015 16:13
To: 'Christopher Larson'; yocto@yoctoproject.org
Subject: Re: [yocto] am335x-boneblack.dtb 'misnamed'? (Fido/BeagleBoneBlack)
Hmmm, ok – maybe I should be baking beyond ‘core-image-minimal’?
As background:
Up until now I’ve just been manua
[mailto:clar...@kergoth.com]
Sent: 24 September 2015 15:27
To: colin.helliw...@ln-systems.com; yocto@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-alterna
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.helliw...@ln-systems.com> wrote:
> Thi
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 t
