search

f9micro / f9-kernel

An efficient and secure microkernel built for ARM Cortex-M cores, inspired by L4
Other
683 stars 145 forks source link

Access to debug via USART on STM32F429I-DISC1 (E01) #163

Open kiritsu-project opened 2 years ago

kiritsu-project commented 2 years ago

Hello, I have been trying to run f9-microkernel on the STM32F429I-DISC1 (revision E01) and interact with it via USART1 on the pins indicated in the user manual ( https://www.st.com/resource/en/user_manual/um1670-discovery-kit-with-stm32f429zi-mcu-stmicroelectronics.pdf ). I couldn´t manage to access the debuger using screen. I wonder if the problem comes from the fact that the board's pin layout differs from the STM32F429IDISCOVERY that was used in the project. Please tell me if you know how to specifically connect to this model (STM32F429I-DISC1) or if you have any idea that could help me. Thanks.

mlouielu commented 2 years ago

Hi, the cause may varies.

The board pin layout is config at [board/*/board.h], for stm32f429, here is the board config: stm32f429, compare to the pin assignment from the sheet, it is the same at PA9 and PA10.

kiritsu-project commented 2 years ago

Thanks I looked at this and effectively the pins seem to be the same. Here are more informations about what I have tried. I am using an esp-prog (ft2232hl) as usart to usb controller connected to stm32 devkit via PA9 and PA10. Another possible cause of the problem I found is that st-link/VCP is connected to usart1 and enabled by default on STM32F429I-DISC1, do you think it is possible that it is somehow blocking usart1 access via pins ? A strange occurence was that i could connect a terminal to USB interface /dev/ttyACM0 on the stm32 and another terminal to interface /dev/ttyUSB1 of the esp-prog and they would just send characters to each other. I think this kind of confirms that st-link interfers with usart1, but I'm not really sure.