Hi all, There is a network forum meeting tomorrow Tue 3 Nov at 8AM PST / 17.00 CET. Current agenda: - WiFi L2 API for non-offloaded devices. See related issue at

Hi Thomas, I’m not sure if the firmware update is even achievable on qemu_x86 platform (same goes with reboot). The lwm2m_client sample does not implement the actual FW update procedure, just

Hi everybody ! I'm trying to builda projet using Zephyr & LWM2M (& Leshan). TL;DR before I startexplaining more precisely my issue : Having issue makinga Firmware Update on a QEMU_x86

Zephyr: Toolchain Working Group When: Monday, 2 November 2020 4:00pm to 5:00pm (GMT+00:00) UTC Where: Microsoft Teams Meeting Description: Live meeting minutes:

Reminder: Zephyr: Toolchain Working Group When: Monday, 2 November 2020, 4:00pm to 5:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

Call for today’s Toolchain WG. Agenda Updates: Thomas: IAR: Updates ? Zephyr SDK. LLVM support compiler-rt. #24917 Linking with lld. Compiler-rt ? Milestones for 2.5, news. Feel free

Hello, I am using the stm32l152re, I am using the mdm_receiver driver to use uart in my project. I want to use a pointer to a callback function in my project to do a k_work_submit in a UART

Hi all, Tuesday (3 Nov) there is a networking forum Teams meeting. Let me know if there are any network related topic you would like to discuss there so I can add it to the agenda. Cheers, Jukka

Zephyr Project: Dev Meeting When: Thursday, 5 November 2020 4:00pm to 5:00pm (UTC+00:00) UTC Repeats: Weekly on Thursday Where: Microsoft Teams Meeting Organizer: devel@... An RSVP is

Reminder: Zephyr Project: Dev Meeting When: Thursday, 29 October 2020, 3:00pm to 4:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

Here’s the agenda topics for this week: * samples: drivers: adc: add demo and fix STM32 sequence configuration: - https://github.com/zephyrproject-rtos/zephyr/pull/25590 * Any PR/issues

Hi, You should just need to add it to the build system's Kconfig and CMakeLists.txt hierarchy like any other file in your module. There are worked examples

Adding an out of tree board is easy, I just set the variable BOARD_ROOT and the build system happily finds my_custom_board. This is nicely described by following the links from here:

Zephyr Project: APIs When: Tuesday, 3 November 2020 5:00pm to 6:00pm (UTC+00:00) UTC Repeats: Weekly on Tuesday Where: Microsoft Teams Meeting Organizer: devel@... An RSVP is requested.

Reminder: Zephyr Project: APIs When: Tuesday, 27 October 2020, 4:00pm to 5:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

Hi all, Agenda for today. - Kernel headers - PR: https://github.com/zephyrproject-rtos/zephyr/pull/29359#issuecomment-713598116 - API and component naming conventions - Issue:

Zephyr: Networking Forum When: Tuesday, 3 November 2020 4:00pm to 5:00pm (UTC+00:00) UTC Repeats: Monthly on the first Tuesday Where: Microsoft Teams Meeting Organizer: tsc@... An RSVP is

Zephyr: Toolchain Working Group When: Monday, 2 November 2020 4:00pm to 5:00pm (UTC+00:00) UTC Repeats: Every 2 weeks on Monday, through Thursday, 17 December 2020 Where: Microsoft Teams

Hi, The use case is for this is could be considered as a intelligent GPIO expander for a much larger project, which offloads peripheral tasks to this chip, but so far

Hi Thomas, Would you mind giving us some details on your use case ? Do you expect to be able to change only the affectation of the pin and apply preconfigured settings ? For instance PIN X is: ALT