Initial 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,21 @@
+{
+    "files.associations": {
+        "optional": "cpp",
+        "istream": "cpp",
+        "ostream": "cpp",
+        "ratio": "cpp",
+        "system_error": "cpp",
+        "array": "cpp",
+        "functional": "cpp",
+        "tuple": "cpp",
+        "type_traits": "cpp",
+        "utility": "cpp",
+        "*.tcc": "cpp",
+        "chrono": "cpp",
+        "ctime": "cpp",
+        "iomanip": "cpp",
+        "limits": "cpp",
+        "numeric": "cpp",
+        "streambuf": "cpp"
+    }
+}

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 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,15 @@
+; 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:pico]
+platform = raspberrypi
+board = pico
+framework = arduino
+upload_protocol = picotool

src/main.cpp

@@ -0,0 +1,99 @@
+#include <Arduino.h>
+#define PORT PWM_2
+class HallButton//TODO
+{
+public:
+  HallButton(byte pin);
+  unsigned long lowTime;
+  unsigned int lowDuration;
+  void Pulse(unsigned long time, bool end = false)
+  {
+  }
+};
+
+HallButton myHallButton[2] = {HallButton(2), HallButton(3)};
+
+// bool is_gpio_fall(char *buf, uint32_t events);
+byte event;
+uint eventGpio;
+void gpio_callback(uint gpio, uint32_t events)
+{
+  eventGpio = gpio;
+  event = events == 4? 1: events == 8? 2: 0;
+  // unsigned long current_time = micros();
+  // bool is_fall = is_gpio_fall(event_str, events);
+  // if (is_fall)
+  // {
+  //   high_time = current_time;
+  //   high_duration = high_time - low_time;
+  // }
+  // else
+  // {
+  //   low_time = current_time;
+  //   low_duration = low_time - high_time;
+  // }
+}
+// static const char *gpio_irq_str[] = {
+//     "LEVEL_LOW",  // 0x1
+//     "LEVEL_HIGH", // 0x2
+//     "EDGE_FALL",  // 0x4
+//     "EDGE_RISE"   // 0x8
+// };
+
+// bool is_gpio_fall(char *buf, uint32_t events)
+// {
+//   bool value = false;
+//   for (uint i = 0; i < 4; i++)
+//   {
+//     uint mask = (1 << i);
+//     if (events & mask)
+//     {
+//       // Copy this event string into the user string
+//       const char *event_str = gpio_irq_str[i];
+//       if (gpio_irq_str[i] == "EDGE_FALL")
+//         value = true;
+//       while (*event_str != '\0')
+//       {
+//         *buf++ = *event_str++;
+//       }
+//       events &= ~mask;
+
+//       // If more events add ", "
+//       if (events)
+//       {
+//         *buf++ = ',';
+//         *buf++ = ' ';
+//       }
+//     }
+//   }
+//   *buf++ = '\0';
+//   return value;
+// }
+void setup()
+{
+  Serial.begin(9600);
+  gpio_set_input_enabled(PORT, true);
+  gpio_pull_up(PORT);
+  gpio_set_input_enabled(3, true);
+  gpio_pull_up(3);
+  // gpio_set_irq_enabled_with_callback(PORT, GPIO_IRQ_EDGE_RISE, true, rising);
+  gpio_set_irq_enabled_with_callback(2, GPIO_IRQ_EDGE_RISE | GPIO_IRQ_EDGE_FALL, true, &gpio_callback);
+  gpio_set_irq_enabled_with_callback(3, GPIO_IRQ_EDGE_RISE | GPIO_IRQ_EDGE_FALL, true, &gpio_callback);
+}
+
+unsigned long flag = 0;
+void loop()
+{
+  // static byte lowest = 100;
+  // byte value = GetPWM(PORT);
+  // if (value < lowest)
+  //   lowest = value;
+  // Serial.print("$" + String(GetPWM(PORT)) + ";\n");
+  // if (is_done)
+    Serial.print("$" + String(eventGpio) + " " + String(event) + ";\n");
+  // unsigned long currentTime = millis();
+  // if (currentTime >= flag + 1)
+  // {
+  //   flag = currentTime;
+  // }
+}

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