add neokey example code with changes for esp32-poe-iso

.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"
+    ]
+}

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,20 @@
+; 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:esp32-poe-iso]
+platform = espressif32
+board = esp32-poe-iso
+framework = arduino
+
+lib_deps=
+    ethernet
+    BluetoothSerial
+    SPI
+    adafruit/Adafruit seesaw Library@^1.7.8

src/main.cpp

@@ -0,0 +1,87 @@
+#include <Arduino.h>
+#include <ETH.h>
+#include "Adafruit_NeoKey_1x4.h"
+#include "seesaw_neopixel.h"
+
+Adafruit_NeoKey_1x4 neokey;  // Create the NeoKey object
+
+void setup() {
+  Serial.begin(115200);
+  while (! Serial) delay(10);
+   
+  if (! neokey.begin(0x30)) {     // begin with I2C address, default is 0x30
+    Serial.println("Could not start NeoKey, check wiring?");
+    while(1) delay(10);
+  }
+  
+  Serial.println("NeoKey started!");
+
+  // Pulse all the LEDs on to show we're working
+  for (uint16_t i=0; i<neokey.pixels.numPixels(); i++) {
+    neokey.pixels.setPixelColor(i, 0x808080); // make each LED white
+    neokey.pixels.show();
+    delay(50);
+  }
+  for (uint16_t i=0; i<neokey.pixels.numPixels(); i++) {
+    neokey.pixels.setPixelColor(i, 0x000000);
+    neokey.pixels.show();
+    delay(50);
+  }
+}
+
+void loop() {
+  uint8_t buttons = neokey.read();
+
+  // Check each button, if pressed, light the matching neopixel
+  
+  if (buttons & (1<<0)) {
+    Serial.println("Button A");
+    neokey.pixels.setPixelColor(0, 0xFF0000); // red
+  } else {
+    neokey.pixels.setPixelColor(0, 0);
+  }
+
+  if (buttons & (1<<1)) {
+    Serial.println("Button B");
+    neokey.pixels.setPixelColor(1, 0xFFFF00); // yellow
+  } else {
+    neokey.pixels.setPixelColor(1, 0);
+  }
+  
+  if (buttons & (1<<2)) {
+    Serial.println("Button C");
+    neokey.pixels.setPixelColor(2, 0x00FF00); // green
+  } else {
+    neokey.pixels.setPixelColor(2, 0);
+  }
+
+  if (buttons & (1<<3)) {
+    Serial.println("Button D");
+    neokey.pixels.setPixelColor(3, 0x00FFFF); // blue
+  } else {
+    neokey.pixels.setPixelColor(3, 0);
+  }  
+
+  neokey.pixels.show();
+  
+  delay(10);    // don't print too fast
+}
+
+
+
+/******************************************/
+
+// Input a value 0 to 255 to get a color value.
+// The colors are a transition r - g - b - back to r.
+uint32_t Wheel(byte WheelPos) {
+  if(WheelPos < 85) {
+   return seesaw_NeoPixel::Color(WheelPos * 3, 255 - WheelPos * 3, 0);
+  } else if(WheelPos < 170) {
+   WheelPos -= 85;
+   return seesaw_NeoPixel::Color(255 - WheelPos * 3, 0, WheelPos * 3);
+  } else {
+   WheelPos -= 170;
+   return seesaw_NeoPixel::Color(0, WheelPos * 3, 255 - WheelPos * 3);
+  }
+  return 0;
+}

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