Zephyr: Toolchain Working Group When: Thursday, 10 September 2020 2:00pm to 3:00pm (GMT+00:00) UTC Where: Microsoft Teams Meeting Description: Live meeting minutes:

Reminder: Zephyr: Toolchain Working Group When: Thursday, 10 September 2020, 2:00pm to 3:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to

Call for today’s Toolchain WG. Agenda Updates: PR #22668: Made it for v2.4.0😊 Thomas: IAR: Updates ? Torsten: Toolchain abstraction: PR #24851: Made it for v2.4.0😊 Next steps ?

Hi George, In Zephyr scheduling, after an ISR is done, can a preemptible thread be swapped out, and a higher priority thread, if ready, is allowed to run? Yes this is guaranteed. There should

Hey George, When coming back from an ISR, Zephyr should switch to the highest priority thread that is ready (with some caveats around multiple cooperative threads being ready). At least that is what I

Hi Jett, It should certainly be possible to do this, where you implement driver logic as just code which makes other system calls at a lower-level bus abstraction to interact with the hardware. It

Hi, Jett ✈ Rink via lists.zephyrproject.org <jettrink=google.com@...> writes: The devicetree describes the hardware. Whether or not a particular software driver runs in user

Hi, In Zephyr scheduling, after an ISR is done, can a preemptible thread be swapped out, and a higher priority thread, if ready, is allowed to run? I understand the behaviour for the cooperative

Hey all, Do all "drivers" need to be run in supervisor mode (within the kernel)? I am specifically thinking about external ICs that are connected to an embedded controller running Zephyr via

Hi, Thank you for the info! Regards, Simon

Reminder: Zephyr Project: APIs When: Tuesday, 8 September 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, Special agenda for today: - In order to help with the 2.4 release we will go through bugs labeled API or drivers and try to clean up or assign as many as we can. Teams link:

Hi everyone, The first release candidate for Zephyr 2.4.0 has been tagged (v2.4.0-rc1). The merge window for features and enhancements is now closed for this release, and it will remain closed

Hi all, I am running zephyr 2.2.0 on my board and while developing a multi-threading application, running into a double free at ZEPHY_BASE/lib/os/mempool.c:163. /*Detect common double-free occurrences

Hello, I am using the default Zephyr BLE stack while using the NCS SDK with nrf52840 development board by Nordic. My setup is as follows Board1 – Running a Peripheral_Uart demo code which

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

Hello, The PR was merged. Now ALL device instances are constant. Along with this change: all isr handlers take a const void pointer. To all relevant stakeholders that this may affect: !!! PLEASE

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

Carles has asked me to stand in for him in coordinating this week's API telecon. Topics include: - #26516 add MODBUS RTU subsystem - Anything else added to

Hi everyone, This is a reminder that the v2.4.0 merge window for new features closes this Friday, 4 September. After that, only bug fixes and documentation will be merged until the final release is