Adding Erwan to see if he might have some insight. - k

#stm32 #flash

I am trying Zephyr for first time and just want to get going on an example on an available evaluation board. I found a match for: https://docs.zephyrproject.org/latest/boards/arm/stm3210c_eval/doc/ind

#stm32 #flash

*Root directory = project folder

#stm32 #can

Josef, The BOARD_ROOT works for me even with Stm32 boards. The pinmux is mandatory for alternate functions on st boards. You can run the following commad to set the board root: west build -b hvac_sens

#stm32 #can

Update: CAN bus is working now with my board. I had to move by board config into the Zephyr tree, then pinmuxing seems to work. I still do not know the root cause. My configuration (for CAN) was ident

#stm32 #can

Hi, the driver is built into the kernel, but what I found out yesterday is, that the pinmuxing is not set up correctly. And the STM32 CAN controller will wait until it has received some bits before it

#stm32 #can

Hi Josef To me, the problem look more like you didn’t include the CAN bus drivers when you built the kernel. Try running ‘make menuconfig’ and turning on the CAN bus, then rebuilding. Lawrence King Pr

#stm32 #can

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

With some more debugging it looks like the STM32 CAN initialization fails in the STM32 HAL code: At HAL_CAN_Init() the loop waiting for the INAK bit in the CAN_MSR register to be reset when the initia

#stm32 #can

Hi, I am trying to get the STM32 CAN bus driver running with the latest revision from git. Unfortunately calling device_get_binding() fails and the reason for that is that the pointer 'driver_api' in

#stm32 #can

Hello,

#uart #stm32

Thank you Rodrigo, I'll work on the code you shared with me and I'll let you know the results.

#uart #stm32

Based on the documentation uart_poll_in returns zero to indicate a character arrived. A negative value, which you're checking for in your code, would indicate the operation failed. Chances are it's wo

#uart #stm32

You have to enable uart interrupt at the conf files.

#uart #stm32

The code is: #include <device.h> #include <misc/printk.h> #include <uart.h> #include <zephyr.h> #define SYS_LOG_DOMAIN "UART_DRIVER" #include <logging/sys_log.h> static void (*__uart_callback)(u8_t) =

#uart #stm32

I am not at home. I’ll take a look if I can share that with you. De nada. Abraço, Rodrigo

#uart #stm32

No, I haven't. Can you share a piece of code of how to do this? Obrigado Rodrigo!

#uart #stm32

I am always using a blocking way to write and a non-blocking way to read. Have you tried?

#uart #stm32

Hi Rodrigo, Yes the pins are okay. I can confirm the STM32 is sending a testing message (I connected the sending UART to my computer and read the input). Looks like the code to read the response is no

#uart #stm32

Gustavo, Are you sure the pins are setup ok? You can try to use a ftdi connector to be sure. Do you have an dts overlay? Best regards, Rodrigo

#uart #stm32