Adding the following to the agenda: * RFC: device: convert device struct instances to const https://github.com/zephyrproject-rtos/zephyr/pull/25208 - k

Reminder: Zephyr Project: Dev Meeting When: Thursday, 14 May 2020, 8:00am to 9:00am, (GMT-07:00) America/Los Angeles Where:Microsoft Teams Meeting An RSVP is requested. Click here to

Zephyr Toolchain Working Group When: Thursday, 14 May 2020 7:00am to 8:00am (GMT-07:00) America/Los Angeles Where: Microsoft Teams Meeting Description: Topic: Zephyr Toolchain Working

Reminder: Zephyr Toolchain Working Group When: Thursday, 14 May 2020, 7:00am to 8:00am, (GMT-07:00) America/Los Angeles Where:Microsoft Teams Meeting View Event Organizer: Maureen

******************************* NOTE: We will be using Microsoft Teams for this meeting instead of zoom. The link is found below. ******************************* Hi, Due to lack of

Here’s the agenda topics for this week: * Review PR/issues’s tagged with dev-review: * Support for buildtesting SoCs w/o boards https://github.com/zephyrproject-rtos/zephyr/issues/25153 *

Thanks for the feedback. I will go ahead and create an issue on github to describe the issue and show what I have tried so far. Thanks! Brian

Hi Brian, Raising an issue would indeed help to provide support. Don't hesitate to share the work you've already done to ease things. BR Erwan

So I think there are a few things going on here, and have begun to unravel it but I might need some guidance on how to proceed. I intend to utilize the STM32F411E MCU on an upcoming board, but I

As part of the SDK 0.11.x SDK we moved from python2.7 to python3.6 as the version of python that GDB is linked against, partially due to the deprecation of python2.7. There have been several issues

Reminder: Zephyr Project: APIs When: Tuesday, 12 May 2020, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles Where:Microsoft Teams Meeting An RSVP is requested. Click here to

Hi all, ************************************************* We will be using Teams instead of

Hi all, I'd like to ask you to set the milestone in all Pull Requests that need to be merged during the stabilization period (be them bugfix and documentation or special cases, in which case they

Hi Jukka And thank you very much for your very quick answer. I am sorry I haven't repsonded before, but we had a national Holiday in Denmark Friday the 8th. I will try to answer on your

> I'm not quite sure what you are trying to mitigate, exactly. This is the desired behavior. You WANT your two custom threads to run instead of your main thread, that's why they're higher

This will help, Andy. Thanks for your inputs! Regards, Raj

Your understanding is correct. If a higher priority thread is available to run, then a preemptible thread will yield to that thread at every scheduling point. I'm not quite sure what

Hi, This is a question related to thread scheduling. Imagine you have 2 custom threads in addition to the “main thread”. The custom threads are created static (K_THREAD_DEFINE) and are

Sure, that was why “riscv32-zephyr-elf-“ toolchain was removed in the SDK 0.11.0 release: https://github.com/zephyrproject-rtos/sdk-ng/commit/5997df8e3dc78184543f05ccbbc425c2d3c2818b

Thank you! if so,it seems riscv32 toolchain also can take this flag and generate the 64 bit program. riscv32-zephyr-elf-gcc -march=rv64i -mabi=lp64 -c main.c -o