initial commit

.gitignore

@@ -0,0 +1 @@
+.pio

LICENSE.txt

@@ -0,0 +1,13 @@
+Copyright (c) 2022, Delan Azabani <[email protected]>
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

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,19 @@
+; 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 = https://github.com/maxgerhardt/platform-raspberrypi.git
+board = pico
+framework = arduino
+board_build.core = earlephilhower
+lib_deps =
+    https://github.com/adafruit/Adafruit-GFX-Library.git
+    https://github.com/adafruit/Adafruit_SSD1306.git
+    https://github.com/sekigon-gonnoc/Pico-PIO-USB.git

src/main.cc

@@ -0,0 +1,77 @@
+#include <Arduino.h>
+#include <Keyboard.h>
+#include <Wire.h>
+
+#include <FreeRTOS.h>
+#include <task.h>
+
+#include <Adafruit_GFX.h>
+#include <Adafruit_SSD1306.h>
+
+static Adafruit_SSD1306 display(128, 32, &Wire1, /* OLED_RESET */ -1);
+static int i = 0;
+
+void feedback(void *) {
+  vTaskCoreAffinitySet(nullptr, 1 << 1);
+  // vTaskDelay(1000 / port_TICK_MS);
+
+  pinMode(18, OUTPUT_12MA);
+  pinMode(19, OUTPUT_12MA);
+
+  while (true) {
+    display.clearDisplay();
+    display.setCursor(0, 0);
+    display.print("Sun input emulator");
+    display.setCursor(0, 12);
+    display.print("CAP  CMP  SCR  NUM");
+    display.drawRoundRect(0, 20, 18, 12, 4, SSD1306_WHITE);
+    display.drawRoundRect(30, 20, 18, 12, 4, SSD1306_WHITE);
+    display.drawRoundRect(60, 20, 18, 12, 4, SSD1306_WHITE);
+    display.drawRoundRect(90, 20, 18, 12, 4, SSD1306_WHITE);
+    display.display();
+
+    digitalWrite(LED_BUILTIN, HIGH);
+    // digitalWrite(18, LOW);
+    // digitalWrite(19, HIGH);
+    delay(420);
+    digitalWrite(LED_BUILTIN, LOW);
+    // digitalWrite(18, HIGH);
+    // digitalWrite(19, LOW);
+    delay(420);
+    // Serial.println(i++);
+  }
+
+  vTaskDelete(nullptr);
+}
+
+void usb(void *) {
+  while (true);
+
+  vTaskDelete(nullptr);
+}
+
+void setup() {
+  // needs to be done manually when using FreeRTOS
+  Serial.begin();
+
+  pinMode(LED_BUILTIN, OUTPUT);
+
+  // Wire1.setSDA(31);
+  // Wire1.setSCL(32);
+  display.begin(SSD1306_SWITCHCAPVCC, /* SCREEN_ADDRESS */ 0x3C);
+  display.setRotation(2);
+  display.cp437(true);
+  display.setTextColor(SSD1306_WHITE, SSD1306_BLACK);
+  display.clearDisplay();
+
+  xTaskCreate(feedback, "feedback", 2048, nullptr, 1, nullptr);
+  xTaskCreate(usb, "usb", 2048, nullptr, 1, nullptr);
+
+  while (!Serial);
+  Serial.write("\r\n\r\nSun input emulator");
+}
+
+void loop() {}
+
+// void serialEvent() {
+// }

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