Date   

Control-flow Enforcement Technology (CET) support

Bisiorowski, Rafal
 

Hi,

I’ve tried building zephyr app with GCC compiler flags to enable CET feature (Control-flow Enforcement Technology) “-fcf-protection=full -z cet-report=error”. Unfortunately there’s “error: missing IBT and SHSTK properties”. I’m not yet fully familiar with what is missing, but by checking zephyr’s code there are no ENDBR instructions in assembly code.

Is there any plan to add support for Control-flow Enforcement Technology (CET) in Zephyr?

Is there possibility to add this support on my own or is there a reason why CET shouldn’t be ever supported by Zephyr?

 

Thanks,

Rafal

 


Intel Technology Poland sp. z o.o.
ul. Słowackiego 173 | 80-298 Gdańsk | Sąd Rejonowy Gdańsk Północ | VII Wydział Gospodarczy Krajowego Rejestru Sądowego - KRS 101882 | NIP 957-07-52-316 | Kapitał zakładowy 200.000 PLN.

Ta wiadomość wraz z załącznikami jest przeznaczona dla określonego adresata i może zawierać informacje poufne. W razie przypadkowego otrzymania tej wiadomości, prosimy o powiadomienie nadawcy oraz trwałe jej usunięcie; jakiekolwiek przeglądanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.


System Level Testing for Zephyr Adopters

Pandey, Mithun
 

HI All

 

For the Teams adopting zephyr, what the adopting teams do for automation at system level when everything is put together , Is there any recommendations from the Zephyr Community, or form any of the existing adopters.

 

Thanks and Regards

Mithun


bme680 sample: I2C address in overlay file (nrf52840) does not match described wiring #i2c #nrf52840 #sensor

chrisduf
 

Running the BME680 sample (zephyr/samples/sensor/bme680) on the nrf52840-dk fails and printk "Device (nil) name is".

My BME680 is already packaged (DFRobot SEN0248), and provides connections only for the SCL and SDA lines, not SDO which the package configures itself when in I2C mode (it can also work with SPI).

Reading the BME680 data sheet, I've found that this SDO line will actually set the slave address to:
- 0x76 when connected to GND
- 0x77 when connected to VDDIO
- undefined when floating

Both my package and the wiring described by the sample's README connect SDO to VDDIO, while the nrf52840's overlay file assumes the BME680 I2C address is 0x76.

If I edit nrf52840dk_nrf52840.overlay to probe for address 0x77 instead of 0x76, the sample works fine.

The Adafruit overlay is correct (probes for 0x77).

chris.


Thread safety with multiple shell instances

mbarrett@...
 

Hello,

I'm planning to use two simultaneous shell instances each with a different backend in my application. I have a couple of questions regarding this.
1. Is this possible?
2. Do I need to use a mutex for commands that write to a resource or variable?

Thanks!
Marshal


Re: Adding HAL for new NXP Kinetis device K32L2B31

Carles Cufi
 

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

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
 

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
 

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

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


Are sockets thread safe? #networking

mbarrett@...
 

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
 

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

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
 

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

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


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

Anis
 

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
 

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

401 - 420 of 3109