Hi all, I'd like to inform STM32 DMA users that I'm pushing a change [1] to simplify the definition of the<dma—cells> properties for dma peripherals of the stm32 MCUs. This change now

Hi Nagesh, USB device re-enumeration is a known issue for RCP and OTBR. The topic is still quite fresh in terms of Zephyr, as we do not implement “software” reset OTBR required so far.

Hi All, Issue Description: I am trying to flash and run openthread rcp sample as explained in the link: https://docs.zephyrproject.org/latest/samples/net/openthread/coprocessor/README.html. I am able

Hi Jeff, I have in plan to improve the lis2ds12 with following stuff: 1. Adding stmemsc HAL i/f support 2. Support multi-instance 3. Use common i2c/spi routines 4. Move FS and ODR properties from

Hi Marvin, The Hexiwear board can use the same SPI driver as the FRDM-K64 board, but you need to configure the SPI pinmuxes. Check the schematic to determine which SPI instance and pins to use. They

Adding Armando as codeowner of this driver.

HI Erwan, Thanks for the reply, The second option worked for me, although the build is still showing as using openocd (its already installed ), One more option is working for me

Hi Mithun, Seeing this: File "C:\Users\username\zephyrproject\zephyr\scripts/west_commands\runners\openocd.py", line 114, in do_run self.require(self.openocd_cmd[0]) It seems that west is

HI, I am following the setup steps in given in https://docs.zephyrproject.org/latest/getting_started/index.html Using a Python (3.6) Virtual environment. I was able to build the Blinky example,

Relatively new Zephyr user here. We have a custom board with a LIS2DS12 IMU on it. I've been somewhat ignoring it up to now as it serves a secondary function and we sort of just threw it on there

Hi guys, I am using Zephyr on the Hexiwear Board. I accomplished to use the hearrate sensor and some other sensors on the board. But I am still having trouble with the integrated Display (SSD1351

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

Hi Jason, You have to enable the peripheral in the board devicetree overlay (see below). &i2s0 { status = "okay"; }; Armand

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

We have created a custom nRF9160 board which arrived in Las Vegas which I debug by Teams. The hardware engineer has the same version of Nordic nRF Connect SDK v1.51 (SES) as on my computer. We both

They are used interchangeably. Its unfortunate we haven’t cleaned up platform to be board. Fixtures are different from what is listed in ’supported’ in the board YAML. The board YAML is meant

Hello, I am trying to get a better understanding of Zephyr's testing framework. I have read the documentation, but I still have two questions: 1. Is there a meaniningful difference between the

Hi, I use a CDC_ACM serial port with Zephyr (from git), and using IRQ driven. Here is my ISR: static void usb_serial_irq(const struct device *usb_dev, void *user_data) { while

No one ? :/ João Costa <joaocostalapin@...> escreveu no dia quarta, 16/06/2021 à(s) 17:21:

Hi, I need to access STM32's general purpose timer's quadrature decoding functionality. I'm trying to understand what exactly is needed to expose this, either write a custom driver accessing