STM32F1xx micro-controller C firmware template
Go to file
King Kévin a1de197209 bootloader is now 8 kB thanks to better dependency handling 2017-08-06 09:53:46 +02:00
lib onewire_slave: remove debug code 2017-08-04 07:43:05 +02:00
libopencm3@ad5ec6af08 add libopencm3 and STM32duino-bootloader submodules dependencies 2016-01-15 15:36:00 +01:00
.gitignore ignore generated documentation 2016-08-14 19:26:46 +02:00
.gitmodules remove STM32duino-bootloader 2016-08-14 19:03:17 +02:00
Doxyfile add changes from spark abacus project 2016-10-23 17:42:27 +02:00
README.md add bootloader information 2017-04-15 13:58:39 +02:00
Rakefile replace Makefile with a Rakefile to better handle dependencies 2017-08-06 09:52:47 +02:00
application.c application: example of 1-Wire slave usage 2017-08-03 20:50:11 +02:00
application.ld bootloader is now 8 kB thanks to better dependency handling 2017-08-06 09:53:46 +02:00
bootloader.c bootloader: fix clang warning 2017-08-01 19:13:56 +02:00
bootloader.ld bootloader is now 8 kB thanks to better dependency handling 2017-08-06 09:53:46 +02:00
global.c global: add ms in us sleep utilities 2017-08-02 13:44:16 +02:00
global.h global: add ms in us sleep utilities 2017-08-02 13:44:16 +02:00

README.md

This firmware template is designed for development boards based around STM32 F1 series micro-controller.

project

summary

describe project purpose

technology

described electronic details

board

The current implementation uses a core board.

The underlying template also supports following board:

Which board is used is defined in the Makefile. This is required to map the user LED and button provided on the board

connections

Connect the peripherals the following way (STM32F10X signal; STM32F10X pin; peripheral pin; peripheral signal; comment):

  • list board to preipheral pin connections

All pins are configured using defines in the corresponding source code.

code

dependencies

The source code uses the libopencm3 library. The projects is already a git submodules. To initialize and it you just need to run once: git submodule init and git submodule update.

firmware

To compile the firmware run make.

documentation

To generate doxygen documentation run make doc.

flash

There are two firmware images: bootloader and application. The bootloader image allows to flash the application over USB using the DFU protocol. The bootloader is started first and immediately jumps to the application if it is valid and the DFU mode is not forced (i.e. by pressing the user button on the board or requesting a DFU detach in the application). The main application should be implemented in application.c. It is up to the application to advertise USB DFU support (i.e. as does the provided USB CDC ACM example).

The bootlaoder image will be flashed using SWD (Serial Wire Debug). For that you need an SWD adapter. The Makefile uses a Black Magic Probe (per default), or a ST-Link V2 along OpenOCD software. To flash the booltoader using SWD run make flash_booloader.

Once the bootloader flashed it is possible to flash the application over USB using the DFU protocol by running make flash. To force the bootloader to start the DFU mode press the user button or short a pin, depending on the board. It is also possible to flash the application using SWD by running make flash_application.

debug

SWD also allows to debug the code running on the micro-controller using GDB. To start the debugging session run make debug.

USB

The firmware offers serial communication over USART1 and USB (using the CDC ACM device class).

You can also reset the board by setting the serial width to 5 bits over USB. To reset the board run make reset. This only works if provided USB CDC ACM is running correctly and the micro-controller isn't stuck.