Hello everyone,
My name is Peng Shun, a freshman in communication engineering. I’ve just setup the environment and changed the greeting to “Hello RTEMS”. The test passed.
Screenshot attached below shows the sis simulation result and the patch.
I have few hands-on experiences with HAL and stm32f4, stm32f1, build projects like three wheels line follower with at8236-driven dc motors, vision tester with uart screen. I also added a HAL-based BSP layer for my line follower.
I’m interested in “Improving the STM32F4 with GPIO, SPI, DMA”.
I’m looking forward to contributing to the project and learn from the experience!
Thanks, you can add yourself to tracking/2026 · main · RTEMS / Programs / Google Summer of Code · GitLab.
There are some topics open already about the STM32F4 project idea(s), you can search here for them. If you don’t find any relevant, you can start a new topic to discuss your projecct interests.
Hello Gedare
Thank you for your reply.
I’ve add myself to the tracking/2026 weeks ago. Recently I’m trying to run the test suite on a f407vet6.
I built arm toolchain, edited config.ini, using USART_1 (PA9/PA10) as console output, using arm-rtems7-objcopy to turn the hello.exe elf into binary file and using openocd to burn it onto the board. I used a ch340, connecting the board to computer. And inspect the output through the UART helper. Nothing printed till replaced #define CONFIGURE_APPLICATION_NEEDS_SIMPLE_CONSOLE_DRIVER to #define CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER in init.c.
I’m going to read the relevant posts on the forum and write my proposal. If appropriate I will engage in the discussions.
