stm32_discovery_arm_gcc

KO | EN

gitlite — search

#typescript #ai-agents #ai #dsh-plugin #deepseek-harness #open-source #cli #claude-code #codex #developer-tools #react #windows

stm32_discovery_arm_gcc

★ 91 Open GitHub ↗

see README.md (below)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

This repository contains source code for the articles
* [STM32 Discovery Development on Linux](http://www.wolinlabs.com/blog/linux.stm32.discovery.gcc.html) 
* [STM32F4 Discovery Semihosting with the GNU Tools for Embedded ARM Processors Toolchain](http://www.wolinlabs.com/blog/stm32f4.semihosting.html)
* [STM32F4 Discovery Virtual COM/Serial Port](http://www.wolinlabs.com/blog/stm32f4.virtual.com.port.html)

<br>
Contents:

1. LED blinker sample code (buildable)
2. USB virtual serial port code (buildable)
2. Semihosting Hello World sample code (buildable)
3. STM sample code (buildable)
4. STM libraries and headers

<br>
STM libraries, headers, and samples have been modified to work with GNU Tools for ARM Embedded Processors toolchain and STM32F4 Discovery EVB.   Generally this just involved adding Makefiles and a slightly modified version of the TrueStudio linker file.   In the Project directory, everything under Demonstration, FW\_upgrade, and Peripheral\_Examples is buildable from the command line by running 'make'

STM's approach toward 'library code' is somewhat non-traditional.  Rather than building libraries up front and linking them with your source, STM appears to intend for you to include their individual source files in your code's build.   Some of their source files include local headers and modules (i.e. stm32f4xx\_conf.h, stm32f4xx\_it.c/h, system\_stm32f4xx.c, etc) that you modify/store in your source tree.  Because of this, building the library up front wouldn't work properly, as the configuration for some library modules could vary from project to project.

stm32_discovery_arm_gcc

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README