Date   

Re: Yocto Image Build for NXP i.MX8M

Aj Cit
 

Hello,

I'm getting the following error when I have tried to simulate the image on QEMU

adminuser@verathon:~/poky/build$ runqemu qemux86
runqemu - INFO - Running MACHINE=qemux86 bitbake -e...
runqemu - ERROR - /home/adminuser/poky/build/tmp/deploy/images/qemux86 not a directory valid DEPLOY_DIR_IMAGE
ls: cannot access '/home/adminuser/poky/build/tmp/deploy/images/qemux86/*.qemuboot.conf': No such file or directory
runqemu - ERROR - Command 'ls -t /home/adminuser/poky/build/tmp/deploy/images/qemux86/*.qemuboot.conf' returned non-zero exit status 2.
runqemu - INFO - Cleaning up


any help would be appreciated.

tnQ

On Thu, Nov 28, 2019 at 5:33 PM Aj Cit via Lists.Yoctoproject.Org <aj.ci.01.239=gmail.com@...> wrote:

Dear Josef,

I've managed to run build command to generate OS image for the target, which is core-image-sato by executing the following command:

     $ bitbake core-image-sato
Can I know how to proceed further?

I'm getting the following response from the Ubuntu 18.04.1 LTS

Loading cache: 100% |#########################################################################################################| Time: 0:00:00
Loaded 1264 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.40.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "qemux86-64"
DISTRO               = "poky"
DISTRO_VERSION       = "2.6.2"
TUNE_FEATURES        = "m64 core2"
TARGET_FPU           = ""
meta
meta-poky
meta-yocto-bsp       = "HEAD:e7f0177ef3b6e06b8bc1722fca0241fef08a1530"

Initialising tasks: 100% |#########################################################################################################| Time: 0:00:02
Checking sstate mirror object availability: 100% |######################################################################################| Time: 0:05:55
Sstate summary: Wanted 1402 Found 329 Missed 2146 Current 708 (23% match, 49% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: sudo-1.8.23-r0 do_fetch: Failed to fetch URL http://ftp.sudo.ws/sudo/dist/sudo-1.8.23.tar.gz, attempting MIRRORS if available
NOTE: Tasks Summary: Attempted 5774 tasks of which 2941 didn't need to be rerun and all succeeded.

Summary: There was 1 WARNING message shown.
adminuser@verathon:~/poky/build$ ls
bitbake-cookerdaemon.log  cache  conf  downloads  sstate-cache  tmp
adminuser@verathon:~/poky/build$ runqemu qemux86
runqemu - INFO - Running MACHINE=qemux86 bitbake -e...
runqemu - ERROR - /home/adminuser/poky/build/tmp/deploy/images/qemux86 not a directory valid DEPLOY_DIR_IMAGE
ls: cannot access '/home/adminuser/poky/build/tmp/deploy/images/qemux86/*.qemuboot.conf': No such file or directory
runqemu - ERROR - Command 'ls -t /home/adminuser/poky/build/tmp/deploy/images/qemux86/*.qemuboot.conf' returned non-zero exit status 2.
runqemu - INFO - Cleaning up
adminuser@verathon:~/poky/build$


Thanks,

Ajith

On Thu, Nov 28, 2019 at 2:34 PM Josef Holzmayr <holzmayr@...> wrote:
On Thu, Nov 28, 2019 at 02:29:08PM +0530, Aj Cit wrote:
> Hi Josef,
>
> Is there specific steps to be followed to build an image for iMX8M?

You need at least a board support (BSP) layer. As I have no clue about
your board, I can only guess that it will probably something freescale
related, mabye https://git.yoctoproject.org/cgit.cgi/meta-freescale/

But first and absolutely foremost:
1) watch the introductory videos
2) consult the documentation of your board vendor.

Greetz

>
> Tnx
> Ajith
>
> On Thu, Nov 28, 2019 at 2:23 PM Josef Holzmayr <
> holzmayr@...> wrote:
>
> > On Thu, Nov 28, 2019 at 02:02:29PM +0530, Aj Cit wrote:
> > > I've followed the instruction from the yocto project:
> > >
> > https://www.yoctoproject.org/docs/3.0/brief-yoctoprojectqs/brief-yoctoprojectqs.html
> >
> > This can not be exactly true, as this guide certainly does not include
> > anything related to the imx8. So you are either still building for qemu
> > (as it defaults to), or using seomthing additional that you're not
> > mentioning.
> >
> > >
> > >
> > > till the bitbake command. However, I'm getting the following error:
> > > ERROR:  OE-core's config sanity checker detected a potential
> > > misconfiguration.
> > >     Either fix the cause of this error or at your own risk disable the
> > > checker (see sanity.conf).
> > >     Following is the list of potential problems / advisories:
> > >
> > >     Do not use Bitbake as root.
> >
> > Here is your answer: do not run botbake as the root user :)
> >
> > In a nutshell, I recommend watching at least the first couple of videos
> > here:
> > https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj
> >
> > Greetz
> > >
> > >
> > > On Thu, Nov 28, 2019 at 12:29 PM Aj Cit <aj.ci.01.239@...> wrote:
> > >
> > > > Hello,
> > > >
> > > > I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s).
> > I
> > > > am getting some error when I execute the bitmake command.
> > > >
> > > > I'd appreciate if you could guide me with next steps. Any Guide or url
> > > > will be helpful.
> > > >
> > > > Thanks
> > > > Ajith
> > > >
> >
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > > Links: You receive all messages sent to this group.
> > >
> > > View/Reply Online (#47444):
> > https://lists.yoctoproject.org/g/yocto/message/47444
> > > Mute This Topic: https://lists.yoctoproject.org/mt/63894854/3618269
> > > Group Owner: yocto+owner@...
> > > Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [
> > holzmayr@...]
> > > -=-=-=-=-=-=-=-=-=-=-=-
> >
> >
> > --
> > ———————————————
> > Josef Holzmayr
> > Software Developer Embedded Systems
> >
> > Tel: +49 8444 9204-48
> > Fax: +49 8444 9204-50
> >
> > R-S-I Elektrotechnik GmbH & Co. KG
> > Woelkestrasse 11
> > D-85301 Schweitenkirchen
> > www.rsi-elektrotechnik.de
> > ———————————————
> > Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
> > Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
> > Ust-IdNr: DE 128592548
> >
> > _____________________________________________________________
> > Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
> > Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
> > USt-IdNr.: DE 128592548
> >
> >

--
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47455): https://lists.yoctoproject.org/g/yocto/message/47455
Mute This Topic: https://lists.yoctoproject.org/mt/63894854/3738872
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [aj.ci.01.239@...]
-=-=-=-=-=-=-=-=-=-=-=-


Re: Architecture of .wic approach; image of images

Leon Woestenberg
 

On Thu, Nov 28, 2019 at 1:52 PM Josef Holzmayr
<holzmayr@...> wrote:

On Thu, Nov 28, 2019 at 01:32:56PM +0100, Leon Woestenberg wrote:
- Does Yocto support building multiple images from one configuration?
Of course it does. If you have set DISTRO and MACHINE, you can
bitbake core-image-minimal
bitbake core-image-x11
bitbake ... whatever image.

Thats exactly the point of the MACHINE / DISTRO / IMAGE seperation.
Yes, up to there everything is clean and nice.
And I understand I can build multiple images. I have used this feature
since 2006.

My point is, that we do not support images of images correctly. Or, I
do not understand how it works.

If I have an initramfs image, my next step is to build a disk image
that has the initramfs.cpio.gz, but without generating a new rootfs.

How would I do that?


Re: Architecture of .wic approach; image of images

Josef Holzmayr <holzmayr@...>
 

On Thu, Nov 28, 2019 at 01:32:56PM +0100, Leon Woestenberg wrote:
Au contraire :) It is the real issue because neither 1) nor 2) is the
correct way, and I pretty much explained why that is.

So let's then consider the case that the WKS is machine specific. I am
fine with that.

- Does Yocto support building multiple images from one configuration?
Of course it does. If you have set DISTRO and MACHINE, you can
bitbake core-image-minimal
bitbake core-image-x11
bitbake ... whatever image.

Thats exactly the point of the MACHINE / DISTRO / IMAGE seperation.

- (How) can I build multiple WIC images with different WKSs?
That on the other hand is a good question. The documentation is not
specific on the number of files you can set in WKS_FILE, so i guess at
the moment it is limited to one. So one could investigate if it is worth
augmenting that, or just harness the multiconfig features we have those
days. Their syntax is a little more complicated, but should totally
serve this purpose.

Greetz.


I am not asking anything strange.
I just cannot find an example of a grub + initramfs + kernel packages
into FAT through WIC.
Or documentation on how to implement this correctly.

Regards,

Leon.
--
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


Re: Architecture of .wic approach; image of images

Leon Woestenberg
 

Au contraire :) It is the real issue because neither 1) nor 2) is the
correct way, and I pretty much explained why that is.

So let's then consider the case that the WKS is machine specific. I am
fine with that.

- Does Yocto support building multiple images from one configuration?
- (How) can I build multiple WIC images with different WKSs?

I am not asking anything strange.
I just cannot find an example of a grub + initramfs + kernel packages
into FAT through WIC.
Or documentation on how to implement this correctly.

Regards,

Leon.


Re: Architecture of .wic approach; image of images

Josef Holzmayr <holzmayr@...>
 

On Thu, Nov 28, 2019 at 12:53:54PM +0100, Leon Woestenberg wrote:
On Thu, Nov 28, 2019 at 12:41 PM Josef Holzmayr
<holzmayr@...> wrote:
On Thu, Nov 28, 2019 at 12:11:52PM +0100, Leon Woestenberg wrote:
Let me then first describe the issue I am having, which I think
results from my misunderstanding then.

I would like to package a UEFI bootloader (GRUB), bzImage and
initramfs.cpio.gz into an FAT partition using WIC.

1) Should I adapt my existing my-initramfs recipe as follows:

IMAGE_FSTYPES += "wic"
WKS_FILE = "my-disk-image.wks"
I think I'm starting to see the problem. Do you set those things in your
image recipe?
IMAGE_FSTYPES += "wic" goes in the image recipe, yes.

WKS_FILE is there as well for this image, because I need to create
multiple images with different WKS's.

If it included things like that, how could we use it
as a "hello world"-style image for about every platform?
I want to create several images. The one I described is a recovery image.
I also want an application image which has a different WKS.

However, this is not the real issue. I first would like to understand
if I need to follow 1) or 2).
Au contraire :) It is the real issue because neither 1) nor 2) is the
correct way, and I pretty much explained why that is.

What you actually describing are two combinations of image+machine or
image+distro, depending on the exact situation.

Greetz

--
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


Re: Yocto Image Build for NXP i.MX8M

Aj Cit
 


Dear Josef,

I've managed to run build command to generate OS image for the target, which is core-image-sato by executing the following command:

     $ bitbake core-image-sato
Can I know how to proceed further?

I'm getting the following response from the Ubuntu 18.04.1 LTS

Loading cache: 100% |#########################################################################################################| Time: 0:00:00
Loaded 1264 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.40.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "qemux86-64"
DISTRO               = "poky"
DISTRO_VERSION       = "2.6.2"
TUNE_FEATURES        = "m64 core2"
TARGET_FPU           = ""
meta
meta-poky
meta-yocto-bsp       = "HEAD:e7f0177ef3b6e06b8bc1722fca0241fef08a1530"

Initialising tasks: 100% |#########################################################################################################| Time: 0:00:02
Checking sstate mirror object availability: 100% |######################################################################################| Time: 0:05:55
Sstate summary: Wanted 1402 Found 329 Missed 2146 Current 708 (23% match, 49% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: sudo-1.8.23-r0 do_fetch: Failed to fetch URL http://ftp.sudo.ws/sudo/dist/sudo-1.8.23.tar.gz, attempting MIRRORS if available
NOTE: Tasks Summary: Attempted 5774 tasks of which 2941 didn't need to be rerun and all succeeded.

Summary: There was 1 WARNING message shown.
adminuser@verathon:~/poky/build$ ls
bitbake-cookerdaemon.log  cache  conf  downloads  sstate-cache  tmp
adminuser@verathon:~/poky/build$ runqemu qemux86
runqemu - INFO - Running MACHINE=qemux86 bitbake -e...
runqemu - ERROR - /home/adminuser/poky/build/tmp/deploy/images/qemux86 not a directory valid DEPLOY_DIR_IMAGE
ls: cannot access '/home/adminuser/poky/build/tmp/deploy/images/qemux86/*.qemuboot.conf': No such file or directory
runqemu - ERROR - Command 'ls -t /home/adminuser/poky/build/tmp/deploy/images/qemux86/*.qemuboot.conf' returned non-zero exit status 2.
runqemu - INFO - Cleaning up
adminuser@verathon:~/poky/build$


Thanks,

Ajith

On Thu, Nov 28, 2019 at 2:34 PM Josef Holzmayr <holzmayr@...> wrote:
On Thu, Nov 28, 2019 at 02:29:08PM +0530, Aj Cit wrote:
> Hi Josef,
>
> Is there specific steps to be followed to build an image for iMX8M?

You need at least a board support (BSP) layer. As I have no clue about
your board, I can only guess that it will probably something freescale
related, mabye https://git.yoctoproject.org/cgit.cgi/meta-freescale/

But first and absolutely foremost:
1) watch the introductory videos
2) consult the documentation of your board vendor.

Greetz

>
> Tnx
> Ajith
>
> On Thu, Nov 28, 2019 at 2:23 PM Josef Holzmayr <
> holzmayr@...> wrote:
>
> > On Thu, Nov 28, 2019 at 02:02:29PM +0530, Aj Cit wrote:
> > > I've followed the instruction from the yocto project:
> > >
> > https://www.yoctoproject.org/docs/3.0/brief-yoctoprojectqs/brief-yoctoprojectqs.html
> >
> > This can not be exactly true, as this guide certainly does not include
> > anything related to the imx8. So you are either still building for qemu
> > (as it defaults to), or using seomthing additional that you're not
> > mentioning.
> >
> > >
> > >
> > > till the bitbake command. However, I'm getting the following error:
> > > ERROR:  OE-core's config sanity checker detected a potential
> > > misconfiguration.
> > >     Either fix the cause of this error or at your own risk disable the
> > > checker (see sanity.conf).
> > >     Following is the list of potential problems / advisories:
> > >
> > >     Do not use Bitbake as root.
> >
> > Here is your answer: do not run botbake as the root user :)
> >
> > In a nutshell, I recommend watching at least the first couple of videos
> > here:
> > https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj
> >
> > Greetz
> > >
> > >
> > > On Thu, Nov 28, 2019 at 12:29 PM Aj Cit <aj.ci.01.239@...> wrote:
> > >
> > > > Hello,
> > > >
> > > > I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s).
> > I
> > > > am getting some error when I execute the bitmake command.
> > > >
> > > > I'd appreciate if you could guide me with next steps. Any Guide or url
> > > > will be helpful.
> > > >
> > > > Thanks
> > > > Ajith
> > > >
> >
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > > Links: You receive all messages sent to this group.
> > >
> > > View/Reply Online (#47444):
> > https://lists.yoctoproject.org/g/yocto/message/47444
> > > Mute This Topic: https://lists.yoctoproject.org/mt/63894854/3618269
> > > Group Owner: yocto+owner@...
> > > Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [
> > holzmayr@...]
> > > -=-=-=-=-=-=-=-=-=-=-=-
> >
> >
> > --
> > ———————————————
> > Josef Holzmayr
> > Software Developer Embedded Systems
> >
> > Tel: +49 8444 9204-48
> > Fax: +49 8444 9204-50
> >
> > R-S-I Elektrotechnik GmbH & Co. KG
> > Woelkestrasse 11
> > D-85301 Schweitenkirchen
> > www.rsi-elektrotechnik.de
> > ———————————————
> > Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
> > Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
> > Ust-IdNr: DE 128592548
> >
> > _____________________________________________________________
> > Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
> > Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
> > USt-IdNr.: DE 128592548
> >
> >

--
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548


Re: Architecture of .wic approach; image of images

Leon Woestenberg
 

On Thu, Nov 28, 2019 at 12:41 PM Josef Holzmayr
<holzmayr@...> wrote:
On Thu, Nov 28, 2019 at 12:11:52PM +0100, Leon Woestenberg wrote:
Let me then first describe the issue I am having, which I think
results from my misunderstanding then.

I would like to package a UEFI bootloader (GRUB), bzImage and
initramfs.cpio.gz into an FAT partition using WIC.

1) Should I adapt my existing my-initramfs recipe as follows:

IMAGE_FSTYPES += "wic"
WKS_FILE = "my-disk-image.wks"
I think I'm starting to see the problem. Do you set those things in your
image recipe?
IMAGE_FSTYPES += "wic" goes in the image recipe, yes.

WKS_FILE is there as well for this image, because I need to create
multiple images with different WKS's.

If it included things like that, how could we use it
as a "hello world"-style image for about every platform?
I want to create several images. The one I described is a recovery image.
I also want an application image which has a different WKS.

However, this is not the real issue. I first would like to understand
if I need to follow 1) or 2).

Regards,

Leon.


Re: Architecture of .wic approach; image of images

Josef Holzmayr <holzmayr@...>
 

On Thu, Nov 28, 2019 at 12:11:52PM +0100, Leon Woestenberg wrote:
Let me then first describe the issue I am having, which I think
results from my misunderstanding then.

I would like to package a UEFI bootloader (GRUB), bzImage and
initramfs.cpio.gz into an FAT partition using WIC.

1) Should I adapt my existing my-initramfs recipe as follows:

IMAGE_FSTYPES += "wic"
WKS_FILE = "my-disk-image.wks"
I think I'm starting to see the problem. Do you set those things in your
image recipe? If thats the case, this is where the misunderstandings
happen. An image file is meant to define what goes *into* the image, not
how its gonna look like for a specific hardware incarnation. Think about
core-image-minimal. If it included things like that, how could we use it
as a "hello world"-style image for about every platform?

So, those are things that are hardware, and therefore MACHINE specific.
And thats where they should end up, in your machine config. Thats the
way things are meant:
- the image recipe defines the contents.
- the machine configuration defines the "shape" (binary, partitions,
layout, whatever) that your specific platform can use.

Greetz


my-disk-image.wks:
part /boot --source bootimg-efi-initramfs
--sourceparams="loader=grub-efi,initrd=my-initramfs.cpio.gz" --ondisk
sda --label msdos --active --align 1024 --use-uuid
bootloader --ptable gpt --timeout=1

2) Or should I create a new recipe that builds the WIC and depends on
the initramfs?

Remember, I have no rootfs other than the (non-bundled) initramfs.
Depending on the answers, I will come up with the issues I see.
--
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


Re: Architecture of .wic approach; image of images

Maciej Pijanowski
 


On 28.11.2019 09:37, Leon Woestenberg wrote:
Hello all,

What is the intended approach of building images using WIC?

Most image types (except .wic) build a (root or initial ram) filesystem from *packages*, then create the respective archive or filesystem from it.
I think the rootfs is *always* assembled in the workdir (no matter which IMAGE_FSTYPES you choose.

The .wic image type however, builds an image from *images* rather than packages.
I'm not sure if this is correct. WIC is just one of the IMAGE_FSTYPES to choose from.
It does a little bit more then the tar.gz FSTYPE. The tar.gz just compresses the content
of rootfs. The WIC FSTYPE creates a disk image and installs the rootfs on a given
partition (depends on the WKS file chosen). The rootfs source is the same in
those both cases, no matter which FSTYPES you choose. It is made up of packages.

It therefore seems incorrect we can just add IMAGE_FSTYPES += "wic", because the corresponding .wks might depend on multiple other images than just ${PN}.

Should we, or do we have a recipe example that builds only a .wic image, based on one or more other existing images? (and thus not populate a filesystem itself)
I have not seen such case yet. IIUC, rootfs in the workdir is always populated when the image is built.

Regards,

Leon.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47445): https://lists.yoctoproject.org/g/yocto/message/47445
Mute This Topic: https://lists.yoctoproject.org/mt/63986097/3616795
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [maciej.pijanowski@...]
-=-=-=-=-=-=-=-=-=-=-=-
-- 
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com


Re: Architecture of .wic approach; image of images

Leon Woestenberg
 

Let me then first describe the issue I am having, which I think
results from my misunderstanding then.

I would like to package a UEFI bootloader (GRUB), bzImage and
initramfs.cpio.gz into an FAT partition using WIC.

1) Should I adapt my existing my-initramfs recipe as follows:

IMAGE_FSTYPES += "wic"
WKS_FILE = "my-disk-image.wks"

my-disk-image.wks:
part /boot --source bootimg-efi-initramfs
--sourceparams="loader=grub-efi,initrd=my-initramfs.cpio.gz" --ondisk
sda --label msdos --active --align 1024 --use-uuid
bootloader --ptable gpt --timeout=1

2) Or should I create a new recipe that builds the WIC and depends on
the initramfs?

Remember, I have no rootfs other than the (non-bundled) initramfs.
Depending on the answers, I will come up with the issues I see.


Re: How to reduce rootfs image size?

JH
 

Thanks Josef, Fabien and Rudolf, it's been great help to clarify it,
very appreciated.

On 11/28/19, Rudolf J Streif <rudolf.streif@...> wrote:
Hi JH,

The image root file system size is based on the actual content of the
root file system. Besides ROOTFS_SIZE there are other variables that
control how the root file system is sized:

IMAGE_ROOTFS_SIZE: Defines the size in kilobytes of the created root
filesystem image. The
build system uses this value as a request or recommendation. The final
root filesystem
image size may be larger depending on the actual space required. The
default value is
65536.

IMAGE_ROOTFS_ALIGNMENT: Defines the alignment of the root filesystem
image in
kilobytes. If the final size of the root filesystem image is not a
multiple of this value, it is
rounded up to the nearest multiple of it. The default value is 1.

IMAGE_ROOTFS_EXTRA_SPACE: Adds extra free space to the root filesystem
image. The
variable specifies the value in kilobytes. For example, to add an
additional 4 GB of space, set
the variable to IMAGE_ROOTFS_EXTRA_SPACE = "4194304". The default value
is 0.

IMAGE_OVERHEAD_FACTOR: This variable specifies a multiplicator for the
root filesystem
image. The factor is applied after the actual space required by the root
filesystem has been
determined. The default value is 1.3.


Here is some pseudo code on how these variables are used to determine
the final root file system size:

_get_rootfs_size():
ROOTFS_SIZE =`du -ks IMAGE_ROOTFS`
BASE_SIZE = ROOTFS_SIZE * IMAGE_OVERHEAD_FACTOR

if (BASE_SIZE < IMAGE_ROOTFS_SIZE):
IMG_SIZE = IMAGE_ROOTFS_SIZE + IMAGE_ROOTFS_EXTRA_SPACE
else:
IMG_SIZE = BASE_SIZE + IMAGE_ROOTFS_EXTRA_SPACE

IMG_SIZE = IMG_SIZE + IMAGE_ROOTFS_ALIGNMENT – 1
IMG_SIZE = IMG_SIZE % IMAGE_ROOTFS_ALIGNMENT

return IMG_SIZE


:rjs

On 11/27/19 3:12 AM, JH wrote:
Hi,

Does the Yocto rootfs image size is based on real contents included in
the image-rootfs.tar.gz?

When I build the image with very large size of applications and
libraries such as boost, I have my image-rootfs.tr.gz about 44 MB,
then I removed all large size of applications and libraries, I changed
IMAGE_ROOTFS_SIZE to a small size IMAGE_ROOTFS_SIZE = 20000, I thought
the image-rootfs.tar.gz should be reduced to a small size, but it is
still 43 MB I don't believe it is that big, which variable I should
use to reduce the image size?

Thank you.

Kind regards,

- jh

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47433):
https://lists.yoctoproject.org/g/yocto/message/47433
Mute This Topic: https://lists.yoctoproject.org/mt/62495609/3617932
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[rudolf.streif@...]
-=-=-=-=-=-=-=-=-=-=-=-
--
-----
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3386 x700


Re: Yocto Image Build for NXP i.MX8M

Laurent Gauthier
 

[ all: Let me share the replay I made in private to Ajit. ]

Hi Ajith,

Unfortunately because you do not provide much information about the
"some error" you are seeing there is not much that can be done right
away to support you.

Here is a useful article on how to ask technical questions.

* https://opensource.com/life/16/10/how-ask-technical-questions

And here is a relevant quote from it that should help you increase
your chances of getting an answer:

You should include a clear description of the issue you're facing or goal you're trying to achieve. Include as
much specific relevant information as you can:

* If the problem is reproducible, what are the exact steps to do so?
* If you're getting an error message or debugging information, make sure you include it verbatim.
* Have you made any recent changes?
* What Linux distribution and version are you using?
* Is the hardware you're using a factor?

The more relevant information you include, the more likely you'll receive a solution that actually works.

You should also include any research you've done and steps you've already taken
to try to solve the issue. This not only prevents receiving a solution you've already
tried, but shows that you've already put effort into solving the issue yourself.
Generic answer about your question based on the information you provided:

* NXP i.MX8M is supported in Yocto through NXP's own Yocto BSP (not
just base Yocto) and your question
is probably more likely to get an answer on NXP's community forums
at https://community.nxp.com/

Kind Regards, Laurent.
--
https://soccasys.com

On Thu, Nov 28, 2019 at 9:53 AM Josef Holzmayr
<holzmayr@...> wrote:

On Thu, Nov 28, 2019 at 02:02:29PM +0530, Aj Cit wrote:
I've followed the instruction from the yocto project:
https://www.yoctoproject.org/docs/3.0/brief-yoctoprojectqs/brief-yoctoprojectqs.html
This can not be exactly true, as this guide certainly does not include
anything related to the imx8. So you are either still building for qemu
(as it defaults to), or using seomthing additional that you're not
mentioning.



till the bitbake command. However, I'm getting the following error:
ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable the
checker (see sanity.conf).
Following is the list of potential problems / advisories:

Do not use Bitbake as root.
Here is your answer: do not run botbake as the root user :)

In a nutshell, I recommend watching at least the first couple of videos
here:
https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj

Greetz


On Thu, Nov 28, 2019 at 12:29 PM Aj Cit <aj.ci.01.239@...> wrote:

Hello,

I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s). I
am getting some error when I execute the bitmake command.

I'd appreciate if you could guide me with next steps. Any Guide or url
will be helpful.

Thanks
Ajith
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47444): https://lists.yoctoproject.org/g/yocto/message/47444
Mute This Topic: https://lists.yoctoproject.org/mt/63894854/3618269
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [holzmayr@...]
-=-=-=-=-=-=-=-=-=-=-=-

--
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47447): https://lists.yoctoproject.org/g/yocto/message/47447
Mute This Topic: https://lists.yoctoproject.org/mt/63894854/3618354
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [laurent.gauthier@...]
-=-=-=-=-=-=-=-=-=-=-=-


--
Laurent Gauthier
Phone: +33 630 483 429
http://soccasys.com


Re: Architecture of .wic approach; image of images

Josef Holzmayr <holzmayr@...>
 

On Thu, Nov 28, 2019 at 09:37:12AM +0100, Leon Woestenberg wrote:
Hello all,

What is the intended approach of building images using WIC?

Most image types (except .wic) build a (root or initial ram) filesystem
from *packages*, then create the respective archive or filesystem from it.

The .wic image type however, builds an image from *images* rather than
packages.
Thats *almost* correct. It builds an image from a *artifacts*.

It therefore seems incorrect we can just add IMAGE_FSTYPES += "wic",
because the corresponding .wks might depend on multiple other images than
just ${PN}.
If it does, then your dependency architecture is probably broken. You
have to understand that building an image might produce artifacts that
are not actually included in the rootfs: many systems expect the kernel
to be external to it, and even most do so for u-boot. Hence, the mindset
is as follows: the image recipe biulds everything that you need. It does
not care about the actual for those things shall be poured into.

Should we, or do we have a recipe example that builds only a .wic image,
based on one or more other existing images? (and thus not populate a
filesystem itself)
See above. The image recipe produces all the needed artififacts, that a
*seomthing* later in the pipeline needs. This *something* then takes
those artifacts and pours them into a binary form you can use. Its maybe
bad naming that the configuration of that binary output form is
IMAGE_FSTYPE, which suggests a relation to the image. But de factor,
mentally replace IMAGE_FSTYPE with BINARY_RESULT_FORMAT, and then it
should become clear that this is actually two seperate stages of the
build pipeline.

Greetz


Regards,

Leon.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47445): https://lists.yoctoproject.org/g/yocto/message/47445
Mute This Topic: https://lists.yoctoproject.org/mt/63986097/3618269
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [holzmayr@...]
-=-=-=-=-=-=-=-=-=-=-=-

--
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


Re: Yocto Image Build for NXP i.MX8M

Josef Holzmayr <holzmayr@...>
 

On Thu, Nov 28, 2019 at 02:02:29PM +0530, Aj Cit wrote:
I've followed the instruction from the yocto project:
https://www.yoctoproject.org/docs/3.0/brief-yoctoprojectqs/brief-yoctoprojectqs.html
This can not be exactly true, as this guide certainly does not include
anything related to the imx8. So you are either still building for qemu
(as it defaults to), or using seomthing additional that you're not
mentioning.



till the bitbake command. However, I'm getting the following error:
ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable the
checker (see sanity.conf).
Following is the list of potential problems / advisories:

Do not use Bitbake as root.
Here is your answer: do not run botbake as the root user :)

In a nutshell, I recommend watching at least the first couple of videos
here:
https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj

Greetz


On Thu, Nov 28, 2019 at 12:29 PM Aj Cit <aj.ci.01.239@...> wrote:

Hello,

I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s). I
am getting some error when I execute the bitmake command.

I'd appreciate if you could guide me with next steps. Any Guide or url
will be helpful.

Thanks
Ajith
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47444): https://lists.yoctoproject.org/g/yocto/message/47444
Mute This Topic: https://lists.yoctoproject.org/mt/63894854/3618269
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [holzmayr@...]
-=-=-=-=-=-=-=-=-=-=-=-

--
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


Re: Yocto Image Build for NXP i.MX8M

Maciej Pijanowski
 


On 28.11.2019 09:32, Aj Cit wrote:

I've followed the instruction from the yocto project:

till the bitbake command. However, I'm getting the following error:
ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Do not use Bitbake as root. 
Isn't this warning message straightforward?
What is your build environment?
Are you using root in fact?
 

On Thu, Nov 28, 2019 at 12:29 PM Aj Cit <aj.ci.01.239@...> wrote:
Hello,

I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s). I am getting some error when I execute the bitmake command.

I'd appreciate if you could guide me with next steps. Any Guide or url will be helpful.

Thanks
Ajith

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47444): https://lists.yoctoproject.org/g/yocto/message/47444
Mute This Topic: https://lists.yoctoproject.org/mt/63894854/3616795
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [maciej.pijanowski@...]
-=-=-=-=-=-=-=-=-=-=-=-
-- 
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com


Architecture of .wic approach; image of images

Leon Woestenberg
 

Hello all,

What is the intended approach of building images using WIC?

Most image types (except .wic) build a (root or initial ram) filesystem from *packages*, then create the respective archive or filesystem from it.

The .wic image type however, builds an image from *images* rather than packages.

It therefore seems incorrect we can just add IMAGE_FSTYPES += "wic", because the corresponding .wks might depend on multiple other images than just ${PN}.

Should we, or do we have a recipe example that builds only a .wic image, based on one or more other existing images? (and thus not populate a filesystem itself)

Regards,

Leon.


Re: Yocto Image Build for NXP i.MX8M

Aj Cit
 


I've followed the instruction from the yocto project:

till the bitbake command. However, I'm getting the following error:
ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Do not use Bitbake as root.  
 


On Thu, Nov 28, 2019 at 12:29 PM Aj Cit <aj.ci.01.239@...> wrote:
Hello,

I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s). I am getting some error when I execute the bitmake command.

I'd appreciate if you could guide me with next steps. Any Guide or url will be helpful.

Thanks
Ajith


Re: Yocto Image Build for NXP i.MX8M

Josef Holzmayr <holzmayr@...>
 

On Thu, Nov 28, 2019 at 12:29:14PM +0530, Aj Cit wrote:
Hello,

I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s). I am
getting some error when I execute the bitmake command.
Please name the layers and their versions in use, the MACHINE setting
that you are using, the bitbake command you are issuing and the error
message. The latter please verbatim, not only the two most prominent
words. Then somebody can have a look.

Greetz


I'd appreciate if you could guide me with next steps. Any Guide or url will
be helpful.

Thanks
Ajith
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47442): https://lists.yoctoproject.org/g/yocto/message/47442
Mute This Topic: https://lists.yoctoproject.org/mt/63894854/3618269
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [holzmayr@...]
-=-=-=-=-=-=-=-=-=-=-=-

--
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


Yocto Image Build for NXP i.MX8M

Aj Cit
 

Hello,

I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s). I am getting some error when I execute the bitmake command.

I'd appreciate if you could guide me with next steps. Any Guide or url will be helpful.

Thanks
Ajith


Re: QA notification for completed autobuilder build (yocto-3.0.1.rc3)

Sangeeta Jain
 

Hello All,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.0.1.rc3.
We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
3. BSP-Qemu

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. MPC8315e-rdb
7. Beaglebone

ETA for completion is next Tuesday, December 3.

Thanks & Regards,
Sangeeta Jain

-----Original Message-----
From: Poky Build User <pokybuild@...>
Sent: Thursday, 28 November, 2019 11:56 AM
To: yocto@...
Cc: otavio@...; yi.zhao@...; Sangal, Apoorv
<apoorv.sangal@...>; Yeoh, Ee Peng <ee.peng.yeoh@...>; Chan,
Aaron Chun Yew <aaron.chun.yew.chan@...>; Ang, Chin Huat
<chin.huat.ang@...>; richard.purdie@...;
akuster808@...; sjolley.yp.pm@...; Jain, Sangeeta
<sangeeta.jain@...>
Subject: QA notification for completed autobuilder build (yocto-3.0.1.rc3)


A build flagged for QA (yocto-3.0.1.rc3) was completed on the autobuilder and is
available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.0.1.rc3


Build hash information:

bitbake: 8569ccb5e9fbdeaaf96b78bd02a263b26de54059
meta-gplv2: 0f4eecc000f66d114ad258fa31aed66afa292166
meta-intel: dc1fcaa858e85273676f4363a645661b5f1fb6e5
meta-mingw: 756963cc28ebc163df7d7f4b4ee004c18d3d3260
oecore: 75a4cabf55e13e6714c0fdb229cd51b5184ddbef
poky: 12a4c177bb541b3187c7a54d5804f30c35f22d8c



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...


10321 - 10340 of 57780