Hi Immo, Thanks for your email and interest in the Zephyr project. Your contributions are certainly welcome! Basic Armv8, Cortex-A support for Zephyr was merged

Hi, I've been following the development of Zephyr ever since I attended the Embedded World in Nuremberg back in 2016, and I'd like to thank all those who have contributed to the system's current

Hi Zephyr developers, The the first Zephyr 2.2 release candidate (v2.2.0-rc1) has been tagged. All required features scheduled for the 2.2 release are now merged into master. As of now we are in the

Hello, West 0.7.0 has been released. The main new feature since 0.6.x is the addition of "manifest imports", which let you pull in west.yml files from elsewhere into your own manifest file. You can

https://github.com/zephyrproject-rtos/zephyr/blob/e3d39032eb91973c6fc696696d442fa0f61f92c4/arch/arm/core/aarch32/thread.c#L449 Pretty sure it was around here. Could be that I'm wrong(haven't found

Sigvart, I’d really appreciate if you could try and remember where you might have added that print to deal with the in-line asm getting optimized away. - k

Reminder: Zephyr Project: Dev Meeting When: Thursday, 6 February 2020, 8:00am to 9:00am, (GMT-08:00) America/Los Angeles Where:https://zoom.us/j/993312203 An RSVP is requested. Click here to

Zephyr Toolchain Working Group When: Thursday, 20 February 2020 9:00am to 10:00am (UTC-06:00) America/Chicago Repeats: Every 2 weeks on Thursday, through Thursday, 23 July

Hi guys, Since to flash on mm_swiftio is not supported by pyocd, I want to override the flash algorithm for an external flash by using user script. The user script use pyocd global "target"

All, Meeting Minutes: https://docs.google.com/document/d/1vfgwa1oRVuLA0f4VZW9pMBD2n2kf7ZgI9QCw_4s01gA/edit?usp=sharing Agenda: GitHub PR/Issues: Add support for SiLabs EFR32BG13P SoC [Piotr M] -

Hi, The MCUboot mailing list has been recently moved. We did not re-subscribe previously subscribed users, so for those interested it is now hosted here: https://groups.io/g/mcuboot Cheers, Fabio

Hi all, As of this morning the 313 commits in the topic-gpio branch have been merged into Zephyr's master branch. What this means for you if: a) You are a GPIO API user: - Big chunks of the

Reminder: Zephyr Project: APIs When: Tuesday, 4 February 2020, 9:00am to 10:00am, (GMT-08:00) America/Los Angeles Where:https://zoom.us/j/177647878 An RSVP is requested. Click here to

Hi all, Today we will talk first about GPIO and the merge of the topic-gpio branch to master: - Cleanup the public and private API with typedefs - Testing status - Issues with master CI that

Hi Scott, Yes, the whole “board” concept needs an overhaul to become instead “instances” or “targets” as you say. In the nRF5340, which is a dual-core asymmetric Cortex-M33, we used

Interesting, some parts of the documentation gave me the (wrong?) impression that a BOARD allowed some level of variation and configuration at build

Thanks Kumar - we will go with this convention for naming the target. ie board_cpu. It will work out as long as there are not multiple cpu's on the same board that need different zephyr builds. At

Hi, Thanks Kumar. Please note that this version of the SDK is now required for development on master and is enabled in CI. Anas On 03/02/2020, 05:56, "users@... on behalf of

Hello Christopher, Yes, I will use the Bluetooth chipset with HCI over UART connection. I will check your advice. Thanks, Arnaud

Hello Peter, The chipset I expect to support first is the CC2564 which is not a SOC but a simple HCI adapter. Zephyr will run on another MCU. Regards, Arnaud Le