feat: project setup

[noodlekid]

Initial Project Setup: STM32F103C8 + FreeRTOS + PlatformIO

Hopefully simple and bloat reduced project setup you guys can start working on. SPI and CAN peripheral have been generated, it is just boilerplate you will have to specify further clock speeds and configure them properly.

Next steps

• Configure SPI (Main Peripheral and Chip Select GPIO)
• Configure CAN Peripheral
• Setup minimal structures for RTOS (Queue? Locks? Depends on how you design it)

[github-actions]

Build Successful

Firmware Size:

Processing bluepill_f103c8 (platform: ststm32; board: bluepill_f103c8; framework: stm32cube)
--------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/ststm32/bluepill_f103c8.html
PLATFORM: ST STM32 (19.4.0) > BluePill F103C8
HARDWARE: STM32F103C8T6 72MHz, 20KB RAM, 64KB Flash
DEBUG: Current (stlink) External (blackmagic, cmsis-dap, jlink, stlink)
PACKAGES: 
 - framework-stm32cubef1 @ 1.8.6 
 - tool-ldscripts-ststm32 @ 0.2.0 
 - toolchain-gccarmnoneeabi @ 1.70201.0 (7.2.1)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain+, Compatibility ~ strict
Found 29 compatible libraries
Scanning dependencies...
Dependency Graph
|-- FreeRTOS @ 10.3.1
Building in release mode
Calculating size .pio/build/bluepill_f103c8/firmware.elf
   text	   data	    bss	    dec	    hex	filename
  11588	    124	  10400	  22112	   5660	.pio/build/bluepill_f103c8/firmware.elf
========================= [SUCCESS] Took 0.91 seconds =========================

Artifacts are available in the workflow run.

[github-actions]

Build Successful

Firmware Size:

Processing bluepill_f103c8 (platform: ststm32; board: bluepill_f103c8; framework: stm32cube)
--------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/ststm32/bluepill_f103c8.html
PLATFORM: ST STM32 (19.4.0) > BluePill F103C8
HARDWARE: STM32F103C8T6 72MHz, 20KB RAM, 64KB Flash
DEBUG: Current (stlink) External (blackmagic, cmsis-dap, jlink, stlink)
PACKAGES: 
 - framework-stm32cubef1 @ 1.8.6 
 - tool-ldscripts-ststm32 @ 0.2.0 
 - toolchain-gccarmnoneeabi @ 1.70201.0 (7.2.1)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain+, Compatibility ~ strict
Found 29 compatible libraries
Scanning dependencies...
Dependency Graph
|-- FreeRTOS @ 10.3.1
Building in release mode
Calculating size .pio/build/bluepill_f103c8/firmware.elf
   text	   data	    bss	    dec	    hex	filename
  11588	    124	  10400	  22112	   5660	.pio/build/bluepill_f103c8/firmware.elf
========================= [SUCCESS] Took 0.92 seconds =========================

Artifacts are available in the workflow run.

[github-actions]

Build Successful

Firmware Size:

Processing bluepill_f103c8 (platform: ststm32; board: bluepill_f103c8; framework: stm32cube)
--------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/ststm32/bluepill_f103c8.html
PLATFORM: ST STM32 (19.4.0) > BluePill F103C8
HARDWARE: STM32F103C8T6 72MHz, 20KB RAM, 64KB Flash
DEBUG: Current (stlink) External (blackmagic, cmsis-dap, jlink, stlink)
PACKAGES: 
 - framework-stm32cubef1 @ 1.8.6 
 - tool-ldscripts-ststm32 @ 0.2.0 
 - toolchain-gccarmnoneeabi @ 1.70201.0 (7.2.1)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain+, Compatibility ~ strict
Found 29 compatible libraries
Scanning dependencies...
Dependency Graph
|-- FreeRTOS @ 10.3.1
Building in release mode
Calculating size .pio/build/bluepill_f103c8/firmware.elf
   text	   data	    bss	    dec	    hex	filename
  11588	    124	  10400	  22112	   5660	.pio/build/bluepill_f103c8/firmware.elf
========================= [SUCCESS] Took 0.95 seconds =========================

Artifacts are available in the workflow run.