[yocto] Run-time discovery of machine for image compatibility check

[Khem Raj]

> On Sep 30, 2015, at 2:31 PM, Eystein Måløy Stenberg <eystein at mender.io> wrote:
> 
> Hi,
> 
> Before starting a bitbake build, we input the MACHINE variable in
> local.conf (e.g. MACHINE ?= beaglebone).
> 
> Is there a way to detect this variable at run-time? I.e. if I have built
> the image, written it to a device, and I'm now logged in to it.

There is no standard bill of materials that you will find on images. Everyone produces it
per own needs. The reason is that we do not have a one OTA mechanism recommended or preferred
in OpenEmbedded or maintained by yocto project. May be this could be a thing to consider come future
right now, there were other big fish to fry around workflow. OTA firmware upgrade, could be big thing for next release
or there after.

I don’t have a better answer for you at the moment. You have to work with device firmware manufacturer
and see if they have put some image info into the image in some form.

> 
> The reason I want this is that I'm working on a project to deploy image
> updates (remotely), and I only want to write the image if the device is
> compatible with the image file. So I need to know both the
> hardware/board type and what the image target is (assuming this is the
> MACHINE variable alone). Then I will only write the image if they are
> the same.
> 
> Also, do you think using the MACHINE variable is the right approach for
> this problem? Maybe someone has had a similar problem?
> 
> I'm new to Yocto, sorry if I'm asking something obvious (but I could not
> find an answer in the docs).
> 
> Thanks!
> 
> --
> 
> Eystein
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20150930/a6c82194/attachment.pgp>