Date   

Re: [meta-tensorflow] maintained?

Armin Kuster
 

On 12/14/20 4:56 AM, Marek Belisko wrote:
Hi,

I'm l;booking for a tensorflow recipe and forum that meta-tensorflow
have support for it (also saw that gatesgarth branch is there) but I
cannot build tensorflow + tensorflow seems to be a bit outdated.
Anybody know if this layer is maintained?
There are two maintainers listed in the maintainer.md file.  You may
want to ping them.

-armin
Thanks.

BR,

marek




[meta-zephyr][PATCH 3/3] conf: machine: add 96boards Avenger96 support

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

The board is based on STMicro STM32MP157AAC 2xCortex-A7+2xCortex-M4
system-on-chip.

Add STM32MP1 family machine config. STM32MP1 support depends on
STM32 HAL and OpenAMP for inter-core communication.

This change has been verified with zephyr-philosophers
and zephyr-shell sample applications on by loading Zephyr image
to Cortex-M4 core from Linux using remoteproc framework.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
---
conf/machine/96b-avenger96.conf | 8 ++++++++
conf/machine/include/stm32mp1-cortex-m4.inc | 11 +++++++++++
2 files changed, 19 insertions(+)
create mode 100644 conf/machine/96b-avenger96.conf
create mode 100644 conf/machine/include/stm32mp1-cortex-m4.inc

diff --git a/conf/machine/96b-avenger96.conf b/conf/machine/96b-avenger96.conf
new file mode 100644
index 0000000..7bcfb4a
--- /dev/null
+++ b/conf/machine/96b-avenger96.conf
@@ -0,0 +1,8 @@
+#@TYPE: Machine
+#@NAME: 96b_avenger96
+
+#@DESCRIPTION: Machine configuration for 96Boards Avenger96 Board.
+
+require conf/machine/include/stm32mp1-cortex-m4.inc
+
+ARCH_96b-avenger96 = "arm"
diff --git a/conf/machine/include/stm32mp1-cortex-m4.inc b/conf/machine/include/stm32mp1-cortex-m4.inc
new file mode 100644
index 0000000..b82b02d
--- /dev/null
+++ b/conf/machine/include/stm32mp1-cortex-m4.inc
@@ -0,0 +1,11 @@
+#@TYPE: Machine
+#@NAME: stm32mp1-cortex-m4
+
+#@DESCRIPTION: Machine configuration for Cortex-M4 core of STMicroelectronics STM32MP1 SoC.
+
+require conf/machine/include/tune-cortexm4.inc
+
+# Include OpenAMP for communication with Cortex-A7 core of the SoC
+MACHINEOVERRIDES =. "stm32:openamp:"
+
+TUNE_FEATURES = "armv7m cortexm4"
--
2.25.1


[meta-zephyr][PATCH 2/3] zephyr-kernel: clone OpenAMP

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

OpenAMP is a framework providing software components enabling
development of software applications for AMP systems.
It is downloaded by default by west from two Zephyr Project
repositories based on original OpenAMP repositories:

- open-amp - IPC layer that implements rpmsg communication
between cores,
- libmetal - HAL abstraction layer used by open-amp.

Clone the repositories so they can be used for building images
for boards with multicore chips.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
---
classes/zephyr-kernel-src.bbclass | 4 ++++
recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 1 +
2 files changed, 5 insertions(+)

diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass
index 4e05182..b7fb81d 100644
--- a/classes/zephyr-kernel-src.bbclass
+++ b/classes/zephyr-kernel-src.bbclass
@@ -7,11 +7,15 @@ SRCREV_default = "7a3b253ced7333f5c0269387a7f3ed1dee69739d"
SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90"
SRCREV_nordic = "d8a6ea9695ddf792bb18bb6035c13b1daac5d79c"
SRCREV_stm32 = "f0e11398128ac9abdff713da5d3035e6c96e9b86"
+SRCREV_open-amp = "de1b85a13032a2de1d8b6695ae5f800b613e739d"
+SRCREV_libmetal = "9d4ee2c3cfd5f49861939447990f3b7d7bf9bf94"

SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.4-branch;name=default \
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \
git://github.com/zephyrproject-rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic;name=nordic \
git://github.com/zephyrproject-rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=stm32 \
+ git://github.com/zephyrproject-rtos/open-amp.git;protocol=https;destsuffix=git/modules/lib/open-amp;name=open-amp \
+ git://github.com/zephyrproject-rtos/libmetal.git;protocol=https;destsuffix=git/modules/hal/libmetal;name=libmetal \
file://0001-cmake-add-yocto-toolchain.patch \
"

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index c7c894e..1357c8f 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -18,6 +18,7 @@ EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto -DBOARD=${BOARD}
EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis"
EXTRA_OECMAKE_append_nordic = "\;${S}/modules/hal/nordic"
EXTRA_OECMAKE_append_stm32 = "\;${S}/modules/hal/stm32"
+EXTRA_OECMAKE_append_openamp = "\;${S}/modules/lib/open-amp\;${S}/modules/hal/libmetal"
export ZEPHYR_BASE="${S}"


--
2.25.1


[meta-zephyr][PATCH 1/3] zephyr-kernel: clone STM32 HAL

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

HAL for STM32 chipsets is one of Zephyr subprojects. It is downloaded
by default by west. Clone the HAL repository so it can be used for
building images for boards with STM32 chips.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
---
classes/zephyr-kernel-src.bbclass | 2 ++
recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 1 +
2 files changed, 3 insertions(+)

diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass
index ea9b30b..4e05182 100644
--- a/classes/zephyr-kernel-src.bbclass
+++ b/classes/zephyr-kernel-src.bbclass
@@ -6,10 +6,12 @@ SRCREV_FORMAT = "default_cmsis"
SRCREV_default = "7a3b253ced7333f5c0269387a7f3ed1dee69739d"
SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90"
SRCREV_nordic = "d8a6ea9695ddf792bb18bb6035c13b1daac5d79c"
+SRCREV_stm32 = "f0e11398128ac9abdff713da5d3035e6c96e9b86"

SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.4-branch;name=default \
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \
git://github.com/zephyrproject-rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic;name=nordic \
+ git://github.com/zephyrproject-rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=stm32 \
file://0001-cmake-add-yocto-toolchain.patch \
"

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index a1f640d..c7c894e 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -17,6 +17,7 @@ ZEPHYR_MAKE_OUTPUT = "zephyr.elf"
EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto -DBOARD=${BOARD} -DARCH=${ARCH} -DCROSS_COMPILE=${CROSS_COMPILE} -DZEPHYR_SYSROOT=${ZEPHYR_SYSROOT} -DZEPHYR_TOOLCHAIN_VARIANT=yocto"
EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis"
EXTRA_OECMAKE_append_nordic = "\;${S}/modules/hal/nordic"
+EXTRA_OECMAKE_append_stm32 = "\;${S}/modules/hal/stm32"
export ZEPHYR_BASE="${S}"


--
2.25.1


[meta-zephyr][PATCH 0/3] Add 96Boards Avenger96 support

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

This patch set adds support of Avenger96 boards based on
STMicro STM32MP157AAC 2xCortex-A7+2xCortex-M4 SoC.
The support consists of:
- cloning dependencies i.e. STM32 HAL and OpenAMP framework,
- adding STM32MP1 and Avenger96 $MACHINE config files.

Verification:

1. Build an example app for Avenger96:

$ DISTRO=zephyr MACHINE=96b-avenger96 bitbake zephyr-philosophers

2. Please be aware that Avenger96's Cortex-M4 core can be
programmed and got out of reset only by software running
on the Cortex-A7 core, e.g. by U-Boot or Linux. Therefore,
despite the SoC can enter DFU mode, it cannot be used
for programming the M4 firmware. This example uses Linux.

3. Linux has to be built with remoteproc support. This can
be verified with simple dmesg inspection:

root@stm32mp1-av96:~# dmesg | grep remoteproc
[ 2.336231] remoteproc remoteproc0: m4 is available

4. Transfer the example app to the board, e.g. using scp.
The elf is located as usual in build/tmp-newlib/deploy/images/96b-avenger96/.

5. On the board, check the expected location of the fimrware image.
Empty path defaults to /lib/firmware. You can leave them as
they are and copy the Zephyr ELF file to the location pointed
by them or you can echo the new path and image name.

root@stm32mp1-av96:~# cat /sys/module/firmware_class/parameters/path
<empty>

root@stm32mp1-av96:~# cat /sys/class/remoteproc/remoteproc0/firmware
rproc-m4-fw

6. After the image path and name are configured, start the M4 core:

root@stm32mp1-av96:~# echo start > /sys/class/remoteproc/remoteproc0/state
remoteproc remoteproc0: powering up m4
remoteprocroc remoteproc0: Booting fw image rproc-m4-fw, size 591544
rproc-srm-core m4@0:m4_system_resources: bound m4@0:m4_system_resources:m4_led (ops 0xc0be1210)
remoteproc remoteproc0: remote processor m4 is now

7. Firmware output can be inspected with:

root@stm32mp1-av96:~# cat /sys/kernel/debug/remoteproc/remoteproc0/trace0
Philosopher 5 [C:-2] STARVING
Philosopher 3 [P: 0] DROPPED ONE FORK
Philosopher 3 [P: 0] THINKING [ 25 ms ]
Philosopher 2 [P: 1] EATING [ 425 ms ]
Philosopher 3 [P: 0] STARVING
Philosopher 4 [C:-1] STARVING
Philosopher 4 [C:-1] HOLDING ONE FORK
Philosopher 4 [C:-1] EATING [ 800 ms ]
Philosopher 3 [P: 0] HOLDING ONE FORK
Philosopher 2 [P: 1] DROPPED ONE FORK
Philosopher 2 [P: 1] THINKING [ 725 ms ]
Philosopher 1 [P: 2] EATING [ 225 ms ]

Wojciech Zmuda (3):
zephyr-kernel: clone STM32 HAL
zephyr-kernel: clone OpenAMP
conf: machine: add 96boards Avenger96 support

classes/zephyr-kernel-src.bbclass | 6 ++++++
conf/machine/96b-avenger96.conf | 8 ++++++++
conf/machine/include/stm32mp1-cortex-m4.inc | 11 +++++++++++
recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 2 ++
4 files changed, 27 insertions(+)
create mode 100644 conf/machine/96b-avenger96.conf
create mode 100644 conf/machine/include/stm32mp1-cortex-m4.inc

--
2.25.1


[meta-tensorflow] maintained?

Marek Belisko
 

Hi,

I'm l;booking for a tensorflow recipe and forum that meta-tensorflow
have support for it (also saw that gatesgarth branch is there) but I
cannot build tensorflow + tensorflow seems to be a bit outdated.
Anybody know if this layer is maintained? Thanks.

BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Re: [meta-raspberrypi] error with sc16is752-spi0 overlay

Romain Crausaz <romain.crausaz@...>
 

Dear Khem,

Thank you for the input.

I tried to remove all text from the variable RPI_KERNEL_DEVICETREE_OVERLAYS and type them again.

The images are now correctly compiling.

I suppose I had an invisible character that created this issue.

Best regards


Re: file /etc/ethertypes conflicts between netbase-1:6.2-r0.corei7_64 and ebtables-2.0.10+4-r4.corei7_64

Dingo <dingo@...>
 

On 12/12/20 3:41 AM, Randy MacLeod wrote:
On 2020-12-11 1:21 p.m., Dingo wrote:
file /etc/ethertypes conflicts between attempted installs of netbase-1:6.2-r0.corei7_64 and ebtables-2.0.10+4-r4.corei7_64
Thanks for the report. Unless someone replies here,
can you submit a fix to the oe-core and/or meta-oe lists?
Okay its been submitted



If not, can you open a bug in the YP Bugzilla?

Create an account here:
https://bugzilla.yoctoproject.org/createaccount.cgi
then file a bug:
https://bugzilla.yoctoproject.org/

Thanks,
../Randy


commit ba069a5a3dae374744f68a57ab9e7869167beb2b
Author: Alexander Kanavin <alex.kanavin@gmail.com>
Date:   Fri Dec 4 21:07:14 2020 +0100
     netbase: upgrade 6.1 -> 6.2
     Not sure why this didn't inherit allarch, but now it does - only
     static data is installed.

     (From OE-Core rev: ae1880436b293449318655f5b0207d2a741052ba)

     Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
     Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
diff --git a/meta/recipes-core/netbase/netbase_6.1.bb b/meta/recipes-core/netbase/netbase_6.2.bb
similarity index 65%
rename from meta/recipes-core/netbase/netbase_6.1.bb
rename to meta/recipes-core/netbase/netbase_6.2.bb
index 33eca459d5..a54d2e7764 100644
--- a/meta/recipes-core/netbase/netbase_6.1.bb
+++ b/meta/recipes-core/netbase/netbase_6.2.bb
@@ -6,17 +6,18 @@ LICENSE = "GPLv2"
  LIC_FILES_CHKSUM = "file://debian/copyright;md5=3dd6192d306f582dee7687da3d8748ab"
  PE = "1"

-SRC_URI = "${DEBIAN_MIRROR}/main/n/${BPN}/${BPN}_${PV}~bpo10+1.tar.xz"
-S = "${WORKDIR}/${BPN}-${PV}~bpo10+1"
+SRC_URI = "${DEBIAN_MIRROR}/main/n/${BPN}/${BPN}_${PV}.tar.xz"

-SRC_URI[md5sum] = "4fa7517285b4045ac0dc8dbf6730dd7a"
-SRC_URI[sha256sum] = "4e9c3082dff8896cb6b6bea9bb2200d82fb0d7c8d8c8fc9b18704fe553316237"
+inherit allarch
+
+SRC_URI[sha256sum] = "309a24146a06347d654b261e9e07a82fab844b173674a42e223803dd8258541e"

  UPSTREAM_CHECK_URI = "${DEBIAN_MIRROR}/main/n/netbase/"
-do_install () {

-       install -d ${D}/${mandir}/man8 ${D}${sysconfdir}
+do_install () {
+       install -d ${D}${sysconfdir}
         install -m 0644 ${S}/etc/rpc ${D}${sysconfdir}/rpc
         install -m 0644 ${S}/etc/protocols ${D}${sysconfdir}/protocols
         install -m 0644 ${S}/etc/services ${D}${sysconfdir}/services
+       install -m 0644 ${S}/etc/ethertypes ${D}${sysconfdir}/ethertypes
  }




Re: curl_easy_perform() failed: Couldn't connect to server #linux #yocto

Vijay Rakesh Munganda
 

Hi Khem raj,

Regarding zbar, I found the video option was disabled in the .bb file, so I had changed it to --enable-video and ran the build, but the build failed at do_install. Do I Need to make change anything else? 

Log:
|  /home/bl-docker/rity/bsp/tmp/hosttools/mkdir -p '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/bin'
|   ./aarch64-poky-linux-libtool   --mode=install /home/bl-docker/rity/bsp/tmp/hosttools/install -c zbarcam/zbarcam '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/bin'
|  /home/bl-docker/rity/bsp/tmp/hosttools/install -c -m 644 ../git/doc/man/zbarcam.1 '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/share/man/man1'
| /home/bl-docker/rity/bsp/tmp/hosttools/install: cannot stat '../git/doc/man/zbarcam.1': No such file or directory
| Makefile:2386: recipe for target 'install-man1' failed
| make[3]: *** [install-man1] Error 1
| make[3]: *** Waiting for unfinished jobs....
| aarch64-poky-linux-libtool: warning: 'zbar/libzbar.la' has not been installed in '/usr/lib'
| aarch64-poky-linux-libtool: install: /home/bl-docker/rity/bsp/tmp/hosttools/install -c zbarcam/.libs/zbarcam /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/bin/zbarcam
| make[3]: Leaving directory '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/build'
| Makefile:2850: recipe for target 'install-am' failed
| make[2]: *** [install-am] Error 2
| make[2]: Leaving directory '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/build'
| Makefile:2541: recipe for target 'install-recursive' failed
| make[1]: *** [install-recursive] Error 1
| make[1]: Leaving directory '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/build'
| Makefile:2844: recipe for target 'install' failed
| make: *** [install] Error 2
| WARNING: /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/temp/run.do_install.15449:1 exit 1 from 'exit 1'

Thanks & Regards,
Vijay Rakesh.


Re: curl_easy_perform() failed: Couldn't connect to server #linux #yocto

Vijay Rakesh Munganda
 

Hi Khem Raj,

It worked. Included gnutls and tested with other network.

Thanks & Regards,
Vijay Rakesh

On 12-Dec-2020, at 00:07, Khem Raj <raj.khem@gmail.com> wrote:

On Fri, Dec 11, 2020 at 9:51 AM <vijayrakeshmunganda@gmail.com> wrote:

On Fri, Dec 11, 2020 at 09:04 AM, Khem Raj wrote:

On 12/11/20 2:26 AM, vijayrakeshmunganda@gmail.com wrote:

Hi,

I'm trying to do HTTPS POST using curl with CA certificate, but I got an
error as "curl_easy_perform() failed: Couldn't connect to server". The
same code works on a Linux machine but not on my target board, I can't
understand what I'm missing. I have an active internet connection
without any firewall. Kindly please give any suggestions.

check what all packageconfig is being used are you using gnutls, then
you might want to try nss or openssl and see if that helps.
hard to say, unless more details are available, usually runtime deps
and build time deps are handled fine but there might
be some outliers.

Thanks & Regards,
Vijay




Hi Khem Raj,

Thanks for the reply. I had installed openssl and curl, but not gnutls because compilation was successful. I’ll definitely try ur suggestion. Thank you!

Please correct me if I’m wrong, even if dependent packages are not installed on target system will compilation done successfully? I’m
also facing similar issue with zbar, compilation was successful and perfectly executing on Linux PC, but not my target board even after installing zbar package.

Thanks & Regards,
Vijay Rakesh.




Re: [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass: support for flashing via pyocd

Naveen Saini
 

Merged. Thank you for patches.

 

Regards,

Naveen

 

From: Wojciech Żmuda <zmuda.w@...>
Sent: Friday, December 11, 2020 12:09 AM
To: Saini, Naveen Kumar <naveen.kumar.saini@...>
Cc: yocto@...
Subject: Re: [yocto] [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass: support for flashing via pyocd

 

Hi Naveen,

 

I investigated the arduino-101-ble problem and for me it's non trivial to fix. It's not related to the same missing variable that I spotted in the Nitrogen case, but rather there are some inconsistencies with architecture-related variables i.e. PACKAGE_ARCHS and TUNE_xxx. I did not find any way to fix it.

 

For now I pushed v3 with Nitrogen support. If I find a way to straighten out the Arduino case, I'll push a separate patch set for that.

 

BTW, I also have 96boards Avenger96 support patch set ready. It depends on one commit from the Nitrogen patch set (Cortex-M4 tune), so I'll send it out right after Nitrogen support is merged.

 

Regards,

Wojciech

 

On Thu, 10 Dec 2020 at 08:20, Saini, Naveen Kumar <naveen.kumar.saini@...> wrote:

Hi Wojciech,

 

Yes, testcases are currently being verified only on qemu, so if we can just build testcases for now that should be sufficient. If you are able to flash and execute tests manually on HW, that would work. Please send v3.

 

Can you fix for arduino-101-ble  as well ?

 

Naveen

 

From: Wojciech Żmuda <zmuda.w@...>
Sent: Wednesday, December 9, 2020 11:07 PM
To: Saini, Naveen Kumar <naveen.kumar.saini@...>
Cc: yocto@...
Subject: Re: [yocto] [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass: support for flashing via pyocd

 

Hi Naveen,

 

I fixed the missing .hex issue and I'm ready to send v3.

 

I also experimented with your last suggestion, i.e. building test cases with MACHINE=96b-nitrogen and I observed the following:

 

It is possible to build when I provide IMGDEPLOYDIR variable somewhere, e.g. in 96b-nitrogen.conf. However, for other platforms, this variable is provided only in classes/zephyr-qemuboot.bbclass. I've also tried to build test cases for arduino-101-ble and it failed with the following reason:

 

    Error, the PACKAGE_ARCHS variable (all any noarch ${PACKAGE_EXTRA_ARCHS_tune-armv6m} cortexm0-vfp arduino_101_ble) for DEFAULTTUNE (cortexm0) does not contain TUNE_PKGARCH (cortexm0t2-vfp).

 

Additionally, when I provided IMGDEPLOYDIR in 96b-nitrogen.conf, I tried to execute test cases with -c testimage. It failed on running qemu.

 

According to my observations, my understanding is that the test cases are currently designed for being verified on qemu. Do you expect the 96b-nitrogen support to contain automatic test cases execution on the hardware, or just the possibility of building? If it just the matter of building the .elf files (you can flash them manually), then I can push v3 today.

 

Best regards,

Wojciech

 

 

On Tue, 8 Dec 2020 at 02:47, Saini, Naveen Kumar <naveen.kumar.saini@...> wrote:

You have missed few of my comments in v2 !

Regards,
Naveen

-----Original Message-----
From: Saini, Naveen Kumar
Sent: Monday, December 7, 2020 8:06 PM
To: 'Wojciech Zmuda' <zmuda.w@...>; yocto@...
Cc: davide.ricci@...; zbigniew.bodek@...; jaroslaw.marek@...; robert.drab@...; Wojciech Zmuda <wojciech.zmuda@...>
Subject: RE: [yocto] [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass: support for flashing via pyocd

Thanks for the patches.  Please find my comments below.

-----Original Message-----
From: yocto@... <yocto@...> On Behalf Of Wojciech Zmuda
Sent: Monday, December 7, 2020 4:15 AM
To: yocto@...
Cc: davide.ricci@...; zbigniew.bodek@...; jaroslaw.marek@...; robert.drab@...; Wojciech Zmuda <wojciech.zmuda@...>
Subject: [yocto] [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass: support for flashing via pyocd

Flash boards supported via pyocd:

    MACHINE=xxx bitbake yyy -c flash_usb

The only supported board for now is 96Boards Nitrogen. Modify its config accordingly.

Modify helloworld and philosopers samples with adidtional .hex output file deployment, as this format is required by pyocd.

Describe the feature in README.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@...>
---
 README.txt                                    | 23 +++++++++++++++++++
 classes/zephyr-flash-pyocd.bbclass            | 17 ++++++++++++++
 conf/machine/96b-nitrogen.conf                |  1 +
 .../zephyr-kernel/zephyr-helloworld.bb        |  1 +
 .../zephyr-kernel/zephyr-philosophers.bb      |  1 +
 5 files changed, 43 insertions(+)
 create mode 100644 classes/zephyr-flash-pyocd.bbclass

diff --git a/README.txt b/README.txt
index 6463339..4366764 100644
--- a/README.txt
+++ b/README.txt
@@ -43,6 +43,29 @@ The same sample, for Nios2 image:
     $ MACHINE=qemu-nios2 bitbake zephyr-philosophers
     $ runqemu qemu-nios2

+Flashing
+=================================
+
+You can flash Zephyr samples to boards. Currently, the following
+MACHINEs are supported:
+ * DFU:
+  - arduino_101_sss
+  - arduino_101
+  - arduino_101_ble
+ * pyocd:
+  - 96b_nitrogen
+
+To flash the example you built with command e.g.
+
+    $ MACHINE=96b_nitrogen bitbake zephyr-philosophers
[Naveen Saini] Typo here, MACHINE=96b-nitrogen
+
+call similar command with explicit flash_usb command:
+
+    $ MACHINE=96b_nitrogen bitbake zephyr-philosophers -c flash_usb
[Naveen Saini]  Same as above

+
+dfu-util and/or pyocd need to be installed in your system. If you
+observe permission errors or the flashing process seem to hang, follow those instructions:
+https://github.com/pyocd/pyOCD/tree/master/udev

 Building and Running Zephyr Tests
 =================================
diff --git a/classes/zephyr-flash-pyocd.bbclass b/classes/zephyr-flash-pyocd.bbclass
new file mode 100644
index 0000000..aafe9e7
--- /dev/null
+++ b/classes/zephyr-flash-pyocd.bbclass
@@ -0,0 +1,17 @@
+
+python do_flash_usb() {
+    from pyocd.core.helpers import ConnectHelper
+    from pyocd.flash.file_programmer import FileProgrammer
+
+    image = f"{d.getVar('DEPLOY_DIR_IMAGE')}/{d.getVar('PN')}.hex"
+    bb.plain(f"Attempting to flash {image} to board
+ {d.getVar('BOARD')}")
+
+    with ConnectHelper.session_with_chosen_probe() as session:
+        FileProgrammer(session).program(image)
+        session.board.target.reset()
+}
+
+addtask do_flash_usb
+
+do_flash_usb[nostamp] = "1"
+do_flash_usb[vardepsexclude] = "BB_ORIGENV"
diff --git a/conf/machine/96b-nitrogen.conf b/conf/machine/96b-nitrogen.conf index d1905f2..998db4c 100644
--- a/conf/machine/96b-nitrogen.conf
+++ b/conf/machine/96b-nitrogen.conf
@@ -4,4 +4,5 @@
 #@DESCRIPTION: Machine configuration for 96Boards Nitrogen Board.

 require conf/machine/include/nrf52832.inc
+ZEPHYR_INHERIT_CLASSES += "zephyr-flash-pyocd"
 ARCH_96b-nitrogen = "arm"
diff --git a/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb b/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb
index 1400e72..9b77975 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb
+++ b/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb
@@ -8,6 +8,7 @@ OECMAKE_SOURCEPATH = "${ZEPHYR_SRC_DIR}"

 do_deploy () {
     install -D ${B}/zephyr/${ZEPHYR_MAKE_OUTPUT}.elf ${DEPLOYDIR}/${PN}.elf
+    install -D ${B}/zephyr/${ZEPHYR_MAKE_OUTPUT}.hex
+ ${DEPLOYDIR}/${PN}.hex
 }
[Naveen Saini]  No *.hex file while building for MACHINE=qemu-x86  Error log:  ...build/zephyr/zephyr.hex': No such file or directory


 addtask deploy after do_compile
diff --git a/recipes-kernel/zephyr-kernel/zephyr-philosophers.bb b/recipes-kernel/zephyr-kernel/zephyr-philosophers.bb
index 5f7fbcb..f720999 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-philosophers.bb
+++ b/recipes-kernel/zephyr-kernel/zephyr-philosophers.bb
@@ -8,6 +8,7 @@ OECMAKE_SOURCEPATH = "${ZEPHYR_SRC_DIR}"

 do_deploy () {
     install -D ${B}/zephyr/${ZEPHYR_MAKE_OUTPUT}.elf ${DEPLOYDIR}/${PN}.elf
+    install -D ${B}/zephyr/${ZEPHYR_MAKE_OUTPUT}.hex
+ ${DEPLOYDIR}/${PN}.hex
 }

[Naveen Saini]  No *.hex file while building for MACHINE=qemu-x86  Error log:  ...build/zephyr/zephyr.hex': No such file or directory

Could you also try to build testcases !!
$ MACHINE=96b-nitrogen bitbake zephyr-kernel-test-all

Build breaks with error: ......build/zephyr/zephyr.elf.elf': No such file or directory

 addtask deploy after do_compile
--
2.25.1


git-lfs #dunfell

joel.winarske@...
 

I am seeing problems in git fetcher using a github repo using lfs + ssh in dunfell.

I find if I set "lfs=0" it still attempts to download the lfs objects and fails.  Same behavior if "lfs=1".

SRC_URI = "git://git@...:/account/cool-thing.git;protocol=ssh;lfs=1;branch=cool_branch"


A suggested workaround by technoweenie here: https://github.com/git-lfs/git-lfs/issues/1044

Only git clone via ssh works (pulls lfs objects) fine outside of the yocto tree.


Any ideas?

Thanks,
Joel

git-lfs/2.9.2 (GitHub; linux amd64; go 1.13.5)
git version 2.25.1

$ git-lfs filter-process
Error downloading object: cool-thing/app/lib/agl/aarch64/libfmt.a (328664b): Smudge error: Error downloading cool-thing/app/lib/agl/aarch64/libfmt.a (328664b0bd0cad33f28722b9a6ccd5ac9adea4485885bacd35082775e41601d8): batch request: missing protocol: "<unknown>"

missing protocol: "<unknown>"
batch request
github.com/git-lfs/git-lfs/errors.newWrappedError
github.com/git-lfs/git-lfs/errors/types.go:198
github.com/git-lfs/git-lfs/errors.Wrap
github.com/git-lfs/git-lfs/errors/errors.go:74
github.com/git-lfs/git-lfs/tq.(*tqClient).Batch
github.com/git-lfs/git-lfs/tq/api.go:68
github.com/git-lfs/git-lfs/tq.Batch
github.com/git-lfs/git-lfs/tq/api.go:40
github.com/git-lfs/git-lfs/tq.(*TransferQueue).enqueueAndCollectRetriesFor
github.com/git-lfs/git-lfs/tq/transfer_queue.go:520
github.com/git-lfs/git-lfs/tq.(*TransferQueue).collectBatches.func1
github.com/git-lfs/git-lfs/tq/transfer_queue.go:432
runtime.goexit
/usr/lib/go-1.13/src/runtime/asm_amd64.s:1357
Error downloading cool-thing/app/lib/agl/aarch64/libfmt.a (328664b0bd0cad33f28722b9a6ccd5ac9adea4485885bacd35082775e41601d8)
github.com/git-lfs/git-lfs/errors.newWrappedError
github.com/git-lfs/git-lfs/errors/types.go:198
github.com/git-lfs/git-lfs/errors.Wrapf
github.com/git-lfs/git-lfs/errors/errors.go:85
github.com/git-lfs/git-lfs/lfs.(*GitFilter).downloadFile
github.com/git-lfs/git-lfs/lfs/gitfilter_smudge.go:115
github.com/git-lfs/git-lfs/lfs.(*GitFilter).Smudge
github.com/git-lfs/git-lfs/lfs/gitfilter_smudge.go:76
github.com/git-lfs/git-lfs/commands.smudge
github.com/git-lfs/git-lfs/commands/command_smudge.go:127
github.com/git-lfs/git-lfs/commands.filterCommand
github.com/git-lfs/git-lfs/commands/command_filter_process.go:118
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra/command.go:766
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra/command.go:850
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra/command.go:800
github.com/git-lfs/git-lfs/commands.Run
github.com/git-lfs/git-lfs/commands/run.go:97
main.main
github.com/git-lfs/git-lfs/git-lfs.go:33
runtime.main
/usr/lib/go-1.13/src/runtime/proc.go:203
runtime.goexit
/usr/lib/go-1.13/src/runtime/asm_amd64.s:1357
Smudge error
github.com/git-lfs/git-lfs/errors.newWrappedError
github.com/git-lfs/git-lfs/errors/types.go:198
github.com/git-lfs/git-lfs/errors.NewSmudgeError
github.com/git-lfs/git-lfs/errors/types.go:284
github.com/git-lfs/git-lfs/lfs.(*GitFilter).Smudge
github.com/git-lfs/git-lfs/lfs/gitfilter_smudge.go:85
github.com/git-lfs/git-lfs/commands.smudge
github.com/git-lfs/git-lfs/commands/command_smudge.go:127
github.com/git-lfs/git-lfs/commands.filterCommand
github.com/git-lfs/git-lfs/commands/command_filter_process.go:118
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra/command.go:766
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra/command.go:850
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra/command.go:800
github.com/git-lfs/git-lfs/commands.Run
github.com/git-lfs/git-lfs/commands/run.go:97
main.main
github.com/git-lfs/git-lfs/git-lfs.go:33
runtime.main
/usr/lib/go-1.13/src/runtime/proc.go:203
runtime.goexit
/usr/lib/go-1.13/src/runtime/asm_amd64.s:1357

Current time in UTC:
2020-12-12 15:41:16

ENV:
LocalWorkingDir=/b/lv-0.1/apps/apps_proc/poky/build/tmp-glibc/work/aarch64-oe-linux/cool-thing/git+AUTOINC+3158acc56b-r0/git
LocalGitDir=/b/lv-0.1/apps/apps_proc/poky/build/tmp-glibc/work/aarch64-oe-linux/cool-thing/git+AUTOINC+3158acc56b-r0/git/.git
LocalGitStorageDir=/b/lv-0.1/apps/apps_proc/poky/build/tmp-glibc/work/aarch64-oe-linux/cool-thing/git+AUTOINC+3158acc56b-r0/git/.git
LocalMediaDir=/b/lv-0.1/apps/apps_proc/poky/build/tmp-glibc/work/aarch64-oe-linux/cool-thing/git+AUTOINC+3158acc56b-r0/git/.git/lfs/objects
LocalReferenceDirs=
TempDir=/b/lv-0.1/apps/apps_proc/poky/build/tmp-glibc/work/aarch64-oe-linux/cool-thing/git+AUTOINC+3158acc56b-r0/git/.git/lfs/tmp
ConcurrentTransfers=3
TusTransfers=false
BasicTransfersOnly=false
SkipDownloadErrors=false
FetchRecentAlways=false
FetchRecentRefsDays=7
FetchRecentCommitsDays=0
FetchRecentRefsIncludeRemotes=true
PruneOffsetDays=3
PruneVerifyRemoteAlways=false
PruneRemoteName=origin
LfsStorageDir=/b/lv-0.1/apps/apps_proc/poky/build/tmp-glibc/work/aarch64-oe-linux/cool-thing/git+AUTOINC+3158acc56b-r0/git/.git/lfs
AccessDownload=none
AccessUpload=none
DownloadTransfers=basic,lfs-standalone-file
UploadTransfers=basic,lfs-standalone-file
GIT_CONFIG_PARAMETERS='core.fsyncobjectfiles=0'
GIT_EXEC_PATH=/usr/lib/git-core
GIT_PREFIX=
GIT_CEILING_DIRECTORIES=/b/lv-0.1/apps/apps_proc/poky/build/tmp-glibc/work/aarch64-oe-linux/cool-thing/git+AUTOINC+3158acc56b-r0



Re: #vmdk with #vmdk #dunfell

Randy MacLeod
 

On 2020-12-10 8:18 a.m., chruetli@... wrote:
Hi,

I switched from warrior to dunfell and want to build an image for Oracles VirtualBox VM.
On warrior there was 'automatically' a hddimg generated on dunfell this is no longer the case. The IMAGE_FSTYPES has to by specified, I use:
WKS_FILE = "virtualbox.wks"
IMAGE_FSTYPES += "wic.vmdk"

This requires me to write an wks file for which I use:
part /boot --source bootimg-pcbios --ondisk sda --label boot --active --align 1024
part / --source rootfs --ondisk sda --fstype=ext4 --label platform --align 1024
bootloader --ptable gpt  --timeout=5  --append="rootfstype=ext4 video=vesafb vga=current console=tty0"

With these settings I get an vmdk image but it fails to boot. I get a "VFS Unable to mount root fs on unknown block(0,0)" dump.

Any ideas?


Not off-hand.

Since no one is available right now to help,

can you report the bug in:

https://bugzilla.yoctoproject.org/

after creating an account:

https://bugzilla.yoctoproject.org/createaccount.cgi

Please give lots of detail about your build host,
and the repos and versions you are using.

Thanks,

../Randy





-- 
# Randy MacLeod
# Wind River Linux


Re: file /etc/ethertypes conflicts between netbase-1:6.2-r0.corei7_64 and ebtables-2.0.10+4-r4.corei7_64

Randy MacLeod
 

On 2020-12-11 1:21 p.m., Dingo wrote:
file /etc/ethertypes conflicts between attempted installs of netbase-1:6.2-r0.corei7_64 and ebtables-2.0.10+4-r4.corei7_64
Thanks for the report. Unless someone replies here,
can you submit a fix to the oe-core and/or meta-oe lists?

If not, can you open a bug in the YP Bugzilla?

Create an account here:
https://bugzilla.yoctoproject.org/createaccount.cgi
then file a bug:
https://bugzilla.yoctoproject.org/

Thanks,
../Randy


commit ba069a5a3dae374744f68a57ab9e7869167beb2b
Author: Alexander Kanavin <alex.kanavin@gmail.com>
Date:   Fri Dec 4 21:07:14 2020 +0100
    netbase: upgrade 6.1 -> 6.2
    Not sure why this didn't inherit allarch, but now it does - only
    static data is installed.
    (From OE-Core rev: ae1880436b293449318655f5b0207d2a741052ba)
    Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
diff --git a/meta/recipes-core/netbase/netbase_6.1.bb b/meta/recipes-core/netbase/netbase_6.2.bb
similarity index 65%
rename from meta/recipes-core/netbase/netbase_6.1.bb
rename to meta/recipes-core/netbase/netbase_6.2.bb
index 33eca459d5..a54d2e7764 100644
--- a/meta/recipes-core/netbase/netbase_6.1.bb
+++ b/meta/recipes-core/netbase/netbase_6.2.bb
@@ -6,17 +6,18 @@ LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://debian/copyright;md5=3dd6192d306f582dee7687da3d8748ab"
 PE = "1"
-SRC_URI = "${DEBIAN_MIRROR}/main/n/${BPN}/${BPN}_${PV}~bpo10+1.tar.xz"
-S = "${WORKDIR}/${BPN}-${PV}~bpo10+1"
+SRC_URI = "${DEBIAN_MIRROR}/main/n/${BPN}/${BPN}_${PV}.tar.xz"
-SRC_URI[md5sum] = "4fa7517285b4045ac0dc8dbf6730dd7a"
-SRC_URI[sha256sum] = "4e9c3082dff8896cb6b6bea9bb2200d82fb0d7c8d8c8fc9b18704fe553316237"
+inherit allarch
+
+SRC_URI[sha256sum] = "309a24146a06347d654b261e9e07a82fab844b173674a42e223803dd8258541e"
 UPSTREAM_CHECK_URI = "${DEBIAN_MIRROR}/main/n/netbase/"
-do_install () {
-       install -d ${D}/${mandir}/man8 ${D}${sysconfdir}
+do_install () {
+       install -d ${D}${sysconfdir}
        install -m 0644 ${S}/etc/rpc ${D}${sysconfdir}/rpc
        install -m 0644 ${S}/etc/protocols ${D}${sysconfdir}/protocols
        install -m 0644 ${S}/etc/services ${D}${sysconfdir}/services
+       install -m 0644 ${S}/etc/ethertypes ${D}${sysconfdir}/ethertypes
 }

--
# Randy MacLeod
# Wind River Linux


Re: curl_easy_perform() failed: Couldn't connect to server #linux #yocto

Khem Raj
 

On Fri, Dec 11, 2020 at 9:51 AM <vijayrakeshmunganda@gmail.com> wrote:

On Fri, Dec 11, 2020 at 09:04 AM, Khem Raj wrote:

On 12/11/20 2:26 AM, vijayrakeshmunganda@gmail.com wrote:

Hi,

I'm trying to do HTTPS POST using curl with CA certificate, but I got an
error as "curl_easy_perform() failed: Couldn't connect to server". The
same code works on a Linux machine but not on my target board, I can't
understand what I'm missing. I have an active internet connection
without any firewall. Kindly please give any suggestions.

check what all packageconfig is being used are you using gnutls, then
you might want to try nss or openssl and see if that helps.
hard to say, unless more details are available, usually runtime deps
and build time deps are handled fine but there might
be some outliers.

Thanks & Regards,
Vijay




Hi Khem Raj,

Thanks for the reply. I had installed openssl and curl, but not gnutls because compilation was successful. I’ll definitely try ur suggestion. Thank you!

Please correct me if I’m wrong, even if dependent packages are not installed on target system will compilation done successfully? I’m
also facing similar issue with zbar, compilation was successful and perfectly executing on Linux PC, but not my target board even after installing zbar package.

Thanks & Regards,
Vijay Rakesh.




file /etc/ethertypes conflicts between netbase-1:6.2-r0.corei7_64 and ebtables-2.0.10+4-r4.corei7_64

Dingo <dingo@...>
 

file /etc/ethertypes conflicts between attempted installs of netbase-1:6.2-r0.corei7_64 and ebtables-2.0.10+4-r4.corei7_64
commit ba069a5a3dae374744f68a57ab9e7869167beb2b
Author: Alexander Kanavin <alex.kanavin@gmail.com>
Date:   Fri Dec 4 21:07:14 2020 +0100
    netbase: upgrade 6.1 -> 6.2
    Not sure why this didn't inherit allarch, but now it does - only
    static data is installed.

    (From OE-Core rev: ae1880436b293449318655f5b0207d2a741052ba)

    Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
diff --git a/meta/recipes-core/netbase/netbase_6.1.bb b/meta/recipes-core/netbase/netbase_6.2.bb
similarity index 65%
rename from meta/recipes-core/netbase/netbase_6.1.bb
rename to meta/recipes-core/netbase/netbase_6.2.bb
index 33eca459d5..a54d2e7764 100644
--- a/meta/recipes-core/netbase/netbase_6.1.bb
+++ b/meta/recipes-core/netbase/netbase_6.2.bb
@@ -6,17 +6,18 @@ LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://debian/copyright;md5=3dd6192d306f582dee7687da3d8748ab"
 PE = "1"

-SRC_URI = "${DEBIAN_MIRROR}/main/n/${BPN}/${BPN}_${PV}~bpo10+1.tar.xz"
-S = "${WORKDIR}/${BPN}-${PV}~bpo10+1"
+SRC_URI = "${DEBIAN_MIRROR}/main/n/${BPN}/${BPN}_${PV}.tar.xz"

-SRC_URI[md5sum] = "4fa7517285b4045ac0dc8dbf6730dd7a"
-SRC_URI[sha256sum] = "4e9c3082dff8896cb6b6bea9bb2200d82fb0d7c8d8c8fc9b18704fe553316237"
+inherit allarch
+
+SRC_URI[sha256sum] = "309a24146a06347d654b261e9e07a82fab844b173674a42e223803dd8258541e"

 UPSTREAM_CHECK_URI = "${DEBIAN_MIRROR}/main/n/netbase/"
-do_install () {

-       install -d ${D}/${mandir}/man8 ${D}${sysconfdir}
+do_install () {
+       install -d ${D}${sysconfdir}
        install -m 0644 ${S}/etc/rpc ${D}${sysconfdir}/rpc
        install -m 0644 ${S}/etc/protocols ${D}${sysconfdir}/protocols
        install -m 0644 ${S}/etc/services ${D}${sysconfdir}/services
+       install -m 0644 ${S}/etc/ethertypes ${D}${sysconfdir}/ethertypes
 }


Re: curl_easy_perform() failed: Couldn't connect to server #linux #yocto

Vijay Rakesh Munganda
 

On Fri, Dec 11, 2020 at 09:04 AM, Khem Raj wrote:
On 12/11/20 2:26 AM, vijayrakeshmunganda@... wrote:
Hi,

I'm trying to do HTTPS POST using curl with CA certificate, but I got an
error as "curl_easy_perform() failed: Couldn't connect to server". The
same code works on a Linux machine but not on my target board, I can't
understand what I'm missing. I have an active internet connection
without any firewall. Kindly please give any suggestions.
check what all packageconfig is being used are you using gnutls, then
you might want to try nss or openssl and see if that helps.

Thanks & Regards,
Vijay




 Hi Khem Raj,

Thanks for the reply. I had installed openssl and curl, but not gnutls because compilation was successful. I’ll definitely try ur suggestion. Thank you! 

Please correct me if I’m wrong, even if dependent packages are not installed on target system will compilation done successfully? I’m
also facing similar issue with zbar, compilation was successful and perfectly executing on Linux PC, but not my target board even after installing zbar package. 

Thanks & Regards,
Vijay Rakesh. 


Re: curl_easy_perform() failed: Couldn't connect to server #linux #yocto

Khem Raj
 

On 12/11/20 2:26 AM, vijayrakeshmunganda@gmail.com wrote:
Hi,
I'm trying to do HTTPS POST using curl with CA certificate, but I got an error as "curl_easy_perform() failed: Couldn't connect to server". The same code works on a Linux machine but not on my target board, I can't understand what I'm missing. I have an active internet connection without any firewall. Kindly please give any suggestions.
check what all packageconfig is being used are you using gnutls, then you might want to try nss or openssl and see if that helps.

Thanks & Regards,
Vijay


Re: [meta-raspberrypi] error with sc16is752-spi0 overlay

Khem Raj
 

On 12/11/20 6:41 AM, Romain Crausaz wrote:
I kept looking and I get the same error with the sdio overlay when I remove the sc16is752.
I think the content of IMAGE_BOOT_FILES would be right place to start looking into the issue.

bitbake -e <yourimage> | grep -e "^IMAGE_BOOT_FILES="

might give more insights into this variable's contents and see if the syntax is ok or not.


Re: [meta-rockchip][PATCH] Fix Rock Pi 4 serial port

Bruce Ashfield
 

On Fri, Dec 11, 2020 at 10:55 AM Joshua Watt <jpewhacker@gmail.com> wrote:


On 12/11/20 9:16 AM, Bruce Ashfield wrote:
On Fri, Dec 11, 2020 at 9:48 AM Joshua Watt <JPEWhacker@gmail.com> wrote:
Fixes the serial port output stopping mid way through the boot process
by reverting the kernel commit that caused it.
If you want, I can also pick this up and merge it directly into
linux-yocto and do a SRCREV bump.

Have you tested against 5.10 ? I'm working through issues with it now,
and it would be nice to fix this before it pops up again on the next
reference kernel bump.
When I use `linux-yocto-dev` as the kernel provider, it works just fine
(in fact, I can't seem to find the commit that *fixes* the problem
there....), so I think 5.10 will be OK? Is there something else I should
try instead?
Nope, that should be enough to show that it has already been addressed
upstream. By default, you'll get a v5.10-rc with -dev in master, so
that confirms the fix.


I'm not sure if we want to backport it to linux-yocto or not... I
presume upstream backported it because it fixed something, so I'd be a
little worried about a regression somewhere else.
True that. And the time spent to prove that, or identify the fix isn't
worth it (since 5.8 is going away). If this was a longer term
version, I'd create a BSP branch and we could isolate it that way, but
again, just not worth the wrangling.

Bruce


Cheers,

Bruce

Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
...-resolve-supply-after-creating-regul.patch | 53 +++++++++++++++++++
recipes-kernel/linux/linux-yocto_5.8.bbappend | 4 ++
2 files changed, 57 insertions(+)
create mode 100644 recipes-kernel/linux/linux-yocto/0001-Revert-regulator-resolve-supply-after-creating-regul.patch
create mode 100644 recipes-kernel/linux/linux-yocto_5.8.bbappend

diff --git a/recipes-kernel/linux/linux-yocto/0001-Revert-regulator-resolve-supply-after-creating-regul.patch b/recipes-kernel/linux/linux-yocto/0001-Revert-regulator-resolve-supply-after-creating-regul.patch
new file mode 100644
index 0000000..3dd336b
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto/0001-Revert-regulator-resolve-supply-after-creating-regul.patch
@@ -0,0 +1,53 @@
+From a414d39b848002e15531f2538d2b6427ce51d07d Mon Sep 17 00:00:00 2001
+From: Joshua Watt <JPEWhacker@gmail.com>
+Date: Thu, 10 Dec 2020 15:59:47 -0600
+Subject: [PATCH] Revert "regulator: resolve supply after creating regulator"
+
+This commit prevents the serial console from working on the Rock Pi 4
+for some reason. It *appears* to possibly be fixed by some other commit
+upstream, but after a lot of head scratching and bisecting, I was unable
+to find which one, so just revert it for now and we can deal with it
+later.
+
+This reverts commit 96c6b5d5775637b3095ef934f871044811fd4db7.
+
+---
+ drivers/regulator/core.c | 21 ++++++++-------------
+ 1 file changed, 8 insertions(+), 13 deletions(-)
+
+diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
+index 25e601bf9383..be8c709a7488 100644
+--- a/drivers/regulator/core.c
++++ b/drivers/regulator/core.c
+@@ -5187,20 +5187,15 @@ regulator_register(const struct regulator_desc *regulator_desc,
+ else if (regulator_desc->supply_name)
+ rdev->supply_name = regulator_desc->supply_name;
+
++ /*
++ * Attempt to resolve the regulator supply, if specified,
++ * but don't return an error if we fail because we will try
++ * to resolve it again later as more regulators are added.
++ */
++ if (regulator_resolve_supply(rdev))
++ rdev_dbg(rdev, "unable to resolve supply\n");
++
+ ret = set_machine_constraints(rdev, constraints);
+- if (ret == -EPROBE_DEFER) {
+- /* Regulator might be in bypass mode and so needs its supply
+- * to set the constraints */
+- /* FIXME: this currently triggers a chicken-and-egg problem
+- * when creating -SUPPLY symlink in sysfs to a regulator
+- * that is just being created */
+- ret = regulator_resolve_supply(rdev);
+- if (!ret)
+- ret = set_machine_constraints(rdev, constraints);
+- else
+- rdev_dbg(rdev, "unable to resolve supply early: %pe\n",
+- ERR_PTR(ret));
+- }
+ if (ret < 0)
+ goto wash;
+
+--
+2.29.2
+
diff --git a/recipes-kernel/linux/linux-yocto_5.8.bbappend b/recipes-kernel/linux/linux-yocto_5.8.bbappend
new file mode 100644
index 0000000..5a31842
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto_5.8.bbappend
@@ -0,0 +1,4 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+SRC_URI_append_rock-pi-4 = " file://0001-Revert-regulator-resolve-supply-after-creating-regul.patch"
+
--
2.29.2



--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

2201 - 2220 of 53919