Hello Zephyr Users, I have inherited a Zephyr project using nRF52832 from another developer and am having an issue migrating from 2.0.0 to 2.1.0. Its probably something simple but I'm fairly new to

Hello Zephyr users and developers, We've just uploaded a pre-release version of west to PyPI with a new feature: manifest imports. We would like your feedback! For a short README you can follow to

Hi all, This week we will focus on a new RFC and GPIO. - RFC: New counter_get_value() API call - https://github.com/zephyrproject-rtos/zephyr/issues/21846 - GPIO: Update on progress - Proposal

For what it's worth 8 months later, I was able to use PyOCD and the the built-in debugger on RT1064-EVK board to flash the Zephyr blinky program using MCUXpresso's flash programmer. Thus avoiding (for

Hi Zephyr users, In order to benefit from a wider range of user options [1], I'm proposing in PR 21791 to upgrade requirement for pyocd to version 0.24.0. Change should not have impact for most users,

Hi, the DHCPv4 code does not really timeout, there is exponential backoff so the system will try to get the IP address as long as needed. For the socket TLS error, you need to enable also mbedTLS as

After further testing, I found that if I step through each instruction with the debugger the individual messages send correctly, but not if I let the program run regularly. In neither case does the

I am attempting to write a basic I2C program using Zephyr, but I am currently unable to sent a single byte over I2C. The program hangs after the first clock falling & rising edge. I'm using external

Hi, using zephyr-v2.1.0 I have build the mqtt_publisher sample application for the stm32f746g_disco and it works fine. I have build the dhcpv4_client sample application for the stm32f746g_disco and it

Hi all, This week we will focus on RFCs and GPIO: - RFC: API Change: PWM: add support for inverted PWM signals. We will try to close on this today. -

Hi Martin, Nrf52832 has 3 RTC's. RTC0 is used for Bluetooth, RTC1 for system clock and RTC2 is usually available for application. You can use RTC2 with counter driver API (see counter.h). Then you

Hi Axel, I've found the following configuration to be the minimal needed to use the Zephyr ieee802154 radio driver w/o the networking stack: CONFIG_IEEE802154=y CONFIG_NETWORKING=y

I forgot to include the overlay file…here it is.

We are trying to understand how to configure sercom3 to allow I2C support. The I2C device is the adafruit_oled_featherwing. I believe I have the I2C, SSD1306, framebuffer (cfg), and display. Below

Dne 06.01.2020 v 18:31 Andy Ross napsal(a): is it 1000ms timeout = 33 cycles, or 1ms timeout = 33 cycles? This is acceptable for short-term timeouts. When this gets into 2.2, can I use

Periodic k_timer's do not work in fractional ticks, no. If you schedule a 1000ms timeout it will be rounded up internally to exactly 33 hardware cycles, and that process will repeat each cycle. So

Hi, I understand that there are some problems because of 32768Hz RTC (I am now using NRF52-DK and want to use NRF52832 in my new HW) as referenced here:

Hi, I understand that there are some problems because of 32768Hz RTC with NRF52832 as referenced here: https://github.com/zephyrproject-rtos/zephyr/issues/9904 , there are some already merged PRs

Instead of adding k_usleep(30), I changed the SPI clock from 210kHz to 406kHz for STM32F769. Then, the problems of A and B are gone. Still I have the problem of C. I receive 0x07 instead of

From what I checked: - A. 74 clocks stop with a change in CS without sufficient delay - B. CMD0 (0x40 0x00 0x00 0x00 0x00 0x94) fails to send 0x40... (instead send 0x20...) - C. CMD0 fails to receive