first commit

.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,10 @@
+{
+    // See http://go.microsoft.com/fwlink/?LinkId=827846
+    // for the documentation about the extensions.json format
+    "recommendations": [
+        "platformio.platformio-ide"
+    ],
+    "unwantedRecommendations": [
+        "ms-vscode.cpptools-extension-pack"
+    ]
+}

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "C_Cpp.errorSquiggles": "enabled"
+}

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,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:nanoatmega328]
+platform = atmelavr
+board = nanoatmega328
+framework = arduino

src/main.cpp

@@ -0,0 +1,107 @@
+#include <Arduino.h>
+
+#define PIN_RED 2
+#define PIN_YELLOW 3
+#define PIN_GREEN 4
+
+class Led {
+  int ledPin;
+  long waitTimeInMs;
+  unsigned long previousMillis;
+  bool pinOnOff;
+
+public:
+  Led(int pin) : Led(pin, 0) {
+  }
+
+  Led(int pin, long wait) {
+    ledPin = pin;
+    waitTimeInMs = wait;
+    pinOnOff = true;
+
+    pinMode(ledPin, OUTPUT);
+    digitalWrite(ledPin, pinOnOff);
+  }
+
+  void setOn(bool on) {
+    if (on == pinOnOff)
+      return;
+
+    pinOnOff = on;
+    waitTimeInMs = 0;
+    previousMillis = millis();
+  }
+
+  void setBlinking(long wait) {
+    waitTimeInMs = wait;
+  }
+
+  void update() {
+    if (waitTimeInMs > 0)
+    {
+      if ((millis() - previousMillis) >= waitTimeInMs)
+      {
+        previousMillis = millis();
+        pinOnOff = !pinOnOff;
+      }
+    }
+    digitalWrite(ledPin, pinOnOff);
+  }
+};
+
+class TrafficLight {
+private:
+  Led leds[3] = {Led(PIN_RED), Led(PIN_YELLOW), Led(PIN_GREEN)};
+
+public:
+  enum Color { RED = 0, YELLOW, GREEN };
+
+  TrafficLight() {
+  }
+
+  void setOn(Color c, bool on) {
+    leds[c].setOn(on);
+  }
+
+  void setBlinking(Color c, long wait) {
+    leds[c].setBlinking(wait);
+  }
+
+  void update() {
+    for (int c = RED; c <= GREEN; c++) {
+      leds[c].update();
+    }
+  }
+};
+
+// put function declarations here:
+int myFunction(int, int);
+
+TrafficLight trafficLight;
+
+void setup()
+{
+  // put your setup code here, to run once:
+  Serial.begin(9600);
+
+  // int result = myFunction(2, 3);
+  trafficLight.setBlinking(TrafficLight::Color::RED, 500);
+  trafficLight.setOn(TrafficLight::Color::YELLOW, false);
+}
+
+void loop()
+{
+  // put your main code here, to run repeatedly:
+  static u32 i = 0;
+  Serial.println(i);
+
+  trafficLight.update();
+  delay(9);
+  i++;
+}
+
+// put function definitions here:
+int myFunction(int x, int y)
+{
+  return x + y;
+}

test/README

@@ -0,0 +1,11 @@
+
+This directory is intended for PlatformIO Test Runner 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/en/latest/advanced/unit-testing/index.html