Re: [yocto] QA notification for completed autobuilder build (yocto-2.7.1.rc1)

[Jain, Sangeeta]

Hello All,



Intel and WR YP QA is planning for QA execution for YP build 2.7.rc1

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 Friday, 5 July.


Thanks & Regards,
Sangeeta Jain


 Forwarded Message 
Subject:

QA notification for completed autobuilder build (yocto-2.7.1.rc1)

Date:

Mon, 1 Jul 2019 03:08:44 +

From:

Poky Build User 


To:

yocto@yoctoproject.org

CC:

ota...@ossystems.com.br, 
yi.z...@windriver.com, 
apoorv.san...@intel.com, 
ee.peng.y...@intel.com, 
aaron.chun.yew.c...@intel.com, 
chin.huat@intel.com, 
richard.pur...@linuxfoundation.org, 
akuster...@gmail.com, 
sjolley.yp...@gmail.com, 
sangeeta.j...@intel.com




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


https://autobuilder.yocto.io/pub/releases/yocto-2.7.1.rc1


Build hash information:
bitbake: 34ed28a412af642a993642c14bd8b95d5ef22cd8
meta-gplv2: 460ba027fd79b99151f95c826446f3aead5d17ff
meta-intel: e84c763090f91196a5d234f62ee39bcf296c7f2e
meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
oecore: 886deb4d0919c7a81036ea14fb8fd0f1619dd3a3
poky: 38d5c8ea98cfa49825c473eba8984c12edf062be



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


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Allow choose of U-Boot config for machine

[JH]

Hi,

The imx6ullevk.conf defined sdcard for booting on imx6 EVK:

imx6ullevk.conf

UBOOT_CONFIG ??= "sd"
UBOOT_CONFIG[sd] = "mx6ull_14x14_evk_config,sdcard"
UBOOT_CONFIG[mfgtool] = "mx6ull_14x14_evk_config"

I need to change it for a customized board referenced from imx6 EVK
but booting from NAND, there are some blogs said it can be done to add
UBOOT_CONFIG=nand either in local.conf or command line. I tried it did
not work:

ERROR: Unable to start bitbake server (None)
--- Starting bitbake server pid 2673 at 2019-07-02 11:54:24.011086 ---
ERROR: local.conf:34: unparsed line: 'UBOOT_CONFIG=nand'

What should be a proper process to overwrite imx6ullevk.conf
UBOOT_CONFIG from sdcard to nand?

Thank you.

Kind regards,

- JH
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 282
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Can't boot to initramfs

[Moritz Porst]

Hello,
I think I found the issue. ( see below )

On 01.07.19 15:57, Zoran Stojsavljevic wrote:

Hello Moritz,

Too hot here, in Belgrade... Where I am resting for the Time being
(actually, this message given to my invisible spying security "angels"
on this list)...  :-) Projected +38C degrees today. Too hot for this
too old Siberian untouchable bobcat!

Luckily it's a rather cold day in germany, thanks that you still take
the time to answer !



I started from the core-image-minimal to have a small image and
extended it with the features I need, which is e.g. a graphical system.
The console=[...] part in the kernel command line is probably a
remnant but my image boots into the GUI. Is this a problem ?

Nope, it is not. If you need to do it correctly, you should use
bitbake -k core-image-sato build command (my best educated guess).
Then, I do not feel comfortable seeing in your kernel command line
serial interface, do you agree?

Yes that is true.

YOCTO maintainers, any additional
advices?


My bootloader is currently grub, the EFI is AM.

Nope. Ek. Wrong. Currently, your boot-loader is UEFI AMI. Your
OS (Linux probably, U name it) boot-loader is GRUB2. Let us keep it
contained, sane and sober.


Sorry but I can't find this info in the EFI.

Could you, please try the following command being root: dmesg | grep
MCU. or grep mcu, or grep CPUID or grep cpuid?? Please, post results
to this list (to me).

No luck unfortunately (used grep -i)


Could you, also, send to YOCTO list/me attached file:
/boot/microcode.cpio so I can somehow (?) inspect it? ;-)

I send it to you directly, so I don't spam the list with a large attachment.



2GB, single channel.

All Cool. E3825 by HW/silicon design could/does NOT support multiple
memory channels. ONLY single... But even YOCTO primes (INTEL ones from
this list) are not gonna tell this to you. Not 'cause they are nasty.
They are NOT aware/they are ignorant (with the purpose)! ;-))


No, the boot does not stop. Even if I do issue "break=premount" I
end up in my graphical interface with the rootfs mounted. This is the
last message in the log: EXT4-fs (sdb2): re-mounted. Opts: (null)
The rootfs partition is always 2, so either /dev/sda2 or /dev/sdb2
(when booting from stick)

Yes, from https://pastebin.com/ya7iCtq7, so it is remounted rw, not
read only. So, it seems that you have passed dracut phase. and mounted
SD or flash rootfs. So, initramfs is NOT your true problem, is it???

The thing is that the boot works but I want an initramfs that can be
used for updating (in case the rootfs is broken). However I need to be
able to intercept the boot process there because otherwise I can't
deploy an update mechanism, that's what I was trying.


Zoran
___



No, the boot does not stop. Even if I do issue "break=premount" I end up
in my graphical interface with the rootfs mounted. This is  the last message
in the log: EXT4-fs (sdb2): re-mounted. Opts: (null) The rootfs partition is
always 2, so either /dev/sda2 or /dev/sdb2 (when booting from stick)




So for the issue...
I expected yocto to put the bundled bzImage onto my rootfs. This was not
the case. My image directory contains 2x bzImage, one bundled and one
unbundled. Apparently yocto puts the >unhttps://wiki.debian.org/InitramfsDebug
I am aware that yocto is no debian but I expected that kernel parameters
(like 'break') would be independent of the distribution.

Lastly I do not really need the interactive shell, it is enough if I can
deploy a custom init script in the initramfs. Still I think that getting
an initramfs shell should be as simple as stating the name of the
initramfs image and setting the "INITRAMFS_DO_BUNDLE" variable.

Best regards
Moritz



On Mon, Jul 1, 2019 at 11:20 AM Moritz Porst  wrote:

Hello Zoran,
thanks for your answer

On 28.06.19 14:26, Zoran Stojsavljevic wrote:


INITRAMFS_IMAGE = "core-image-minimal-initramfs"
INITRAMFS_IMAGE_BUNDLE = "1"

...

You can find the /var/log/dmesg here: https://pastebin.com/ya7iCtq7I

Some hints...

[1] Kernel command line: BOOT_IMAGE=/bzImage 
root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet rootwait rootwait rootfstype=ext4 console=ttyS0,115200 
console=tty0

input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
fbcon: inteldrmfb (fb0) is primary device
Console: switching to colour frame buffer device 128x48
i915 :00:02.0: fb0: inteldrmfb frame buffer device
snd_hda_intel :00:1b.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])

Hm... You are using console and serial, but full i915 GFX kernel driver is 
still included in the build???

I started from the core-image-minimal to have a small image and extended it 
with the features I need, which is e.g. a graphical system. The console=[...] 
part in the kernel command line is probably a remnant but my image boots into 
the GUI. Is this a problem ?


[2] efi: EFI v2.31 by American Megatrends

Using AMI BIOS as boot 

Re: [yocto] Can't boot to initramfs

[Zoran Stojsavljevic]

Hello Moritz,

Too hot here, in Belgrade... Where I am resting for the Time being
(actually, this message given to my invisible spying security "angels"
on this list)...  :-) Projected +38C degrees today. Too hot for this
too old Siberian untouchable bobcat!

> I started from the core-image-minimal to have a small image and
> extended it with the features I need, which is e.g. a graphical system.
> The console=[...] part in the kernel command line is probably a
> remnant but my image boots into the GUI. Is this a problem ?

Nope, it is not. If you need to do it correctly, you should use
bitbake -k core-image-sato build command (my best educated guess).
Then, I do not feel comfortable seeing in your kernel command line
serial interface, do you agree? YOCTO maintainers, any additional
advices?

> My bootloader is currently grub, the EFI is AM.

Nope. Ek. Wrong. Currently, your boot-loader is UEFI AMI. Your
OS (Linux probably, U name it) boot-loader is GRUB2. Let us keep it
contained, sane and sober.

> Sorry but I can't find this info in the EFI.

Could you, please try the following command being root: dmesg | grep
MCU. or grep mcu, or grep CPUID or grep cpuid?? Please, post results
to this list (to me).

Could you, also, send to YOCTO list/me attached file:
/boot/microcode.cpio so I can somehow (?) inspect it? ;-)

> 2GB, single channel.

All Cool. E3825 by HW/silicon design could/does NOT support multiple
memory channels. ONLY single... But even YOCTO primes (INTEL ones from
this list) are not gonna tell this to you. Not 'cause they are nasty.
They are NOT aware/they are ignorant (with the purpose)! ;-))

> No, the boot does not stop. Even if I do issue "break=premount" I
> end up in my graphical interface with the rootfs mounted. This is the
> last message in the log: EXT4-fs (sdb2): re-mounted. Opts: (null)
> The rootfs partition is always 2, so either /dev/sda2 or /dev/sdb2
> (when booting from stick)

Yes, from https://pastebin.com/ya7iCtq7, so it is remounted rw, not
read only. So, it seems that you have passed dracut phase. and mounted
SD or flash rootfs. So, initramfs is NOT your true problem, is it???

Zoran
___


> No, the boot does not stop. Even if I do issue "break=premount" I end up
> in my graphical interface with the rootfs mounted. This is  the last message
> in the log: EXT4-fs (sdb2): re-mounted. Opts: (null) The rootfs partition is
> always 2, so either /dev/sda2 or /dev/sdb2 (when booting from stick)








On Mon, Jul 1, 2019 at 11:20 AM Moritz Porst  wrote:
>
> Hello Zoran,
> thanks for your answer
>
> On 28.06.19 14:26, Zoran Stojsavljevic wrote:
>
> > INITRAMFS_IMAGE = "core-image-minimal-initramfs"
> > INITRAMFS_IMAGE_BUNDLE = "1"
> ...
> > You can find the /var/log/dmesg here: https://pastebin.com/ya7iCtq7I
>
> Some hints...
>
> [1] Kernel command line: BOOT_IMAGE=/bzImage 
> root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
> break=premount quiet rootwait rootwait rootfstype=ext4 console=ttyS0,115200 
> console=tty0
>
> input: Video Bus as 
> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
> fbcon: inteldrmfb (fb0) is primary device
> Console: switching to colour frame buffer device 128x48
> i915 :00:02.0: fb0: inteldrmfb frame buffer device
> snd_hda_intel :00:1b.0: bound :00:02.0 (ops 
> i915_audio_component_bind_ops [i915])
>
> Hm... You are using console and serial, but full i915 GFX kernel driver 
> is still included in the build???
>
> I started from the core-image-minimal to have a small image and extended it 
> with the features I need, which is e.g. a graphical system. The console=[...] 
> part in the kernel command line is probably a remnant but my image boots into 
> the GUI. Is this a problem ?
>
>
> [2] efi: EFI v2.31 by American Megatrends
>
> Using AMI BIOS as boot loader FW... OK?! Am I correct?
>
> My bootloader is currently grub, the EFI is AM.
>
>
> [3] smpboot: CPU0: Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz (family: 0x6, 
> model: 0x37, stepping: 0x9)
>
> This is CPUID ID 0x30679, which uses MCU... Which MicroCodeUnit? M0130679xxx 
> (info from AMI BIOS)?
>
> Sorry but I can't find this info in the EFI
>
>
> [4] Using INTEL ATOM BYT E3825 dual core (sans Hyper-threading), implies that 
> you are using
> 4GB (e820 messages) as single channel (one memory module DDR3 as 4GB)! Am I 
> correct (important)?
>
> 2GB, single channel.
>
>
> [5] Dracut phase?!
> > To my understanding the initramfs should be embedded in /boot/bzImage.
> > However since I use an intel platform I also have a /boot/microcode.cpio
> > which gets loaded via "initrd /microcode.cpio". Removing this line in
> > grub does not enable me to get an initramfs prompt either (again, using
> > break as option).
>
> You are obviously stopping in boot phase called dracut. Please, try to mount 
> by hand
> /dev/sda(whatever)... You should use fdisk -l command, or do ls -al /dev | 
> grep sda to
> dig out which partition you need to mount to /tmp dir to see 

Re: [yocto] Getting a package PV from another

[Mike Looijmans]

The version of your OE layer is all the version that you'll ever (technically) 
need. That version (usually a git hash) dictates all other versions.

When asked for version numbers of included packages, I always just dump the 
manifest file into their lap.

You can also ask and report the version numbers at runtime (e.g. using opkg or 
dpkg). That also prevents lying to your users :)

On 01-07-19 11:28, Gabriele Zampieri wrote:
> Up, with more details:
> 
> I have a top recipe that depends on *my-image:do_build*. I'd like to retrieve 
> the PV of a couple of packages (from that top recipe) that are used to mark 
> our custom software. Any suggestions?
> 
> Gabriele
> 
> Il giorno ven 28 giu 2019 alle ore 11:25 Gabriele Zampieri 
> mailto:gabbla.mal...@gmail.com>> ha scritto:
> 
> Hi all,
> 
> is there a way to get a specific package version from another?
> 
> Best regards,
> Gabriele
> 
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Syntax for zero-padding a number in a recipe?

[Aaron Biver]

 [Sending again because I initially replied to Claudius only, and not
mailing list]

I found using back-ticks with printf also works in a recipe:

NUMBER = "1"
NUMBER_PADDED="FOO_`printf "02d" ${NUMBER}`_MOARFOO"

On Fri, Jun 28, 2019 at 4:48 PM Claudius Heine  wrote:

> Hi,
>
> Quoting Aaron Biver (2019-06-28 18:44:40)
> > Is there such a thing as zero padding a number in a recipe (or vice
> versa?
> > I'd be just as happy starting with a zero-padded number, and converting
> it
> > to non-zero-padded.
>
> In bitbake you could do this with inline python:
>
> NUMBER = "1"
> NUMBER_PADDED = "${@"{:02d}".format(d.getVar("NUMBER", True))}"
> NUMBER_PADDED2 = "0012"
> NUMBER2 = "${@str(int(d.getVar("NUMBER_PADDED2", True)))}"
>
> I have not tested this and it could possible be done more elegant, but
> it should work.
>
> regards,
> Claudius
>
> > The crux of the dilemma is that I must have zero-padding for file-naming,
> > but I CAN'T have zero padding in these numbers when I pass them to the C
> > code (or the C code treats them as octal).
> >
> > I'd like to start with:
> > VERSION_MAJOR="1"
> > VERSION_MINOR="19"
> >
> > And turn this into "01" and "19" for purposes of naming the output file
> > from the recipe.
> >
> > I've tried the bash-style printf -v, but the recipe kicks the printf
> lines
> > out with a parse error.
> >
> > VERSION_MAJOR="01"
> > VERSION_MINOR="19"
> >
> > VERSION_MAJOR_STR=""
> > VERSION_MINOR_STR=""
> >
> > printf -v VERSION_MAJOR_STR "%02d" VERSION_MAJOR
> > printf -v VERSION_MINOR_STR "%02d" VERSION_MINOR
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
> --
> DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: c...@denx.de
>
>PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
>  Keyserver: hkp://pool.sks-keyservers.net
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Can't boot to initramfs

[Moritz Porst]

Hey,
So I have proceeded a tiny bit.
What I did was to copy the core-image-minimal-initramfs.cpio.gz to my
/boot partition and boot using (EFI grub):

linux /bzimage
initrd /initramfs.cpio.gz

This way the boot process starts and at some point it says "can't find
rootfs.img, dropping to a shell". It doesn't drop to a shell though...
(busybox is included)
Booting without the initrd (or with initrd /microcode.cpio) results in a
kernel panic. This leads me to the suspicion that meta-intel overwrites
my initramfs (since microcode.cpio is present in boot)
Further more think I shouldn't even be required to set initrd for boot
since it should be embedded into the kernel ?
(INITRAMFS_IMAGE_BUNDLE="1") I got the relevant variables from bitbake
-e here, maybe someone more experienced can spot an error ?

# $INITRAMFS_FSTYPES [2 operations]
#   set /opt/thudPoky/meta/conf/documentation.conf:228
# [doc] "Defines the format for the output image of an initial RAM
disk (initramfs), which is used during boot."
#   set? /opt/thudPoky/meta/conf/bitbake.conf:770
# "cpio.gz"
# pre-expansion value:
#   "cpio.gz"
INITRAMFS_FSTYPES="cpio.gz"
#
# $INITRAMFS_IMAGE
#   set /opt/thudPoky/build/conf/local.conf:257
# "core-image-minimal-initramfs"
INITRAMFS_IMAGE="core-image-minimal-initramfs"
#
# $INITRAMFS_IMAGE_BUNDLE
#   set /opt/thudPoky/build/conf/local.conf:258
# "1"
INITRAMFS_IMAGE_BUNDLE="1"
#
# $INITRAMFS_MAXSIZE [2 operations]
#   set /opt/thudPoky/meta-ccns5/conf/machine/ccns5.conf:34
# "20"
#   set /opt/thudPoky/meta/conf/bitbake.conf:774
# [_defaultval] "131072"
# pre-expansion value:
#   "20"
INITRAMFS_MAXSIZE="20"
#
# $INITRD
#   set /opt/thudPoky/meta/conf/documentation.conf:229
# [doc] "Indicates a list of filesystem images to concatenate and
use as an initial RAM disk (initrd)."
#
# $INITRD_IMAGE_LIVE
#   set? /opt/thudPoky/meta/classes/image-live.bbclass:39
# "${MLPREFIX}core-image-minimal-initramfs"
INITRD_IMAGE_LIVE="core-image-minimal-initramfs"
#
# $INITRD_LIVE [2 operations]
#   _prepend /opt/thudPoky/meta-intel/conf/machine/include/meta-intel.inc:23
# "${@bb.utils.contains('MACHINE_FEATURES', 'intel-ucode',
'${DEPLOY_DIR_IMAGE}/microcode.cpio ', '', d)}"
#   set? /opt/thudPoky/meta/classes/image-live.bbclass:40
# "${DEPLOY_DIR_IMAGE}/${INITRD_IMAGE_LIVE}-${MACHINE}.cpio.gz"
# pre-expansion value:
#   "${@bb.utils.contains('MACHINE_FEATURES', 'intel-ucode',
'${DEPLOY_DIR_IMAGE}/microcode.cpio ', '',
d)}${DEPLOY_DIR_IMAGE}/${INITRD_IMAGE_LIVE}-${MACHINE}.cpio.gz"
INITRD_LIVE="/opt/thudPoky/build/tmp/deploy/images/ccns5/microcode.cpio
/opt/thudPoky/build/tmp/deploy/images/ccns5/core-image-minimal-initramfs-ccns5.cpio.gz"

The last line seems strange to me because 2 different images are set.
.cpio on it's own is not included in INITRAMFS_FSTYPES and I can not
find any documentation on the variable INITRD_LIVE.

Best regards
Moritz

On 01.07.19 11:19, Moritz Porst wrote:


Hello Zoran,
thanks for your answer

On 28.06.19 14:26, Zoran Stojsavljevic wrote:

> INITRAMFS_IMAGE = /*"core-image-minimal-initramfs"*/
> INITRAMFS_IMAGE_BUNDLE = "1"
...
> You can find the /var/log/dmesg here: https://pastebin.com/ya7iCtq7I

Some hints...

[1] Kernel command line: BOOT_IMAGE=/bzImage
root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet rootwait rootwait rootfstype=ext4
/*console=ttyS0,115200 console=tty0*/
/*
*/
input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
fbcon: inteldrmfb (fb0) is primary device
Console: switching to colour frame buffer device 128x48
/*i915 :00:02.0: fb0: inteldrmfb frame buffer device*/
snd_hda_intel :00:1b.0: bound :00:02.0 (ops
i915_audio_component_bind_ops [i915])

Hm... You are using console and serial, but full i915 GFX kernel
driver is still included in the build???

I started from the core-image-minimal to have a small image and
extended it with the features I need, which is e.g. a graphical
system. The console=[...] part in the kernel command line is probably
a remnant but my image boots into the GUI. Is this a problem ?

/*
*/
[2] efi: EFI v2.31 by American Megatrends

Using AMI BIOS as boot loader FW... OK?! Am I correct?

My bootloader is currently grub, the EFI is AM.


[3] smpboot: CPU0: Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz (family:
0x6, model: 0x37, stepping: 0x9)

This is CPUID ID 0x30679, which uses MCU... Which MicroCodeUnit?
M0130679xxx (info from AMI BIOS)?

Sorry but I can't find this info in the EFI


[4] Using INTEL ATOM BYT E3825 dual core (sans Hyper-threading),
implies that you are using
4GB (e820 messages) as single channel (one memory module DDR3 as
4GB)! Am I correct (important)?

2GB, single channel.


[5] Dracut phase?!
> To my understanding the initramfs should be embedded in /boot/bzImage.
> However since I use an intel platform I also have a
/boot/microcode.cpio
> which gets loaded via "initrd /microcode.cpio". Removing this line in
> grub 

Re: [yocto] Yocto stucks when building!

[Maciej Pijanowski]

On 01.07.2019 09:39, Onur Eser wrote:
> Hello,
Hi
> I am trying to build a yocto for i.MX6, with a QT5 layer, everything
> is okay, but it freezes on 2666th task! When 4 tasks are running at
> the same time in normal, when it comes to 2666th, it is only one task
> and takes forever! (I made it wait for one night)
>
> Build Configuration:
> BB_VERSION        = "1.26.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-16.04"
> TARGET_SYS        = "i586-poky-linux"
> MACHINE           = "qemux86"
First of all, it seems you are not building for the iMX6, but for the
qemux86.
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.8.2"
> TUNE_FEATURES     = "m32 i586"
> TARGET_FPU        = ""
> meta              = "fido:87631919819b6f85f23f57689cd1065c64d7fb03"
> meta-qt5          = "fido:90919b9d86988e7da01fa2c0a07246b5b5600a5d"
> meta-fsl-arm      = "fido:c9f259a4bf8472dfa3ff75f1c3fcbe5e0ded7aaf"
> meta-solidrun-arm-imx6 = "fido:3e496c0895b0abf8d2aaca2c622246c1f9f3ed75"
> meta-yocto        
> meta-yocto-bsp    = "fido:87631919819b6f85f23f57689cd1065c64d7fb03"
fido release is *really* old. Where did you get the documentation to
start this build from?
I think you might have difficult time getting support with such old release.
>
> NOTE: Preparing RunQueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> Currently 1 running tasks (2666 of 5960):
> 0: attr-native-2.4.47-r0 do_compile (pid 3485)
>
> How to solve this?
> Thanks,
> Onur
>
-- 
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Getting a package PV from another

[Gabriele Zampieri]

Up, with more details:

I have a top recipe that depends on *my-image:do_build*. I'd like to
retrieve the PV of a couple of packages (from that top recipe) that are
used to mark our custom software. Any suggestions?

Gabriele

Il giorno ven 28 giu 2019 alle ore 11:25 Gabriele Zampieri <
gabbla.mal...@gmail.com> ha scritto:

> Hi all,
>
> is there a way to get a specific package version from another?
>
> Best regards,
> Gabriele
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Can't boot to initramfs

[Moritz Porst]

Hello Zoran,
thanks for your answer

On 28.06.19 14:26, Zoran Stojsavljevic wrote:

> INITRAMFS_IMAGE = /*"core-image-minimal-initramfs"*/
> INITRAMFS_IMAGE_BUNDLE = "1"
...
> You can find the /var/log/dmesg here: https://pastebin.com/ya7iCtq7I

Some hints...

[1] Kernel command line: BOOT_IMAGE=/bzImage
root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet rootwait rootwait rootfstype=ext4
/*console=ttyS0,115200 console=tty0*/
/*
*/
input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
fbcon: inteldrmfb (fb0) is primary device
Console: switching to colour frame buffer device 128x48
/*i915 :00:02.0: fb0: inteldrmfb frame buffer device*/
snd_hda_intel :00:1b.0: bound :00:02.0 (ops
i915_audio_component_bind_ops [i915])

Hm... You are using console and serial, but full i915 GFX kernel
driver is still included in the build???

I started from the core-image-minimal to have a small image and extended
it with the features I need, which is e.g. a graphical system. The
console=[...] part in the kernel command line is probably a remnant but
my image boots into the GUI. Is this a problem ?

/*
*/
[2] efi: EFI v2.31 by American Megatrends

Using AMI BIOS as boot loader FW... OK?! Am I correct?

My bootloader is currently grub, the EFI is AM.


[3] smpboot: CPU0: Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz (family:
0x6, model: 0x37, stepping: 0x9)

This is CPUID ID 0x30679, which uses MCU... Which MicroCodeUnit?
M0130679xxx (info from AMI BIOS)?

Sorry but I can't find this info in the EFI


[4] Using INTEL ATOM BYT E3825 dual core (sans Hyper-threading),
implies that you are using
4GB (e820 messages) as single channel (one memory module DDR3 as 4GB)!
Am I correct (important)?

2GB, single channel.


[5] Dracut phase?!
> To my understanding the initramfs should be embedded in /boot/bzImage.
> However since I use an intel platform I also have a /boot/microcode.cpio
> which gets loaded via "initrd /microcode.cpio". Removing this line in
> grub does not enable me to get an initramfs prompt either (again, using
> break as option).

You are obviously stopping in boot phase called dracut. Please, try to
mount by hand
/dev/sda(whatever)... You should use fdisk -l command, or do ls -al
/dev | grep sda to
dig out which partition you need to mount to /tmp dir to see
rootfstype=ext4 (HDD/SSD)

No, the boot does not stop. Even if I do issue "break=premount" I end up
in my graphical interface with the rootfs mounted. This is the last
message in the log:
EXT4-fs (sdb2): re-mounted. Opts: (null)
The rootfs partition is always 2, so either /dev/sda2 or /dev/sdb2 (when
booting from stick)

___

Just thinking loud... .. .

Hope this helps (has very little to do with YOCTO build system, BTW) . ;-)

Zoran
___


On Fri, Jun 28, 2019 at 11:22 AM Moritz Porst mailto:moritz.po...@gmx.de>> wrote:

Hello,
I currently try to deploy a single rootfs update mechanism for my
embedded device. I can't boot to initramfs using either "break" or
"break=premount" (without quotes...). I tried this in systemd-boot and
grub-efi (always efi boot) but the boot process just continues
normally.
If I insert at the same point e.g. "quiet" this argument is
recognised.
I boot the .wic image with a separate boot partition from a USB stick.
in local.conf I have set:
INITRAMFS_IMAGE = "core-image-minimal-initramfs"
INITRAMFS_IMAGE_BUNDLE = "1"

In order to reduce complexity I now use the standard
core-image-minimal-initramfs without .bbappend. I can confirm (from
seeing the task) that bitbake bundled the kernel with the initramfs.

You can find the /var/log/dmesg here: https://pastebin.com/ya7iCtq7

To my understanding the initramfs should be embedded in /boot/bzImage.
However since I use an intel platform I also have a
/boot/microcode.cpio
which gets loaded via "initrd /microcode.cpio". Removing this line in
grub does not enable me to get an initramfs prompt either (again,
using
break as option).

Did I forget some configuration or do I have to put the break
statement
at a very specific position within the "linux ..." boot command ?
Do you
know which bitbake variables to check ? (both set in local.conf do not
get overwritten, already checked this). I got the thud branch checked
out in all my meta-layers except for meta-qt which is currently on
master branch.

Help is much appreciated !

Best regards
Moritz

--
___
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto stucks when building!

[Burton, Ross]

First, Fido/1.8 is very old: released in April 2015 and is now out of
support, has no security fixes, etc.  So I'd first suggest upgrading
to a supported release.

If you can't, then the easiest thing to do would be to look at the
log.do_compile for that recipe in your build directory, or use ps in
'forest' mode to see what process is hanging and figure out why that
is.

Ross

On Mon, 1 Jul 2019 at 08:40, Onur Eser  wrote:
>
> Hello,
> I am trying to build a yocto for i.MX6, with a QT5 layer, everything is okay, 
> but it freezes on 2666th task! When 4 tasks are running at the same time in 
> normal, when it comes to 2666th, it is only one task and takes forever! (I 
> made it wait for one night)
>
> Build Configuration:
> BB_VERSION= "1.26.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-16.04"
> TARGET_SYS= "i586-poky-linux"
> MACHINE   = "qemux86"
> DISTRO= "poky"
> DISTRO_VERSION= "1.8.2"
> TUNE_FEATURES = "m32 i586"
> TARGET_FPU= ""
> meta  = "fido:87631919819b6f85f23f57689cd1065c64d7fb03"
> meta-qt5  = "fido:90919b9d86988e7da01fa2c0a07246b5b5600a5d"
> meta-fsl-arm  = "fido:c9f259a4bf8472dfa3ff75f1c3fcbe5e0ded7aaf"
> meta-solidrun-arm-imx6 = "fido:3e496c0895b0abf8d2aaca2c622246c1f9f3ed75"
> meta-yocto
> meta-yocto-bsp= "fido:87631919819b6f85f23f57689cd1065c64d7fb03"
>
> NOTE: Preparing RunQueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> Currently 1 running tasks (2666 of 5960):
> 0: attr-native-2.4.47-r0 do_compile (pid 3485)
>
> How to solve this?
> Thanks,
> Onur
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto stucks when building!

[Onur Eser]

Hello,
I am trying to build a yocto for i.MX6, with a QT5 layer, everything is
okay, but it freezes on 2666th task! When 4 tasks are running at the same
time in normal, when it comes to 2666th, it is only one task and takes
forever! (I made it wait for one night)

Build Configuration:
BB_VERSION= "1.26.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-16.04"
TARGET_SYS= "i586-poky-linux"
MACHINE   = "qemux86"
DISTRO= "poky"
DISTRO_VERSION= "1.8.2"
TUNE_FEATURES = "m32 i586"
TARGET_FPU= ""
meta  = "fido:87631919819b6f85f23f57689cd1065c64d7fb03"
meta-qt5  = "fido:90919b9d86988e7da01fa2c0a07246b5b5600a5d"
meta-fsl-arm  = "fido:c9f259a4bf8472dfa3ff75f1c3fcbe5e0ded7aaf"
meta-solidrun-arm-imx6 = "fido:3e496c0895b0abf8d2aaca2c622246c1f9f3ed75"
meta-yocto
meta-yocto-bsp= "fido:87631919819b6f85f23f57689cd1065c64d7fb03"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
Currently 1 running tasks (2666 of 5960):
0: attr-native-2.4.47-r0 do_compile (pid 3485)

How to solve this?
Thanks,
Onur
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto