Hi, We are pleased to announce the release of Zephyr kernel version 1.14.0. The 1.14.0 will be the first Zephyr LTS release that we will support for at least 2 years. Major enhancements with this rele

Adding Erwan to see if he might have some insight. - k

#stm32 #flash

Hi all, We have just tagged Zephyr 1.14.0-rc3. At this point ONLY PRs related to docs or related to a GitHub issue / bug will go in. If a PR fixes a bug it MUST have an associated GitHub issue. Our bu

Hi all, We have just tagged Zephyr 1.14.0-rc2. At this point we are freezing the code base. The focus at this point will be to close out any serious bugs and documentation issues. There will be far mo

The is the first release of the Zephyr SDK that utilizes crosstool-ng to build the toolchains. We utilize crosstool-ng-1.24.0-rc2. Toolchain version: • GCC 8.3 • GDB 8.2.1 • BINUTILS 2.32 • NEWLIB 3.1

The nordic guys probably know better, but its possible that the flash that isn’t carved up is used for code. - k

How is CONFIG_GPIO_PCAL9535A_0_DEV_NAME getting set in your build? - k

Hi all, We have just tagged Zephyr 1.14.0-rc1. All required features that have not been pushed out to 1.14 are now merged, and so we begin the stabilization phase that should run for around 4 weeks th

The reg for max170xx is incorrect, this should be the I2C address you use to talk to the max170xx. This is what you should be doing. Might need the node name to be ‘max170xx@4’ but that shouldn’t impa

That is the version of the ARM embedded toolchain. You can use that version, however Zephyr has an SDK under linux. 0.9.3 is the version of the Zephyr SDK under linux. - k

#nrf52840

Really quickly, I’m not sure if we’ve done anything like this. Typically the testing support has been focused on what we’d use as a developer community for the zephyr project. So we have things like t

#test #ztest

There isn’t anything in particular in Zephyr that would preclude this working. However you’d need to see if the board is capable of exposing all those UARTs, than get all the pin cfg setup in the code

We support boards/SoC with 8KB of RAM like nucleo_f030r8 - k

One would need to port the Happy Gecko SoC and a board to Zephyr. Since Wonder Gecko has been ported, I’d expect that it wouldn’t be too difficult to do this. - k

FYI. - k Begin forwarded message: From: Brett Preston <bpreston@...> Subject: Re: [Zephyr-tsc] OpenIoT Summit / ELCE - CFP Opportunity (closes January 7, 2018) Date: January 3, 2018 at

You should be able to use an device tree overlap file. There’s examples in ./samples/bluetooth/hci_uart. The overlay file needs to be named BOARD_NAME.overlay. I opened up Issue #5408 in GitHub to wor

Curious why on OS-X we need conf build before hand instead of doing what we do on linux? Or are we getting conf from the SDK on linux? - k

I feel like Maureen had written up instructions on bluetooth w/FRDM-K64F, but I can’t seem to find them now. - k

I don’t believe there is a way to change the amount of memory in qemu. Even with switching to the KW41Z guess you are going to run into memory issues (as it has 128k). So are you building your own app

If you just use printf() you will get strings outputted to serial with most default configurations. - k