Date   

API meeting: Agenda

Carles Cufi
 


SDK 0.13.1 Release

Kumar Gala
 

Hi,

There is a new SDK 0.13.1 release. This is mainly a bug fix release with the main aspect pulling in fixes for an ARM CVE w/GCC, v8m, and trustzone.

https://nvd.nist.gov/vuln/detail/CVE-2021-35465

Latest version of the SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.13.1

Please download and try things out and report any issues.


• gdb:

• Fix ELF file format support issue on MacOS
• newlib:

• Fixed Xtensa malloc failure issue reported in zephyrproject-rtos/zephyr#38258.
• gcc:

• Pull in patches for Arm-GCC-CVE-2021-35465
• qemu:

• Allow setup of ARC's "virt" board memory size

Thanks to all that contributed fixes and enhancements to this version of the SDK.

- k


Build errors "error: expected ';' before '_Bool'"

marko.panger@...
 
Edited

Hi, I've been building and using Zephyr with success so far. While adding *.c files and include paths to my project the build stared to fail at some point. It looks like "bool" is not defined withing Zephyr when building it. I'm copy pasting the offending part my build output. I've been trying to play around with including stdbool.h in my project, but the issue seems to be how the Zephyr build system stages the build. I'm no expert in this so bear with me.

-- Configuring done
-- Generating done
-- Build files have been written to: /home/markopa/Projects/wm-fork/wm-zephyr/build
-- west build: building application
cmake version 3.16.3 is OK; minimum version is 3.13.1
Running CMake: /usr/bin/cmake --build /home/markopa/Projects/wm-fork/wm-zephyr/build -- -v
[1/190] cd /home/markopa/Projects/wm-fork/wm-zephyr/build/zephyr && /usr/bin/python3.8 /home/markopa/Projects/wm-fork/zephyr/scripts/parse_syscalls.py --include /home/markopa/Projects/wm-fork/zephyr/include --include /home/markopa/Projects/wm-fork/zephyr/drivers --include /home/markopa/Projects/wm-fork/zephyr/subsys/net --json-file /home/markopa/Projects/wm-fork/wm-zephyr/build/zephyr/misc/generated/syscalls.json --tag-struct-file /home/markopa/Projects/wm-fork/wm-zephyr/build/zephyr/misc/generated/struct_tags.json
[2/190] /home/markopa/zephyr-sdk-0.12.4/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DBUILD_VERSION=v2.6.0-rc1-ncs1 -DKERNEL -DNRF52840_XXAA -DUSE_PARTITION_MANAGER=0 -D_FORTIFY_SOURCE=2 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -I/home/markopa/Projects/wm-fork/zephyr/kernel/include -I/home/markopa/Projects/wm-fork/zephyr/arch/arm/include -I/home/markopa/Projects/wm-fork/nrf/drivers/mpsl/clock_control -I/home/markopa/Projects/wm-fork/zephyr/include -Izephyr/include/generated -I/home/markopa/Projects/wm-fork/zephyr/soc/arm/nordic_nrf/nrf52 -I/home/markopa/Projects/wm-fork/zephyr/lib/libc/newlib/include -I/home/markopa/Projects/wm-fork/zephyr/subsys/bluetooth -I/home/markopa/Projects/wm-fork/nrf/include -I/home/markopa/Projects/wm-fork/nrf/lib/multithreading_lock/. -I/home/markopa/Projects/wm-fork/nrf/subsys/bluetooth/controller/. -I/home/markopa/Projects/wm-fork/modules/hal/cmsis/CMSIS/Core/Include -I/home/markopa/Projects/wm-fork/modules/hal/nordic/nrfx -I/home/markopa/Projects/wm-fork/modules/hal/nordic/nrfx/drivers/include -I/home/markopa/Projects/wm-fork/modules/hal/nordic/nrfx/mdk -I/home/markopa/Projects/wm-fork/zephyr/modules/hal_nordic/nrfx/. -I/home/markopa/Projects/wm-fork/modules/crypto/tinycrypt/lib/include -I/home/markopa/Projects/wm-fork/nrfxlib/mpsl/include -I/home/markopa/Projects/wm-fork/nrfxlib/softdevice_controller/include -isystem /home/markopa/Projects/wm-fork/nrfxlib/crypto/nrf_cc310_platform/include -Os -imacros /home/markopa/Projects/wm-fork/wm-zephyr/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -fdiagnostics-color=always -mcpu=cortex-m4 -mthumb -mabi=aapcs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -imacros /home/markopa/Projects/wm-fork/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-address-of-packed-member -Wno-unused-but-set-variable -Werror=implicit-int -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr=CMAKE_SOURCE_DIR -fmacro-prefix-map=/home/markopa/Projects/wm-fork/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/home/markopa/Projects/wm-fork=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=nano.specs -std=c99 -MD -MT zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj -MF zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj.d -o zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj -c /home/markopa/Projects/wm-fork/zephyr/arch/arm/core/offsets/offsets.c
[3/190] cd /home/markopa/Projects/wm-fork/wm-zephyr/build/zephyr && /usr/bin/python3.8 /home/markopa/Projects/wm-fork/zephyr/scripts/gen_offset_header.py -i /home/markopa/Projects/wm-fork/wm-zephyr/build/zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj -o /home/markopa/Projects/wm-fork/wm-zephyr/build/zephyr/include/generated/offsets.h
[4/190] /home/markopa/zephyr-sdk-0.12.4/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DBUILD_VERSION=v2.6.0-rc1-ncs1 -DCNSL_PWD=\"\" -DKERNEL -DNRF52840_XXAA -DNRF52_SERIES -DQP_API_VERSION=691 -DUSE_PARTITION_MANAGER=0 -D_FORTIFY_SOURCE=2 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/inc -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/./components/generated -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../qpc_6.9.2/src -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../qpc_6.9.2/include -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../qpc_6.9.2/ports/zephyr -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/.. -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../components -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../components/generated -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/cbet/CBET/dec -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/mqttsn -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/mqttsn/packets -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/fft/FFT -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/dbspl -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../NordicMeshSDK/mesh/core/api -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../NordicMeshSDK/mesh/core/include -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../NordicMeshSDK/mesh/bearer/api -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../NordicMeshSDK/mesh/bearer/include -I/home/markopa/Projects/wm-fork/nrf/drivers/mpsl/clock_control -I/home/markopa/Projects/wm-fork/zephyr/include -Izephyr/include/generated -I/home/markopa/Projects/wm-fork/zephyr/soc/arm/nordic_nrf/nrf52 -I/home/markopa/Projects/wm-fork/zephyr/lib/libc/newlib/include -I/home/markopa/Projects/wm-fork/zephyr/subsys/bluetooth -I/home/markopa/Projects/wm-fork/nrf/include -I/home/markopa/Projects/wm-fork/nrf/lib/multithreading_lock/. -I/home/markopa/Projects/wm-fork/nrf/subsys/bluetooth/controller/. -I/home/markopa/Projects/wm-fork/modules/hal/cmsis/CMSIS/Core/Include -I/home/markopa/Projects/wm-fork/modules/hal/nordic/nrfx -I/home/markopa/Projects/wm-fork/modules/hal/nordic/nrfx/drivers/include -I/home/markopa/Projects/wm-fork/modules/hal/nordic/nrfx/mdk -I/home/markopa/Projects/wm-fork/zephyr/modules/hal_nordic/nrfx/. -I/home/markopa/Projects/wm-fork/modules/crypto/tinycrypt/lib/include -I/home/markopa/Projects/wm-fork/nrfxlib/mpsl/include -I/home/markopa/Projects/wm-fork/nrfxlib/softdevice_controller/include -isystem /home/markopa/Projects/wm-fork/nrfxlib/crypto/nrf_cc310_platform/include -Os -imacros /home/markopa/Projects/wm-fork/wm-zephyr/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -fdiagnostics-color=always -mcpu=cortex-m4 -mthumb -mabi=aapcs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -imacros /home/markopa/Projects/wm-fork/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-address-of-packed-member -Wno-unused-but-set-variable -Werror=implicit-int -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr=CMAKE_SOURCE_DIR -fmacro-prefix-map=/home/markopa/Projects/wm-fork/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/home/markopa/Projects/wm-fork=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=nano.specs -std=c99 -MD -MT CMakeFiles/app.dir/home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c.obj -MF CMakeFiles/app.dir/home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c.obj.d -o CMakeFiles/app.dir/home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c.obj -c /home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c
FAILED: CMakeFiles/app.dir/home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c.obj
/home/markopa/zephyr-sdk-0.12.4/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DBUILD_VERSION=v2.6.0-rc1-ncs1 -DCNSL_PWD=\"\" -DKERNEL -DNRF52840_XXAA -DNRF52_SERIES -DQP_API_VERSION=691 -DUSE_PARTITION_MANAGER=0 -D_FORTIFY_SOURCE=2 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/inc -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/./components/generated -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../qpc_6.9.2/src -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../qpc_6.9.2/include -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../qpc_6.9.2/ports/zephyr -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/.. -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../components -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../components/generated -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/cbet/CBET/dec -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/mqttsn -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/mqttsn/packets -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/fft/FFT -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../libs/dbspl -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../NordicMeshSDK/mesh/core/api -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../NordicMeshSDK/mesh/core/include -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../NordicMeshSDK/mesh/bearer/api -I/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../NordicMeshSDK/mesh/bearer/include -I/home/markopa/Projects/wm-fork/nrf/drivers/mpsl/clock_control -I/home/markopa/Projects/wm-fork/zephyr/include -Izephyr/include/generated -I/home/markopa/Projects/wm-fork/zephyr/soc/arm/nordic_nrf/nrf52 -I/home/markopa/Projects/wm-fork/zephyr/lib/libc/newlib/include -I/home/markopa/Projects/wm-fork/zephyr/subsys/bluetooth -I/home/markopa/Projects/wm-fork/nrf/include -I/home/markopa/Projects/wm-fork/nrf/lib/multithreading_lock/. -I/home/markopa/Projects/wm-fork/nrf/subsys/bluetooth/controller/. -I/home/markopa/Projects/wm-fork/modules/hal/cmsis/CMSIS/Core/Include -I/home/markopa/Projects/wm-fork/modules/hal/nordic/nrfx -I/home/markopa/Projects/wm-fork/modules/hal/nordic/nrfx/drivers/include -I/home/markopa/Projects/wm-fork/modules/hal/nordic/nrfx/mdk -I/home/markopa/Projects/wm-fork/zephyr/modules/hal_nordic/nrfx/. -I/home/markopa/Projects/wm-fork/modules/crypto/tinycrypt/lib/include -I/home/markopa/Projects/wm-fork/nrfxlib/mpsl/include -I/home/markopa/Projects/wm-fork/nrfxlib/softdevice_controller/include -isystem /home/markopa/Projects/wm-fork/nrfxlib/crypto/nrf_cc310_platform/include -Os -imacros /home/markopa/Projects/wm-fork/wm-zephyr/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -fdiagnostics-color=always -mcpu=cortex-m4 -mthumb -mabi=aapcs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -imacros /home/markopa/Projects/wm-fork/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-address-of-packed-member -Wno-unused-but-set-variable -Werror=implicit-int -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=/home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr=CMAKE_SOURCE_DIR -fmacro-prefix-map=/home/markopa/Projects/wm-fork/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/home/markopa/Projects/wm-fork=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=nano.specs -std=c99 -MD -MT CMakeFiles/app.dir/home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c.obj -MF CMakeFiles/app.dir/home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c.obj.d -o CMakeFiles/app.dir/home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c.obj -c /home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c
In file included from /home/markopa/Projects/wm-fork/zephyr/include/kernel_includes.h:31,
from /home/markopa/Projects/wm-fork/zephyr/include/kernel.h:17,
from /home/markopa/Projects/wm-fork/zephyr/include/zephyr.h:18,
from /home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../qpc_6.9.2/ports/zephyr/qf_port.h:5,
from /home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c:41:
/home/markopa/Projects/wm-fork/zephyr/include/syscall.h:93:21: error: expected ';' before '_Bool'
93 | static ALWAYS_INLINE bool z_syscall_trap(void)
| ^
| ;
In file included from /home/markopa/Projects/wm-fork/zephyr/include/kernel_includes.h:32,
from /home/markopa/Projects/wm-fork/zephyr/include/kernel.h:17,
from /home/markopa/Projects/wm-fork/zephyr/include/zephyr.h:18,
from /home/markopa/Projects/wm-fork/wm-zephyr/bsp_wm_zephyr/../qpc_6.9.2/ports/zephyr/qf_port.h:5,
from /home/markopa/Projects/wm-fork/wm-zephyr/qpc_6.9.2/src/qf/qf_ps.c:41:
/home/markopa/Projects/wm-fork/zephyr/include/sys/printk.h:59:22: error: expected declaration specifiers or '...' before numeric constant
59 | extern __printf_like(1, 2) void printk(const char *fmt, ...);


Re: jlink RTT on stm32 nucleo board #stm32 #jlink

Erwan Gouriou
 

Hi, 

There's actually a PR proposed to solve this:

Please have a test

On Tue, 14 Sept 2021 at 03:01, <medanis.messaoud@...> wrote:

does jlink RTT currently work on stm32 boards?

I am testing the demo projects, I can get RTT to work on nrf52dk but not on stm32.

is there any specific settings that needs to be added for stm32 chips?

thanks


jlink RTT on stm32 nucleo board #stm32 #jlink

medanis.messaoud@...
 

does jlink RTT currently work on stm32 boards?

I am testing the demo projects, I can get RTT to work on nrf52dk but not on stm32.

is there any specific settings that needs to be added for stm32 chips?

thanks


Re: Help using SystemView on an STM32 Nucleo board with re-flashed ST-Link #jlink #stm32

medanis.messaoud@...
 

this only works on nrf boards, it doesn't seem to work on stm32.

did you guys have any luck with getting SystemView to work on an STM32 Nucleo board


Re: HCI Driver not registered on the ST SensorTile.box #bluetooth #stm32 #hci

Erwan Gouriou
 

Hi Garret,

Unfortunately no, BT is not enabled on this platform.
Actually the bluetooth application processor (BlueNRG-M2) is not ported in Zephyr yet.
This might not be a major work as it would consist in enabling communication between
Zephyr BLE host and BlueNRG controller, using existing hci over (spi/uart ?) driver.
Apparently, no one took the time to do it yet (or succeeded to do it).

Cheers
Erwan




On Wed, 8 Sept 2021 at 22:01, <garrett.battaglia@...> wrote:
Hello y'all.
Looking at the supported board docs for the ST SensorTile.box it seems like zephyr should support bluetooth on this board. However, when I try and enable bluetooth (using bt_enable(...)) I get back "bt_hci_core: No HCI driver registered" and "main:Bluetooth init failed (err -19)". I believe I have my config set up correctly but I'm not 100% sure.

I have also tried other samples in the zephyr repo to no avail.

Any thoughts or ideas on how to resolve this would be greatly appreciated.

Thanks, Garrett


FW: Moving from Slack to Discord

Carles Cufi
 

-----Original Message-----
From: Cufi, Carles
Sent: 03 September 2021 19:38
To: devel@lists.zephyrproject.org
Subject: Moving from Slack to Discord

Hi all,

As voted during the TSC meeting on the 11th of August this year, the Zephyr Project is transitioning from Slack to Discord for real-time chat.
This transition will take place starting today, and the following steps have been taken already:

- Zephyr's new Discord server is up and running
- The new address for joining Zephyr's chat (i.e. Discord) is https://chat.zephyrproject.org/
- A subset of the existing Slack channels has been re-created in Discord. If you require additional channels to be created please contact the #discord channel in Discord itself
- An automated message will warn users on Slack about the transition so that they are informed.

[1] https://docs.google.com/document/d/1eHxigBEO1dDiq1O8IP5wX807CtLphh60Guu7jW_etKk/edit#


Thanks,

Carles


MCUboot/HCI-USB bug #hci #mcuboot #nrf52

mhamel@...
 

I believe I have found a bug in the current HCI-USB code for the nRF52 series when it is started from the MCUboot bootloader. This is on the current Zephyr 2.6 branch.
In usb_dc_nrfx.c, usb_dc_attach() there is provision for dealing with the absence of a NRFX_POWER_USB_EVT_DETECTED when starting up from a USB bootloader, by generating such an event. This eventually calls nrfx_usbd.c, usbd_enable(). This code hangs in usbd_eventcause_wait_and_clear(NRF_USBD_EVENTCAUSE_READY_MASK), waiting for a ready state that never occurs.
What seems to have recently changed is that the USB driver comes up in the NRFX_POWER_USB_STATE_READY state, not NRFX_POWER_USB_STATE_CONNECTED.
My workaround for this problem is to edit nrfx_usbd.c to add

if (nrfx_power_usbstatus_get() != NRFX_POWER_USB_STATE_READY)

just before the call to usbd_eventcause_wait_and_clear(), but although this seems to fix the problem I have no idea whether its the right solution or not.


HCI Driver not registered on the ST SensorTile.box #bluetooth #stm32 #hci

Garrett
 

Hello y'all.
Looking at the supported board docs for the ST SensorTile.box it seems like zephyr should support bluetooth on this board. However, when I try and enable bluetooth (using bt_enable(...)) I get back "bt_hci_core: No HCI driver registered" and "main:Bluetooth init failed (err -19)". I believe I have my config set up correctly but I'm not 100% sure.

I have also tried other samples in the zephyr repo to no avail.

Any thoughts or ideas on how to resolve this would be greatly appreciated.

Thanks, Garrett


Re: NRF52832 BLE controller (HCI_UART sample) not working

Carles Cufi
 

Hi there,

Can you please try this patch:
https://github.com/zephyrproject-rtos/zephyr/pull/38367

Thanks,

Carles

-----Original Message-----
From: users@lists.zephyrproject.org <users@lists.zephyrproject.org> On
Behalf Of VinhTran via lists.zephyrproject.org
Sent: 08 September 2021 14:09
To: users@lists.zephyrproject.org
Subject: [Zephyr-users] NRF52832 BLE controller (HCI_UART sample) not
working

Hi,

I tried to follow the instructions here:
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdevelope
r.nordicsemi.com%2FnRF_Connect_SDK%2Fdoc%2F1.3.0%2Fzephyr%2Fsamples%2Fblue
tooth%2Fhci_uart%2FREADME.html&amp;data=04%7C01%7Ccarles.cufi%40nordicsemi
.no%7C772157d7716a4ae3290408d972c54359%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%
7C0%7C0%7C637667014102464076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL
CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=cqfmNNgIlTz
Ufv0RRGavW0jz0Vl4wl5CTxzTGXg0z70%3D&amp;reserved=0.
The Zephyr version is 2.6.0, with SDK 0.13.0. On my machine Kubuntu
20.04 is running (kernel ver. 5.11.0),  with BlueZ v. 5.53

btmon seem to report device detection as in this gist:
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.git
hub.com%2Fvinhtran99%2F9ddaf9bf6d4406cf8d0b401a5879703e&amp;data=04%7C01%7
Ccarles.cufi%40nordicsemi.no%7C772157d7716a4ae3290408d972c54359%7C28e5afa2
bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637667014102469054%7CUnknown%7CTWFpbGZs
b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3
000&amp;sdata=%2FKpiwXkTM%2FAmn2%2FyXbL7fIE3WJkNGza0G9ZWDg4qxGo%3D&amp;res
erved=0

But any command from btmgmt only returns failed with status 0x11 (Invalid
Index).

Best regards,

Tran





NRF52832 BLE controller (HCI_UART sample) not working

thevinh130799@...
 

Hi,

I tried to follow the instructions here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.3.0/zephyr/samples/bluetooth/hci_uart/README.html. The Zephyr version is 2.6.0, with SDK 0.13.0. On my machine Kubuntu 20.04 is running (kernel ver. 5.11.0),  with BlueZ v. 5.53

btmon seem to report device detection as in this gist: https://gist.github.com/vinhtran99/9ddaf9bf6d4406cf8d0b401a5879703e

But any command from btmgmt only returns failed with status 0x11 (Invalid Index).

Best regards,

Tran


Re: rs485 driver #stm32

Dave Nadler
 

Careful, while that may work in some cases,
we've always needed to implement fast control of xmit/receive switching in the driver
to avoid multiple devices sometimes trying to drive the bus.

Can any Zephyr users/developers provide further information about driver support for RS-485??

Thanks,
Best Regards, Dave

On 9/2/2021 10:03 AM, Rodrigo Peixoto wrote:
Hi Arsenii.
I have already used that with an external transceiver driving the RE/DE every time we would write to and disable it after that as a generic GPIO (output). We write the data using a regular UART driver. The RS485 part is performed by the transceiver. 

I hope it helps.
Best regards,
Rodrigo Peixoto. 

On Wed, Sep 1, 2021 at 8:35 AM Arsenii Soitu <seniasoitu@...> wrote:
Hello.
Is there any driver or may be some way to use rs485 on zephyr?
May be someone used zephyr for rs485 communication with RE/DE support?
Thank you
_._,_._,_

Links:

You receive all messages sent to this group.

View/Reply Online (#2694) | Reply To Sender | Reply To Group | Mute This Topic | New Topic
Mute #stm32
Your Subscription | Contact Group Owner | Unsubscribe [drn@...]


-- 
Dave Nadler, USA East Coast voice (978) 263-0097, drn@..., Skype 
 Dave.Nadler1


Zephyr Question

Hulbert Zeng <hzeng012@...>
 

Dear Whom It May Concern,


I'm currently using Zephyr on a Nordic Thingy 52 to collect environment data and I was wondering how I might be able to lower the power consumption in between measurements?


Thank You,

Hulbert Zeng


Re: rs485 driver #stm32

Rodrigo Peixoto <rodrigopex@...>
 

Hi Arsenii.
I have already used that with an external transceiver driving the RE/DE every time we would write to and disable it after that as a generic GPIO (output). We write the data using a regular UART driver. The RS485 part is performed by the transceiver. 

I hope it helps.
Best regards,
Rodrigo Peixoto. 

On Wed, Sep 1, 2021 at 8:35 AM Arsenii Soitu <seniasoitu@...> wrote:
Hello.
Is there any driver or may be some way to use rs485 on zephyr? May be someone used zephyr for rs485 communication with RE/DE support?
Thank you


rs485 driver #stm32

Arsenii Soitu
 

Hello.
Is there any driver or may be some way to use rs485 on zephyr? May be someone used zephyr for rs485 communication with RE/DE support?
Thank you


Re: #stm32 build failure #stm32

alt.mcarter@...
 

I think I sent a private reply rather than to group. Let me try again ...
Which version of which toolchain are you using, and which version of zephyr?
Everything is a recent install.
zephyr-sdk-0.13.0

Version of zephyr I'm using:
commit fcfe597e5dadb96ecef5d6e8c82ffc99b5f4d59c (HEAD -> main, origin/main, origin/HEAD)
Author: Iuliana Prodan <iuliana.prodan@...>
Date:   Sat Aug 28 01:08:19 2021 +0300
OK, so now I checkout tag zephyr-v2.6.0.

Then I do
rm -rf build

mkdir build

cd build

cmake ..

I get
Including boilerplate (Zephyr base): /home/pi/zephyrproject/zephyr/cmake/app/boilerplate.cmake
CMake Deprecation Warning at /home/pi/zephyrproject/zephyr/cmake/app/boilerplate.cmake:37 (cmake_policy):
  The OLD behavior for policy CMP0079 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.

I had that before, though.

My errors are now:
Parsing /home/pi/zephyrproject/zephyr/Kconfig
/home/pi/zephyrproject/zephyr/scripts/kconfig/kconfig.py: /home/pi/zephyrproject/my_blinky/build/Kconfig/Kconfig.modules:2: Could not open '/home/pi/zephyrproject/zephyr/' (in 'osource "$(ZEPHYR_CANOPENNODE_KCONFIG)"') (EISDIR: Is a directory)
CMake Error at /home/pi/zephyrproject/zephyr/cmake/kconfig.cmake:264 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /home/pi/zephyrproject/zephyr/cmake/app/boilerplate.cmake:565 (include)
  /home/pi/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /home/pi/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
  CMakeLists.txt:4 (find_package)


-- Configuring incomplete, errors occurred!


Re: #stm32 build failure #stm32

Nick Stoughton
 

Which version of which toolchain are you using, and which version of zephyr?
-- 
Nick


On Tue, Aug 31, 2021 at 11:34 AM <alt.mcarter@...> wrote:
I'm trying to build a project. I'm getting:
 48%] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/cpu_idle.S.obj
cc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
cc: error: unrecognized argument in option '-mabi=aapcs'
cc: note: valid arguments to '-mabi=' are: ms sysv
cc: error: unrecognized command-line option '-mthumb'
gmake[2]: *** [zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/build.make:75: zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/cpu_idle.S.obj] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:2814: zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/all] Error 2
gmake: *** [Makefile:91: all] Error 2
FATAL ERROR: command exited with status 2: /home/pi/.local/bin/cmake --build /home/pi/zephyrproject/my_blinky/build
Here's my CMakeLists.txt file:
cmake_minimum_required(VERSION 3.20.0)
set(BOARD blackpill_f411ce)
#include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(zblinky)
target_sources(app PRIVATE main.c)
What is going wrong?


#stm32 build failure #stm32

alt.mcarter@...
 

I'm trying to build a project. I'm getting:
 48%] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/cpu_idle.S.obj
cc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
cc: error: unrecognized argument in option '-mabi=aapcs'
cc: note: valid arguments to '-mabi=' are: ms sysv
cc: error: unrecognized command-line option '-mthumb'
gmake[2]: *** [zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/build.make:75: zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/cpu_idle.S.obj] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:2814: zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/all] Error 2
gmake: *** [Makefile:91: all] Error 2
FATAL ERROR: command exited with status 2: /home/pi/.local/bin/cmake --build /home/pi/zephyrproject/my_blinky/build
Here's my CMakeLists.txt file:
cmake_minimum_required(VERSION 3.20.0)
set(BOARD blackpill_f411ce)
#include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(zblinky)
target_sources(app PRIVATE main.c)
What is going wrong?


Re: west installation error

Moiz Terem <moiz.terem@...>
 

Thanks for the answers,  yes disabling the Symantec solve the issue.

Best Regards,
Moiz


From: Bolivar, Marti <Marti.Bolivar@...>
Sent: Monday, August 23, 2021 9:09:57 PM
To: Moiz Terem <moiz.terem@...>; users@... <users@...>
Subject: Re: [Zephyr-users] west installation error
 
CAUTION: External Email.

Hi,

See inline.

"Moiz Terem via lists.zephyrproject.org"
<moiz.terem=inomize.com@...> writes:

> Can you also temporarily disable the Symantec ? to check if this is
> the issue?

I'm not sure what you are asking. PyPI doesn't have any relationship
with Symantec that I am aware of, if that's what you mean.

>
> Best Regards,
> Moiz Terem
>
> From: Moiz Terem
> Sent: Sunday, 22 August 2021 15:02
> To: users@...
> Subject: west installation error
>
> Hi,
>
> I am trying to install Zephyr for Windows. I followed your installation steps.
>
> When installing west, I am getting the following errors:
>
> Thanks for your help.
>
>
> [Window]

Looks like an SSL issue. Perhaps your computer doesn't have the
necessary certificate authorities configured? I don't think this is a
PyPI issue; it's rather more likely an issue with your local
environment.

Sorry I'm not more help, but maybe someone else more familiar with
Windows SSL issues like these can chime in.

Best,
Martí

>
>
> Best Regards,
> Moiz Terem
>
>
>
>

101 - 120 of 2796