Hi Pauli, If you are able to do what you want with Cube HAL then, to interface with zephyr, you just need to redefine the HAL callback (defined as weak in HAL drivr) in your zephyr application. You ca

#stm32

Hi Neo I'd advise you to have a look to STM32 clock control driver. It provides MCO support. It might not provide exactly the requested configuration, but at least it would be a working point that you

#stm32

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 Murad, Seems Cmake somehow convert you build path to a reserved Cmake string that trigger the issue. I'm not familiar with build on windows, but I'd suggest to work around your build path. Erwan

Hi Gustavo, Sorry, I'm not familiar with Dragino, nor J-Link, maybe Endre would know better, as he did the board port. Erwan

Hi Joseph, Which board are you using? Did you check that CAN driver is available for this board? Not sure it has been deployed for the whole STM32 family. Erwan

#stm32 #can

Hi Evan, You'll find the information in SoC's CMSIS file, available in STM32Cube SDK and under ext/hal/st/.../stm32f0/soc/ In that file, there's an enum with IRQ numbers. Erwan

Hi Evan, On most stm32, pinx from all gpios will share the same interrupt. For instance PA3, PC3 and PE3 share the same interrupt and hence same callback. Besides depending on series, you'll have furt

Hi Rob, clock_control_on won't help you for now as it is designed to enabled clock for subsystem (peripheral bus), and not to handle power management operations. The piece of code you need to (re)star

Hi Rob, When exiting stop mode PLL is disabled so you're running on HSI(or similar). This explain the change of clock speed after stop mode is exited. So you need to reconfigure and enable the PLL bef

Hi Stefan There is a PR opened on this exact topic: https://github.com/zephyrproject-rtos/zephyr/pull/8306 I suggest you have a look. Hih Cheers Erwan

#uart #flowcontrol #stm32

Hi Stefan, I've not heard about DFSM support so far, but support would be welcomed indeed. About ADC, I advise to have a look to adc drivers implemented so far /drivers/adc/. You could rely on STM32Cu

Ok, so openoncd support is indeed not provided for this board. And it happens it is not present neither in openocd. Though, it will work by re-using configuration provided for nucleo_l476rg. Duplicate

Hi Carles, There is no particular limitation on STM32L4 that should prevent you to flash and debug. Can you provide us more details on your set up to understand what is going on (board, SW, environmen

Fyi, created https://github.com/zephyrproject-rtos/zephyr/issues/5703

Ok, Thanks Carles. So let me create an issue as a start, and we'll build on that. Regards Erwan

Hi all, Does anyone have ever looked to a NFC library that could be integrated into Zephyr?Would there be any interest? Thanks Erwan

Hi, Can you have a try with following configuration ? #CONFIG_CLOCK_STM32_SYSCLK_SRC_PLL=y CONFIG_CLOCK_STM32_SYSCLK_SRC_HSI=y Erwan

Hi, Looking to the picture of the board you sent me, I can see some differences with the board I have: -Lack of X2, C32, C31, R34, R36 on your board -Lack of C26 on my board. This might be a variant I

Hi, Did you follow steps documented here ? https://www.zephyrproject.org/doc/boards/arm/nucleo_f401re/doc/nucleof401re.html Else, can you provide more information: *command used ("make BOARD=nucleo_f4