Initial commit

Author: DaveVdE

.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

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

README.md

@@ -0,0 +1,2 @@
+# Fire
+ 

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,17 @@
+; 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:adafruit_matrix_portal_m4]
+platform = atmelsam
+board = adafruit_matrix_portal_m4
+framework = arduino
+lib_deps = 
+	adafruit/Adafruit Protomatter@^1.0.10
+	adafruit/Adafruit BusIO@^1.7.1

src/main.cpp

@@ -0,0 +1,120 @@
+#include <Arduino.h>
+#include <Wire.h>
+#include <SPI.h>
+#include <Adafruit_Protomatter.h> // For RGB matrix
+
+#define WIDTH   64
+#define HEIGHT  32
+#define FIRE_WIDTH  32
+#define FIRE_HEIGHT 65
+#define MAX_FPS 25
+
+// Remaining pins are the same for all matrix sizes. These values
+// are for MatrixPortal M4. See "simple" example for other boards.
+uint8_t rgbPins[]  = {7, 8, 9, 10, 11, 12};
+uint8_t addrPins[] = {17, 18, 19, 20};
+uint8_t clockPin   = 14;
+uint8_t latchPin   = 15;
+uint8_t oePin      = 16;
+
+Adafruit_Protomatter matrix(
+  WIDTH, 6, 1, rgbPins, sizeof(addrPins), addrPins,
+  clockPin, latchPin, oePin, true);
+
+uint16_t palette[256];
+
+uint8_t fire[FIRE_HEIGHT][FIRE_WIDTH];
+
+uint16_t HSLto565(float H, float S, float V) {
+  float s = S/100;
+  float v = V/100;
+  float C = s*v;
+  float X = C*(1-abs(fmod(H/60.0, 2)-1));
+  float m = v-C;
+  float r,g,b;
+
+  if(H >= 0 && H < 60){
+      r = C,g = X,b = 0;
+  }
+  else if(H >= 60 && H < 120){
+      r = X,g = C,b = 0;
+  }
+  else if(H >= 120 && H < 180){
+      r = 0,g = C,b = X;
+  }
+  else if(H >= 180 && H < 240){
+      r = 0,g = X,b = C;
+  }
+  else if(H >= 240 && H < 300){
+      r = X,g = 0,b = C;
+  }
+  else{
+      r = C,g = 0,b = X;
+  }
+  int R = (r+m)*255;
+  int G = (g+m)*255;
+  int B = (b+m)*255;
+
+  return matrix.color565(R, G, B);  
+}
+
+void setup() {
+  // put your setup code here, to run once:
+  ProtomatterStatus status = matrix.begin();
+  if(status != PROTOMATTER_OK) {
+    // DO NOT CONTINUE if matrix setup encountered an error.
+    for(;;);
+  }
+
+  // Calculate palette
+  for (int index = 0; index < 128; ++index) {
+    palette[index] = HSLto565(index / 6, 100, (index * 2.0) * 100 / 256);
+  }
+
+  for (int index = 128; index < 256; ++index) {
+    palette[index] = HSLto565(index / 6, (384 - index) * 100 / 256, 100);
+  }
+
+  // Clear buffer
+  for (int y = 0; y < FIRE_HEIGHT; ++y) {
+    for (int x = 0; x < FIRE_WIDTH; ++x) {
+      fire[y][x] = 0;
+    }
+  }
+}
+
+uint32_t prevTime = 0;
+
+void loop() {
+  uint32_t t;
+  while(((t = micros()) - prevTime) < (1000000L / MAX_FPS));
+  prevTime = t;
+
+  // Randomize bottom row
+  for (int x = 0; x < FIRE_WIDTH; ++x) {
+    int n = random(4) + 1;
+    fire[FIRE_HEIGHT - 1][x] = n * n * n * n - 1;
+  }
+
+  //do the fire calculations for every pixel, from top to bottom
+  for(int y = 0; y < FIRE_HEIGHT - 1; y++)
+  for(int x = 0; x < FIRE_WIDTH; x++)
+  {
+    fire[y][x] =
+      ((fire[(y + 1) % FIRE_HEIGHT][(x - 1 + FIRE_WIDTH) % FIRE_WIDTH]
+      + fire[(y + 1) % FIRE_HEIGHT][(x) % FIRE_WIDTH]
+      + fire[(y + 1) % FIRE_HEIGHT][(x + 1) % FIRE_WIDTH]
+      + fire[(y + 2) % FIRE_HEIGHT][(x) % FIRE_WIDTH])
+      * 32) / 132;
+  }
+
+  // Draw fire
+  for (int y = 0; y < matrix.width(); ++y) {
+    for (int x = 0; x < matrix.height(); ++x) {
+      // Things are rotated 90 CCW
+      matrix.drawPixel(y, x, palette[fire[y][x]]);
+    }
+  }
+
+  matrix.show();
+}

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