|
Re: [PATCH] mfgtools: add recipe
Stefan Agner
Hi Ming,
Thanks for tackling this. On 15.06.2019 12:42, liu.ming50@... wrote: From: Ming Liu <liu.ming50@...>We use a static build to create a binary which is rather easy to run on a variety of new and old distributions, but not sure if that is the default use case. I would rather prefer if we enable this package config in a local bbappend or similar and leave it non-static by default. We might even argue whether compiling statically is something an upstream recipe should provide. But I leave that decision up to the maintainers... -- Stefan +PACKAGECONFIG[doc] = "-DBUILD_DOC=ON,-DBUILD_DOC=OFF,doxygen-native"
|
|
|
|
Re: /var/run conflicts
Vincent Prince
Hi, did you try this one? Best regards, Vincent
Le jeu. 30 mai 2019 à 18:53, Srinivas Madishetti <msrinivas.tech@...> a écrit :
|
|
|
|
[PATCH] mfgtools: add recipe
liu.ming50@...
From: Ming Liu <liu.ming50@...>
Freescale/NXP I.MX Chip image deploy tools, uuu (Universal Update Utility), mfgtools 3.0. Signed-off-by: Ming Liu <liu.ming50@...> --- .../0001-CMakeLists.txt-fix-libzip-name.patch | 54 ++++++++++++++++++++++ ...MakeLists.txt-support-building-static-uuu.patch | 32 +++++++++++++ recipes-bsp/mfgtools/mfgtools_git.bb | 31 +++++++++++++ 3 files changed, 117 insertions(+) create mode 100644 recipes-bsp/mfgtools/mfgtools/0001-CMakeLists.txt-fix-libzip-name.patch create mode 100644 recipes-bsp/mfgtools/mfgtools/0001-CMakeLists.txt-support-building-static-uuu.patch create mode 100644 recipes-bsp/mfgtools/mfgtools_git.bb diff --git a/recipes-bsp/mfgtools/mfgtools/0001-CMakeLists.txt-fix-libzip-name.patch b/recipes-bsp/mfgtools/mfgtools/0001-CMakeLists.txt-fix-libzip-name.patch new file mode 100644 index 0000000..03f68a5 --- /dev/null +++ b/recipes-bsp/mfgtools/mfgtools/0001-CMakeLists.txt-fix-libzip-name.patch @@ -0,0 +1,54 @@ +From b11bd93be67c5ad92e279f071a812234486c128b Mon Sep 17 00:00:00 2001 +From: Ming Liu <liu.ming50@...> +Date: Thu, 13 Jun 2019 16:52:45 +0200 +Subject: [PATCH] CMakeLists.txt: fix libzip name + +Change libzip -> zlib, this is needed for building with OE. + +Upstream-Status: Inappropriate [oe specific] + +Signed-off-by: Ming Liu <liu.ming50@...> +--- + libuuu/CMakeLists.txt | 2 +- + uuu/CMakeLists.txt | 5 ++--- + 2 files changed, 3 insertions(+), 4 deletions(-) + +diff --git a/libuuu/CMakeLists.txt b/libuuu/CMakeLists.txt +index 740d7ed..30324d0 100644 +--- a/libuuu/CMakeLists.txt ++++ b/libuuu/CMakeLists.txt +@@ -5,7 +5,7 @@ set(CMAKE_CXX_STANDARD_REQUIRED ON) + + find_package(PkgConfig REQUIRED) + pkg_check_modules(LIBUSB REQUIRED libusb-1.0>=1.0.16) +-pkg_check_modules(LIBZIP REQUIRED libzip) ++pkg_check_modules(LIBZIP REQUIRED zlib) + find_package(Threads) + + include_directories(${LIBUSB_INCLUDE_DIRS} include) +diff --git a/uuu/CMakeLists.txt b/uuu/CMakeLists.txt +index a2d8c87..1ca8013 100644 +--- a/uuu/CMakeLists.txt ++++ b/uuu/CMakeLists.txt +@@ -5,8 +5,7 @@ set(CMAKE_CXX_STANDARD_REQUIRED ON) + + find_package(PkgConfig REQUIRED) + pkg_check_modules(LIBUSB REQUIRED libusb-1.0>=1.0.16) +-pkg_check_modules(LIBZIP REQUIRED libzip) +-pkg_check_modules(LIBZ REQUIRED zlib) ++pkg_check_modules(LIBZIP REQUIRED zlib) + find_package(Threads) + + +@@ -27,7 +26,7 @@ set(LSTS + sd_burn_all.lst + ) + +-link_directories(${CMAKE_CURRENT_SOURCE_DIR}/libuuu ${LIBUSB_LIBRARY_DIRS} ${LIBZIP_LIBRARY_DIRS} ${LIBZ_LIBRARY_DIRS}) ++link_directories(${CMAKE_CURRENT_SOURCE_DIR}/libuuu ${LIBUSB_LIBRARY_DIRS} ${LIBZIP_LIBRARY_DIRS}) + + set(CLIST_EXECUTABLE ${CMAKE_CURRENT_SOURCE_DIR}/gen_txt_include.sh) + set(generated_files_dir "${CMAKE_BINARY_DIR}/uuu/gen") +-- +2.7.4 + diff --git a/recipes-bsp/mfgtools/mfgtools/0001-CMakeLists.txt-support-building-static-uuu.patch b/recipes-bsp/mfgtools/mfgtools/0001-CMakeLists.txt-support-building-static-uuu.patch new file mode 100644 index 0000000..bb69c87 --- /dev/null +++ b/recipes-bsp/mfgtools/mfgtools/0001-CMakeLists.txt-support-building-static-uuu.patch @@ -0,0 +1,32 @@ +From 2ccb6fa0ae52981c78f79afa7009ccab11c6703f Mon Sep 17 00:00:00 2001 +From: Ming Liu <liu.ming50@...> +Date: Sat, 15 Jun 2019 05:18:10 +0800 +Subject: [PATCH] CMakeLists.txt: support building static uuu + +Upstream-Status: Inappropriate [oe specific] + +Signed-off-by: Ming Liu <liu.ming50@...> +--- + CMakeLists.txt | 6 ++++++ + 1 file changed, 6 insertions(+) + +diff --git a/CMakeLists.txt b/CMakeLists.txt +index 302f8cb..f23871e 100644 +--- a/CMakeLists.txt ++++ b/CMakeLists.txt +@@ -4,6 +4,12 @@ set(CMAKE_CXX_STANDARD 11) + set(CMAKE_CXX_STANDARD_REQUIRED ON) + + option(BUILD_DOC "Build documentation" OFF) ++option(BUILD_STATIC "Build static uuu binary" OFF) ++ ++if (BUILD_STATIC) ++ set(CMAKE_FIND_LIBRARY_SUFFIXES ".a") ++ set(CMAKE_EXE_LINKER_FLAGS "-static -static-libgcc -static-libstdc++") ++endif (BUILD_STATIC) + + add_subdirectory(libuuu) + add_subdirectory(uuu) +-- +2.7.4 + diff --git a/recipes-bsp/mfgtools/mfgtools_git.bb b/recipes-bsp/mfgtools/mfgtools_git.bb new file mode 100644 index 0000000..4ba6065 --- /dev/null +++ b/recipes-bsp/mfgtools/mfgtools_git.bb @@ -0,0 +1,31 @@ +SUMMARY = "uuu (Universal Update Utility), mfgtools 3.0" +DESCRIPTION = "Freescale/NXP I.MX Chip image deploy tools, uuu (Universal Update Utility), mfgtools 3.0." +HOMEPAGE = "https://github.com/NXPmicro/mfgtools" +SECTION = "devel" +LICENSE = "BSD" +LIC_FILES_CHKSUM = "file://README.md;md5=653656dfc74a26684d74346214abe93a" + +SRC_URI = "gitsm://github.com/NXPmicro/mfgtools;branch=master \ + file://0001-CMakeLists.txt-fix-libzip-name.patch \ + file://0001-CMakeLists.txt-support-building-static-uuu.patch \ + " + +# uuu_1.2.91 +SRCREV = "3799f4d7b0464cc9253b4597ba7ccc54deefca20" + +PV = "1.2.91+git${SRCPV}" + +S = "${WORKDIR}/git" + +DEPENDS = "libusb1 zlib bzip2" + +inherit pkgconfig cmake + +PACKAGECONFIG ??= "static" +PACKAGECONFIG[doc] = "-DBUILD_DOC=ON,-DBUILD_DOC=OFF,doxygen-native" +PACKAGECONFIG[static] = "-DBUILD_STATIC=ON,-DBUILD_STATIC=OFF" + +# Do not set RPATH if static build is intended. +OECMAKE_RPATH_forcevariable = "${@bb.utils.contains('PACKAGECONFIG', 'static', '', '${libdir}', d)}" + +BBCLASSEXTEND = "native" -- 2.7.4
|
|
|
|
Re: [alsa] do_populate_sdk: No manifest generated from: lib32-alsa-lib
Mans Zigher
Adding
toggle quoted messageShow quoted text
PACKAGE_EXTRA_ARCHS = "${PACKAGE_EXTRA_ARCHS_tune-${DEFAULTTUNE}} armv7ahf-neon-mx8mm" to my machine config solved it but dose not feel right to solve it this way. Any thoughts? BR Månz Zigher Den tors 6 juni 2019 kl 11:00 skrev Måns Zigher <mans.zigher@...>:
|
|
|
|
[meta-freescale-3rdparty] [thud] Backport request
Alex Gonzalez
Hi,
Could you please backport the following commit into the thud branch: https://github.com/Freescale/meta-freescale-3rdparty/commit/5d88f226ed2c72ac37752fe54808feff4ec7c1ed That would allow the ccimx6ulsbcexpress platform to build with the v4.20 kernel in thud. Thanks, Alex
|
|
|
|
[alsa] do_populate_sdk: No manifest generated from: lib32-alsa-lib
Mans Zigher
Hi,
I am trying to build an SDK I suspect the same error would pop up when building an image. The problem that I am facing is that I need to include lib32-alsa-lib to my SDK but I am getting the following error ERROR: strix-sdk-1.0-r0 do_populate_sdk: No manifest generated from: lib32-alsa-lib in virtual:multilib:lib32:/home/builder/workdir/layers/poky/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb ERROR: strix-sdk-1.0-r0 do_populate_sdk: Function failed: do_populate_sdk ERROR: Logfile of failure stored in: /home/builder/workdir/builds/imx8mm/tmp/work/imx8mm-strix-linux/strix-sdk/1.0-r0/temp/log.do_populate_sdk.138 ERROR: Task (/home/builder/workdir/layers/meta-strix/meta-strix-common/recipes-core/images/strix-sdk.bb:do_populate_sdk) failed with exit code '1' The reason for this is that that PACKAGE_ARCH is overwritten at meta-freescale/recipes-multimedia/alsa/alsa-lib_%.bbappend:Line 10 PACKAGE_ARCH_imx = "${MACHINE_SOCARCH}" and that the find_sstate_manifest function in poky https://github.com/kraj/poky/blob/2b8d484f9623b9e998d642cff44c09dcf4a0b2b8/meta/lib/oe/sstatesig.py#L579 will not look for the manifest named armv7ahf-neon-mx8mm since it is not part of the list. Do you have any idea how I can solve this? Based on the code in https://github.com/kraj/poky/blob/2b8d484f9623b9e998d642cff44c09dcf4a0b2b8/meta/lib/oe/sstatesig.py#L580 It should be possible to add armv7ahf-neon-mx8mm to PACKAGE_EXTRA_ARCHS but I cannot find how I should do that. BR Måns Zigher
|
|
|
|
IMX zImage with ramdisk
JH
Hi,
I build i.MX6 image, I can install imx.wic.gz to an SD card and run it well i.MX EVK, now I need to build i.MX6 image with ramdisk to install it to the RAM of a customized i.MX processor board, the download and boot was via USB HID using iMX uuu, bootz with zImage, I got following error: Boot from USB for mfgtools Use default environment for mfgtools Run bootcmd_mfg: run mfgtool_args; if test ${tee} = yes; then bootm ${tee_addr}; Hit any key to stop autoboot: 0 Kernel image @ 0x80800000 [ 0x000000 - 0x89e1d8 ] Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid Apparently, the zImage needs be compiled with ramdisk, I can see several initramfs recipes but I cannot find any ramdisk recipes, could anyone advise how to build the zImage with ramdisk not initramfs? Or should it be a separate process to command line manually creat ramdisk on zImage? Should I also modify the kernel defconfig for supporting zImage ramdisk format? If so, which device driver needs be enabled in defconfig? Thank you. Kind regards, - jupiter
|
|
|
|
Re: [EXT] Why not support aarch64 BE any more.
leimaohui
Hi, Guo
We can not support aarch64BE now .Thanks for your reply. Best regards Lei -----Original Message-----
|
|
|
|
Re: imx53 and thud
maillinglists18@...
On Thu, May 30, 2019 at 1:25 AM Otavio Salvador
<otavio.salvador@...> wrote: I got it working. I was using wrong image. -Teemu
|
|
|
|
/var/run conflicts
Srinivas
Hi Team,
I am building core-image-minimal target for i.MX8 eval board. I could succeeded in making the image.
When trying to add recipe - /meta-telephony/asterisk and getting below error during do_rootfs call:
“file /var/run conflicts between attempted installs of asterisk-13.5.0-r0.aarch64 and base-files-3.0.14-r89.imx8mqevk”
I could not find any resolutions online and need your help.
Thanks Srinivas
|
|
|
|
Re: imx53 and thud
Otavio Salvador <otavio.salvador@...>
On Mon, Apr 8, 2019 at 7:52 AM Teemu K <maillinglists18@...> wrote:
I'm trying to build newer image for imx53 based hw (it's actuallyWhich U-Boot version are you referring to? The wic image was supposed to work just fine. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
|
|
|
|
Unsubscribe
ID - David Torres <dtorres@...>
Unsubscribe
De: meta-freescale-bounces@... <meta-freescale-bounces@...>
En nombre de Vahid Gharaee
Dear all,
How could I add qt5 support in fsl-community-bsp I added the meta-qt5 but there is no image to bitbake the rootfs. multimedia image does not include qt5.
Thank you in advanced Vahid
|
|
|
|
qt5
Vahid Gharaee <vgharaee@...>
Dear all, How could I add qt5 support in fsl-community-bsp I added the meta-qt5 but there is no image to bitbake the rootfs. multimedia image does not include qt5. Thank you in advanced Vahid
|
|
|
|
Qt 5.12 on IMX6Q
Sergei Poselenov <sposelenov@...>
Hello,
Has anyone tried to build the newest meta-qt5 with Qt 5.12, and does it work on IMX6Q? I heard that Qt 5.12 have some problems and don't build or don't work. Thanks! Regards, Sergei Poselenov, Emcraft Systems
|
|
|
|
Re: [EXT] Why not support aarch64 BE any more.
C.r. Guo <chunrong.guo@...>
Hello lei,
toggle quoted messageShow quoted text
We can not support aarch64BE now . So I removed BE machine config . You can add machine config to meta-freescale if you need be machine config. Thanks Chunrong
-----Original Message-----
From: Lei, Maohui [mailto:leimaohui@...] Sent: 2019年5月17日 10:10 To: C.r. Guo <chunrong.guo@...> Cc: meta-freescale@... Subject: [EXT] [meta-freescale] Why not support aarch64 BE any more. Caution: EXT Email Hi, Guo I'm working on Distro for aarch64BE(ls1046a), and I noticed that you removed ls1043ardb-be.conf from meta-freescale recently. Would you mind tell me why doesn't support aarch64BE anymore? Best regards Lei Maohui
|
|
|
|
Why not support aarch64 BE any more.
leimaohui
Hi, Guo
I'm working on Distro for aarch64BE(ls1046a), and I noticed that you removed ls1043ardb-be.conf from meta-freescale recently. Would you mind tell me why doesn't support aarch64BE anymore? Best regards Lei Maohui
|
|
|
|
Re: [Documentation][PATCH] Use release-notes machine-list.inc In user-guide
Daiane
On Thu, May 16, 2019 at 9:40 AM Thomas A. F. Thorne
<tafthorne@...> wrote: Thanks for the patch. PR merged! Daiane
|
|
|
|
[Documentation][PATCH] Use release-notes machine-list.inc In user-guide
Thomas Thorne
The user-guide gets little attention compared to the release notes.
Frequently the correct list of supported machines is visible in the release notes but the user-guide is left very out of date. This change switches to using the machine-list.inc file in the release directory in both documents to help ensure the user-guide stays up to date. This issue is described in GitHub Issue #28 Signed-off-by: Thomas A. F. Thorne <TafThorne@...> --- user-guide/source/machine-list.inc | 65 ------------------------------ user-guide/source/machines.rst | 2 +- 2 files changed, 1 insertion(+), 66 deletions(-) delete mode 100644 user-guide/source/machine-list.inc diff --git a/user-guide/source/machine-list.inc b/user-guide/source/machine-list.inc deleted file mode 100644 index f5f1f2a..0000000 --- a/user-guide/source/machine-list.inc +++ /dev/null @@ -1,65 +0,0 @@ -====================== ================================================== ======================= ================== - Machine Name SoC Layer -====================== ================================================== ======================= ================== -apalis-imx6 Toradex Apalis iMX6Q/D i.MX6 meta-fsl-arm-extra -cfa10036 Crystalfontz CFA-10036 i.MX28 meta-fsl-arm-extra -cfa10037 Crystalfontz CFA-10037 i.MX28 meta-fsl-arm-extra -cfa10049 Crystalfontz CFA-10049 i.MX28 meta-fsl-arm-extra -cfa10055 Crystalfontz CFA-10055 i.MX28 meta-fsl-arm-extra -cfa10056 Crystalfontz CFA-10056 i.MX28 meta-fsl-arm-extra -cfa10057 Crystalfontz CFA-10057 i.MX28 meta-fsl-arm-extra -cfa10058 Crystalfontz CFA-10058 i.MX28 meta-fsl-arm-extra -cgtqmx6 Congatec QMX6 Evaluation board i.MX6 Q/DL meta-fsl-arm-extra -cm-fx6 CompuLab CM-FX6 i.MX6 Q/DL meta-fsl-arm-extra -colibri-imx6 Toradex Colibri iMX6DL/S i.MX6 DL/S meta-fsl-arm-extra -colibri-imx7 Toradex Colibri iMX7D/S i.MX 7Dual / i.MX 7Solo meta-fsl-arm-extra -colibri-vf Toradex Colibri VF50/VF61 VF500/VF610 meta-fsl-arm-extra -cubox-i SolidRun CuBox-i and HummingBoard i.MX6 Q/DL meta-fsl-arm-extra -imx233-olinuxino-maxi OLIMEX iMX233-OLinuXino-Maxi i.MX23 meta-fsl-arm-extra -imx233-olinuxino-micro OLIMEX iMX233-OLinuXino-Micro i.MX23 meta-fsl-arm-extra -imx233-olinuxino-mini OLIMEX iMX233-OLinuXino-Mini i.MX23 meta-fsl-arm-extra -imx233-olinuxino-nano OLIMEX iMX233-OLinuXino-Nano i.MX23 meta-fsl-arm-extra -imx23evk Freescale i.MX23 Evaluation Kit i.MX23 meta-fsl-arm -imx28evk Freescale i.MX28 Evaluation Kit i.MX28 meta-fsl-arm -imx51evk Freescale i.MX51 Evaluation Kit i.MX51 meta-fsl-arm -imx53ard Freescale i.MX53 SABRE Automotive Board i.MX53 meta-fsl-arm -imx53qsb Freescale i.MX53 Quick Start Board i.MX53 meta-fsl-arm -imx6dl-riotboard RIoTboard i.MX6S meta-fsl-arm-extra -imx6dlsabreauto Freescale i.MX6DL SABRE Automotive i.MX6DL meta-fsl-arm -imx6dlsabresd Freescale i.MX6DL SABRE Smart Device i.MX6DL meta-fsl-arm -imx6q-dms-ba16 Advantech DMS BA16 i.MX6Q meta-fsl-arm-extra -imx6qdl-variscite-som Variscite i.MX6Q/DL VAR-SOM-MX6 i.MX6Q/DL meta-fsl-arm-extra -imx6qpsabreauto Freescale i.MX6Q Plus SABRE Automotive i.MX6QP meta-fsl-arm -imx6qpsabresd Freescale i.MX6Q Plus SABRE Smart Device i.MX6QP meta-fsl-arm -imx6qsabreauto Freescale i.MX6Q SABRE Automotive i.MX6Q meta-fsl-arm -imx6qsabrelite Boundary Devices i.MX6Q SABRE Lite i.MX6Q meta-fsl-arm-extra -imx6qsabresd Freescale i.MX6Q SABRE Smart Device i.MX6Q meta-fsl-arm -imx6sl-warp WaRP i.MX6SL meta-fsl-arm-extra -imx6slevk Freescale i.MX6SL Evaluation Kit i.MX6SL meta-fsl-arm -imx6solosabreauto Freescale i.MX6Solo SABRE Automotive i.MX6S meta-fsl-arm -imx6solosabresd Freescale i.MX6Solo SABRE Smart Device i.MX6S meta-fsl-arm -imx6sxsabreauto Freescale i.MX6SoloX Sabre Automotive i.MX6SX meta-fsl-arm -imx6sxsabresd Freescale i.MX6SoloX SabreSD i.MX6SX meta-fsl-arm -imx6ul-pico-hobbit Hobbitboard (PICO-IMX6UL) i.MX6UL meta-fsl-arm-extra -imx6ulevk Freescale i.MX6UL Evaluation Kit i.MX6UL meta-fsl-arm -imx7dsabresd Freescale i.MX7D SABRE Smart Device i.MX7D meta-fsl-arm -imx7s-warp WaRP7 i.MX7S meta-fsl-arm-extra -ls1021atwr Freescale LS1021ATWR board ls102xa meta-fsl-arm -m28evk DENX M28 SoM Evaluation Kit i.MX28 meta-fsl-arm-extra -m53evk DENX M53 SoM Evaluation Kit i.MX53 meta-fsl-arm-extra -nitrogen6sx Boundary Devices Nitrogen6SX i.MX6SX meta-fsl-arm-extra -nitrogen6x Boundary Devices Nitrogen6X i.MX6 Q/DL meta-fsl-arm-extra -nitrogen6x-lite Boundary Devices Nitrogen6X Lite i.MX6S meta-fsl-arm-extra -nitrogen7 Boundary Devices Nitrogen7 i.MX7D meta-fsl-arm-extra -pcm052 Phytec phyCORE Vybrid Development Kit vf60 meta-fsl-arm-extra -twr-vf65gs10 Freescale Vybrid TWR-VF65GS10 VF610 meta-fsl-arm -tx6q-10x0 Ka-Ro electronics i.MX6Q TX6Q Computer-On-Module i.MX6Q meta-fsl-arm-extra -tx6q-11x0 Ka-Ro electronics i.MX6Q TX6Q Computer-On-Module i.MX6Q meta-fsl-arm-extra -tx6s-8034 Ka-Ro electronics i.MX6S TX6S Computer-On-Module i.MX6S meta-fsl-arm-extra -tx6s-8035 Ka-Ro electronics i.MX6S TX6S Computer-On-Module i.MX6S meta-fsl-arm-extra -tx6u-8033 Ka-Ro electronics i.MX6DL TX6DL Computer-On-Module i.MX6DL meta-fsl-arm-extra -tx6u-80x0 Ka-Ro electronics i.MX6DL TX6DL Computer-On-Module i.MX6DL meta-fsl-arm-extra -tx6u-81x0 Ka-Ro electronics i.MX6DL TX6DL Computer-On-Module i.MX6DL meta-fsl-arm-extra -ventana i.MX6Q/DL Ventana Platform i.MX6Q/DL meta-fsl-arm-extra -wandboard Wandboard i.MX6 Wandboard Quad/Dual/Solo i.MX6Q/DL meta-fsl-arm-extra -====================== ================================================== ======================= ================== diff --git a/user-guide/source/machines.rst b/user-guide/source/machines.rst index c32e550..3f848f5 100644 --- a/user-guide/source/machines.rst +++ b/user-guide/source/machines.rst @@ -10,5 +10,5 @@ Please refer to the table below for the complete list of supported boards. .. tabularcolumns:: c | p{5cm} | c | c .. table:: Supported machines - .. include:: machine-list.inc + .. include:: ../../release-notes/source/machine-list.inc -- 2.17.1
|
|
|
|
imx8mmevk : Cannot build image with warrior release
Carlos Rafael Giani
When I try to build an image, the rootfs generation fails, because both firmware-qca9377 and firmware-qca6174 want to install /etc/bluetooth/firmware.conf .
This happens with both core-image-base and core-image-weston. The hack to circumvent this is to remove qca9377 or qca6174 from the imx8mmevk.conf MACHINE_FEATURES. Is this a known issue?
|
|
|
|
Re: i.MX6, Mesa, GLES2, Vivante GC320 + GC880
Gaëtan Carlier
Hi,
On 5/10/19 7:52 AM, Gaëtan Carlier wrote: Hi ,Finally, this is not working. I fixed the problem with u-boot by replacing u-boot-imx by DHCom version: === #UBOOT_MACHINE ?= "mx6sabresd_defconfig" # Use fslc u-boot by default. See also imx-base.inc. #UBOOT_MAKE_TARGET = "all" #UBOOT_SUFFIX = "img" #SPL_BINARY = "SPL" #WKS_FILE = "imx-uboot-spl-bootpart.wks" PREFERRED_PROVIDER_virtual/bootloader = "u-boot-imx6-dhcom" PREFERRED_PROVIDER_u-boot = "u-boot-imx6-dhcom" PREFERRED_VERSION_u-boot-imx6-dhcom = "v2018.05" IMAGE_BOOTLOADER ?= "u-boot" #UBOOT_CONFIG ??= "all" UBOOT_CONFIG ??= "dl" UBOOT_CONFIG[all] = "dh_imx6_defconfig" UBOOT_CONFIG[solo] = "dh_imx6s_config" #UBOOT_CONFIG[dl] = "dh_imx6dl_config" UBOOT_CONFIG[dl] = "dh_imx6_defconfig" UBOOT_CONFIG[d] = "dh_imx6q_config" UBOOT_CONFIG[q] = "dh_imx6q_config" UBOOT_MAKE_TARGET = "u-boot.imx" UBOOT_BINARY = "u-boot.imx" === But now, another error occurs about xf86-video-imx-vivante: === Build Configuration: BB_VERSION = "1.42.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "imx6qdlsabresd" DISTRO = "poky" DISTRO_VERSION = "2.7" TUNE_FEATURES = "arm vfp cortexa9 neon thumb callconvention-hard" TARGET_FPU = "hard" meta meta-poky meta-yocto-bsp = "warrior:0e392026ffefee098a890c39bc3ca1f697bacb52" meta-freescale = "warrior:a047911c5ad1e06d7878dfdffa8674a7edc28961" meta-dhcom_imx6 = "thud:74785e4121c13a235ab6d2ba3de7390d8b84d7c4" ERROR: core-image-x11-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/gc/Documents/projects/dev_git/imx28/poky/build-warrior/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/core-image-x11/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=info -y -c /home/gc/Documents/projects/dev_git/imx28/poky/build-warrior/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/core-image-x11/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/gc/Documents/projects/dev_git/imx28/poky/build-warrior/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/core-image-x11/1.0-r0/rootfs/etc/yum.repos.d --installroot=/home/gc/Documents/projects/dev_git/imx28/poky/build-warrior/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/core-image-x11/1.0-r0/rootfs --setopt=logdir=/home/gc/Documents/projects/dev_git/imx28/poky/build-warrior/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/core-image-x11/1.0-r0/temp --repofrompath=oe-repo,/home/gc/Documents/projects/dev_git/imx28/poky/build-warrior/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/core-image-x11/1.0-r0/oe-rootfs-repo --nogpgcheck install dnf packagegroup-base-extended packagegroup-core-boot packagegroup-core-x11-base psplash rpm run-postinsts locale-base-en-us locale-base-en-gb' returned 1: DNF version: 4.1.0 cachedir: /home/gc/Documents/projects/dev_git/imx28/poky/build-warrior/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/core-image-x11/1.0-r0/rootfs/var/cache/dnf Added oe-repo repo from /home/gc/Documents/projects/dev_git/imx28/poky/build-warrior/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/core-image-x11/1.0-r0/oe-rootfs-repo repo: using cache for: oe-repo not found other for: not found modules for: not found deltainfo for: not found updateinfo for: oe-repo: using metadata from Fri 10 May 2019 08:07:09 AM UTC. Last metadata expiration check: 0:00:01 ago on Fri 10 May 2019 08:07:10 AM UTC. No module defaults found --> Starting dependency resolution --> Finished dependency resolution Error: Problem: package packagegroup-core-x11-base-1.0-r1.noarch requires packagegroup-core-x11-xserver, but none of the providers can be installed - conflicting requests - nothing provides xf86-video-imx-vivante needed by packagegroup-core-x11-xserver-1.0-r40.imx6qdlsabresd (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) ERROR: core-image-x11-1.0-r0 do_rootfs: ERROR: core-image-x11-1.0-r0 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/gc/Documents/projects/dev_git/imx28/poky/build-warrior/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_rootfs.15071 ERROR: Task (/home/gc/Documents/projects/dev_git/imx28/poky/meta/recipes-graphics/images/core-image-x11.bb:do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 5065 tasks of which 5060 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/gc/Documents/projects/dev_git/imx28/poky/meta/recipes-graphics/images/core-image-x11.bb:do_rootfs Summary: There was 1 WARNING message shown. Summary: There were 3 ERROR messages shown, returning a non-zero exit code. === I do not change anything but UBOOT variables in imx6qdlsabresd.conf file. Only U-Boot recipe from DHcom is active there is no bb/bbappend that overrides other recipes. Does anyone have any idea how to solve that ? Best regards, Gaëtan
|
|
|