initial

.gitignore

@@ -0,0 +1,5 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+    // See http://go.microsoft.com/fwlink/?LinkId=827846
+    // for the documentation about the extensions.json format
+    "recommendations": [
+        "platformio.platformio-ide"
+    ]
+}

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

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 <Foo.h>
+#include <Bar.h>
+
+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

platformio.ini

@@ -0,0 +1,21 @@
+; 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:blackpill_f401cc]
+platform = ststm32
+board = blackpill_f401cc
+framework = arduino
+upload_protocol = dfu
+lib_deps = stm32duino/STM32duino FreeRTOS@^10.2.1
+build_flags =
+  -D PIO_FRAMEWORK_ARDUINO_ENABLE_CDC
+  -D PIO_FRAMEWORK_ARDUINO_NANOLIB_FLOAT_PRINTF
+
+monitor_port = COM8

src/main.cpp

@@ -0,0 +1,61 @@
+#include <Arduino.h>
+#include <STM32FreeRTOS.h>
+#include <pivector.h>
+
+
+//global vars
+volatile int val = 0;
+
+
+//functions
+void TaskBlink(void *pvParameters);
+void keyPressed();
+
+
+// initialization
+void setup() {
+  Serial.begin(9600);
+  while (!Serial);
+  pinMode(A0, INPUT_PULLUP);
+  attachInterrupt(A0, keyPressed, FALLING);
+  xTaskCreate(
+    TaskBlink,
+    (const portCHAR *)"Blink",   // A name just for humans
+    128,  // This stack size can be checked & adjusted by reading the Stack Highwater
+    NULL,
+    2,  // Priority, with 3 (configMAX_PRIORITIES - 1) being the highest, and 0 being the lowest.
+    NULL
+  );
+  Serial.println("Starting");
+  Serial.flush();
+  vTaskStartScheduler(); // start FreeRTOS, function don't exit
+  Serial.println("Start FreeRTOS failed! Insufficient RAM");
+  while(1); // panic
+}
+
+void loop(){} // unused
+
+
+// This is a task.
+void TaskBlink(void *) {
+  int d = 100;
+  pinMode(PC13, OUTPUT);
+  PIVector<float> vec;
+  vec.resize(10, [](size_t i){return i*2;});
+  while (1) {
+    Serial.println("TaskBlink");
+    for (float f : vec) Serial.println(f);
+    if (val > 0) d = 300;
+    else d = 100;
+    digitalWrite(PC13, HIGH);
+    vTaskDelay(d / portTICK_PERIOD_MS);
+    digitalWrite(PC13, LOW);
+    vTaskDelay(d / portTICK_PERIOD_MS);
+  }
+}
+
+
+// key interrupt
+void keyPressed() {
+  val = 1 - val;
+}

test/README

@@ -0,0 +1,11 @@
+
+This directory is intended for PlatformIO 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 PlatformIO Unit Testing:
+- https://docs.platformio.org/page/plus/unit-testing.html