Hi everyone, We are pleased to announce the release of Zephyr RTOS version 2.4.0! Major enhancements with this release include: Introduced initial support for virtual memory management. Added Bluetoot

Hi everyone, The third release candidate for Zephyr v2.4.0 has been tagged (v2.4.0-rc3). The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.4.0-rc3 Th

Hi everyone, The second release candidate for Zephyr v2.4.0 has been tagged (v2.4.0-rc2). The merge window for features and enhancements remains closed until v2.4.0 is released. During the stabilizati

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 until 2

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 ta

Hi Muhammad, Please use the Zephyr 2.3.0 release with MicroPython instead of Zephyr master. Maureen

There is already a MicroPython port for Zephyr: https://github.com/micropython/micropython/tree/master/ports/zephyr

Hi everyone, This week the TSC approved the list of current maintainers in #24152. As a result, I have invited all of the approved maintainers to join the zephyrproject-rtos GitHub organization and as

Hi Michele, Yes, this would be a welcome addition. Maureen

Hi Robert, There is a pull request for RT1010. We’re still working on getting it into a mergeable state. https://github.com/zephyrproject-rtos/zephyr/pull/19335 Maureen

Hi Christopher, It’s possible that a stack overflowed. Kinetis platforms have a “system MPU” instead of the Arm MPU, and memory access violations trigger a bus fault. Maureen

It looks like you may have forgotten to #include <nxp/nxp_rt.dtsi> in your board dts file.

API meeting agenda for 9 Jul 2019: Sensors (Maureen/Kevin/Tom) Discussion is postponed on the following. Please review and submit feedback in GitHub before next week: GPIO #15611 (Piotr M) Driver-spec

API meeting agenda for 2 Jul 2019: Counter (Krzysztof C) GPIO (Piotr M) Sensors (Maureen/Kevin/Tom) Driver-specific functions (Peter B) Additional items in the "Triage" column in the GitHub project ma

Hi Aymeric, There is a bare metal flexcan driver in ext/hal/nxp/imx/drivers that you can use as a starting point. You can create a shim to adapt it to the Zephyr CAN API, similar to what has been done

Hi Nick, Once you’ve generated your project with CMake and imported it into Eclipse, you can edit source files in Eclipse and click the “Make” button to recompile your application. Just be careful if

The current Linux kernel version for this device is 4.9. https://www.nxp.com/support/developer-resources/run-time-software/i.mx-developer-resources/i.mx-software-and-development-tool:IMX_SW?&tid=vanIM

Which NXP device are you running embedded Linux? I can check to see if we have plans to update the kernel version.

In Windows you can run zephyr-env.cmd to set ZEPHYR_BASE. It also has a hook to invoke your own zephyrrc.cmd which is handy for setting ZEPHYR_TOOLCHAIN_VARIANT and GCCARMEMB_TOOLCHAIN_PATH.

#gettingstartedguide

Hi all, We are pleased to announce the release of Zephyr kernel version 1.12.0. Major enhancements with this release include: - Asymmetric multiprocessing (AMP) via integration of OpenAMP - Persistent