On Fri, Jul 12, 2019 at 1:02 PM Srinivasan, Usha
wrote:
>
> I will start with the caveat: this is my first time trying to cross compile
> for a target running a yocto bitbaked image. So I am surely not doing the
> right thing.
>
>
>
> I have generated both a core-image-sato &
I will start with the caveat: this is my first time trying to cross compile for
a target running a yocto bitbaked image. So I am surely not doing the right
thing.
I have generated both a core-image-sato & core-image-sato-dev. I am developing
an application to run on my target machine. My
Hello All,
by building the image I encountered this issue during populating SDK
Any idea where and how to fix it?
Thanks.
ERROR: Error executing a python function in exec_python_func()
autogenerated:
The stack trace of python calls that resulted in this exception/failure was:
File:
Hello Max,
Remember me? Zoran Stojsavljevic, from very far in Past... From Y2017!
Could you, please, help Onur with this problem? I know that U R Subject
Matter Expert with iMX6 and Qt5, and probably U already met this problem
not too far in The Past...
Please, could you read carefully the
Following parsing error will occure while "selinux" not configured
in DISTRO_FEATURES:
ERROR: ParseError in /workspace/zhanglin/CGEL/CGEL6X.new2/CGEL/cge-
l6x_yocto/sources/meta-selinux/recipes-devtools/python/: not a Bit-
Bake file
to fix this, including a empty file: python_default.inc in
On Fri, 12 Jul 2019 at 15:38, Moritz Porst wrote:
> If I use the .wic image, APPEND is ignored. You need to write your own
> kickstart file for this and include --append option. This usually means
> copy what you need from existing files (check license compliance) and
> add what you need. See
Hey Jupiter,
you seem to confuse a few concepts, at least as far as I understand
Am 12.07.2019 um 14:53 schrieb JH:
Hi Moritz,
On 7/12/19, Moritz Porst wrote:
Hey
On 12.07.19 10:05, JH wrote:
BOOT_IMAGE=/bzImage root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet
Hi Moritz,
On 7/12/19, Moritz Porst wrote:
> Hey
>
> On 12.07.19 10:05, JH wrote:
>>> BOOT_IMAGE=/bzImage root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
>> break=premount quiet rootwait rootwait rootfstype=ext4
>> console=ttyS0,115200 console=tty0
>>
>> Which file did you add kernel boot
Hello Scott (Rifenbark),
Could you, please, document somewhere (YOCTO-Mega-Manual for example)
this topic (booting to YOCTO initramfs rescue shell), as we are
discussing it?
It would be very beneficial to YOCTO WWW audience, don't you agree?
Thank you,
Zoran
___
On Fri, Jul 12, 2019 at
Hey
On 12.07.19 10:05, JH wrote:
BOOT_IMAGE=/bzImage root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet rootwait rootwait rootfstype=ext4
console=ttyS0,115200 console=tty0
Which file did you add kernel boot command for bootargs, bootcmd, etc?
I use meta-freescale, but I
> BOOT_IMAGE=/bzImage root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet rootwait rootwait rootfstype=ext4
console=ttyS0,115200 console=tty0
Which file did you add kernel boot command for bootargs, bootcmd, etc?
I use meta-freescale, but I could not find BOOT_IMAGE is
Hi Moritz,
I could not find zImage-initramfs:
$ grep zImage tempfile
ARCH_DEFAULT_KERNELIMAGETYPE="bzImage"
KERNEL_IMAGETYPE="bzImage"
KERNEL_IMAGETYPES="bzImage"
QB_DEFAULT_KERNEL="bzImage"
$ grep zImage-initramfs tempfile
$ grep INITRAMFS_IMAGE_BUNDLE tempfile
# $INITRAMFS_IMAGE_BUNDLE
Forgot to CC Jupiter and the most important thing:
PACKAGE_INSTALL += "initramfs-module-debug" (To my understanding this
enables the rescue shell)
On 12.07.19 08:22, Moritz Porst wrote:
Hey,
The only thing I can add to what I already said is my
"core-image-minimal-initramfs.bbappend":
Hey,
The only thing I can add to what I already said is my
"core-image-minimal-initramfs.bbappend":
PACKAGE_INSTALL += "\
busybox \
base-files \
base-passwd \
bash \
14 matches
Mail list logo
