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

Let’s get started on a new round of meetings. Agenda Updates: Wayne: PR22668: News / Replacements. Thomas: IAR: Updates Torsten: Toolchain abstraction: Issue:#16031, Draft

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

Hello, I am trying to use Zephyr in my current project. Unfortunately, I can not find any sample project, which is based on a ARM Cortex A7 architecture. Mainly, my idea was to use an already

Hi, Thanks for the confirmation of the patch. And thanks for the update. I was waiting for confirmation before sending update on mailing list. See more comments below. /Torsten

Sorry for the delay in response, got pulled into other duties and was not able to follow up on this in the immediate time frame. Thank you for this PR. More importantly, thank you for fixing the

Hi all, Agenda for tomorrow: - Extend LED API - PR: https://github.com/zephyrproject-rtos/zephyr/pull/26101 - [RFC] API change - Device structure attribute renaming - PR:

Hi, Find answers inline. And for convenience, a link to the fix:https://github.com/dkalowsk/broked_zephyr/pull/1 /torsten

Trying to respond to both replies in the same email here... Sorry if the crudely generated ascii art was not clear enough. The Kconfig* files are in the product directory. I will not claim to know

Hi, I have retested the functionality by relocating SoCs from ${ZEPHYR_BASE}/soc into modules, and this worked as expected. Both when using `zephyr/module.yml` and `-DSOC_ROOT=<path>`. So I

Torsten, Please re-read the original message. You have a hidden dependency that has been overlooked that causes completely out of tree SOCs to not work. The setup works fine for in-tree and within

Hi All, I am looking for help/hints/directions/advice regarding converting Linux device drivers to zephyr? I am mostly interested in sensors. I would appreciate the input of anyone with experience

Charles, Thanks for the prompt response. Do please keep me CC'd on this as I am not on the mailing list. Torsten the longer version might provide some background context for the debug. Happy to

Hi, > Please re-read the original message. You have a hidden dependency that has been overlooked that causes completely out of tree SOCs to not work. The setup works fine for in-tree and within

Note, I will also look into a fix that allows out of tree socs to be located directly under the `${SOC_ROOT}/soc` folder. /torsten

Hi Dan, Sorry for any trouble the latest changes is causing you. With https://github.com/zephyrproject-rtos/zephyr/pull/26715 it is now possible to provide multiple SoC roots, allowing for

Hi Dan, Assuming you have the latest upstream master, then this might be a regression introduced by: https://github.com/zephyrproject-rtos/zephyr/pull/26715 We are certainly not dropping

Hey Zephyr team, Long time no talk. Short version: Using the latest HEAD, I am finding that the kconfig SOC_DIR is not being populated for an out of tree SOC build. This causes a compilation failure

Reminder: Zephyr Project: Dev Meeting When: Thursday, 6 August 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: * Continue discussion on CONFIG_MULTITHREADING=n - Do we continue to support it and what functionality should be expected to work in that