[meta-ti] TI boot-monitor recipe doesn't install the boot monitor binary in the image

[Denys Dmytriyenko]

On Mon, Feb 10, 2014 at 07:21:30AM +0000, Jose Alarcon wrote:
> Hello Denys,
> 
> Thanks for your comments. I am following the instructions on the MCSDK wiki 
> page: 
> http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#UBI.2FUBIFS
> 
>   NAND Layout
>   The NAND flash in the EVM contains three partitions:-
> 
>     bootloader - Contains u-boot
>     params - contains env variables
>     ubifs - contains following UBI volumes:-
>     boot volume - contains Kernel image (uImage), device tree blob etc,
>     rootfs volume - contains the rootfs which is the primary filesystem
> 
> After flashing the ubi image, the boad doesn't boot up unless I force the 
> installation of the boot monitor under the /boot dir in the rootfs. The 
> kernel and the device tree were there already (didn't check which recipe 
> install those).

The instructions above talk extensively about boot-monitor and the need to 
load it in RAM from U-boot. It doesn't say the image should be part of roofs.


> About the update of the keystone recipes to a newer yocto release, do you 
> have any estimation on when that will be ready? I am anticipating some work 
> on our side as well after this update.

The necessary Keystone recipes and updates are now being submitted, reviewed 
and pushed to main meta-ti (and meta-arago) repositories. No ETA yet.


> Thanks and sorry for the top posting. Using Outlook here :-(
> 
> --
> Jose
> ________________________________________
> From: Denys Dmytriyenko [denys at ti.com]
> Sent: Friday, February 07, 2014 9:10 PM
> To: Jose Alarcon
> Cc: meta-ti at yoctoproject.org
> Subject: Re: [meta-ti] TI boot-monitor recipe doesn't install the boot monitor binary in the image
> 
> On Fri, Feb 07, 2014 at 10:36:09AM +0000, Jose Alarcon wrote:
> > Hi there,
> >
> > In order to boot ubi images on our Keystone2-evem, we had to modify the
> > boot-monitor recipe so that the boot monitor binary gets installed into the
> > image.
> >
> > We fixed this in our own layers with a bbappend file like this:
> >
> >     PROVIDES += "boot-monitor"
> >
> >     do_install () {
> >         install -d ${D}/boot
> >         install ${S}/${BOOT_MONITOR_BINARY} ${D}/boot/${BOOT_MONITOR_IMAGE}
> >         ln -sf ${BOOT_MONITOR_IMAGE} ${D}/boot/${BOOT_MONITOR_BINARY}
> >     }
> >
> >     FILES_${PN} = "/boot ${sysconfdir}"
> >
> > Should this be fixed in the boot-monitor_git.bb recipe itself?
> >
> > I am using danny branch of meta-ti, commit 0039248515b16b88161844aef5d507737331c834
> 
> Jose,
> 
> boot-monitor gets deployed as a standalone image, like u-boot, kernel,
> devitrees etc. I don't think it needs to go into the rootfs...
> 
> Plus, danny branch is long since outdated. Currently we are in the process of
> updating Keystone recipes, so please stay tuned. Thanks.
> 
> --
> Denys