Hi Thomas, Would you mind giving us some details on your use case ? Do you expect to be able to change only the affectation of the pin and apply preconfigured settings ? For instance PIN X is: ALT FUN

TL;DR: - Upcoming device tree based pin configuration for STM32 based boards - Script generated, SoC package specific *-pinctrl.dtsi files are available in hal_stm32 modules - Each *.pcintrl.dtsi file

Thanks Marti for sharing!

Hi Brian, Raising an issue would indeed help to provide support. Don't hesitate to share the work you've already done to ease things. BR Erwan

#samples

Hi, Can you check following readme section and see if it answers your point? https://github.com/zephyrproject-rtos/hal_stm32/blob/master/README.rst#use-stm32cube-in-your-application Cheers Erwan

Hi Allen, Pinmuxing is one of the remaining areas where device tree is not in use (except for socs with specific pin management such as nrf). So we still rely on the c definition for this. Cheers

Hi, Modifying board pinmux.c (along with boards .dst nd Kconfig.defconfig) is indeed the way to enable the device. It cannot be done otherwise. Once this is done (and tested ok) you can submit the wor

Hi Jan, If you're able to go till the main function, I guess this means QSPI configuration is working correctly. If issue happens following k_sleep call, I'd check potential syscall check issue, but o

Hi all, Optional property 'erase-block-size' is used to describe the minimum size of flash sector on which an erase operation could be applied. It is generated as a device tree generic define DT_FLASH

Hi Adam, We've started to push briks to enable power management on STM32. Two first PRs are: - https://github.com/zephyrproject-rtos/zephyr/pull/18582 that enable LPTIMER to enable a tick source in sl

Hi Marcio, Setting of public address based on flash registers should be done as part of controller init in hci driver. In function bt_ipm_ble_init in drivers/bluetooth/hci/ipm_stm32wb.c It should be d

Hi Jun, I had it working on basic samples like dns_resolve (on latest master). Are you facing some issues ? Erwan

Hi Kumar, What about doc PRs? Thanks Erwan

Hi Stefan, Thanks for sharing code and experience, this is useful! Indeed, we should have a proper DMA driver that could be called from other drivers. While I agree DMA has numerous benefits, I don't

Hi, So, actually, what you request is a revert of https://github.com/zephyrproject-rtos/zephyr/pull/11736, which was fixing LED pinmux from PB12 to PC13, thought which missed doc update. As you mentio

Hi Aaron, This is indeed the expected way to do it. Don't forget to also add "arduino_i2c" in boards' yaml files. Cheers Erwan

Hi Stefan, To generate #define's from dt, you need to provide the matching yaml binding to indicate how fields should be decided, this should be done under dts/bindings/... Generated #define's will be

Making different names is good, but then I think one should be able to identify quickly which is struct and which isn't, What about k_struct_poll_signal or k_poll_signal_struct ?

Sure, would be great to have this LORA board in tree.

You don't have to care about VCP, this is internal to ST-Link chip, just make sure that console is set to uart2(.DTS) and enabled (_defconfig). Great, you should be fine then!