kingkevin
/
stm32f1
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
STM32F1xx micro-controller C firmware template
234 Commits 22 Branches 0 Tags 3.3 MiB
C 98.3%
Ruby 1.6%
Go to file
King Kévin a0b5e2059f add GPLv3 license file 2018-02-13 15:14:55 +01:00
lib BV HiZ: make pin test faster an user interruptable 2018-02-12 17:13:22 +01:00
libopencm3@ad5ec6af08 add libopencm3 and STM32duino-bootloader submodules dependencies 2016-01-15 15:36:00 +01:00
.gitignore ignore vim and gdb files 2018-01-14 13:35:28 +01: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
LICENSE.txt add GPLv3 license file 2018-02-13 15:14:55 +01:00
README.md README: fix typo 2017-12-23 15:13:35 +01:00
Rakefile Rakefile: remove stripping since it does not decrease the size on binary output 2018-02-13 13:50:43 +01:00
application.c application: display build date and device ID 2018-02-06 21:17:00 +01:00
application.ld correct flash size to 256 kB of STM32F103xC 2018-02-06 11:52:23 +01:00
bootloader.c bootloader: show red LED on BV 2018-02-12 19:41:20 +01:00
bootloader.ld bootloader: fix linker script to indicate correct flash size for STM32F103xC 2018-02-13 13:47:03 +01:00
global.c global: remove wait_space since it can be done by user_input_get 2018-01-25 10:41:02 +01:00
global.h global: fix typo 2018-02-12 19:40:05 +01:00

README.md

This firmware for the BusVoodoo.

project

summary

The BusVoodoo is a multi-protocol debugging adapter. This tool allows to quickly communicate with various other electronic devices.

board

The BusVoodoo uses a custom board based on a STM32F103RC micro-controller.

connections

The BusVoodoo provides:

  • a USB port for a connection to the PC
  • an I/O port for the 0-5V protocols
  • an I2C port to control an OLED display
  • a programming port for debugging usindg SWD and UART

Check the BusVoodoo hardware files for more details.

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. It will be initialized when compiling the firmware. Alternatively you can run once: git submodule init and git submodule update.

firmware

To compile the firmware run rake.

documentation

To generate doxygen documentation run rake 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. The application image is the main application and is implemented in application.c.

The bootloader 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 rake flash_booloader.

Once the bootloader is flashed it is possible to flash the application over USB using the DFU protocol by running rake flash. The application advertises USB DFU support (along with the USB CDC ACM class). If the application is broken, force the bootloader to start the DFU mode by shorting the contacts marked as DFU on the board while powering up. It is also possible to flash the application image using SWD by running rake flash_application.

debug

SWD also allows to debug the code running on the micro-controller using GDB. To start the debugging session run rake 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 rake reset. This only works if provided USB CDC ACM is running correctly and the micro-controller isn't stuck.