Hello, There's no need to open an issue. The alias should be named eeprom-0 in a DTS file, aliases { eeprom-0 = ...; }; but needs to be eeprom_0 (i.e. "lowercase-and-underscores" form) in

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

Hi Carles, thanks, I managed like this: / { aliases { eeprom_0 = &eeprom0; }; }; but eeprom_0 is not a valid alias: dtlib.DTError: /aliases: alias property name 'eeprom_0' should

Hi all, A small addition to the agenda: - PWM: add functions for capturing pwm pulse width and period - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/26026 Carles

Hi all, ************************************************* We will be using Teams instead of

For properties there is /delete-property/ to delete one and then be able to override it. In the case of an alias I am not sure, have you tried to override it directly? Carles On 08/06/2020,

Dear Zephyr developers, According to the Zephyr Project Roles and Contribution Guidelines documentation (https://docs.zephyrproject.org/latest/contribute/project_roles.html#merge-criteria), pull

Hi there, I'm trying to compile test/drivers/eeprom for my board. I see that the code requires the alias 'eeprom_0' defined, but my board does not have it natively. I managed to compile changing in

All, Please make sure to rebase PRs post the 2.3 merge window opening as the change to make C99 integer (PR #25679) types the default supported type in Zephyr will impact most PRs. Ensuring a rebase

HI Michael, I’d say he cleanest way is to do it at the SoC level, like this: https://github.com/zephyrproject-rtos/zephyr/blob/master/soc/arm/atmel_sam/same70/Kconfig.defconfig.series#L83

Hi there. I'm adding a new SAM0 based board. What's the best way to enable optional peripherals? For example, not all users need the PWM driver. Should I: - Put CONFIG_PWM=y and CONFIG_PWM_SAM0=y

Hi all, We are pleased to announce the release of Zephyr RTOS version 2.3.0. Major enhancements with this release include: * A new Zephyr CMake package has been introduced, reducing the need

Zephyr: Toolchain Working Group When: Thursday, 28 May 2020 2:00pm to 3:00pm (UTC+00:00) UTC Repeats: Every 2 weeks on Thursday, through Thursday, 23 July 2020 Where: Microsoft Teams

Zephyr Project: Dev Meeting When: Thursday, 21 May 2020 3:00pm to 4:00pm (UTC+00:00) UTC Repeats: Weekly on Thursday Where: Microsoft Teams Meeting Organizer: devel@... An RSVP is

Reminder: Zephyr Project: Dev Meeting When: Thursday, 4 June 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: * Concept Overview for improving support for serial flash devices via SPI and QSPI [Peter]: https://github.com/zephyrproject-rtos/zephyr/issues/25958 *

Zephyr Project: APIs When: Tuesday, 26 May 2020 4:00pm to 5:00pm (UTC+00:00) UTC Repeats: Weekly on Tuesday Where: Microsoft Teams Meeting Organizer: devel@... An RSVP is requested. Click

Hi all, The second release candidate for Zephyr 2.3.0 has now been tagged (v2.3.0-rc2). The current issue counts are: - 1 high-priority bug - 16 medium-priority bugs The high-priority bug (#23364)

Hi, I am new to Zephyr. I managed to get the LWM2M client working using qemu. How do I get lwm2m working on the nucleo_wb55rg? On RIOT OS, I had to make use of a border router and tap interface to

Zephyr Project: APIs When: Tuesday, 26 May 2020 4:00pm to 5:00pm (UTC+00:00) UTC Repeats: Weekly on Tuesday Where: Microsoft Teams Meeting Organizer: devel@... An RSVP is requested. Click