From 87f936d7b5c0cdf5d778e99dd1bb6a4eb68a5efd Mon Sep 17 00:00:00 2001 From: Kyle Isom Date: Mon, 31 Dec 2018 09:00:46 -0800 Subject: [PATCH] pio: add bluepill blink. --- pio/bluepill/blink/README.md | 4 +++ pio/bluepill/blink/include/README | 39 ++++++++++++++++++++++++++ pio/bluepill/blink/lib/README | 46 +++++++++++++++++++++++++++++++ pio/bluepill/blink/platformio.ini | 14 ++++++++++ pio/bluepill/blink/src/blinky.c | 14 ++++++++++ pio/bluepill/blink/test/README | 11 ++++++++ 6 files changed, 128 insertions(+) create mode 100644 pio/bluepill/blink/README.md create mode 100644 pio/bluepill/blink/include/README create mode 100644 pio/bluepill/blink/lib/README create mode 100644 pio/bluepill/blink/platformio.ini create mode 100644 pio/bluepill/blink/src/blinky.c create mode 100644 pio/bluepill/blink/test/README diff --git a/pio/bluepill/blink/README.md b/pio/bluepill/blink/README.md new file mode 100644 index 0000000..01c95f8 --- /dev/null +++ b/pio/bluepill/blink/README.md @@ -0,0 +1,4 @@ +blink +===== + +PlatformIO version of the opencm3 [pill-blink](https://github.com/satoshinm/pill_blink). diff --git a/pio/bluepill/blink/include/README b/pio/bluepill/blink/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/pio/bluepill/blink/include/README @@ -0,0 +1,39 @@ + +This directory is intended for project header files. + +A header file is a file containing C declarations and macro definitions +to be shared between several project source files. You request the use of a +header file in your project source file (C, C++, etc) located in `src` folder +by including it, with the C preprocessing directive `#include'. + +```src/main.c + +#include "header.h" + +int main (void) +{ + ... +} +``` + +Including a header file produces the same results as copying the header file +into each source file that needs it. Such copying would be time-consuming +and error-prone. With a header file, the related declarations appear +in only one place. If they need to be changed, they can be changed in one +place, and programs that include the header file will automatically use the +new version when next recompiled. The header file eliminates the labor of +finding and changing all the copies as well as the risk that a failure to +find one copy will result in inconsistencies within a program. + +In C, the usual convention is to give header files names that end with `.h'. +It is most portable to use only letters, digits, dashes, and underscores in +header file names, and at most one dot. + +Read more about using header files in official GCC documentation: + +* Include Syntax +* Include Operation +* Once-Only Headers +* Computed Includes + +https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html diff --git a/pio/bluepill/blink/lib/README b/pio/bluepill/blink/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/pio/bluepill/blink/lib/README @@ -0,0 +1,46 @@ + +This directory is intended for project specific (private) libraries. +PlatformIO will compile them to static libraries and link into executable file. + +The source code of each library should be placed in a an own separate directory +("lib/your_library_name/[here are source files]"). + +For example, see a structure of the following two libraries `Foo` and `Bar`: + +|--lib +| | +| |--Bar +| | |--docs +| | |--examples +| | |--src +| | |- Bar.c +| | |- Bar.h +| | |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html +| | +| |--Foo +| | |- Foo.c +| | |- Foo.h +| | +| |- README --> THIS FILE +| +|- platformio.ini +|--src + |- main.c + +and a contents of `src/main.c`: +``` +#include +#include + +int main (void) +{ + ... +} + +``` + +PlatformIO Library Dependency Finder will find automatically dependent +libraries scanning project source files. + +More information about PlatformIO Library Dependency Finder +- https://docs.platformio.org/page/librarymanager/ldf.html diff --git a/pio/bluepill/blink/platformio.ini b/pio/bluepill/blink/platformio.ini new file mode 100644 index 0000000..47d5b38 --- /dev/null +++ b/pio/bluepill/blink/platformio.ini @@ -0,0 +1,14 @@ +; PlatformIO Project Configuration File +; +; Build options: build flags, source filter +; Upload options: custom upload port, speed and extra flags +; Library options: dependencies, extra library storages +; Advanced options: extra scripting +; +; Please visit documentation for the other options and examples +; https://docs.platformio.org/page/projectconf.html + +[env:bluepill_f103c8] +platform = ststm32 +board = bluepill_f103c8 +framework = libopencm3 diff --git a/pio/bluepill/blink/src/blinky.c b/pio/bluepill/blink/src/blinky.c new file mode 100644 index 0000000..9d29b31 --- /dev/null +++ b/pio/bluepill/blink/src/blinky.c @@ -0,0 +1,14 @@ +#include +#include + +int main(void) { + rcc_periph_clock_enable(RCC_GPIOC); + gpio_set_mode(GPIOC, GPIO_MODE_OUTPUT_2_MHZ, GPIO_CNF_OUTPUT_PUSHPULL, GPIO13); + + while(1) { + gpio_set(GPIOC, GPIO13); + for (int i = 0; i < 1000000; ++i) __asm__("nop"); + gpio_clear(GPIOC, GPIO13); + for (int i = 0; i < 500000; ++i) __asm__("nop"); + } +} diff --git a/pio/bluepill/blink/test/README b/pio/bluepill/blink/test/README new file mode 100644 index 0000000..df5066e --- /dev/null +++ b/pio/bluepill/blink/test/README @@ -0,0 +1,11 @@ + +This directory is intended for PIO Unit Testing and project tests. + +Unit Testing is a software testing method by which individual units of +source code, sets of one or more MCU program modules together with associated +control data, usage procedures, and operating procedures, are tested to +determine whether they are fit for use. Unit testing finds problems early +in the development cycle. + +More information about PIO Unit Testing: +- https://docs.platformio.org/page/plus/unit-testing.html