Hi all, Exactly as the subject line says, is it possible to configure the master clock frequency of an I2S peripheral in the device tree? I’m using an nRF5340. I can see that there’s a clock-source pr

Hi Nash, Is this a new installation of WSL Ubuntu, or one that’s been used for other purposes for a while? I ask because I believe the errors you’re seeing are due to those packages already existing o

Hi Christian, You may be able to simplify your conditional statement by instead testing for the presence of CONFIG_BOARD_QEMU_X86 or CONFIG_BOARD_DISCO_L475_IOT1. These should be set somewhere in a *_

I’m sure you’ll get a slew of possible implementations, but have you considered implementing the observer pattern? https://en.wikipedia.org/wiki/Observer_pattern . If I were to implement this, I’d giv

Hi, I’m writing some firmware for both sides of a BLE link. I would like to scan for advertisers, filter the results to find my device, then store the address to be connected later, without necessaril

Hi David. I'm also not an expert, but I'll try to help you if I can. More experienced users can feel free to correct me on this. First off, regarding "And accordingly its the devicetree contains an i2

Solved, and yes, it was a stupid question. Given a closer read of the DT_GPIO_CTLR documentation, I noticed that it returns a node identifier, and not, as I expected a device handle. The correct state

Hi, I’m sure this is a very stupid question, but I haven’t been able to get to get this working. I’ve got the following device tree fragment: gpio0: gpio@842500 { compatible = "nordic,nrf-gpio"; gpio-

There’s not a lot happening behind the scenes. This is the definition of uart_callback_set(): static inline int uart_callback_set(const struct device *dev, uart_callback_t callback, void *user_data) {

Hi, I'm also quite new at Zephyr, but it sounds like west isn't properly detecting the extensions defined by Zephyr, or may have been configured to disallow extensions. As a first step, are you aware

Hi, I’m not an expert in this by any means, but I’d like to point you to https://docs.zephyrproject.org/latest/reference/kconfig/index-all.html , which is a list of all of the config symbols as define

#nrf52832

Sounds good. Thanks for the clarification, Johan. Jason

Hi, It seems as though there are two ways to invoke a callback when a BLE device has been scanned. I can register a callback with bt_le_scan_cb_register, where my callback is the .recv field of the bt

Hi, I’m developing a broadcast audio application with the nRF5340 SoC, based on the iso_broadcast and iso_receive sample. At the moment, I can connect the broadcaster with multiple receivers and trans

Hey Marti, thanks for the advice. In this case specifically, I tracked it down to a pretty silly mistake. I was using the nRF extension for VS Code, but also had the CMake extension installed. I had b

Hey Marti, As far as I can tell, I don't have west currently installed outside of the virtual environment. This project I'm trying to get going predates a tonne of build environment issues I've been f

Hi. I’m trying to build zephyr inside a python virtual environment. It looks like it’s somehow pulling in the base python interpreter, rather than the fake one provided in the virtual environment. Thi

Hi, I’m porting some code from an nRF5340 eval board to my own board, and I’ve run into an issue. While waiting for the net core to boot up, I enter a loop and call k_sleep until an initialization cal

Thanks Armand, I think I‘ve got that working, now, and referenced properly in the CMakeList. A devicetree binding somewhere requires a couple pin definitions, but I can handle that. I did come across

Hi, I’m a complete newcomer to zephyr and devicetree, and I’m running into some trouble trying to enable the I2S peripheral on the nRF5340dk board. I’ve enabled both the I2S driver (Modules->hal_nordi