Skip to contentSkip to conversation

Run-time discovery of machine for image compatibility check

DISCUSSION Eystein Måløy Stenberg 4 participants 6 messages Sep 30, 2015 – Nov 14, 2015

lore
Share & tools
lore
#0 lore raw

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.

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

#1 lore raw

Hi in my case I have a machine for each board and I choose the right device-tree at "machine".conf. So MACHINE can be determined by the device tree Im running.

Other option would be echoing the machine to /etc/issue of the image. I do this with DISTRO_VERSION. You can use ROOTFS_POSTPROCESS_COMMAND to achieve this.

Regards
Em 30/09/2015 18:32, "Eystein Måløy Stenberg" <[email protected]> escreveu:

Quoted 32 lines

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.

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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#2 lore raw
In reply to Eystein Måløy Stenberg
Quoted 10 lines · Eystein Måløy Stenberg

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.

Quoted 24 lines

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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#3 lore raw

Thanks to everyone on the input on this issue. I eventually solved it by using an image feature called "buildinfo".

In case someone come across a similar need in the future I've created these two blog post to advertise buildinfo it a bit more and show how to use it:

* https://www.mender.io/blog/build-info-yocto-1
* https://www.mender.io/blog/build-info-yocto-2

Quoted 45 lines · Khem Raj
Quoted 10 lines · Eystein Måløy Stenberg

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.

Quoted 24 lines

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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 1 line
Eystein
#4 lore raw

The recommendations on your blog suggest modifying image-buildinfo.bbclass to change IMAGE_BUILDINFO_VARS. You /should/ be able to avoid this by simply adding something like

IMAGE_BUILDINFO_VARS_append = " MACHINE DEVICE_MODEL DEVICE_TYPE" or
IMAGE_BUILDINFO_VARS = "DISTRO DISTRO_VERSION MACHINE DEVICE_MODEL DEVICE_TYPE" to local.conf.

The first version should extend the value whereas the second should completely replace it. This should work because image-buildinfo.bbclass used the ?= operator to set the variable. For the same reason you should NOT use += to extend the variable, but should use _append instead.

This should be easier to maintain when updating your 'version of yocto'.

NOTE: In /extreme/ summary this would mean

Add the following to local.conf
INHERIT += "image-buildinfo"
DEVICE_MODEL = "some-extra-identifying-details" IMAGE_BUILDINFO_VARS_append = " MACHINE DEVICE_MODEL"

to get a /etc/build file in your resulting image with information similar to the build configuration summary bitbake outputs during a build.

Quoted 68 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Eystein Måløy Stenberg
Sent: Tuesday, November 10, 2015 8:29 PM
To: Khem Raj
Cc: [email protected]
Subject: Re: [yocto] Run-time discovery of machine for image compatibility check

Thanks to everyone on the input on this issue. I eventually solved it by using an image feature called "buildinfo".

In case someone come across a similar need in the future I've created these two blog post to advertise buildinfo it a bit more and show how to use it:

* https://www.mender.io/blog/build-info-yocto-1
* https://www.mender.io/blog/build-info-yocto-2

Quoted 2 lines · Khem Raj
Quoted 2 lines

On Sep 30, 2015, at 2:31 PM, Eystein Måløy Stenberg <[email protected]>

Quoted 6 lines · wrote:
Quoted 6 lines

Hi,

Before starting a bitbake build, we input the MACHINE variable in local.conf (e.g. MACHINE ?= beaglebone).

Quoted 8 lines
Quoted 2 lines

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.

Quoted 3 lines

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.

Quoted 17 lines
Quoted 17 lines

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!

Quoted 9 lines
Quoted 8 lines

--

Eystein
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 8 lines

--

Eystein
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

________________________________

Notice to recipient: This email is meant for only the intended recipient of the transmission, and may be a communication privileged by law, subject to export control restrictions or that otherwise contains proprietary information. If you receive this email by mistake, please notify us immediately by replying to this message and then destroy it and do not review, disclose, copy or distribute it. Thank you in advance for your cooperation.

#5 lore raw

Virgil,

Thank you for pointing this out, I've updated the post to override the variable instead!

Quoted 107 lines · Virgil

The recommendations on your blog suggest modifying image-buildinfo.bbclass to change IMAGE_BUILDINFO_VARS. You /should/ be able to avoid this by simply adding something like

IMAGE_BUILDINFO_VARS_append = " MACHINE DEVICE_MODEL DEVICE_TYPE" or
IMAGE_BUILDINFO_VARS = "DISTRO DISTRO_VERSION MACHINE DEVICE_MODEL DEVICE_TYPE" to local.conf.

The first version should extend the value whereas the second should completely replace it. This should work because image-buildinfo.bbclass used the ?= operator to set the variable. For the same reason you should NOT use += to extend the variable, but should use _append instead.

This should be easier to maintain when updating your 'version of yocto'.

NOTE: In /extreme/ summary this would mean

Add the following to local.conf
INHERIT += "image-buildinfo"
DEVICE_MODEL = "some-extra-identifying-details" IMAGE_BUILDINFO_VARS_append = " MACHINE DEVICE_MODEL"

to get a /etc/build file in your resulting image with information similar to the build configuration summary bitbake outputs during a build.

Quoted 68 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Eystein Måløy Stenberg
Sent: Tuesday, November 10, 2015 8:29 PM
To: Khem Raj
Cc: [email protected]
Subject: Re: [yocto] Run-time discovery of machine for image compatibility check

Thanks to everyone on the input on this issue. I eventually solved it by using an image feature called "buildinfo".

In case someone come across a similar need in the future I've created these two blog post to advertise buildinfo it a bit more and show how to use it:

* https://www.mender.io/blog/build-info-yocto-1
* https://www.mender.io/blog/build-info-yocto-2

Quoted 2 lines · Khem Raj
Quoted 2 lines

On Sep 30, 2015, at 2:31 PM, Eystein Måløy Stenberg <[email protected]>

Quoted 6 lines · wrote:
Quoted 6 lines

Hi,

Before starting a bitbake build, we input the MACHINE variable in local.conf (e.g. MACHINE ?= beaglebone).

Quoted 8 lines
Quoted 2 lines

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.

Quoted 3 lines

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.

Quoted 17 lines
Quoted 17 lines

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!

Quoted 9 lines
Quoted 8 lines

--

Eystein
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 8 lines

--

Eystein
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

________________________________

Notice to recipient: This email is meant for only the intended recipient of the transmission, and may be a communication privileged by law, subject to export control restrictions or that otherwise contains proprietary information. If you receive this email by mistake, please notify us immediately by replying to this message and then destroy it and do not review, disclose, copy or distribute it. Thank you in advance for your cooperation.

Signature · 1 line
Eystein