users@lists.zephyrproject.org

Re: Adding HAL for new NXP Kinetis device K32L2B31

Carles Cufi

#2718

Hi there,

Why don’t you send a Pull Request to the hal_nxp repository to add the HAL you need?

Thanks,

Carles

From: users@... <users@...> On Behalf Of Claude Henry via lists.zephyrproject.org
Sent: 23 September 2021 16:19
To: users@...
Subject: [Zephyr-users] Adding HAL for new NXP Kinetis device K32L2B31

Hi,

I need to add a new CPU "K32L2B31A" HAL from NXP to the NXP HAL module.

Can I do this by creating an external NXP module an using the ZEPHYR_EXTRA_MODULES variable to declare this new module ?

I tried this way without success because the build mechanism was searching this module in the Zephyr tree.

I think the problem is that my module must be known as an "hal_nxp" module which is in conflict with the Zephyr based "hal_nxp" module.

Is the best way to directly integrate this new CPU in the "hal_nxp" module repository ?

Regards

Claude Henry

Adding HAL for new NXP Kinetis device K32L2B31

claude@...

#2717

Hi,

I need to add a new CPU "K32L2B31A" HAL from NXP to the NXP HAL module.

Can I do this by creating an external NXP module an using the ZEPHYR_EXTRA_MODULES variable to declare this new module ?

I tried this way without success because the build mechanism was searching this module in the Zephyr tree.

I think the problem is that my module must be known as an "hal_nxp" module which is in conflict with the Zephyr based "hal_nxp" module.

Is the best way to directly integrate this new CPU in the "hal_nxp" module repository ?

Regards

Claude Henry

How to use gsm_modem sample on the nrf5340dk #networking #nrf5340

Brenton Chetty

#2716

Hi Zephyr Users

Hope all is good with everyone.

- I am trying to use the nrf5340dk with the Ublox Lara-R211 GSM modem.
- I managed to get the nucleo_f746zg board working with this modem using the gsm_modem sample.
- I am not sure how to use this example with the nrf5340dk, as the nrf requires programming of "cpuapp" and "cpunet"
The gsm_modem example compiles successfully for cpunet but it gives the following error for cpuapp
"
zephyr-sdk-0.12.4/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/libzephyr.a(ppp.c.obj): in function `sys_rand32_get':
zephyrproject/zephyr/build/zephyr/include/generated/syscalls/rand32.h:35: undefined reference to `z_impl_sys_rand32_get'
"

Could someone please assist me with regards to how to program the nrf5340dk to use the gsm_modem sample correctly.

With thanks
Brenton

Re: Are sockets thread safe? #networking

Lubos, Robert

#2715

Hi,

Yes, socket API is thread safe.

Regards,

Robert

From: users@... <users@...> On Behalf Of mbarrett via lists.zephyrproject.org
Sent: środa, 22 września 2021 20:11
To: users@...
Subject: [Zephyr-users] Are sockets thread safe? #networking

I would like to open multiple TCP sockets in different threads, but before diving in and writing code I thought I would check and see. Are sockets thread safe? Each thread would have sole access to the socket.

Thanks!

Re: Are sockets thread safe? #networking

mbarrett@...

#2714

From some previous release notes it appear so.
https://lists.zephyrproject.org/g/users/message/992

Are sockets thread safe? #networking

mbarrett@...

#2713

I would like to open multiple TCP sockets in different threads, but before diving in and writing code I thought I would check and see. Are sockets thread safe? Each thread would have sole access to the socket.

Thanks!

Minimum required Zephyr SDK version update to 0.13.1

Stephanos Ioannidis

#2712

Hi all,

The Zephyr SDK 0.13.1 will be required to build the Zephyr main branch after #38733 is merged (to be merged in a day or so).

Please download and install the Zephyr SDK 0.13.1 from the following link:

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

Regards,

Stephanos

Re: [Zephyr-devel] API meeting: Agenda

Carlo Caione <ccaione@...>

#2711

On 20/09/2021 22:07, Carles Cufi wrote:
Hi all,
Agenda for tomorrow:
- Pinctrl: Now focusing on #37572 as the single PR to target our efforts
   - PR: https://github.com/zephyrproject-rtos/zephyr/pull/37572
         - Updates by Gerard and Kumar on the state of the PR
   - Discussion, specifically Devicetree layout format: https://github.com/zephyrproject-rtos/zephyr/discussions/35077#discussioncomment-1201394
If you have additional items please let me know.Hey Carles,
can we talk about https://github.com/zephyrproject-rtos/zephyr/issues/38609 as well?

Thank you,

-- 
Carlo Caione

Re: API meeting: Agenda

Carles Cufi

#2710

Additional item, as per the Stable API Change procedure:

- RFC: API Change: IPM
  - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/38609
  - PR: https://github.com/zephyrproject-rtos/zephyr/pull/38523

Carles

Show quoted text

-----Original Message-----
From: Cufi, Carles
Sent: 20 September 2021 22:07
To: devel@...
Cc: users@...
Subject: API meeting: Agenda

Hi all,

Agenda for tomorrow:

- Pinctrl: Now focusing on #37572 as the single PR to target our efforts
  - PR: https://github.com/zephyrproject-rtos/zephyr/pull/37572
        - Updates by Gerard and Kumar on the state of the PR
  - Discussion, specifically Devicetree layout format:
https://github.com/zephyrproject-
rtos/zephyr/discussions/35077#discussioncomment-1201394

If you have additional items please let me know.

Teams link: https://teams.microsoft.com/l/meetup-
join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40threa
d.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-
b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-
5e334e88f6d8%22%7d

https://lists.zephyrproject.org/g/devel/calendar
https://github.com/zephyrproject-rtos/zephyr/projects/18

Minutes:
https://docs.google.com/document/d/1lv-
8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles

API meeting: Agenda

Carles Cufi

#2709

Hi all,

Agenda for tomorrow:

- Pinctrl: Now focusing on #37572 as the single PR to target our efforts
  - PR: https://github.com/zephyrproject-rtos/zephyr/pull/37572
        - Updates by Gerard and Kumar on the state of the PR
  - Discussion, specifically Devicetree layout format: https://github.com/zephyrproject-rtos/zephyr/discussions/35077#discussioncomment-1201394

If you have additional items please let me know.

Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d

https://lists.zephyrproject.org/g/devel/calendar
https://github.com/zephyrproject-rtos/zephyr/projects/18

Minutes:
https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles

SDK 0.13.1 Release

Kumar Gala

#2708

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@...

#2707
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

#2706

Hi,

There's actually a PR proposed to solve this:

https://github.com/zephyrproject-rtos/zephyr/pull/38561

Please have a test

Show quoted text

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

Anis

#2705

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

Anis

#2704

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

#2703

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

Show quoted text

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

#2702

Show quoted text

-----Original Message-----
From: Cufi, Carles 
Sent: 03 September 2021 19:38
To: devel@...
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@...

#2701

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

#2700

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

#2699

Hi there,

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

Thanks,

Carles

Show quoted text

-----Original Message-----
From: users@... <users@...> On
Behalf Of VinhTran via lists.zephyrproject.org
Sent: 08 September 2021 14:09
To: users@...
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