|
Using FreeRadius project on Yocto
Rakesh Kumar <rakeshkumar0815@...>
Hi Team, I am trying to build radius server with the use of Yocto project and looks like freeradius recipe is already included in meta-openembedded/meta-networking/recipes-connectivity/freeradius I have included meta-openembedded layer in my conf/bblayers.conf file and built core-image-base image. But I couldn't see anything related to radius server in my <workspace>/tmp directory "tmp/work/ccimx6ul/core-image-base/1.0-r0/rootfs/etc/init.d" Could you please let me know do I need to add anything specific to build radius server apart from using meta-openembedded recipe? I apologize if this is the wrong mailing list. Thanks much! Best Regards Rakesh kumar
|
|
|
|
Yocto BUILD ENV
Monsees, Steven C (US)
I am using a pre-installed tools on my linux development box for centos7, that being devtoolset-8…
Running “source /opt/rh/devtoolset-8/enable” allows me to build my bootapp, kernel, and the standard SDK without issues…, but there seems to be a problem when I go to build the extended SDK.
It appears to end up referencing the wrong/default tool set.
Is the something I need to set in my sdk-extra.conf (or one of the vcarious other configuration files) to make the extended SDK build aware of the environment dependency ?
/opt/rh/devtoolset-8/enable script does the following:
# General environment variables export PATH=/opt/rh/devtoolset-8/root/usr/bin${PATH:+:${PATH}} export MANPATH=/opt/rh/devtoolset-8/root/usr/share/man:${MANPATH} export INFOPATH=/opt/rh/devtoolset-8/root/usr/share/info${INFOPATH:+:${INFOPATH}} export PCP_DIR=/opt/rh/devtoolset-8/root # Some perl Ext::MakeMaker versions install things under /usr/lib/perl5 # even though the system otherwise would go to /usr/lib64/perl5. export PERL5LIB=/opt/rh/devtoolset-8/root//usr/lib64/perl5/vendor_perl:/opt/rh/devtoolset-8/root/usr/lib/perl5:/opt/rh/devtoolset-8/root//usr/share/perl5/vendor_perl${PERL5LIB:+:${PERL5LIB}} # bz847911 workaround: # we need to evaluate rpm's installed run-time % { _libdir }, not rpmbuild time # or else /etc/ld.so.conf.d files? rpmlibdir=$(rpm --eval "%{_libdir}") # bz1017604: On 64-bit hosts, we should include also the 32-bit library path. if [ "$rpmlibdir" != "${rpmlibdir/lib64/}" ]; then rpmlibdir32=":/opt/rh/devtoolset-8/root${rpmlibdir/lib64/lib}" fi export LD_LIBRARY_PATH=/opt/rh/devtoolset-8/root$rpmlibdir$rpmlibdir32${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}} export LD_LIBRARY_PATH=/opt/rh/devtoolset-8/root$rpmlibdir$rpmlibdir32:/opt/rh/devtoolset-8/root$rpmlibdir/dyninst$rpmlibdir32/dyninst${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}} # duplicate python site.py logic for sitepackages pythonvers=2.7 export PYTHONPATH=/opt/rh/devtoolset-8/root/usr/lib64/python$pythonvers/site-packages:/opt/rh/devtoolset-8/root/usr/lib/python$pythonvers/site-packages${PYTHONPATH:+:${PYTHONPATH}} export PKG_CONFIG_PATH=/opt/rh/devtoolset-8/root/usr/lib64/pkgconfig${PKG_CONFIG_PATH:+:${PKG_CONFIG_PATH}}
|
|
|
|
Re: [meta-rockchip] [PATCH v2] trusted-firmware-a: replace baudrate with the one specified in machine conf
On Tue, Dec 14, 2021 at 3:39 AM Quentin Schulz
<quentin.schulz@theobroma-systems.com> wrote: perhaps applying the sed expression via do_configure:prepend() is simple ? and maybe make it rk3399 specific with do_configure:prepend:rk3399 --
|
|
|
|
Yocto Project Status WW50`21
Stephen Jolley
Current Dev Position: YP 3.5 M1 Next Deadline: 6th Dec. 2021 YP 3.5 M1 build
Next Team Meetings:
Key Status/Updates:
Ways to contribute:
YP 3.5 Milestone Dates:
Upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.5_M1.rc2)
Teoh, Jay Shen
Hi everyone,
toggle quoted messageShow quoted text
Intel and WR YP QA is planning for QA execution for YP build yocto-3.5_M1.rc2. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. Beaglebone ETA for completion this Friday, 17th of December. Thanks, Jay
-----Original Message-----
|
|
|
|
Re: echo and read shell script functions in post install script doesn't display messages
Alexander Kanavin
The postinst scriptlets are script fragments and not standalone scripts. Putting an interpreter to their first line will not work. Also, they are not running on an interactive console, but by a helper executor, so they have to be entirely automated. What is the problem that you would like to solve? Alex
On Tue, 14 Dec 2021 at 13:01, <sanjaycvr35412@...> wrote:
|
|
|
|
echo and read shell script functions in post install script doesn't display messages
sanjaycvr35412@...
Hi All,
I am trying to execute a script in “pkg_postinst_ontarget_${PN}” to configure the static IP address of the embedded board. The script executes at first boot, but it doesn’t display echo or read messages. These messages are required to improve user experience with the setup process.
Script is as below: pkg_postinst_ontarget_${PN} () { #!/bin/sh -e # This will run on first boot echo "Starting setup script..."
read -p "Enter the IP address: " ipAddress read -p "Enter the netmask: " netmask read -p "Enter network gateway: " gateway
cat >> /etc/network/interfaces << EOF
iface eth0 inet static address $ipAddress netmask $netmask gateway $gateway EOF }
Please help me to fix the problem in displaying echo and read messages to improve user experience with the setup process.
Thanks, Sanjay Kumar
|
|
|
|
Re: [PATCH v2] trusted-firmware-a: replace baudrate with the one specified in machine conf
Quentin Schulz
Sorry, this was meant for meta-rockchip, sending a new mail with the
toggle quoted messageShow quoted text
proper topic. Cheers, Quentin
On Tue, Dec 14, 2021 at 10:50:18AM +0100, Quentin Schulz wrote:
Not all Rockchip boards have their console running at 1500000 baud in
|
|
|
|
[meta-rockchip] [PATCH v2] trusted-firmware-a: replace baudrate with the one specified in machine conf
Quentin Schulz
Not all Rockchip boards have their console running at 1500000 baud in
U-Boot and the kernel. Such is the case for puma-haikou RK3399-based SoM+Carrierboard. In order to prepare for the addition of puma-haikou to meta-rockchip, let's replace the baudrate in TF-A by the one defined in the machine conf file in the RK_CONSOLE_BAUD variable. Cc: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> --- v2: use a less restrictive regular expression .../files/serial-console-baudrate.patch | 36 ------------------- .../trusted-firmware-a_%.bbappend | 6 +++- 2 files changed, 5 insertions(+), 37 deletions(-) delete mode 100644 recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch diff --git a/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch b/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch deleted file mode 100644 index 2d6e9bf..0000000 --- a/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch +++ /dev/null @@ -1,36 +0,0 @@ -From 840d6b6420e1fd8cdf6e4de7fa58a6f8de151622 Mon Sep 17 00:00:00 2001 -From: Yann Dirson <yann@blade-group.com> -Date: Tue, 6 Apr 2021 17:28:45 +0200 -Subject: [PATCH] Set serial console baudrate back to 1500000. -Upstream-Status: Inappropriate[other] - -TF-A runs between two u-boot stages which both uses 1500000 baud, it -just makes no sense to use the same UART at a different rate. - -This effectively reverts part of 0c05748bdebfad9fa43a80962186438bb8fbce62. -Main reason for that change stated in https://developer.trustedfirmware.org/T762 -is ChromeOS compatibility. - -Looks like this patch may become unnecessary in the future, when -u-boot and TF-A get to communicate this value. - ---- - plat/rockchip/rk3399/rk3399_def.h | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/plat/rockchip/rk3399/rk3399_def.h b/plat/rockchip/rk3399/rk3399_def.h -index ba83242eb..8d6ecfbe6 100644 ---- a/plat/rockchip/rk3399/rk3399_def.h -+++ b/plat/rockchip/rk3399/rk3399_def.h -@@ -17,7 +17,7 @@ - /************************************************************************** - * UART related constants - **************************************************************************/ --#define RK3399_BAUDRATE 115200 -+#define RK3399_BAUDRATE 1500000 - #define RK3399_UART_CLOCK 24000000 - - /****************************************************************************** --- -2.30.2 - diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend index 513cea1..07fae1e 100644 --- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend +++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend @@ -7,7 +7,6 @@ COMPATIBLE_MACHINE:append:rk3328 = "|rk3328" FILESEXTRAPATHS:prepend := "${THISDIR}/files:" SRC_URI += "\ - file://serial-console-baudrate.patch \ file://0001-dram-Fix-build-with-gcc-11.patch \ file://0001-plat_macros.S-Use-compatible-.asciz-asm-directive.patch \ file://0001-pmu-Do-not-mark-already-defined-functions-as-weak.patch \ @@ -19,3 +18,8 @@ SRC_URI += "\ # this needs fixing until then use gcc TOOLCHAIN:rk3399 = "gcc" +fixup_rk3399_baudrate() { + sed -i "s/#define RK3399_BAUDRATE\s\+.*/#define RK3399_BAUDRATE ${RK_CONSOLE_BAUD}/" ${S}/plat/rockchip/rk3399/rk3399_def.h +} + +do_patch[postfuncs] += "fixup_rk3399_baudrate" -- 2.33.1
|
|
|
|
Re: [meta-rockchip][PATCH] kernel: linux-yocto: fix broken Ethernet MAC controller on RK3399 on 5.14 >= version <= 5.14.11
Quentin Schulz
Hi all,
On Mon, Dec 13, 2021 at 05:30:05PM -0500, Trevor Woerner wrote: Hi Quentin/Khem,No frustration on my side, just a debate/discussion on what we should do. Would this have been solved by (me) creating a honister branch? I usuallyNo, the problem is the same because it is broken only in Honister 3.4. So if we take this patch in, we basically have some code only for "patching" honister 3.4 but anything different than that, the patch is not necessary. So with a honister branch the "problem" stays the same. The question is more what's the policy with that kind of patch. Would you be ok taking that kind of patch which applies only to one dot release of Yocto and nothing else? Or do we just ignore it until the next dot release so it's fixed? Also do we expect to support honister 3.4 or once 3.4.1 is out (it is), we decide 3.4 is not supported at all? I'd like at least to mention somewhere that meta-rockchip is supposed to be used with something different than honister 3.4. Anyway, it's ok not to answer now and hope a similar issue does not happen later, or this discussion will be brought up again :) Cheers, Quentin
|
|
|
|
Re: [meta-rockchip][PATCH] trusted-firmware-a: replace baudrate with the one specified in machine conf
Quentin Schulz
Hi Trevor,
On Mon, Dec 13, 2021 at 05:37:32PM -0500, Trevor Woerner wrote: On Fri 2021-12-10 @ 11:15:56 AM, Trevor Woerner via lists.yoctoproject.org wrote:Yes, sorry just sent it :)On Fri 2021-12-10 @ 03:50:19 PM, Quentin Schulz wrote:Am I correct in thinking a v2 is coming (or did it get swallowed up by my mailHi Trevor,Sounds good. Cheers, Quentin
|
|
|
|
[PATCH v2] trusted-firmware-a: replace baudrate with the one specified in machine conf
Quentin Schulz
Not all Rockchip boards have their console running at 1500000 baud in
U-Boot and the kernel. Such is the case for puma-haikou RK3399-based SoM+Carrierboard. In order to prepare for the addition of puma-haikou to meta-rockchip, let's replace the baudrate in TF-A by the one defined in the machine conf file in the RK_CONSOLE_BAUD variable. Cc: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> --- v2: use a less restrictive regular expression .../files/serial-console-baudrate.patch | 36 ------------------- .../trusted-firmware-a_%.bbappend | 6 +++- 2 files changed, 5 insertions(+), 37 deletions(-) delete mode 100644 recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch diff --git a/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch b/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch deleted file mode 100644 index 2d6e9bf..0000000 --- a/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch +++ /dev/null @@ -1,36 +0,0 @@ -From 840d6b6420e1fd8cdf6e4de7fa58a6f8de151622 Mon Sep 17 00:00:00 2001 -From: Yann Dirson <yann@blade-group.com> -Date: Tue, 6 Apr 2021 17:28:45 +0200 -Subject: [PATCH] Set serial console baudrate back to 1500000. -Upstream-Status: Inappropriate[other] - -TF-A runs between two u-boot stages which both uses 1500000 baud, it -just makes no sense to use the same UART at a different rate. - -This effectively reverts part of 0c05748bdebfad9fa43a80962186438bb8fbce62. -Main reason for that change stated in https://developer.trustedfirmware.org/T762 -is ChromeOS compatibility. - -Looks like this patch may become unnecessary in the future, when -u-boot and TF-A get to communicate this value. - ---- - plat/rockchip/rk3399/rk3399_def.h | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/plat/rockchip/rk3399/rk3399_def.h b/plat/rockchip/rk3399/rk3399_def.h -index ba83242eb..8d6ecfbe6 100644 ---- a/plat/rockchip/rk3399/rk3399_def.h -+++ b/plat/rockchip/rk3399/rk3399_def.h -@@ -17,7 +17,7 @@ - /************************************************************************** - * UART related constants - **************************************************************************/ --#define RK3399_BAUDRATE 115200 -+#define RK3399_BAUDRATE 1500000 - #define RK3399_UART_CLOCK 24000000 - - /****************************************************************************** --- -2.30.2 - diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend index 513cea1..07fae1e 100644 --- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend +++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend @@ -7,7 +7,6 @@ COMPATIBLE_MACHINE:append:rk3328 = "|rk3328" FILESEXTRAPATHS:prepend := "${THISDIR}/files:" SRC_URI += "\ - file://serial-console-baudrate.patch \ file://0001-dram-Fix-build-with-gcc-11.patch \ file://0001-plat_macros.S-Use-compatible-.asciz-asm-directive.patch \ file://0001-pmu-Do-not-mark-already-defined-functions-as-weak.patch \ @@ -19,3 +18,8 @@ SRC_URI += "\ # this needs fixing until then use gcc TOOLCHAIN:rk3399 = "gcc" +fixup_rk3399_baudrate() { + sed -i "s/#define RK3399_BAUDRATE\s\+.*/#define RK3399_BAUDRATE ${RK_CONSOLE_BAUD}/" ${S}/plat/rockchip/rk3399/rk3399_def.h +} + +do_patch[postfuncs] += "fixup_rk3399_baudrate" -- 2.33.1
|
|
|
|
Re: [meta-rockchip][PATCH] kernel: linux-yocto: fix broken Ethernet MAC controller on RK3399 on 5.14 >= version <= 5.14.11
Quentin Schulz
Hi Trevor,
toggle quoted messageShow quoted text
Gentle ping :) Honister 3.4.1 being out it's less of an issue but the question remains at least for settling on a policy :) Cheers, Quentin
On Tue, Nov 16, 2021 at 10:50:13AM -0800, Khem Raj wrote:
On Tue, Nov 16, 2021 at 10:03 AM Quentin Schulz <foss@0leil.net> wrote:meta-rockchip does not have honister branch for now. So it expects
|
|
|
|
Re: [meta-rockchip][PATCH] trusted-firmware-a: replace baudrate with the one specified in machine conf
Quentin Schulz
Hi Trevor,
On Fri, Dec 10, 2021 at 09:43:39AM -0500, Trevor Woerner wrote: On Thu 2021-11-11 @ 06:00:02 PM, Quentin Schulz wrote:WouldNot all Rockchip boards have their console running at 1500000 baud inThis looks fragile to me, any change in the number of spaces/tabs and this sed -i "s/#define RK3399_BAUDRATE\s\+.*/#define RK3399_BAUDRATE plep/" ${S}/plat/rockchip/rk3399/rk3399_def.h work for you? This makes sure that only RK3399_BAUDRATE definition will be changed, no comment, no RK3399_BAUDRATE_OTHER_VAR or RK3399_BAUDRATE being used in code/other constant in this file. Cheers, Quentin
|
|
|
|
#dunfell #qt5 #raspberrypi #sdk #linux
#dunfell
#qt5
#raspberrypi
#sdk
#linux
arthur.forey@...
Hello everybody,
I come today to try to solve my problem. I am building a bsp and sdk for a raspberry pi (MACHINE = raspberrypi4-64) in the form of a compute module. I'm trying to compile this app: https://github.com/YvesBas/Tadarida-D/tree/master/sources for the raspberry pi). I know that in the Libs directory, the libraries are compiled for an x86_64 architecture. This is why I try to integrate them into the sources without this directory. I am also modifying the .pro to match with the correct libs. The integration of these two libs are present in the image of the raspberry pi, but in the sdk I only have the libsndfile1, so the libfftw3.h / .so is missing. Here are elements for the creation of the bsp and the sdk: Build Configuration: BB_VERSION = "1.46.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-poky-linux" MACHINE = "raspberrypi4-64" DISTRO = "poky" DISTRO_VERSION = "3.1.12" TUNE_FEATURES = "aarch64 cortexa72 crc crypto" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "dunfell:cf5a00721f721d5077c73d1f4e812e5c79833fba" meta-oe meta-python meta-networking meta-multimedia = "dunfell:69f94af4d91215e7d4e225bab54bf3bcfee42f1c" meta-qt5 = "dunfell:b4d24d70aca75791902df5cd59a4f4a54aa4a125" meta-raspberrypi = "dunfell:934064a01903b2ba9a82be93b3f0efdb4543a0e8" In conf/local.conf : IMAGE_INSTALL_append = " libfftw libfftwl libfftwf fftw-dev libsndfile1" When I do bitbake meta-toolchain-qt5, I don't have libfftw3.h / .so . What can i do ? Thanks a lot. Arthur
|
|
|
|
libsdl2 virtual/nativesdk-libgles2 issue
sateesh m
Hi Team,
I am facing a problem libsdl2 while building the core-image-base. Can anybody know this please suggest me. NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'virtual/nativesdk-libgles2' (but virtual:nativesdk:/home/sateesh/sample-kde/openembedded-core/meta/recipes-graphics/libsdl2/libsdl2_2.0.12.bb DEPENDS on or otherwise requires it). Close matches:
virtual/nativesdk-libgl
virtual/nativesdk-libsdl
virtual/nativesdk-libsdl2
NOTE: Runtime target 'nativesdk-qemu' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nativesdk-qemu', 'nativesdk-libsdl2', 'virtual/nativesdk-libgles2']
NOTE: Runtime target 'nativesdk-packagegroup-sdk-host' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nativesdk-packagegroup-sdk-host', 'nativesdk-qemu', 'nativesdk-libsdl2', 'virtual/nativesdk-libgles2']
ERROR: Required build target 'core-image-base' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-base', 'nativesdk-packagegroup-sdk-host', 'nativesdk-qemu', 'nativesdk-libsdl2', 'virtual/nativesdk-libgles2']
Regards, Sateesh
|
|
|
|
Re: Running unittests built by SDK
On Mon, Dec 13, 2021 at 6:21 PM Rusty Howell <rustyhowell@gmail.com> wrote:
I think using qemux86-64 might be your best bet, its fairly automated with runqemu script all you would need to do is package up the gtests as ptest package with a runner Thanks
|
|
|
|
Running unittests built by SDK
Rusty Howell
We are building our software with a Yocto SDK we created against our imx8m board. We would like to be able to execute unit tests (C++ tests written in Google Test) quickly without having to copy our unittest binaries over to an actual imx board to execute them. For sanity, we are also building our linux distro for MACHINE=qemux86-64 and beaglebone-yocto. So we have SDKs for imx8m, qemux86-64 and beaglebone-yocto. Is there a MACHINE type that we could build that would be suitable for executing compiled C++ google test binaries directly on Ubuntu 18.04 or 20.04? Thanks
|
|
|
|
Re: [meta-rockchip][PATCH] trusted-firmware-a: replace baudrate with the one specified in machine conf
Trevor Woerner
On Fri 2021-12-10 @ 11:15:56 AM, Trevor Woerner via lists.yoctoproject.org wrote:
On Fri 2021-12-10 @ 03:50:19 PM, Quentin Schulz wrote:Am I correct in thinking a v2 is coming (or did it get swallowed up by my mailHi Trevor,Sounds good. client)? Otherwise, I can just fixup your v2 and apply it if you wish?
|
|
|
|
Re: [meta-rockchip][PATCH v2] override syntax fixup
Trevor Woerner
On Sat 2021-12-11 @ 08:55:43 AM, Trevor Woerner wrote:
The _virtual notation is not an override. These syntax "fixes" need to beApplied to meta-rockchip, master.
|
|
|