devel@lists.zephyrproject.org

Zephyr 2.0.0-rc3 tagged

Glaropoulos, Ioannis

#6228

Hi Zephyr developers,

We have now tagged Zephyr 2.0.0-rc3!

All major external dependencies and components, are now up-to-date. All high-priority bugs (including last-minute high-priority issues) have been addressed, and the corresponding PRs are merged to master. We, currently have 16 medium-priority bugs, which is below the threshold required for release.

Details here: https://github.com/zephyrproject-rtos/zephyr/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22priority%3A+medium%22+sort%3Aupdated-desc+-milestone%3Av1.14.1+

We are now in the release testing phase. Master branch is now open only for documentation updates and patches that contribute to the release notes for 2.0. Everything else should wait until after we open the merge window, again.

The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.0.0-rc3

More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

We expect to release Zephyr 2.0 after the release testing completes successfully.

Thanks to everybody who has contributed to this release!

Ioannis Glaropoulos

Från: Glaropoulos, Ioannis
Skickat: den 29 augusti 2019 13:17
Till: devel@...; announce@...
Ämne: VB: Zephyr 2.0.0-rc2 tagged

Hi Zephyr developers,

We have now tagged Zephyr 2.0.0-rc2!

All major external dependencies and components, are now up-to-date. All high-priority bugs have been addressed, and the corresponding PRs are merged to master.

We still have a (relatively short) list of bug-fix PRs that need to be reviewed and merged, in order to drop the bug count below the threshold that is required for the release.

Besides that, documentation updates and patches that contribute to the release notes for 2.0 may be merged to master.

Everything else should wait until after we open the merge window, again.

The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.0.0-rc2

More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

The final release is tentatively scheduled for August 30^th.

Thanks to everybody who has contributed to this release!

Ioannis Glaropoulos

Från: Glaropoulos, Ioannis
Skickat: den 12 augusti 2019 00:38
Till: devel@...; announce@...
Ämne: Zephyr 2.0.0-rc1 tagged

Hi Zephyr developers,

We have just tagged Zephyr 2.0.0-rc1.

All required features scheduled for 2.0 release are now merged into master. As of now we are in the stabilization phase for 2.0 release; the merge window is closed for new features and enhancements, and will remain closed until the release date. We will also start working on filling in the existing skeleton for the release notes.

During the stabilization period bug-fix, documentation, and stabilization-related patches may be merged to master. Additional features or enhancements for 2.0 release will need to be approved by TSC.

As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers.

Testing Zephyr release candidate branches is also highly appreciated; please, test the code base and file bug reports so they can be addressed before the release deadline.

The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.0.0-rc1

More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

The final release is tentatively scheduled for August 30^th.

Thanks to everybody who contributed to this release!

Ioannis Glaropoulos

Upcoming Event: Zephyr Project: APIs - Tue, 09/03/2019 9:00am-10:00am, Please RSVP #cal-reminder

devel@lists.zephyrproject.org Calendar <devel@...>

#6227

Reminder: Zephyr Project: APIs

When: Tuesday, 3 September 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/177647878

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878

Or iPhone one-tap :
    US: +16465588656,,177647878# or +16699006833,,177647878#
Or Telephone:
    Dial(for higher quality, dial a number based on your current location):
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 177 647 878
    International numbers available: https://zoom.us/zoomconference?m=ioAR9GK1OE5LkN1ojt-heTCl7yPcJrhY

Live meeting minutes: https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit?usp=sharing

API meeting: agenda

Carles Cufi

#6226

Hi all,

This week we will look at:

Agenda:

- Sensor API: Potential sharing between V4Z and rtio
- GPIO: Update on https://github.com/zephyrproject-rtos/zephyr/pull/16648 and possibly merging it

Additional items in the "Triage" column in the GitHub project may be discussed if time permits.
If you want an item included in the meeting, please add it to the GitHub project. 

https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-discussion
https://github.com/zephyrproject-rtos/zephyr/projects/18
https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles

Re: OpenThread development guide

Benjamin Lindqvist

#6225

Thanks, I really appreciate the response and especially the PR reference. Will check it out.

Show quoted text

On Mon, Sep 2, 2019 at 12:51 PM Lubos, Robert <Robert.Lubos@...> wrote:

Hi Benjamin,

Sorry for late reply, I’ve just came back from holiday. See my responses inline.

Regards,

Robert

From: devel@... [mailto:devel@...] On Behalf Of Benjamin Lindqvist via Lists.Zephyrproject.Org
Sent: Tuesday, August 27, 2019 13:31
To: devel@...
Cc: devel@...
Subject: [Zephyr-devel] OpenThread development guide

Hi,

I've verified basic OT functionality using the echo_client/server samples with the openthread overlays. That's nice, but it's not obvious to me how I proceed after this. A few things that had me confused:

- how do I configure my Zephyr device as a sleepy end device?

It is not possible to configure Sleepy End Device on current master, there is a PR that adds this functionality though (https://github.com/zephyrproject-rtos/zephyr/pull/15552). It’s been open for some time now, feel free to comment in there if it’s a desired feature for you.

- can I setup my west.yml to clone openthread + dependencies as a module to prevent cmake from doing it at build every time?

This has already been done recently, make sure to check out the current master. West will now download OpenThread for you as a Zephyr module, and use it during OT samples builds.

- can I modify the network credentials at run-time? Or in other words, does Zephyr support anything but hardcoded OT commissioning?

Zephyr supports two ways of obtaining network credentials (commissioning):

Use a preconfigured, hardcoded defaults, specified by Kconfig (good for samples, not really for real applications),
Or perform a commissioning procedure defined by Thread specification during startup (see CONFIG_OPENTHREAD_JOINER_AUTOSTART option).

Both methods will configure your device during initial startup, and store network parameters in the flash. If, for whatever reason, you’d want to modify the network credentials afterwards, you’d need to call OpenThread API directly, there’s no support in Zephyr for that. See https://github.com/zephyrproject-rtos/openthread/blob/0dbecf508e7a79aae8ed9631f1a63fc65478b213/include/openthread/thread.h#L393 for available API functions. Just note, that in order to use OT API directly, you’d need to obtain OT context first from the OT network interface.

- can I build NCP firmware for a border router using Zephyr?

No, Zephyr cannot be configured as a NCP. For a NCP application, check the OpenThread repository.

etc. Right now I get the impression that the openthread integration is in a sort of proof-of-concept stage. Is this the case? If not, it would be nice with some more documentation, perhaps even a sample app...

Well, for sure I’d not call it a proof-of-concept at this point, yet indeed there’s still work to do. Lack of time/resources to push it forward is the only answer I can provide for now.

Re: OpenThread development guide

Lubos, Robert

#6224

Hi Benjamin,

Sorry for late reply, I’ve just came back from holiday. See my responses inline.

Regards,

Robert

Show quoted text

From: devel@... [mailto:devel@...] On Behalf Of Benjamin Lindqvist via Lists.Zephyrproject.Org
Sent: Tuesday, August 27, 2019 13:31
To: devel@...
Cc: devel@...
Subject: [Zephyr-devel] OpenThread development guide

Hi,

I've verified basic OT functionality using the echo_client/server samples with the openthread overlays. That's nice, but it's not obvious to me how I proceed after this. A few things that had me confused:

- how do I configure my Zephyr device as a sleepy end device?

It is not possible to configure Sleepy End Device on current master, there is a PR that adds this functionality though (https://github.com/zephyrproject-rtos/zephyr/pull/15552). It’s been open for some time now, feel free to comment in there if it’s a desired feature for you.

- can I setup my west.yml to clone openthread + dependencies as a module to prevent cmake from doing it at build every time?

This has already been done recently, make sure to check out the current master. West will now download OpenThread for you as a Zephyr module, and use it during OT samples builds.

- can I modify the network credentials at run-time? Or in other words, does Zephyr support anything but hardcoded OT commissioning?

Zephyr supports two ways of obtaining network credentials (commissioning):

Use a preconfigured, hardcoded defaults, specified by Kconfig (good for samples, not really for real applications),
Or perform a commissioning procedure defined by Thread specification during startup (see CONFIG_OPENTHREAD_JOINER_AUTOSTART option).

Both methods will configure your device during initial startup, and store network parameters in the flash. If, for whatever reason, you’d want to modify the network credentials afterwards, you’d need to call OpenThread API directly, there’s no support in Zephyr for that. See https://github.com/zephyrproject-rtos/openthread/blob/0dbecf508e7a79aae8ed9631f1a63fc65478b213/include/openthread/thread.h#L393 for available API functions. Just note, that in order to use OT API directly, you’d need to obtain OT context first from the OT network interface.

- can I build NCP firmware for a border router using Zephyr?

No, Zephyr cannot be configured as a NCP. For a NCP application, check the OpenThread repository.

etc. Right now I get the impression that the openthread integration is in a sort of proof-of-concept stage. Is this the case? If not, it would be nice with some more documentation, perhaps even a sample app...

Well, for sure I’d not call it a proof-of-concept at this point, yet indeed there’s still work to do. Lack of time/resources to push it forward is the only answer I can provide for now.

Re: Build posix sample problem (cmake error) #samples #adc

Bolivar, Marti

#6223

"Alberto Escolar Piedras (ALPI)" <ALPI@demant.com> writes:

Hi Marti,

I get a build error following along with the getting started guide:That would seem to be just a warning.
(At least another developer has also reported it, and I think he was also using Arch Linux)
As far as a I understand it is harmless.

The binary (build/zephyr/zephyr.exe) should have been produced without
issues.You're right, of course.

I looked at the output itself without seeing the "warning" prefix. This
is building and running fine (apart from the warning) using
ZEPHYR_TOOLCHAIN_VARIANT=zephyr for me on my arch system.

Thanks for your fast response!

Andrew, can you please try again with the same toolchain configuration
and let us know if you're still having problems?

Thanks
Marti


BR
Alberto

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On Behalf Of Bolivar, Marti via Lists.Zephyrproject.Org
Sent: Saturday 31 August 2019 06:48
To: andrewtholt60@gmail.com; devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] Build posix sample problem (cmake error) #samples #samples #adc #samples

I can't reproduce this exact issue, but I can confirm that with ZEPHYR_TOOLCHAIN_VARIANT=zephyr and ZEPHYR_TOOLCHAIN_VARIANT=host, I get a build error following along with the getting started guide:

[74/74] Linking C executable zephyr/zephyr.elf
/usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0
/usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0
/usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0

My host objdump is v2.32 on Arch; my zephyr SDK version is 0.10.3.

Marti

"Andrew Holt via Lists.Zephyrproject.Org"
<andrewtholt60=gmail.com@lists.zephyrproject.org> writes:

Hi,

On running:

west build -b native_posix samples/hello_world

I get the following error, any advice or suggestions ?

-- west build: build configuration:
source directory: 
/media/andrewh/SOURCE/Source/zephyrproject/zephyr/samples/hello_world
build directory: 
/media/andrewh/SOURCE/Source/zephyrproject/zephyr/build
BOARD: native_posix (origin: command line)
-- west build: generating a build system CMake Error: The source 
directory "" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
ERROR: command exited with status 1: /usr/bin/cmake 
-B/media/andrewh/SOURCE/Source/zephyrproject/zephyr/build 
-S/media/andrewh/SOURCE/Source/zephyrproject/zephyr/samples/hello_worl
d -GNinja -DBOARD=native_posix

Re: Build posix sample problem (cmake error) #samples #adc

alpi@...

#6222

Hi Marti,

I get a build error following along with the getting started guide:That would seem to be just a warning.
(At least another developer has also reported it, and I think he was also using Arch Linux)
As far as a I understand it is harmless.

The binary (build/zephyr/zephyr.exe) should have been produced without issues.

BR
Alberto

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On Behalf Of Bolivar, Marti via Lists.Zephyrproject.Org
Sent: Saturday 31 August 2019 06:48
To: andrewtholt60@gmail.com; devel@lists.zephyrproject.org
Cc: devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] Build posix sample problem (cmake error) #samples #samples #adc #samples

I can't reproduce this exact issue, but I can confirm that with ZEPHYR_TOOLCHAIN_VARIANT=zephyr and ZEPHYR_TOOLCHAIN_VARIANT=host, I get a build error following along with the getting started guide:

[74/74] Linking C executable zephyr/zephyr.elf
/usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0
/usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0
/usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0

My host objdump is v2.32 on Arch; my zephyr SDK version is 0.10.3.

Marti

"Andrew Holt via Lists.Zephyrproject.Org"
<andrewtholt60=gmail.com@lists.zephyrproject.org> writes:

Hi,

On running:

west build -b native_posix samples/hello_world

I get the following error, any advice or suggestions ?

-- west build: build configuration:
source directory: 
/media/andrewh/SOURCE/Source/zephyrproject/zephyr/samples/hello_world
build directory: 
/media/andrewh/SOURCE/Source/zephyrproject/zephyr/build
BOARD: native_posix (origin: command line)
-- west build: generating a build system CMake Error: The source 
directory "" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
ERROR: command exited with status 1: /usr/bin/cmake 
-B/media/andrewh/SOURCE/Source/zephyrproject/zephyr/build 
-S/media/andrewh/SOURCE/Source/zephyrproject/zephyr/samples/hello_worl
d -GNinja -DBOARD=native_posix

回复: add new boards based on i.mxrt1050

nie ninesun

#6221

Dear Maureen Helm

Thank for your indication.I check the dts file. then I find the upcase of letter for the dts file name is wrong. after I correct. the compile is sucessful

发件人: Maureen Helm <maureen.helm@...>
发送时间: 2019年8月30日 23:22
收件人: xz_nie@... <xz_nie@...>; devel@... <devel@...>
主题: RE: add new boards based on i.mxrt1050

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

Show quoted text

From: devel@... <devel@...> On Behalf Of nie ninesun via Lists.Zephyrproject.Org
Sent: Thursday, August 29, 2019 6:05 PM
To: devel@...
Cc: devel@...
Subject: [Zephyr-devel] add new boards based on i.mxrt1050

Hi, I want to add new board based on boards of mimxrt1050_evk, The difference is flash for mimxrt1050_evk, The flash on my board is winbond w25q32. Then I combine the mimxrt1050_ek.dts and mimxrt1050_evk_qspi.dts.I add following code in mimxrt1050_evk.dts file:

&flexspi0 {

reg = <0x402a8000 0x4000>, <0x60000000 0x800000>;

w25q32: w25q32@0 {

compatible = "winbond,w25q32", "jedec,spi-nor";

label = "W25Q32";

reg = <0>;

spi-max-frequency = <100000000>;

status = "okay";

jedec-id = [ef 40 16];

};

then I use cmake -GNinja -DBOARD=mimxrt1050_OK1052 -DBOARD_ROOT=$rootdir .. to build the configuration. then i use ninja to build the firmware. The following error is displayed:

In file included from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/generated_dts_board.h:20,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/arch.h:20,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/cpu.h:17,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/kernel_includes.h:34,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/kernel.h:17,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/kernel/include/kernel_structs.h:10,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/arch/arm/core/offsets/offsets.c:26:

/home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/asm_inline_gcc.h: In function 'z_arch_irq_lock':

zephyr/include/generated/generated_dts_board_fixups.h:11:32: error: 'DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS' undeclared (first use in this function)

#define DT_NUM_IRQ_PRIO_BITS DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS

^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

zephyr/include/generated/generated_dts_board_fixups.h:11:32: note: in definition of macro 'DT_NUM_IRQ_PRIO_BITS'

#define DT_NUM_IRQ_PRIO_BITS DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS

^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/exc.h:40:31: note: in expansion of macro 'Z_EXC_PRIO'

#define _EXC_IRQ_DEFAULT_PRIO Z_EXC_PRIO(_IRQ_PRIO_OFFSET)

^~~~~~~~~~

/home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/asm_inline_gcc.h:91:9: note: in expansion of macro '_EXC_IRQ_DEFAULT_PRIO'

: "i"(_EXC_IRQ_DEFAULT_PRIO)

^~~~~~~~~~~~~~~~~~~~~

zephyr/include/generated/generated_dts_board_fixups.h:11:32: note: each undeclared identifier is reported only once for each function it appears in

#define DT_NUM_IRQ_PRIO_BITS DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS

^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

zephyr/include/generated/generated_dts_board_fixups.h:11:32: note: in definition of macro 'DT_NUM_IRQ_PRIO_BITS'

#define DT_NUM_IRQ_PRIO_BITS DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS

^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/exc.h:40:31: note: in expansion of macro 'Z_EXC_PRIO'

#define _EXC_IRQ_DEFAULT_PRIO Z_EXC_PRIO(_IRQ_PRIO_OFFSET)

^~~~~~~~~~

/home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/asm_inline_gcc.h:91:9: note: in expansion of macro '_EXC_IRQ_DEFAULT_PRIO'

: "i"(_EXC_IRQ_DEFAULT_PRIO)

^~~~~~~~~~~~~~~~~~~~~

In file included from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/cortex_m/mpu/arm_mpu_v7m.h:10,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/cortex_m/mpu/arm_mpu.h:13,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/arch.h:245,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/cpu.h:17,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/kernel_includes.h:34,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/kernel.h:17,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/kernel/include/kernel_structs.h:10,

from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/arch/arm/core/offsets/offsets.c:26:

/home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/cortex_m/cmsis.h: At top level:

/home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/cortex_m/cmsis.h:92:2: error: #error "DT_NUM_IRQ_PRIO_BITS and __NVIC_PRIO_BITS are not set to the same value"

#error "DT_NUM_IRQ_PRIO_BITS and __NVIC_PRIO_BITS are not set to the same value"

^~~~~

ninja: build stopped: subcommand failed.

who can give me some suggestions about it? Thanks

Re: Build posix sample problem (cmake error) #samples #adc

Bolivar, Marti

#6220

I can't reproduce this exact issue, but I can confirm that with
ZEPHYR_TOOLCHAIN_VARIANT=zephyr and ZEPHYR_TOOLCHAIN_VARIANT=host, I get
a build error following along with the getting started guide:

[74/74] Linking C executable zephyr/zephyr.elf
/usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0
/usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0
/usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0

My host objdump is v2.32 on Arch; my zephyr SDK version is 0.10.3.

Marti

"Andrew Holt via Lists.Zephyrproject.Org"
<andrewtholt60=gmail.com@lists.zephyrproject.org> writes:

Show quoted text

Hi,

On running:

west build -b native_posix samples/hello_world

I get the following error, any advice or suggestions ?

-- west build: build configuration:
source directory: /media/andrewh/SOURCE/Source/zephyrproject/zephyr/samples/hello_world
build directory: /media/andrewh/SOURCE/Source/zephyrproject/zephyr/build
BOARD: native_posix (origin: command line)
-- west build: generating a build system
CMake Error: The source directory "" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
ERROR: command exited with status 1: /usr/bin/cmake -B/media/andrewh/SOURCE/Source/zephyrproject/zephyr/build -S/media/andrewh/SOURCE/Source/zephyrproject/zephyr/samples/hello_world -GNinja -DBOARD=native_posix

Re: add new boards based on i.mxrt1050

Maureen Helm

#6219