date:20231207

[yocto] [ANNOUNCEMENT] Yocto Project 4.3.1 is Released

2023-12-07 Thread Lee Chee Yang

Hi

We are pleased to announce the Yocto Project 4.3.1 Release is now available for 
download.

http://downloads.yoctoproject.org/releases/yocto/yocto-4.3.1/poky-bf9f2f6f60387b3a7cd570919cef6c4570edcb82.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.3.1/poky-bf9f2f6f60387b3a7cd570919cef6c4570edcb82.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-4.3.1/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-4.3.1/testreport.txt

Note:

During testing of the release a number of intermittent test failures were 
encountered which didn't recur when the tests were re-executed. We have decided 
not to block the release on these. The project is working to try and identify 
fixes for them but has limited resources for this.
The number/frequency of such failures does appear to be rising.

Thank you for everyone's contributions to this release.

Chee Yang
chee.yang@intel.com
Yocto Project Build and Release


- --
yocto-4.3.1 Release Notes
- --


- --
Repositories/Downloads
- --

Repository Name: poky
Repository Location: https://git.yoctoproject.org/poky
Branch: nanbield
Tag: yocto-4.3.1
Git Revision: bf9f2f6f60387b3a7cd570919cef6c4570edcb82
Release Artefact: poky-bf9f2f6f60387b3a7cd570919cef6c4570edcb82
sha: 9b4351159d728fec2b63a50f1ac15edc412e2d726e9180a40afc06051fadb922
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.3.1/poky-bf9f2f6f60387b3a7cd570919cef6c4570edcb82.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.3.1/poky-bf9f2f6f60387b3a7cd570919cef6c4570edcb82.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: nanbield
Tag: yocto-4.3.1
Git Revision: cce77e8e79c860f4ef0ac4a86b9375bf87507360
Release Artefact: oecore-cce77e8e79c860f4ef0ac4a86b9375bf87507360
sha: e6cde08e7c549f57a67d833a36cdb942648fba81558dc8b0e65332d2a2c023cc
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.3.1/oecore-cce77e8e79c860f4ef0ac4a86b9375bf87507360.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.3.1/oecore-cce77e8e79c860f4ef0ac4a86b9375bf87507360.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/meta-mingw
Branch: nanbield
Tag: yocto-4.3.1
Git Revision: 49617a253e09baabbf0355bc736122e9549c8ab2
Release Artefact: meta-mingw-49617a253e09baabbf0355bc736122e9549c8ab2
sha: 2225115b73589cdbf1e491115221035c6a61679a92a93b2a3cf761ff87bf4ecc
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.3.1/meta-mingw-49617a253e09baabbf0355bc736122e9549c8ab2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.3.1/meta-mingw-49617a253e09baabbf0355bc736122e9549c8ab2.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: 2.6
Tag: yocto-4.3.1
Git Revision: 936fcec41efacc4ce988c81882a9ae6403702bea
Release Artefact: bitbake-936fcec41efacc4ce988c81882a9ae6403702bea
sha: efbdd5fe7f29227a3fd26d6a08a368bf8215083a588b4d23f3adf35044897520
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.3.1/bitbake-936fcec41efacc4ce988c81882a9ae6403702bea.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.3.1/bitbake-936fcec41efacc4ce988c81882a9ae6403702bea.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/yocto-docs
Branch: nanbield
Tag: yocto-4.3.1
Git Revision: 6b98a6164263298648e89b5a5ae1260a58f1bb35


- ---
Contributors
- ---
Alejandro Hernandez Samaniego
Alex Stewart
Archana Polampalli
Arne Schwerdt
BELHADJ SALEM Talel
Dmitry Baryshkov
Eero Aaltonen
Joshua Watt
Julien Stephan
Jérémy Rosen
Khem Raj
Lee Chee Yang
Marta Rybczynska
Max Krummenacher
Michael Halstead
Michael Opdenacker
Paul Eggleton
Peter Kjellerstedt
Peter Marko
Quentin Schulz
Richard Purdie
Robert P. J. Day
Ross Burton
Rouven Czerwinski
Steve Sakoman
Trevor Gamblin
Wang Mingyu
William Lyu
Xiangyu Chen
luca fancellu


- ---
Known Issues
- ---
N/A


- ---
Security Fixes
- ---
libsndfile1: Fix CVE-2022-33065
libxml2: Ignore CVE-2023-45322
linux-yocto/6.1: Ignore CVE-2020-27418 CVE-2023-4244 CVE-2023-4563 
CVE-2023-4732 CVE-2023-5158 CVE-2023-5197 CVE-2023-5345 CVE-2023-31085 
CVE-2023-34324 CVE-2023-39189 CVE-2023-39192 CVE-2023-39193 CVE-2023-39194 
CVE-2023-42754 CVE-2023-42756 CVE-2023-44466 CVE-2023-45862 CVE-2023-45863 
CVE-2023-45871 CVE-2023-45898
linux-yocto/6.5: Ignore CVE-2020-27418 CVE-2023-1193 CVE-2023-4610 
CVE-2023-4732 CVE-2023-39191 CVE-2023-39194 CVE-2023-40791 CVE-2023-44466 
CVE-2023-45862 CVE-2023-45863
openssl: Fix CVE-2023-5363
pixman: Ignore CVE-2023-37769
vim: Fix CVE-2023-46246
zlib: Ignore CVE-2023-45853


- ---
Fixes
- ---
baremetal-helloworld:

[yocto] bitbake error need help #kernel #yocto

2023-12-07 Thread srivijayjain94

Dear Friends
i am facing below issue kindly sugest me to build :
Loading cache: 100% 
||
 Time: 0:00:00
Loaded 1845 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.6.0"
BUILD_SYS    = "x86_64-linux"
NATIVELSBSTRING  = "ubuntu-22.04"
TARGET_SYS   = "arm-poky-linux-gnueabi"
MACHINE  = "beaglebone-yocto"
DISTRO   = "poky"
DISTRO_VERSION   = "4.3.1"
TUNE_FEATURES    = "arm vfp cortexa8 neon callconvention-hard"
TARGET_FPU   = "hard"
meta
meta-poky
meta-yocto-bsp   = "my-nanbield:508acf3ab70684338f562bd065d64d42d8cceee9"

NOTE: Fetching uninative binary shim 
http://downloads.yoctoproject.org/releases/uninative/4.3/x86_64-nativesdk-libc-4.3.tar.xz;sha256sum=1c35f09a75c4096749bbe1e009df4e3968cde151424062cf4aa3ed89db22b030
 (will check PREMIRRORS first)
WARNING: Failed to fetch URL 
http://downloads.yoctoproject.org/releases/uninative/4.3/x86_64-nativesdk-libc-4.3.tar.xz;sha256sum=1c35f09a75c4096749bbe1e009df4e3968cde151424062cf4aa3ed89db22b030,
 attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export 
DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export 
SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export 
PATH="/home/vijay/Workspace/Yocto_BB/poky/scripts:${sources}/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/defaultpkgname/1.0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:${sources}/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/defaultpkgname/1.0/recipe-sysroot/usr/bin/crossscripts:${sources}/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/defaultpkgname/1.0/recipe-sysroot-native/usr/sbin:${sources}/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/defaultpkgname/1.0/recipe-sysroot-native/usr/bin:${sources}/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/defaultpkgname/1.0/recipe-sysroot-native/sbin:${sources}/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/defaultpkgname/1.0/recipe-sysroot-native/bin:/home/vijay/Workspace/Yocto_BB/poky/bitbake/bin:${sources}/tmp/hosttools";
 export HOME="/home/vijay"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O 
'${sources}/downloads/uninative/1c35f09a75c4096749bbe1e009df4e3968cde151424062cf4aa3ed89db22b030/x86_64-nativesdk-libc-4.3.tar.xz.tmp'
 -P 
${sources}/downloads/uninative/1c35f09a75c4096749bbe1e009df4e3968cde151424062cf4aa3ed89db22b030
 
'http://downloads.yoctoproject.org/releases/uninative/4.3/x86_64-nativesdk-libc-4.3.tar.xz'
 --progress=dot -v failed with exit code 127, no output
WARNING: Disabling uninative as unable to fetch uninative tarball: Fetcher 
failure for URL: 
'http://downloads.yoctoproject.org/releases/uninative/4.3/x86_64-nativesdk-libc-4.3.tar.xz;sha256sum=1c35f09a75c4096749bbe1e009df4e3968cde151424062cf4aa3ed89db22b030'.
 Unable to fetch URL from any source.
WARNING: To build your own uninative loader, please bitbake uninative-tarball 
and set UNINATIVE_TARBALL appropriately.
Initialising tasks: 100% 
|###|
 Time: 0:00:06
Sstate summary: Wanted 4520 Local 0 Mirrors 0 Missed 4520 Current 0 (0% match, 
0% complete)
NOTE: Executing Tasks
ERROR: packagegroup-core-x11-xserver-1.0-r0 do_populate_lic: Error executing a 
python function in exec_func_python() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_func_python() autogenerated', lineno: 2, function: 
0001:
*** 0002:sstate_task_postfunc(d)
0003:
File: '/home/vijay/Workspace/Yocto_BB/poky/meta/classes-global/sstate.bbclass', 
lineno: 801, function: sstate_task_postfunc
0797:
0798:    omask = os.umask(0o002)
0799:    if omask != 0o002:
0800:   bb.note("Using umask 0o002 (not %0o) for sstate packaging" % omask)
*** 0801:    sstate_package(shared_state, d)
0802:    os.umask(omask)
0803:
0804:    sstateinst = d.getVar("SSTATE_INSTDIR")
0805:    d.setVar('SSTATE_FIXMEDIR', shared_state['fixmedir'])
File: '/home/vijay/Workspace/Yocto_BB/poky/meta/classes-global/sstate.bbclass', 
lineno: 660, function: sstate_package
0656:
0657:    sstatebuild = d.expand("${WORKDIR}/sstate-build-%s/" % ss['task'])
0658:    sde = int(d.getVar("SOURCE_DATE_EPOCH") or time.time())
0659:    d.setVar("SSTATE_CURRTASK", ss['task'])
*** 0660:    bb.utils.remove(sstatebuild, recurse=True)
0661:    bb.utils.mkdirhier(sstatebuild)
0662:    for state in ss['dirs']:
0663:    if not os.path.exists(state[1]):
0664:    continue
File: '/home/vijay/Workspace/Yocto_BB/poky/bitbake/lib/bb/utils.py', lineno: 
728, function: remove
0724:    # shutil.rmtree(name) would be ideal but its too slow
0725:    cmd = []
0726:

[linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am335x: add preempt-rt support and boards full features support

2023-12-07 Thread Xulin Sun via lists.yoctoproject.org

- Add preempt-rt kernel type support.
- Add AM335X EVM & BeagleBone Black boards with full features support.

Signed-off-by: Xulin Sun 
---
 bsp/ti-am335x/ti-am335x-preempt-rt.scc |  9 +++
 bsp/ti-am335x/ti-am335x.cfg| 84 +-
 2 files changed, 90 insertions(+), 3 deletions(-)
 create mode 100644 bsp/ti-am335x/ti-am335x-preempt-rt.scc

diff --git a/bsp/ti-am335x/ti-am335x-preempt-rt.scc 
b/bsp/ti-am335x/ti-am335x-preempt-rt.scc
new file mode 100644
index ..0b33635e
--- /dev/null
+++ b/bsp/ti-am335x/ti-am335x-preempt-rt.scc
@@ -0,0 +1,9 @@
+# SPDX-License-Identifier: MIT
+define KMACHINE ti-am335x
+define KTYPE preempt-rt
+define KARCH arm
+
+include ktypes/preempt-rt
+branch ti-am335x
+
+include ti-am335x.scc
diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg
index bdf54c5d..b8deb025 100644
--- a/bsp/ti-am335x/ti-am335x.cfg
+++ b/bsp/ti-am335x/ti-am335x.cfg
@@ -35,6 +35,8 @@ CONFIG_REGMAP_IRQ=y
 
 CONFIG_REGULATOR_TPS65910=y
 CONFIG_REGULATOR_TPS65217=y
+CONFIG_FW_LOADER_USER_HELPER=y
+CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y
 
 #
 # CPU Frequency
@@ -85,6 +87,8 @@ CONFIG_TI_CPSW_PHY_SEL=y
 CONFIG_TI_CPSW=y
 CONFIG_TI_CPTS=y
 CONFIG_PHYLIB=y
+CONFIG_NET_SWITCHDEV=y
+CONFIG_TI_CPSW_SWITCHDEV=y
 
 CONFIG_SMSC_PHY=y
 CONFIG_FIXED_PHY=y
@@ -156,19 +160,28 @@ CONFIG_TWL6040_CORE=y
 # LCD
 #
 CONFIG_DRM=y
-CONFIG_DRM_OMAP=y
+CONFIG_DRM_OMAP=m
 CONFIG_OMAP2_DSS_DPI=y
 CONFIG_DRM_TILCDC=y
 CONFIG_DRM_I2C_NXP_TDA998X=y
+CONFIG_DRM_LEGACY=y
+CONFIG_DRM_PANEL_SIMPLE=m
+CONFIG_DRM_PANEL_EDP=m
 
 CONFIG_LCD_CLASS_DEVICE=y
 CONFIG_LCD_PLATFORM=y
 CONFIG_BACKLIGHT_CLASS_DEVICE=y
-CONFIG_BACKLIGHT_GENERIC=y
 CONFIG_PWM=y
 CONFIG_BACKLIGHT_PWM=y
 CONFIG_BACKLIGHT_GPIO=y
-
+CONFIG_PWM_TIECAP=m
+CONFIG_PWM_TIEHRPWM=m
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_PWM=y
+CONFIG_OMAP5_DSS_HDMI=y
+CONFIG_DRM_TI_TFP410=m
+CONFIG_DRM_TI_TPD12S015=m
 
 CONFIG_SOUND=m
 CONFIG_SND=m
@@ -187,6 +200,8 @@ CONFIG_USB_EHCI_TT_NEWSCHED=y
 CONFIG_USB_EHCI_HCD_OMAP=m
 CONFIG_USB_MUSB_HDRC=m
 
+CONFIG_USB_GADGET=m
+
 #
 # USB Physical Layer drivers Peripheral Controller
 #
@@ -194,6 +209,11 @@ CONFIG_USB_PHY=y
 CONFIG_NOP_USB_XCEIV=m
 CONFIG_AM335X_CONTROL_USB=m
 CONFIG_AM335X_PHY_USB=m
+CONFIG_USB_MUSB_AM35X=m
+CONFIG_USB_OTG=y
+CONFIG_USB_MUSB_DUAL_ROLE=y
+CONFIG_USB_MUSB_TUSB6010=m
+CONFIG_USB_MUSB_OMAP2PLUS=m
 
 # Platform Glue Layer
 CONFIG_USB_MUSB_DSPS=m
@@ -251,3 +271,61 @@ CONFIG_TI_PIPE3=y
 CONFIG_ARM_PMU=y
 
 CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
+
+# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
+#
+# Audio support for Texas Instruments SoCs
+#
+CONFIG_SND_SOC_DAVINCI_MCASP=m
+CONFIG_SND_SOC_TLV320AIC3X=m
+CONFIG_SND_SOC_TLV320AIC3X_I2C=m
+
+CONFIG_CFG80211=m
+CONFIG_MAC80211=m
+
+#
+# Wifi support for Texas Instruments SoCs
+#
+CONFIG_WL12XX=m
+CONFIG_WL18XX=m
+CONFIG_WLCORE=m
+CONFIG_WLCORE_SDIO=m
+
+CONFIG_CAN=y
+CONFIG_CAN_RAW=y
+CONFIG_CAN_BCM=y
+CONFIG_CAN_GW=y
+CONFIG_CAN_DEV=y
+CONFIG_CAN_C_CAN=y
+CONFIG_CAN_C_CAN_PLATFORM=y
+CONFIG_CAN_NETLINK=y
+CONFIG_CAN_CALC_BITTIMING=y
+
+CONFIG_WKUP_M3_RPROC=m
+CONFIG_PRU_REMOTEPROC=m
+
+CONFIG_SOC_TI=y
+CONFIG_TI_PRUSS=m
+
+CONFIG_BT=y
+CONFIG_BT_RFCOMM=y
+CONFIG_BT_RFCOMM_TTY=y
+CONFIG_BT_LE=y
+CONFIG_BT_HS=y
+CONFIG_BT_HCIUART=y
+CONFIG_BT_HCIUART_H4=y
+CONFIG_SERIAL_DEV_BUS=y
+CONFIG_BT_HCIUART_LL=y
+
+CONFIG_MAILBOX=y
+CONFIG_OMAP2PLUS_MBOX=y
+CONFIG_SRAM=y
+CONFIG_TI_EMIF_SRAM=m
+CONFIG_WKUP_M3_IPC=m
+CONFIG_AMX3_PM=m
+
+CONFIG_IIO=y
+CONFIG_IIO_BUFFER=y
+CONFIG_TI_AM335X_ADC=y
+CONFIG_FB=y
+CONFIG_PERF_EVENTS=y
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13397): 
https://lists.yoctoproject.org/g/linux-yocto/message/13397
Mute This Topic: https://lists.yoctoproject.org/mt/103048926/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Static library created by recipe arch is not correct #sdk #yocto

2023-12-07 Thread Khem Raj

Can you run file command on libiobb.a it seems its not built for either 
correct architecture or is corrupted in SDK somehow.


It will be good to use AR/RANLIB/CC/CXX variables in your Makefile and 
weakly assign them e.g.


CC ?= cc

AR ?= ar

...


On 12/7/23 4:28 AM, Iurascu Teodor wrote:

Hello,

I have created a recipe to include the IOBB library in the SDK. Trying 
to compile a .c file in the SDK environment gives me this error:


$ ${CC} pb-test-inputs.c -liobb
/opt/poky/4.2.2/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/12.3.0/ld: 
/opt/poky/4.2.2/sysroots/cortexa8hf-neon-poky-linux-gnueabi/usr/local/lib/libiobb.a: 
error adding symbols: file format not recognized


Recipe file:

do_compile () {
    # You will almost certainly need to add additional arguments here
    oe_runmake cc=${CC}
}

do_install () {
    # This is a guess; additional arguments may be required
    oe_runmake install locatie=${D}
    #rm ${D}/usr/local/lib/libiobb.a
}


Makefile:

libiobb.a: ${LIB_PATH}BBBiolib.c ${LIB_PATH}BBBiolib.h 
BBBiolib_PWMSS.o BBBiolib_McSPI.o BBBiolib_ADCTSC.o i2cfunc.o

${cc}-c ${LIB_PATH}BBBiolib.c -o ${LIB_PATH}BBBiolib.o
ar -rs ${LIB_PATH}libiobb.a ${LIB_PATH}BBBiolib.o 
${LIB_PATH}BBBiolib_PWMSS.o ${LIB_PATH}BBBiolib_McSPI.o 
${LIB_PATH}BBBiolib_ADCTSC.o ${LIB_PATH}i2cfunc.o


Thank you!






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61835): https://lists.yoctoproject.org/g/yocto/message/61835
Mute This Topic: https://lists.yoctoproject.org/mt/103032949/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #sdk:https://lists.yoctoproject.org/g/yocto/mutehashtag/sdk
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] initramfs creation

2023-12-07 Thread Khem Raj

On Thu, Dec 7, 2023 at 3:04 AM Ross Burton  wrote:
>
> On 6 Dec 2023, at 21:47, mattwood2000 via lists.yoctoproject.org 
>  wrote:
> >
> >  Hi,
> >
> > I'm trying to create a custom initramfs to handle some things before 
> > switching root to my actual filesystem.  I followed the docs and have been 
> > able to use INITRAMFS_IMAGE = "custom-image" and INITRAMFS_IMAGE_BUNDLE = 
> > "1" to generate a zImage for my ARM platform.
> >
> > The custom-image.bb recipe is based on the core-image-minimal-initramfs 
> > recipe and is in a meta-layer that has another image recipe for the actual 
> > eMMC filesystem image.  Both the eMMC image and initramfs bundle are 
> > created.
> >
> > In custom-image.bb, PACKAGE_INSTALL includes INITRAMFS_SCRIPTS which seem 
> > to be geared towards live-image things but that's not what I want.
> >
> > The image boots but hangs waiting for removable media.  I figured out that 
> > /init is not pointing to systemd but the live-image script from 
> > recipes-core/initrdscripts.
>
> The problem is most likely that your kernel is missing eMMC drivers.  They’re 
> most likely built as kernel modules, but you didn’t install the modules into 
> the initramfs.  One easy fix is to just add kernel-modules to your initramfs.

Right, this is how we tame bbb to include some USB drivers into kernel
proper so that we can read the USB stick in initramfs

https://github.com/YoeDistro/yoe-distro/blob/master/sources/meta-yoe/dynamic-layers/meta-ti/recipes-kernel/linux/files/updater.cfg

>
> I do have some tweaks to the initramfs images to post, but they’re not quite 
> ready yet. You can see the WIP in poky-contrib:ross/genericarm64.
>
> Ross
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61834): https://lists.yoctoproject.org/g/yocto/message/61834
Mute This Topic: https://lists.yoctoproject.org/mt/103022933/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [PATCH yocto-autobuilder-helper] script/run-toaster-test : Added new global variables needed to run test in toaster build folder

2023-12-07 Thread Marlon Rodriguez Garcia



- Original Message -
From: "Marlon Rodriguez Garcia" 
To: yocto@lists.yoctoproject.org
Sent: Thursday, December 7, 2023 4:08:34 PM
Subject: [PATCH yocto-autobuilder-helper] script/run-toaster-test : Added new 
global variables needed to run test in toaster build folder

Update run-toaster-test to include BUILDDIR and TOASTER_TEST_USE_SSTATE_MIRROR 
which will be use in the build test in toaster

Signed-off-by: Marlon Rodriguez Garcia 

---
 scripts/run-toaster-tests | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/scripts/run-toaster-tests b/scripts/run-toaster-tests
index b694e37..ba1f6db 100755
--- a/scripts/run-toaster-tests
+++ b/scripts/run-toaster-tests
@@ -20,6 +20,8 @@ export SSTATE_DIR=$(grep '^SSTATE_DIR=' bbenv | cut -d "=" 
-f2- | sed -e 's/^"//
 export DL_DIR=$(grep '^DL_DIR=' bbenv | cut -d "=" -f2- | sed -e 's/^"//' -e 
's/"$//')
 export TOASTER_DJANGO_TMPDIR=$builddir
 export TOASTER_DIR=$builddir
+export TOASTER_TEST_USE_SSTATE_MIRROR=True
+export BUILDDIR=$builddir/
 
 mkdir -p toaster_logs
 
-- 
2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61833): https://lists.yoctoproject.org/g/yocto/message/61833
Mute This Topic: https://lists.yoctoproject.org/mt/103043812/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [PATCH yocto-autobuilder-helper] script/run-toaster-test : Added new global variables needed to run test in toaster build folder

2023-12-07 Thread Marlon Rodriguez Garcia

Update run-toaster-test to include BUILDDIR and TOASTER_TEST_USE_SSTATE_MIRROR 
which will be use in the build test in toaster

Signed-off-by: Marlon Rodriguez Garcia 

---
 scripts/run-toaster-tests | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/scripts/run-toaster-tests b/scripts/run-toaster-tests
index b694e37..ba1f6db 100755
--- a/scripts/run-toaster-tests
+++ b/scripts/run-toaster-tests
@@ -20,6 +20,8 @@ export SSTATE_DIR=$(grep '^SSTATE_DIR=' bbenv | cut -d "=" 
-f2- | sed -e 's/^"//
 export DL_DIR=$(grep '^DL_DIR=' bbenv | cut -d "=" -f2- | sed -e 's/^"//' -e 
's/"$//')
 export TOASTER_DJANGO_TMPDIR=$builddir
 export TOASTER_DIR=$builddir
+export TOASTER_TEST_USE_SSTATE_MIRROR=True
+export BUILDDIR=$builddir/
 
 mkdir -p toaster_logs
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61832): https://lists.yoctoproject.org/g/yocto/message/61832
Mute This Topic: https://lists.yoctoproject.org/mt/103043812/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [yocto-kernel-cache yocto-5.15] enable NVME kernel config for marvell cn102xx

2023-12-07 Thread Bruce Ashfield

In message: [linux-yocto] [yocto-kernel-cache yocto-5.15] enable NVME kernel 
config for marvell cn102xx
on 07/12/2023 Ruiqiang Hao wrote:

> Hi Bruce,
> 
> Please help to merge code into our linux-yocto repo.
> 
> repo:
>   yocto-kernel-cache

merged.

Bruce

> branch:
>   yocto-5.15
> 
> Thanks,
> Ruiqiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13396): 
https://lists.yoctoproject.org/g/linux-yocto/message/13396
Mute This Topic: https://lists.yoctoproject.org/mt/103031448/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/linux-yocto/leave/6687884/21656/624485779/xyzzy
 [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Static library created by recipe arch is not correct #yocto #sdk

2023-12-07 Thread Ross Burton

On 7 Dec 2023, at 13:35, Iurascu Teodor via lists.yoctoproject.org 
 wrote:
> Running file on any object files in the archive returns:
> $ file BBBiolib.o  
> BBBiolib.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped

Well that’s not right. :)

I note that your makefile doesn’t have any clean functionalty, so it’s entirely 
possible that it’s reusing previous binaries from when cc wasn’t set correctly. 
Adding a ‘clean’ target that deletes all built files from the build tree would 
be a good idea.

You can test this theory by doing bitbake -C unpack bbio (assuming your recipe 
is called bbio) to force it to rebuild the recipe, and then rebuilding your SDK.

Also have a look at the log.do_compile in the recipe build directory to check 
it actually is using the arm cross compiler.

I’ll note that Makefiles are hard and if you’re writing your own makefile it’s 
good to use something else instead.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61831): https://lists.yoctoproject.org/g/yocto/message/61831
Mute This Topic: https://lists.yoctoproject.org/mt/103032949/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #sdk:https://lists.yoctoproject.org/g/yocto/mutehashtag/sdk
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Static library created by recipe arch is not correct #yocto #sdk

2023-12-07 Thread Iurascu Teodor

Thanks for the reply Ross!

This is the whole Makefile:

LIB_PATH = ./BBBio_lib/
DEMO_PATH = ./Demo/
TOOLKIT_PATH = ./Toolkit/
LAB_PATH = ./Lab/

LIBRARIES = iobb

cc ="gcc"

all : libiobb.a LED ADT7301 SEVEN_SCAN SMOTOR LED_GPIO DEBOUNCING 4x4keypad ADC 
ADC_VOICE GPIO_STATUS EP_STATUS ADC_CALC lcd3-test test-outputs pb-test-outputs 
test-inputs pb-test-inputs

libiobb.a : ${ LIB_PATH } BBBiolib.c ${ LIB_PATH } BBBiolib.h BBBiolib_PWMSS.o 
BBBiolib_McSPI.o BBBiolib_ADCTSC.o i2cfunc.o
${ cc } -c ${ LIB_PATH } BBBiolib.c -o ${ LIB_PATH } BBBiolib.o
ar -rs ${ LIB_PATH } libiobb.a ${ LIB_PATH } BBBiolib.o ${ LIB_PATH } 
BBBiolib_PWMSS.o ${ LIB_PATH } BBBiolib_McSPI.o ${ LIB_PATH } BBBiolib_ADCTSC.o 
${ LIB_PATH } i2cfunc.o
cp ${ LIB_PATH } libiobb.a ./
cp ${ LIB_PATH } BBBiolib.h ./iobb.h
cp ${ LIB_PATH } BBBiolib_ADCTSC.h ./
cp ${ LIB_PATH } BBBiolib_McSPI.h ./
cp ${ LIB_PATH } BBBiolib_PWMSS.h ./
cp ${ LIB_PATH } i2cfunc.h ./

BBBiolib_PWMSS.o : ${ LIB_PATH } BBBiolib_PWMSS.c ${ LIB_PATH } BBBiolib_PWMSS.h
${ cc } -c ${ LIB_PATH } BBBiolib_PWMSS.c -o ${ LIB_PATH } BBBiolib_PWMSS.o -W

BBBiolib_McSPI.o : ${ LIB_PATH } BBBiolib_McSPI.c ${ LIB_PATH } BBBiolib_PWMSS.h
${ cc } -c ${ LIB_PATH } BBBiolib_McSPI.c -o ${ LIB_PATH } BBBiolib_McSPI.o -W

BBBiolib_ADCTSC.o : ${ LIB_PATH } BBBiolib_ADCTSC.c ${ LIB_PATH } 
BBBiolib_ADCTSC.h
${ cc } -c ${ LIB_PATH } BBBiolib_ADCTSC.c -o ${ LIB_PATH } BBBiolib_ADCTSC.o -W

i2cfunc.o : ${ LIB_PATH } i2cfunc.c ${ LIB_PATH } i2cfunc.h
${ cc } -c ${ LIB_PATH } i2cfunc.c -o ${ LIB_PATH } i2cfunc.o

install :
ifndef locatie
$( info locatie is [${ locatie }])
rm -f /usr/local/include/BBBiolib.h
cp ${ LIB_PATH } libiobb.a /usr/local/lib
cp ${ LIB_PATH } BBBiolib.h /usr/local/include/iobb.h
cp ${ LIB_PATH } BBBiolib_ADCTSC.h /usr/local/include
cp ${ LIB_PATH } BBBiolib_McSPI.h /usr/local/include
cp ${ LIB_PATH } BBBiolib_PWMSS.h /usr/local/include
cp ${ LIB_PATH } i2cfunc.h /usr/local/include
ln -s /usr/local/include/iobb.h /usr/local/include/BBBiolib.h
else
$( info locatie is [${ locatie }])
rm -f $( locatie ) /usr/local/include/BBBiolib.h
mkdir -p $( locatie ) /usr/local/lib
mkdir -p $( locatie ) /usr/local/include
cp ${ LIB_PATH } libiobb.a $( locatie ) /usr/local/lib
cp ${ LIB_PATH } BBBiolib.h $( locatie ) /usr/local/include/iobb.h
cp ${ LIB_PATH } BBBiolib_ADCTSC.h $( locatie ) /usr/local/include
cp ${ LIB_PATH } BBBiolib_McSPI.h $( locatie ) /usr/local/include
cp ${ LIB_PATH } BBBiolib_PWMSS.h $( locatie ) /usr/local/include
cp ${ LIB_PATH } i2cfunc.h $( locatie ) /usr/local/include
cp $( locatie ) /usr/local/include/iobb.h $( locatie ) 
/usr/local/include/BBBiolib.h
endif

#---
# Demo
#---

test-outputs : test-io/test-outputs.c libiobb.a
${ cc } -o test-outputs test-io/test-outputs.c -I. -L. -liobb

pb-test-outputs : test-io/pb-test-outputs.c libiobb.a
${ cc } -o pb-test-outputs test-io/pb-test-outputs.c -I. -L. -liobb

test-inputs : test-io/test-inputs.c libiobb.a
${ cc } -o test-inputs test-io/test-inputs.c -I. -L. -liobb

pb-test-inputs : test-io/pb-test-inputs.c libiobb.a
${ cc } -o pb-test-inputs test-io/pb-test-inputs.c -I. -L. -liobb

LED : ${ DEMO_PATH } Demo_LED/LED.c libiobb.a
${ cc } -o LED ${ DEMO_PATH } Demo_LED/LED.c -L ${ LIB_PATH } -liobb

lcd3-test : ${ DEMO_PATH } Demo_I2C/lcd3-test.c libiobb.a
${ cc } -o lcd3-test ${ DEMO_PATH } Demo_I2C/lcd3-test.c -I. -L ${ LIB_PATH } 
-liobb

ADT7301 : ${ DEMO_PATH } Demo_ADT7301/ADT7301.c libiobb.a
${ cc } -o ADT7301 ${ DEMO_PATH } Demo_ADT7301/ADT7301.c -L ${ LIB_PATH } -liobb

ADXL345 : ${ DEMO_PATH } Demo_ADXL345/ADXL345.c libiobb.a
${ cc } -o ADXL345 ${ DEMO_PATH } Demo_ADXL345/ADXL345.c -L ${ LIB_PATH } -liobb
ADXL345_NET : ${ DEMO_PATH } Demo_ADXL345/ADXL345_net.c libiobb.a
${ cc } -o ADXL345 ${ DEMO_PATH } Demo_ADXL345/ADXL345_net.c -L ${ LIB_PATH } 
-liobb

L3G4200D : ${ DEMO_PATH } Demo_L3G4200D/L3G4200D.c libiobb.a
${ cc } -o L3G4200D ${ DEMO_PATH } Demo_L3G4200D/L3G4200D.c -L ${ LIB_PATH } 
-liobb

SEVEN_SCAN : ${ DEMO_PATH } Demo_SevenScan/SevenScan.c libiobb.a
${ cc } -o SevenScan ${ DEMO_PATH } Demo_SevenScan/SevenScan.c -L ${ LIB_PATH } 
-liobb

SMOTOR : ${ DEMO_PATH } Demo_ServoMotor/ServoMotor.c libiobb.a
${ cc } -o SMOTOR ${ DEMO_PATH } Demo_ServoMotor/ServoMotor.c -L ${ LIB_PATH } 
-liobb

LED_GPIO : ${ DEMO_PATH } Demo_LED_GPIO/LED_GPIO.c libiobb.a
${ cc } -o LED_GPIO ${ DEMO_PATH } Demo_LED_GPIO/LED_GPIO.c -L ${ LIB_PATH } 
-liobb -pthread

DEBOUNCING : ${ DEMO_PATH } Demo_Debouncing/Debouncing.c libiobb.a
${ cc } -o Debouncing ${ DEMO_PATH } Demo_Debouncing/Debouncing.c -L ${ 
LIB_PATH } -liobb

4x4keypad : ${ DEMO_PATH } Demo_4x4keypad/4x4keypad.c libiobb.a
${ cc } -o 4x4keypad ${ DEMO_PATH } Demo_4x4keypad/4x4keypad.c -L ${ LIB_PATH } 
-liobb

PWM : ${ DEMO_PATH } Demo_PWM/PWM.c libiobb.a
${ cc } -o PWM ${ DEMO_PATH } Demo_PWM/PWM.c -L ${ LIB_PATH } -liobb

ADC : ${ DEMO_PATH } Demo_ADC/ADC.c

Re: [yocto] Static library created by recipe arch is not correct #sdk #yocto

2023-12-07 Thread Ross Burton

On 7 Dec 2023, at 12:28, Iurascu Teodor via lists.yoctoproject.org 
 wrote:
> 
> Hello,
> 
> I have created a recipe to include the IOBB library in the SDK. Trying to 
> compile a .c file in the SDK environment gives me this error:
> 
> $ ${CC} pb-test-inputs.c -liobb 
> /opt/poky/4.2.2/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/12.3.0/ld:
>  
> /opt/poky/4.2.2/sysroots/cortexa8hf-neon-poky-linux-gnueabi/usr/local/lib/libiobb.a:
>  error adding symbols: file format not recognized
> 
> Recipe file:
> 
> do_compile () {
> # You will almost certainly need to add additional arguments here
> oe_runmake cc=${CC}
> }
> 
> do_install () {
> # This is a guess; additional arguments may be required
> oe_runmake install locatie=${D}
> #rm ${D}/usr/local/lib/libiobb.a
> }
> 
> 
> Makefile:
> 
> libiobb.a : ${LIB_PATH}BBBiolib.c ${LIB_PATH}BBBiolib.h BBBiolib_PWMSS.o 
> BBBiolib_McSPI.o BBBiolib_ADCTSC.o i2cfunc.o
> ${cc} -c ${LIB_PATH}BBBiolib.c -o ${LIB_PATH}BBBiolib.o
> ar -rs ${LIB_PATH}libiobb.a ${LIB_PATH}BBBiolib.o ${LIB_PATH}BBBiolib_PWMSS.o 
> ${LIB_PATH}BBBiolib_McSPI.o ${LIB_PATH}BBBiolib_ADCTSC.o ${LIB_PATH}i2cfunc.o

That’s not the whole makefile, can you verify that it’s actually using ${CC} 
and not gcc in every build step?

Run file on the libiobb.a to verify it contains what you expect.

Also install the library to ${D}${libdir}, /usr/local/ is for non-managed files 
and by writing a recipe it’s managed.

I also note that iobb is long-dead so there might be a better alternative now.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61829): https://lists.yoctoproject.org/g/yocto/message/61829
Mute This Topic: https://lists.yoctoproject.org/mt/103032949/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #sdk:https://lists.yoctoproject.org/g/yocto/mutehashtag/sdk
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Static library created by recipe arch is not correct #sdk #yocto

2023-12-07 Thread Iurascu Teodor

Hello,

I have created a recipe to include the IOBB library in the SDK. Trying to 
compile a .c file in the SDK environment gives me this error:

$ ${CC} pb-test-inputs.c -liobb
/opt/poky/4.2.2/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/12.3.0/ld:
 
/opt/poky/4.2.2/sysroots/cortexa8hf-neon-poky-linux-gnueabi/usr/local/lib/libiobb.a:
 error adding symbols: file format not recognized

Recipe file:

do_compile () {
# You will almost certainly need to add additional arguments here
oe_runmake cc=${CC}
}

do_install () {
# This is a guess; additional arguments may be required
oe_runmake install locatie=${D}
#rm ${D}/usr/local/lib/libiobb.a
}

Makefile:

libiobb.a : ${ LIB_PATH } BBBiolib.c ${ LIB_PATH } BBBiolib.h BBBiolib_PWMSS.o 
BBBiolib_McSPI.o BBBiolib_ADCTSC.o i2cfunc.o
${ cc } -c ${ LIB_PATH } BBBiolib.c -o ${ LIB_PATH } BBBiolib.o
ar -rs ${ LIB_PATH } libiobb.a ${ LIB_PATH } BBBiolib.o ${ LIB_PATH } 
BBBiolib_PWMSS.o ${ LIB_PATH } BBBiolib_McSPI.o ${ LIB_PATH } BBBiolib_ADCTSC.o 
${ LIB_PATH } i2cfunc.o

Thank you!

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61828): https://lists.yoctoproject.org/g/yocto/message/61828
Mute This Topic: https://lists.yoctoproject.org/mt/103032949/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #sdk:https://lists.yoctoproject.org/g/yocto/mutehashtag/sdk
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] The postinstall intercept hook 'update_mime_database' failed

2023-12-07 Thread Mans Zigher

Yes, thanks. I am currently doing that but I am struggling to
understand where to look. From what I can tell the layers are not on
an official kirkstone release, not sure the reason for this. It is
based on a imx-5.15.71-2.2.0.xml release but then the layers have been
moved to a different sha. I have been able to build the
imx-5.15.71-2.2.0.xml from scratch but right now the customer would
like to be able to build the current setup. But I will continue to
work on it. The reference build still builds so it is just when trying
to duplicate the build and building from scratch.

/Måns

Den fre 1 dec. 2023 kl 13:20 skrev Alexander Kanavin :
>
> You need to try plain poky then because the error does not happen
> there. Then figure out where the difference is.
>
> Alex
>
> On Fri, 1 Dec 2023 at 12:56, Mans Zigher  wrote:
> >
> > I have now tried building a multitude of different machines and
> > switched to core-minimal-image and still I get these postinstall
> > intercept scripts failing. Depending what distro and machine I build I
> > get different errors but It is always a postinstall intercept hook
> > script that fails and it is always related to missing some directory
> > under the rootfs of the image that I am currently trying to build.
> >
> > BR
> >
> > Den tors 30 nov. 2023 kl 19:11 skrev Måns :
> > >
> > > Hi,
> > >
> > > I have taken over a imx8mm project that is based on kirkstone. I don't
> > > think it is an official release and some layers are not even a
> > > kirkstone release. The project has a reference build but currently it
> > > is not possible to build from scratch. I have been fixing some issues
> > > on the way to try and build a complete build from scratch but now I
> > > have encountered an issue when creating the rootfs that I am
> > > struggling with. The issues that I am getting is
> > >
> > > ERROR: fsl-image-gui-1.0-r0 do_rootfs: The postinstall intercept hook
> > > 'update_mime_database' failed, details in
> > > /workspace/mender-imx8mm/builds/tmp/work/imx8mm_var_dart-fslc-linux/fsl-image-gui/1.0-r0/temp/log.do_rootfs
> > > ERROR: Logfile of failure stored in:
> > > /workspace/mender-imx8mm/builds/tmp/work/imx8mm_var_dart-fslc-linux/fsl-image-gui/1.0-r0/temp/log.do_rootfs.335539
> > > ERROR: Task 
> > > (/workspace/mender-imx8mm/sources/meta-variscite-sdk/recipes-fsl/images/fsl-image-gui.bb:do_rootfs)
> > > failed with exit code '1'
> > >
> > > checking the log file
> > >
> > > NOTE: Running intercept scripts:
> > > NOTE: > Executing update_mime_database intercept ...
> > > NOTE: Exit code 1. Output:
> > > Updating MIME database... this may take a while.
> > > Directory 
> > > '/workspace/mender-imx8mm/builds/tmp/work/imx8mm_var_dart-fslc-linux/fsl-image-gui/1.0-r0/rootfs/packages'
> > > does not exist!
> > >
> > > In poky/meta/classes/mime.bbclass there is a comment that seems to
> > > refer to this issue
> > >
> > > # $D${MIMEDIR}/packages belong to package shared-mime-info-data,
> > > # packages like libfm-mime depend on shared-mime-info-data.
> > > # after shared-mime-info-data uninstalled, $D${MIMEDIR}/packages
> > > # is removed, but update-mime-database need this dir to update
> > > # database, workaround to create one and remove it later
> > > if [ ! -d $D${MIMEDIR}/packages ]; then
> > >mkdir -p $D${MIMEDIR}/packages
> > >update-mime-database $D${MIMEDIR}
> > >rmdir --ignore-fail-on-non-empty $D${MIMEDIR}/packages
> > >else
> > >update-mime-database $D${MIMEDIR}
> > >fi
> > >
> > > This is not called so no packages directory doesn't exist and the
> > > intercept script failed. I can adjust the script
> > > poky/scripts/postinst-intercepts/update_mime_database
> > >
> > > echo "Updating MIME database... this may take a while."
> > > update-mime-database $D${mimedir}
> > >
> > > By adding a similar logic I will get forward but with my build but
> > > that doesn't seem like the right solution. Also I just get some other
> > > issue related to a second intercept script update_desktop_database so
> > > to me it seems more like something is not correctly set up in the
> > > build. I am trying to understand how these intercept scripts are
> > > configured and why they are not working for my build. Any pointers on
> > > how to move forward would be much appreciated.
> > >
> > > BR
> >
> > 
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61827): https://lists.yoctoproject.org/g/yocto/message/61827
Mute This Topic: https://lists.yoctoproject.org/mt/102901287/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] How to handle user network configuration on a OTA environment

2023-12-07 Thread Josef Holzmayr

Hi Renato,

I would suggest to start with the tutorial we have exactly for this usecase
here:
https://hub.mender.io/t/how-to-configure-networking-using-systemd-in-yocto-project/1097.
Once you have it replicated and working, add and modify the bits and pieces
that are specific to your requirements.

Greetz,
Josef

On Wed, Dec 6, 2023 at 10:49 PM Renato Mendes 
wrote:

> Using a Raspberry Pi Zero W, I have build an image with the following
> layers:
>
> # POKY_BBLAYERS_CONF_VERSION is increased each time
> build/conf/bblayers.conf
> # changes incompatibly
> POKY_BBLAYERS_CONF_VERSION = "2"
>
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
>
> BBLAYERS ?= " \
> /home/release_1/src/poky/meta \
> /home/release_1/src/poky/meta-poky \
> /home/release_1/src/poky/meta-yocto-bsp \
> /home/release_1/src/meta-openembedded/meta-oe \
> /home/release_1/src/meta-openembedded/meta-python \
> /home/release_1/src/meta-openembedded/meta-multimedia \
> /home/release_1/src/meta-openembedded/meta-networking \
> /home/release_1/src/meta-raspberrypi \
> /home/release_1/src/meta-mender/meta-mender-core \
> /home/release_1/src/meta-mender/meta-mender-raspberrypi \
> "
>
> I'm using Mender for OTA.
>
> The image is fine and runs Yocto Distro at my Raspi.
>
> As this is my first project using OTA, I'm now about to setup networking.
> I've build a custom captive portal using Nodejs what will allow user to
> choose the WiFi network.
>
> Here is the logic I need:
> a) If there is network configuration stored (in a file, ie), device goes
> to Access Point mode with fixed IP (ex: 192.168.0.1). Then the user will
> connect, choose WiFi network and save it to a file
>
> b) If there is WiFi configuration, will connect automatically
>
> c) If user reset the device (a physical push button), the WiFi
> configuration is erased and device goes back to (a) mode
>
> My questions are how to exactly handle the desired scenario. My doubts:
>
> a) How will the device knows on boot if there is a network configuration
> file to load
>
> b) How can the device choose between AP ou WiFi mode based on the
> existance of the given file
>
> c) How will this file behave on a OTA update (Mender.io says, must be
> stored at /media/ directory to be preserved on updates)
>
> Thanks for helping... I've read several different articles for some days
> and I'm very confused on where to start from...
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61826): https://lists.yoctoproject.org/g/yocto/message/61826
Mute This Topic: https://lists.yoctoproject.org/mt/103022968/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [RFC PATCH 0/1] lts mixin: kirkstone/nodejs proposal

2023-12-07 Thread Jose Quaresma

António Oliveira  escreveu no dia terça, 5/12/2023 à(s)
18:26:

> On Tue, Dec 5, 2023 at 10:44 AM Jose Quaresma 
> wrote:
> >
> >
> >
> > António Oliveira  escreveu no dia segunda,
> 4/12/2023 à(s) 18:31:
> >>
> >> Hi all,
> >>
> >> This patch contains my proposal for an mixin layer that adds nodejs v18
> >> and v20 to kirkstone.
> >>
> >> Kirkstone ships with nodejs-16, whose maintenance window ended in
> >> October 2023 (a).
> >>
> >> Kirkstone will be supported until April 2026 and it would be nice to
> have
> >> some level of support for a maintained version of nodejs during that
> time
> >> window.
> >>
> >> This proposal seeks to address that by adding nodejs-18 and nodejs-20,
> >> which will be maintained until April 2025 and 2026, respectively.
> >>
> >> The recipes for nodejs-18 are taken from Mickledore and the recipes for
> >> nodejs-20 from master.
> >>
> >> The variable NODE_VERSION can be ser in local.conf to choose either v18
> >> or v20 (the default).
> >>
> >> This is my first attempt at sending a patch upstream with git send-email
> >> so any comments or suggestions for improvement are welcome. That's also
> >> the reason why I marked this as an RFC.
> >
> >
> > Hi Antonio,
> >
> > If the patchset was made with more and smaller commits it would make the
> review easier
> > but it is perfect in my opinion with the context well explained.
> > The git send-mail is much simpler than it seems.
> > Thanks for your contributions.
>
> I thought of that but couldn't really settle for something.
>
> I guess I can break it down into smaller pieces, like:
> * layer config, license, readme...
> * nodejs-18
> * nodejs-20
> * setting the choice of node version in layer.conf.
>
> Would that work?
>

It will be better in my opinion but not strictly necessary.

Jose


>
> I can break
> >
> > Jose
> >
> >>
> >>
> >> Cheers,
> >> António
> >>
> >> António Oliveira (1):
> >>   initial commit
> >>
> >> --
> >> 2.34.1
> >>
> >>
> >> 
> >>
> >
> >
> > --
> > Best regards,
> >
> > José Quaresma
>


-- 
Best regards,

José Quaresma

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61825): https://lists.yoctoproject.org/g/yocto/message/61825
Mute This Topic: https://lists.yoctoproject.org/mt/102976461/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] initramfs creation

2023-12-07 Thread Ross Burton

On 6 Dec 2023, at 21:47, mattwood2000 via lists.yoctoproject.org 
 wrote:
> 
>  Hi,
> 
> I'm trying to create a custom initramfs to handle some things before 
> switching root to my actual filesystem.  I followed the docs and have been 
> able to use INITRAMFS_IMAGE = "custom-image" and INITRAMFS_IMAGE_BUNDLE = "1" 
> to generate a zImage for my ARM platform.
> 
> The custom-image.bb recipe is based on the core-image-minimal-initramfs 
> recipe and is in a meta-layer that has another image recipe for the actual 
> eMMC filesystem image.  Both the eMMC image and initramfs bundle are created.
> 
> In custom-image.bb, PACKAGE_INSTALL includes INITRAMFS_SCRIPTS which seem to 
> be geared towards live-image things but that's not what I want.
> 
> The image boots but hangs waiting for removable media.  I figured out that 
> /init is not pointing to systemd but the live-image script from 
> recipes-core/initrdscripts.

The problem is most likely that your kernel is missing eMMC drivers.  They’re 
most likely built as kernel modules, but you didn’t install the modules into 
the initramfs.  One easy fix is to just add kernel-modules to your initramfs.

I do have some tweaks to the initramfs images to post, but they’re not quite 
ready yet. You can see the WIP in poky-contrib:ross/genericarm64.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61824): https://lists.yoctoproject.org/g/yocto/message/61824
Mute This Topic: https://lists.yoctoproject.org/mt/103022933/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] initramfs creation

2023-12-07 Thread Zoran

Please, read carefully thru this yocto @ thread.

https://www.yoctoproject.org/pipermail/yocto/2018-July/041680.html

I hope this does help.

Zee
___

On Wed, Dec 6, 2023 at 10:47 PM  wrote:
>
>  Hi,
>
> I'm trying to create a custom initramfs to handle some things before 
> switching root to my actual filesystem.  I followed the docs and have been 
> able to use INITRAMFS_IMAGE = "custom-image" and INITRAMFS_IMAGE_BUNDLE = "1" 
> to generate a zImage for my ARM platform.
>
> The custom-image.bb recipe is based on the core-image-minimal-initramfs 
> recipe and is in a meta-layer that has another image recipe for the actual 
> eMMC filesystem image.  Both the eMMC image and initramfs bundle are created.
>
> In custom-image.bb, PACKAGE_INSTALL includes INITRAMFS_SCRIPTS which seem to 
> be geared towards live-image things but that's not what I want.
>
> The image boots but hangs waiting for removable media.  I figured out that 
> /init is not pointing to systemd but the live-image script from 
> recipes-core/initrdscripts.
>
> For testing I manually symlinked systemd to /init and the board boots but it 
> wants a login password which was never created, I'm guessing its not 
> inheriting debug-tweaks from my local.conf?
>
> So my question is, what is the correct way to create a minimal initramfs 
> image along side the real recipe/image within a meta-layer?
>
> Does anyone have an example of doing this?
>
> Thanks, Matt.
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61823): https://lists.yoctoproject.org/g/yocto/message/61823
Mute This Topic: https://lists.yoctoproject.org/mt/103022933/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [yocto-kernel-cache yocto-5.15] enable NVME kernel config for marvell cn102xx

2023-12-07 Thread Ruiqiang Hao via lists.yoctoproject.org

Hi Bruce,

Please help to merge code into our linux-yocto repo.

repo:
yocto-kernel-cache
branch:
yocto-5.15

Thanks,
Ruiqiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13395): 
https://lists.yoctoproject.org/g/linux-yocto/message/13395
Mute This Topic: https://lists.yoctoproject.org/mt/103031448/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH] marvell-cn10xxx: enable NVME config for cn102xx

2023-12-07 Thread Ruiqiang Hao via lists.yoctoproject.org

From: Ruiqiang Hao 

The Marvell cn102xx board has an NVME interface, so we should enable the
NVME kernel configuration for this BSP.

Signed-off-by: Ruiqiang Hao 
---
 bsp/marvell-cn106xx/marvell-cn106xx.cfg | 4 
 1 file changed, 4 insertions(+)

diff --git a/bsp/marvell-cn106xx/marvell-cn106xx.cfg 
b/bsp/marvell-cn106xx/marvell-cn106xx.cfg
index 5503d3fd..a33e17b0 100644
--- a/bsp/marvell-cn106xx/marvell-cn106xx.cfg
+++ b/bsp/marvell-cn106xx/marvell-cn106xx.cfg
@@ -173,6 +173,10 @@ CONFIG_ARM_SMMU_V3_PMU=y
 CONFIG_MARVELL_CN10K_TAD_PMU=y
 CONFIG_MARVELL_CN10K_DDR_PMU=y
 
+# NVME
+CONFIG_NVME_CORE=y
+CONFIG_BLK_DEV_NVME=y
+
 # Currently this driver only work for cn96xx, but it is set to 'm' by default.
 # So we have to disable it explicitly.
 # CONFIG_OCTEONTX_SERDES is not set
-- 
2.35.5


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13394): 
https://lists.yoctoproject.org/g/linux-yocto/message/13394
Mute This Topic: https://lists.yoctoproject.org/mt/103031447/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Regarding Complete Yocto source transfer/migration from one ubuntu machine to other

2023-12-07 Thread Poornesh G ( India - Bangalore )

Greetings !

I am new here , I have setup the Yocto source (dunfell) for AM335x SoC. Now I 
need to set up the same source copy in my remote location .But there internet 
is prohibited hence I cannot able to initiate the fresh build. So I am trying 
the copy the entire working source to the PC where there is no internet .
Is doing copy of the yocto source from one ubuntu machine to other ubuntu 
machine is recommended ? If not please help me with the suggestions that how I 
can setup the same copy without internet.

Thanks in advance

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61822): https://lists.yoctoproject.org/g/yocto/message/61822
Mute This Topic: https://lists.yoctoproject.org/mt/103031410/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-mingw][Honister] runqemu Command in SDK Generated by meta-mingw for Windows Host

2023-12-07 Thread Nicolas Wirth via lists.yoctoproject.org

Dear Yocto Community,

I hope this message finds you well.

I'm currently exploring the possibilities of using the SDK generated by 
meta-mingw for a Windows-based host environment. I'd like to inquire whether 
it's feasible to have the 'runqemu' command functionality within this SDK.

Is there a known method or workaround to implement 'runqemu' functionality in 
the SDK tailored for a Windows host using meta-mingw?

This is the list of my current qemu tools available on my Windows host:
08/03/2022 13:58 314’481 qemu-edid.exe 08/03/2022 13:58 2’115’186 qemu-ga.exe 
08/03/2022 13:58 11’027’778 qemu-img.exe 08/03/2022 13:58 10’805’911 
qemu-io.exe 08/03/2022 13:58 11’557’686 qemu-nbd.exe 08/03/2022 13:58 
13’021’015 qemu-storage-daemon.exe 08/03/2022 13:58 100’200’820 
qemu-system-aarch64.exe 08/03/2022 13:58 100’200’820 qemu-system-aarch64w.exe 
08/03/2022 13:58 80’779’407 qemu-system-arm.exe 08/03/2022 13:58 80’779’407 
qemu-system-armw.exe 08/03/2022 13:58 44’318’247 qemu-system-microblaze.exe 
08/03/2022 13:58 52’717’763 qemu-system-microblazeel.exe 08/03/2022 13:58 
52’717’763 qemu-system-microblazeelw.exe 08/03/2022 13:58 44’318’247 
qemu-system-microblazew.exe 08/03/2022 13:58 63’534’183 qemu-system-x86_64.exe 
08/03/2022 13:58 63’534’183 qemu-system-x86_64w.exe

Any insights, guidance, or previous experiences on this matter would be greatly 
appreciated.

Thank you for your time and assistance.

Best regards,
Nicolas Wirth

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61821): https://lists.yoctoproject.org/g/yocto/message/61821
Mute This Topic: https://lists.yoctoproject.org/mt/103030707/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [ANNOUNCEMENT] Yocto Project 4.3.1 is Released

[yocto] bitbake error need help #kernel #yocto

[linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am335x: add preempt-rt support and boards full features support

Re: [yocto] Static library created by recipe arch is not correct #sdk #yocto

Re: [yocto] initramfs creation

Re: [yocto] [PATCH yocto-autobuilder-helper] script/run-toaster-test : Added new global variables needed to run test in toaster build folder

[yocto] [PATCH yocto-autobuilder-helper] script/run-toaster-test : Added new global variables needed to run test in toaster build folder

Re: [linux-yocto] [yocto-kernel-cache yocto-5.15] enable NVME kernel config for marvell cn102xx

Re: [yocto] Static library created by recipe arch is not correct #yocto #sdk

Re: [yocto] Static library created by recipe arch is not correct #yocto #sdk

Re: [yocto] Static library created by recipe arch is not correct #sdk #yocto

[yocto] Static library created by recipe arch is not correct #sdk #yocto

Re: [yocto] The postinstall intercept hook 'update_mime_database' failed

Re: [yocto] How to handle user network configuration on a OTA environment

Re: [yocto] [RFC PATCH 0/1] lts mixin: kirkstone/nodejs proposal

Re: [yocto] initramfs creation

Re: [yocto] initramfs creation

[linux-yocto] [yocto-kernel-cache yocto-5.15] enable NVME kernel config for marvell cn102xx

[linux-yocto] [PATCH] marvell-cn10xxx: enable NVME config for cn102xx

[yocto] Regarding Complete Yocto source transfer/migration from one ubuntu machine to other

[yocto] [meta-mingw][Honister] runqemu Command in SDK Generated by meta-mingw for Windows Host

21 matches

Site Navigation

Mail list logo

Footer information