Re: [yocto] PXE booting ISO image fails with message "Waiting for removable media..."
Hi Raymond, > I'd recently gone through similar issue that you're experiencing. The > "Waiting for Removable Media" hang had been there for at least 7-8 years. A > workaround was put in around 2013. See here: > https://patchwork.openembedded.org/patch/42291/ > > Add "debugshell=30" (30 is in second, for timeout, or any other reasonable > value that you like) to the append > statement in your pxelinux.cfg/default file. Then you'd timeout when you > "normally" hangs, break into a shell, > where you could initiate udhcpc to configure networking, after which you > could transfer your bootable image onto > your RAM, and write out onto your HDD/SSD. Unfortunately, we cannot use this trick because the MB which boots using PXE is not accessible and we want to use PXE booting for every boot... > It seems this kernel boot option of debugshell isn't documented officially in > kernel-parameters.txt file. > You could also look for init-live.sh on your yocto tree, and look for > "Waiting for Removable Media", and see the > surrounding code to get a fell how this debugshell thing works. I think this is what we will have to do .. I read the description of the internals of the initrd provided by Archlinux. The main difference is that Yocto initrd searches for the final rootfs on physical device (/dev/sdX) whereas the Archlinux initrd identifies (using LABEL) the support it was launched from and then searches on this support for the final rootfs. I guess this approach would unify all booting: from USB, CD-ROM and PXE.. But at the moment, I don't know how to reproduce the archlinux initrd works with Yocto... If only a guru of Yocto could help ... Vincent Date: Thu, 3 May 2018 14:27:46 + From: Vincent Daanen <vincent.daa...@orthotaxy.com<mailto:vincent.daa...@orthotaxy.com>> To: "yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>" <yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>> Subject: [yocto] PXE booting ISO image fails with message "Waiting for removable media..." Message-ID: <vi1p192mb01430b16a66d217cb44829098d...@vi1p192mb0143.eurp192.prod.outlook.com<mailto:vi1p192mb01430b16a66d217cb44829098d...@vi1p192mb0143.eurp192.prod.outlook.com>> Content-Type: text/plain; charset="utf-8" Hi, We want to deploy image created with Yocto (Rocko) via PXE. The target board is a Intel-based SBC (AAEON GENE BT05). At first, we tried with a ISO from Archlinux and the target-board successfully booted. Then we create a ISO using Yocto but boot hangs with a message ?Waiting for removable media ...?. Googling this message points me to this post: http://thread.gmane.org/gmane.linux.embedded.yocto.general/20611 which relates exactly the same problem, explain why the issue raises, gives an indication to how to fix .. and that?s all ? So at this point, we know that the problem comes from the /recipes-core/initrdscripts/files/init-live.sh file. It seems searching for an /dev/sdx should be protected by a timeout set by default to 30 secs but during our trials, no timeout seems to exist. What we do not understand, is how to highlight the differences between the Yocto-based and the Archlinux ISO files so that we can ?unblock? the boot using the Yocto-based ISO file. Is the someone here how could help? Thanks Vincent -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] PXE booting ISO image fails with message "Waiting for removable media..."
Hi, We want to deploy image created with Yocto (Rocko) via PXE. The target board is a Intel-based SBC (AAEON GENE BT05). At first, we tried with a ISO from Archlinux and the target-board successfully booted. Then we create a ISO using Yocto but boot hangs with a message “Waiting for removable media ...”. Googling this message points me to this post: http://thread.gmane.org/gmane.linux.embedded.yocto.general/20611 which relates exactly the same problem, explain why the issue raises, gives an indication to how to fix .. and that’s all ☹ So at this point, we know that the problem comes from the /recipes-core/initrdscripts/files/init-live.sh file. It seems searching for an /dev/sdx should be protected by a timeout set by default to 30 secs but during our trials, no timeout seems to exist. What we do not understand, is how to highlight the differences between the Yocto-based and the Archlinux ISO files so that we can “unblock” the boot using the Yocto-based ISO file. Is the someone here how could help? Thanks Vincent -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Need Help for meta-qt5
Hi, Sorry for the late reply, I have to work on other topics.. I found that building qtbase-native would meet my needs but I cannot figure out how to build it 'alone' ... if it is possible I added the file myMeta/recipes-qt/qt5/ qtbase-native_%.bbappend but bitbake still build qtbase... Any idea ? Thanks Vince -Message d'origine- De : Zoran Stojsavljevic <zoran.stojsavlje...@gmail.com> Envoyé : jeudi 19 avril 2018 08:00 À : Vincent Daanen <vincent.daa...@orthotaxy.com> Cc : yocto@yoctoproject.org Objet : Re: [yocto] Need Help for meta-qt5 http://developer.toradex.com/knowledge-base/how-to-set-up-qt-creator-to-cross-compile-for-embedded-linux#contents http://developer.toradex.com/knowledge-base/board-support-package/openembedded-(core)#Adding_the_Qt5_Layer Hope this helps, Zoran ___ On Wed, Apr 18, 2018 at 6:24 PM, Vincent Daanen <vincent.daa...@orthotaxy.com> wrote: > Hi, > > > > I have to add Qt5 QtCore libs to my image. I know I must use meta-qt5 > but as I’m not familiar with qt configuration, I simply do not know how to > start ! > > So can someone help me to configure meta-qt5 to simply build and add > QtCore to my image ? > > Thank you > > > > Vincent > > > > > > > -- > ___ > 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] Need Help for meta-qt5
Hi, I have to add Qt5 QtCore libs to my image. I know I must use meta-qt5 but as I'm not familiar with qt configuration, I simply do not know how to start ! So can someone help me to configure meta-qt5 to simply build and add QtCore to my image ? Thank you Vincent -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Adding support for GPIO chipset, Am I doing it right ?
Hi, I'm using poky Rocko. I'm building a linux-rt based system (I'm using bitbake image-core-rt). The GPIO chip (Fintek F81866d) is not supported by the kernel we selected (4.4). I downloaded the patch which adds support of Fintek F81866d to kernel (from https://patchwork.ozlabs.org/patch/566380/) and add the patch to my kernel linux recipes (via SRC_URI +=) When building the image, the kernel is being recompiled but the patch is not applied (I still get an error message saying that the chip is not supported when I try to modprobe the module). Is this way of adding support of the Fintek F81866d to the kernel is the right way ? How can I check that the patch is applied ? Thanks Vincent -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig file (or fragment files) not used
Hi > On 03/29/18 16:12 PM, Bruce Ashfield wrote: > [cut] > Do you have all of the CAN* Kconfig dependencies in your defconfig ? No only the ones I need > If you don't, the kernel config subsystem will turn them off. > > Also note that a 'defconfig' translates to a merge config run (yes, even with > just a defconfig) of 'allnoconfig', so that can also be turning off > dependencies if they were only valid via their default and were not > explicitly specified. > > You can set KCONFIG_MODE="alldefconfig" in a linux-yocto bbappend to change > what mode merge-config uses. I tried this but got the same result ☹! Do you think I have to set all the "CAN*" dependencies? Vincent -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig file (or fragment files) not used
Hi,
What’s the difference between fragment and patch ?
I can easily make a patch but how do I make sure the patch will be applied to
the .config file ?
Thanks for your help
Vincent
De : Prakash Ks <prakashpk...@gmail.com>
Envoyé : jeudi 29 mars 2018 11:46
À : Khem Raj <raj.k...@gmail.com>
Cc : Vincent Daanen <vincent.daa...@orthotaxy.com>; yocto@yoctoproject.org
Objet : Re: [yocto] defconfig file (or fragment files) not used
Hi Vincent,
Its better to create patch and apply from platform specific kernel recipes.
if you need more info let me know.
Thanks!
Prakash
On Thu, Mar 29, 2018 at 1:55 PM, Khem Raj
<raj.k...@gmail.com<mailto:raj.k...@gmail.com>> wrote:
On 3/28/18 11:00 PM, Vincent Daanen wrote:
On 3/28/18 9:27 AM, Vincent Daanen wrote:
Hi,
I want to add CAN driver support to the kernel. Here is the procedure
I
followed:
1. Generate a .config file
2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
3. Update it: set at the end the config to enable CAN as follows
# CAN Bus
CONFIG_NET=y
CONFIG_CAN=y
CONFIG_CAN_RAW=y
CONFIG_CAN_BCM=y
CONFIG_CAN_GW=y
#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=y
# CONFIG_CAN_SLCAN is not set
CONFIG_CAN_DEV=y
# CONFIG_CAN_CALC_BITTIMING is not set
# CONFIG_CAN_LEDS is not set
# CONFIG_CAN_SJA1000 is not set
4. Update the linux-yocto_%.bbappend file as follows
SUMMARY = "Recipe to configure kernel as required"
LICENSE = "CLOSED"
inherit kernel-yocto
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += file://defconfig
5. Request rebuilt:
bitbake linux-yocto-rt -c cleansstate
bitbake -k linux-yocto-rt
Once the image started (with qemu), I check if the CAN is enabled
(using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”
I also tried using fragment and I got the same result ☹
According the user manual, it seems to me I’m doing the right think!
Does someone know why my defconfig file is not taken into account ?
If you are using linux-yocto for your kernel provider then I wouldr recommend
that you look into developer manual.
you should look into using config fragments to modify the needed
options e.g. see
https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#cha
nging-the-configuration
I don't understand what you mean. That's what I'm doing. I followed the
procedure described in the link you provide... Can u explain ?
Create a file for config fragment say can.cfg and put all options you want to
change in that file and then add that to SRC_URI
you dont need to create full defconfig.
Thanks
Vincent
--
___
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto
--
Thanks and Regards,
Prakash K S
+91 9620140303
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig file (or fragment files) not used
>On 3/28/18 9:27 AM, Vincent Daanen wrote:
>> Hi,
>>
>> I want to add CAN driver support to the kernel. Here is the procedure
>> I
>> followed:
>>
>> 1. Generate a .config file
>> 2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
>> 3. Update it: set at the end the config to enable CAN as follows
>>
>> # CAN Bus
>>
>> CONFIG_NET=y
>>
>> CONFIG_CAN=y
>>
>> CONFIG_CAN_RAW=y
>>
>> CONFIG_CAN_BCM=y
>>
>> CONFIG_CAN_GW=y
>>
>> #
>>
>> # CAN Device Drivers
>>
>> #
>>
>> CONFIG_CAN_VCAN=y
>>
>> # CONFIG_CAN_SLCAN is not set
>>
>> CONFIG_CAN_DEV=y
>>
>> # CONFIG_CAN_CALC_BITTIMING is not set
>>
>> # CONFIG_CAN_LEDS is not set
>>
>> # CONFIG_CAN_SJA1000 is not set
>>
>> 4. Update the linux-yocto_%.bbappend file as follows
>>
>> SUMMARY = "Recipe to configure kernel as required"
>>
>> LICENSE = "CLOSED"
>>
>> inherit kernel-yocto
>>
>> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>>
>> SRC_URI += file://defconfig
>>
>> 5. Request rebuilt:
>>
>> bitbake linux-yocto-rt -c cleansstate
>>
>> bitbake -k linux-yocto-rt
>>
>> Once the image started (with qemu), I check if the CAN is enabled
>> (using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”
>>
>> I also tried using fragment and I got the same result ☹
>>
>> According the user manual, it seems to me I’m doing the right think!
>>
>> Does someone know why my defconfig file is not taken into account ?
>>
>
>If you are using linux-yocto for your kernel provider then I wouldr recommend
>that you look into developer manual.
>
>you should look into using config fragments to modify the needed
>options e.g. see
>https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#cha
>nging-the-configuration
I don't understand what you mean. That's what I'm doing. I followed the
procedure described in the link you provide... Can u explain ?
Thanks
Vincent
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] defconfig file (or fragment files) not used
Hi,
I want to add CAN driver support to the kernel. Here is the procedure I
followed:
1. Generate a .config file
2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
3. Update it: set at the end the config to enable CAN as follows
# CAN Bus
CONFIG_NET=y
CONFIG_CAN=y
CONFIG_CAN_RAW=y
CONFIG_CAN_BCM=y
CONFIG_CAN_GW=y
#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=y
# CONFIG_CAN_SLCAN is not set
CONFIG_CAN_DEV=y
# CONFIG_CAN_CALC_BITTIMING is not set
# CONFIG_CAN_LEDS is not set
# CONFIG_CAN_SJA1000 is not set
1. Update the linux-yocto_%.bbappend file as follows
SUMMARY = "Recipe to configure kernel as required"
LICENSE = "CLOSED"
inherit kernel-yocto
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += file://defconfig
1. Request rebuilt:
bitbake linux-yocto-rt -c cleansstate
bitbake -k linux-yocto-rt
Once the image started (with qemu), I check if the CAN is enabled (using zcat
/proc/config.gz | grep CAN) and I always get “CAN not set”
I also tried using fragment and I got the same result ☹
According the user manual, it seems to me I’m doing the right think!
Does someone know why my defconfig file is not taken into account ?
Thanks
Vincent
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to "compute" path to install module file
Hi Thanks for your answer, it helps me to get module installation work. But now I have another problem ... Stay tune the mail willarrive soon on the mailing list > On 3/22/18 12:31 AM, Vincent Daanen wrote: > > Hi, > > > > I'm porting the makefile to build SocketCan for Ixxat on yocto. At > > this time I successfully build the module file. > > Have you checked out the CANopen drivers? > https://github.com/ros-industrial/ros_canopen > https://github.com/bmwcarit/meta-ros/tree/master/recipes-ros/ros-canopen > > There are already recipes for this if it happens to work for your part. > > Just figured I'd mention it :) > > For adding the Ixxat driver, this documentation might help: > https://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#working-with-out-of-tree > modules > > > > > Build fails with the following error: > > > > nothing provides kernel-module-ixx-pci-4.12.14-yocto-standard needed > > by kernel-module-ixxat-candriver-1.0-r0.qemux86_64 > > Do you have a recipe that provides ixx-pci? If so it needs to say: > > PROVIDES = "ixx-pci" > > https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-PROVIDES > > Also, you need to be sure that it is being built, so I would add that recipe > into some RDEPENDS variable, > > for example: > > MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "ixx-pci" > > (in this case in your machine conf, assuming the package name is "ixx-pci") > > > > > I don't understand how yocto computes to module filename. It adds the > > kernel-version to the default filename... > > check out the "module_pattern" variables in: > meta/classes/kernel-module-split.bbclass > > I believe this is done during packaging. > > Cheers, > Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] TR: how to "compute" path to install module file
Hi,
I'm porting the makefile to build SocketCan for Ixxat on yocto. At this time I
successfully build the module file.
I now have to install it in the target image.
The "install" procedure from the original makefile does not work
out-of-the-box. It copies files in the following directories starting by /lib
and thus it tries to install in the host system, not the target system..
In order to install in the target image, the installation is performed in a
customized do_install function in the bb file, and the problem starts here !
In the original makefile, installation process copies a file in the following
directory : /lib/modules/$(shell uname -r)/kernel/drivers/net/.
In the bb file, I "compute" the kernel version using ${KERNEL_VERSION}
Thus the bb file contains the following lines:
#MODDIR = Module file destination directory
MODDIR
="${nonarch_base_libdir}/modules/${KERNEL_VERSION}/kernel/drivers/net/can/ixxat"
do_install() {
install -d ${D}${base_libdir}/firmware
install -m 0755 ${WORKDIR}/can-ibxxx_socketcan/ixx-can-ib-1.9.3.fw
${D}${base_libdir}/firmware
install -d ${D}${MODDIR}
install -m 0755 ${WORKDIR}/can-ibxxx_socketcan/ixx_pci.ko ${D}${MODDIR}
}
FILES_${PN} += " ${base_libdir}/firmware ${MODDIR}"
Build fails with the following error:
nothing provides kernel-module-ixx-pci-4.12.14-yocto-standard needed by
kernel-module-ixxat-candriver-1.0-r0.qemux86_64
I don't understand how yocto computes to module filename. It adds the
kernel-version to the default filename...
Is it the standard way for computing module filename with yocto (I searched and
did not find any info about this) or could it be a side-effect of my bb file
(and in this case, how can I identify where this side-effect occurs) or ..
maybe if bug in bitbake ??
Thanks for helping
Vincent
--
___
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] how to "compute" path to install module file
Hi,
I'm porting the makefile to build SocketCan for Ixxat on yocto. At this time I
successfully build the module file.
I now have to install it in the target image.
The "install" procedure from the original makefile does not work
out-of-the-box. It copies files in the following directories starting by /lib
and thus it tries to install in the host system, not the target system..
In order to install in the target image, the installation is performed in a
customized do_install function in the bb file, and the problem starts here !
In the original makefile, installation process copies a file in the following
directory : /lib/modules/$(shell uname -r)/kernel/drivers/net/.
In the bb file, I "compute" the kernel version using ${KERNEL_VERSION}
Thus the bb file contains the following lines:
#MODDIR = Module file destination directory
MODDIR
="${nonarch_base_libdir}/modules/${KERNEL_VERSION}/kernel/drivers/net/can/ixxat"
do_install() {
install -d ${D}${base_libdir}/firmware
install -m 0755 ${WORKDIR}/can-ibxxx_socketcan/ixx-can-ib-1.9.3.fw
${D}${base_libdir}/firmware
install -d ${D}${MODDIR}
install -m 0755 ${WORKDIR}/can-ibxxx_socketcan/ixx_pci.ko ${D}${MODDIR}
}
FILES_${PN} += " ${base_libdir}/firmware ${MODDIR}"
Build fails with the following error:
nothing provides kernel-module-ixx-pci-4.12.14-yocto-standard needed by
kernel-module-ixxat-candriver-1.0-r0.qemux86_64
I don't understand how yocto computes to module filename. It adds the
kernel-version to the default filename...
Is it the standard way for computing module filename with yocto (I searched and
did not find any info about this) or could it be a side-effect of my bb file
(and in this case, how can I identify where this side-effect occurs) or ..
maybe if bug in bitbake ??
Thanks for helping
Vincent
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] directory not created in /lib/firmware rootfs
Hi,
I have to install a firmware in /lib/firmware.
In the recipe, the function do_install() is the following
do_install() {
install -d ${base_libdir}/firmware
install -m 0755 ${WORKDIR}/firmware_manufacturer/firmware.fw
${base_libdir}/firmware
}
FILES_${PN} += " ${base_libdir}/firmware/firmware.fw "
And the build fails with an error: "cannot create regular file
'/lib/firmware/firmware.fw': Permission denied
So I comment the install statement relative to the firmware (install -m
0755...) and change FILES_${PN} to FILES_${PN} += " ${base_libdir}/firmware "
The build succeeds but when I look at the image (with qemu) the directory
/lib/firmware does not exists..
What am I doing wrong ?
Vincent
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Integrating Ixxat SocketCAN Drivers in image
Hi,
I have to integrate Ixxat SocketCAN driver in the image which will run our
system.
The organisation of the files is the following
Yocto/MyCompany/meta-myCompany/recipes-candriver/ixxat-socketcan
This directory contains the file ixxat-socketcan.bb.
The content of this file is the following
SUMMARY = "..."
LICENSE = "CLOSED"
SRC_URI=
https://www.ixxat.com/docs/librariesprovider8/default-document-library/downloads/other-drivers/socketcan.zip
SRC_URI[sha256sum] = <... > (the sha256 sum is correct)
S="${WORKDIR}"
The problems I run into are the following:
Although the recipe is found (it appears in the output of bitbake-layer
show-recipe), and that the file is processed by bitbake (if I intentionally add
a typo, the build breaks), it seems to not be processed (the zip file is not
downloaded) when I invoke bitbake core-image-minimal..
When I invoke bitbake -b ixxat-socketcan, it fails with the following output
(sorry for the formatting of the text)
ERROR: ixxat-socketcan-1.0-r0 do_unpack: Unpack failure for URL:
'https://www.ixxat.com/docs/librariesprovider8/default-document-library/downloads/other-drivers/socketcan.zip'.
Unpack command
PATH="/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/rd-otx/yocto/sources/poky/scripts:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot/usr/bin/crossscripts:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/usr/sbin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/usr/bin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/sbin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/bin:/home/rd-otx/yocto/sources/poky-rocko-18.0.1/bitbake/bin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/hosttools"
unzip -q -o
'/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/downloads/socketcan.zip' failed
with return value 127
ERROR: ixxat-socketcan-1.0-r0 do_unpack: Function failed: base_do_unpack
ERROR: Logfile of failure stored in:
/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/temp/log.do_unpack.16493
ERROR: ixxat-socketcan-1.0-r0 do_make_scripts: Function failed: do_make_scripts
(log file is located at
/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/temp/log.do_make_scripts.16494)
ERROR: Task
(/home/rd-otx/yocto/RCU_Yocto/meta-OtxLayer/recipes-candriver/ixxat-socketcan/ixxat-socketcan.bb:do_unpack)
failed with exit code '1'
ERROR: Logfile of failure stored in:
/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/temp/log.do_make_scripts.16494
I found on the net that the first error is sometimes due to the
fact that the archive file is corrupted but this is not the case. I could
unpack the file manually using unzip .
Can someone point me to information or help me to figure out what's wrong ??
Thanks
Vincent
------------
Vincent Daanen, PhD - System Integration Director
>>>> New Phone Number +33 (0) 4 76 54 95 22
Orthotaxy
5 avenue du Grand Sablon
38700 La Tronche
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: Integrating Ixxat SocketCAN Drivers in image
Hi,
I have to integrate Ixxat SocketCAN driver in the image which will run our
system.
The organisation of the files is the following
Yocto/MyCompany/meta-myCompany/recipes-candriver/ixxat-socketcan
This directory contains the file ixxat-socketcan.bb.
The content of this file is the following
SUMMARY = “…”
LICENSE = “CLOSED”
SRC_URI=
https://www.ixxat.com/docs/librariesprovider8/default-document-library/downloads/other-drivers/socketcan.zip
SRC_URI[sha256sum] = «… » (the sha256 sum is correct)
S=”${WORKDIR}”
The problems I run into are the following:
Although the recipe is found (it appears in the output of bitbake-layer
show-recipe), and that the file is processed by bitbake (if I intentionally add
a typo, the build breaks), it seems to not be processed (the zip file is not
downloaded) when I invoke bitbake core-image-minimal..
When I invoke bitbake -b ixxat-socketcan, it fails with the following output
(sorry for the formatting of the text)
ERROR: ixxat-socketcan-1.0-r0 do_unpack: Unpack failure for URL:
'https://www.ixxat.com/docs/librariesprovider8/default-document-library/downloads/other-drivers/socketcan.zip'.
Unpack command
PATH="/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/rd-otx/yocto/sources/poky/scripts:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot/usr/bin/crossscripts:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/usr/sbin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/usr/bin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/sbin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/bin:/home/rd-otx/yocto/sources/poky-rocko-18.0.1/bitbake/bin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/hosttools"
unzip -q -o
'/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/downloads/socketcan.zip' failed
with return value 127
ERROR: ixxat-socketcan-1.0-r0 do_unpack: Function failed: base_do_unpack
ERROR: Logfile of failure stored in:
/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/temp/log.do_unpack.16493
ERROR: ixxat-socketcan-1.0-r0 do_make_scripts: Function failed: do_make_scripts
(log file is located at
/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/temp/log.do_make_scripts.16494)
ERROR: Task
(/home/rd-otx/yocto/RCU_Yocto/meta-OtxLayer/recipes-candriver/ixxat-socketcan/ixxat-socketcan.bb:do_unpack)
failed with exit code '1'
ERROR: Logfile of failure stored in:
/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/temp/log.do_make_scripts.16494
I found on the net that the first error is sometimes due to the
fact that the archive file is corrupted but this is not the case. I could
unpack the file manually using unzip .
Can someone point me to information or help me to figure out what’s wrong ??
Thanks
Vincent
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Integrating Ixxat SocketCAN Drivers in image
Hi,
I have to integrate Ixxat SocketCAN driver in the image which will run our
system.
The organisation of the files is the following
Yocto/MyCompany/meta-myCompany/recipes-candriver/ixxat-socketcan
This directory contains the file ixxat-socketcan.bb.
The content of this file is the following
SUMMARY = "..."
LICENSE = "CLOSED"
SRC_URI=
https://www.ixxat.com/docs/librariesprovider8/default-document-library/downloads/other-drivers/socketcan.zip
SRC_URI[sha256sum] = <... > (the sha256 sum is correct)
S="${WORKDIR}"
The problems I run into are the following:
1. Although the recipe is found (it appears in the output of bitbake-layer
show-recipe), and that the file is processed by bitbake (if I intentionally add
a typo, the build breaks), it seems to not be processed (the zip file is not
downloaded) when I invoke bitbake core-image-minimal..
1. When I invoke bitbake -b ixxat-socketcan, it fails with the following
output (sorry for the formatting of the text)
ERROR: ixxat-socketcan-1.0-r0 do_unpack: Unpack failure for URL:
'https://www.ixxat.com/docs/librariesprovider8/default-document-library/downloads/other-drivers/socketcan.zip'.
Unpack command
PATH="/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/rd-otx/yocto/sources/poky/scripts:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot/usr/bin/crossscripts:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/usr/sbin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/usr/bin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/sbin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/recipe-sysroot-native/bin:/home/rd-otx/yocto/sources/poky-rocko-18.0.1/bitbake/bin:/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/hosttools"
unzip -q -o
'/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/downloads/socketcan.zip' failed
with return value 127
ERROR: ixxat-socketcan-1.0-r0 do_unpack: Function failed: base_do_unpack
ERROR: Logfile of failure stored in:
/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/temp/log.do_unpack.16493
ERROR: ixxat-socketcan-1.0-r0 do_make_scripts: Function failed: do_make_scripts
(log file is located at
/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/temp/log.do_make_scripts.16494)
ERROR: Task
(/home/rd-otx/yocto/RCU_Yocto/meta-OtxLayer/recipes-candriver/ixxat-socketcan/ixxat-socketcan.bb:do_unpack)
failed with exit code '1'
ERROR: Logfile of failure stored in:
/home/rd-otx/yocto/RCU_Yocto/build-firstBoot/tmp/work/qemux86_64-poky-linux/ixxat-socketcan/1.0-r0/temp/log.do_make_scripts.16494
I found on the net that the first error is sometimes due to the
fact that the archive file is corrupted but this is not the case. I could
unpack the file manually using unzip .
Can someone point me to information or help me to figure out what's wrong ??
Thanks
Vincent
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] bbappend file not used
Dears, I want to build an image using systemd and system-networkd as network manager and set static ip address to eth0. To do so, I use a bbappend file to systemd. The problem is that the systemd_%.bbappend file does not appear when calling bitbake-layers show-appends. I'm quite sure it is not processed because when a voluntary add a typo, it does not break the bitbake process. What did I do wrong ?? Below is my "files architecture": Yocto |-- Sources (Rocko 2.4.1) |-- myDir |-- build |-- conf Local.conf |-- meta-myLayer |-- conf |-- recipes-core |-- images my-image.bb |-- systemd systemd_%.bbappend |-- system eth.network The target is a generic x86_64 board (AAEON GENE BT 05 with J1900 processor). Host system is ubuntu 16.04 LTS Thanks Vince -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bbappend file not used
Yes these lines are in the layer.conf file
De : Burton, Ross [mailto:ross.bur...@intel.com]
Envoyé : mardi 6 mars 2018 13:28
À : Vincent Daanen <vincent.daa...@orthotaxy.com>
Cc : yocto@yoctoproject.org
Objet : Re: [yocto] bbappend file not used
Does your layer.conf tell bitbake to read bbappends? Should be something like:
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
Ross
On 6 March 2018 at 12:07, Vincent Daanen
<vincent.daa...@orthotaxy.com<mailto:vincent.daa...@orthotaxy.com>> wrote:
Dears,
I want to build an image using systemd and system-networkd as network manager
and set static ip address to eth0.
To do so, I use a bbappend file to systemd.
The problem is that the systemd_%.bbappend file does not appear when calling
bitbake-layers show-appends. I’m quite sure it is not processed because when a
voluntary add a typo, it does not break the bitbake process.
What did I do wrong ??
Below is my “files architecture”:
Yocto
|-- Sources (Rocko 2.4.1)
|-- myDir
|-- build
|-- conf
Local.conf
|-- meta-myLayer
|-- conf
|-- recipes-core
|-- images
my-image.bb<http://my-image.bb>
|-- systemd
systemd_%.bbappend
|-- system
eth.network
The target is a generic x86_64 board (AAEON GENE BT 05 with J1900 processor).
Host system is ubuntu 16.04 LTS
Thanks
Vince
--
___
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bbappend file not used
Hi guys,
After having spent some time to find what was wrong, I decided to rewrite all
the files and … the bbappend file is not processed…
May be there was a typo I did not see or some ‘code’ I copied/pasted from
internet included utf characters..
Anyway, I can continue building my image..
Regards
Vince
De : Burton, Ross [mailto:ross.bur...@intel.com]
Envoyé : mardi 6 mars 2018 13:28
À : Vincent Daanen <vincent.daa...@orthotaxy.com>
Cc : yocto@yoctoproject.org
Objet : Re: [yocto] bbappend file not used
Does your layer.conf tell bitbake to read bbappends? Should be something like:
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
Ross
On 6 March 2018 at 12:07, Vincent Daanen
<vincent.daa...@orthotaxy.com<mailto:vincent.daa...@orthotaxy.com>> wrote:
Dears,
I want to build an image using systemd and system-networkd as network manager
and set static ip address to eth0.
To do so, I use a bbappend file to systemd.
The problem is that the systemd_%.bbappend file does not appear when calling
bitbake-layers show-appends. I’m quite sure it is not processed because when a
voluntary add a typo, it does not break the bitbake process.
What did I do wrong ??
Below is my “files architecture”:
Yocto
|-- Sources (Rocko 2.4.1)
|-- myDir
|-- build
|-- conf
Local.conf
|-- meta-myLayer
|-- conf
|-- recipes-core
|-- images
my-image.bb<http://my-image.bb>
|-- systemd
systemd_%.bbappend
|-- system
eth.network
The target is a generic x86_64 board (AAEON GENE BT 05 with J1900 processor).
Host system is ubuntu 16.04 LTS
Thanks
Vince
--
___
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] bbappend file not used
Dears, I want to build an image using systemd and system-networkd as network manager and set static ip address to eth0. To do so, I use a bbappend file to systemd. The problem is that the systemd_%.bbappend file does not appear when calling bitbake-layers show-appends. I'm quite sure it is not processed because when a voluntary add a typo, it does not break the bitbake process. What did I do wrong ?? Below is my "files architecture": Yocto |-- Sources (Rocko 2.4.1) |-- myDir |-- build |-- conf Local.conf |-- meta-myLayer |-- conf |-- recipes-core |-- images my-image.bb |-- systemd systemd_%.bbappend |-- system eth.network The target is a generic x86_64 board (AAEON GENE BT 05 with J1900 processor). Host system is ubuntu 16.04 LTS Thanks Vince -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
