Initial Commit

.gitignore

@@ -0,0 +1,3 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/

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

src/main.cpp

@@ -0,0 +1,56 @@
+#include "Arduino.h"
+
+#define LEDstripRED 11               // Referente ao pino Vermelho da Fita de Leds
+#define LEDstripGREEN 9              // Referente ao pino Verde da Fita de Leds
+#define LEDstripBLUE 10              // Referente ao pino Azul da Fita de Leds
+#define SOUND 2                      // Referente à entrada do Sensor de Intensidade Sonora. Deve ser 2 ou 3 em função do uso de interrupção (para arduino Arduino Uno)
+#define offDelay 5                   // Delay de varredura quando soundState está em nível lógico alto  (ligado/colorido)
+#define onDelay 10           // Delay de varredura quando soundState está em nível lógico baixo (apagado)
+#define debouncingDelay 1            // Delay durante interrupção. 
+#define colorChanging  250   // Velocidade da mudanaça de cores
+#define intensityFraction 0.05
+
+volatile int soundState = 0; // variável de comunicação de informações alteradas na interrupção
+volatile int color1 = 0;  // Variáveis para controlar a cor da fita de led
+volatile int color2 = 0;
+volatile int color3 = 0;
+
+void setup()
+{
+  pinMode(SOUND,         INPUT_PULLUP);   // iniciali000000zação de pino para interrupção
+  pinMode(LEDstripRED,   OUTPUT);
+  pinMode(LEDstripGREEN, OUTPUT);
+  pinMode(LEDstripBLUE,  OUTPUT);
+  attachInterrupt(digitalPinToInterrupt(SOUND), soundEvent , RISING);   // associar pino de interrupção (SOUND) e tipo de evento (CHANGE) com a função de tratamento (soundEvent)
+  // Serial.begin(9600); // DEBUG SERIAL
+}
+
+void loop()
+{
+  for (int ii = 0; ii < colorChanging ; ii++) {
+    if (soundState) {   // se o nível lógico da variável for 1, a fita de leds é acesa com uma cor
+      analogWrite(LEDstripRED,   color1);
+      analogWrite(LEDstripGREEN, color2);
+      analogWrite(LEDstripBLUE,  color3);
+      soundState = 0;
+      delay(onDelay);
+    }
+    else {       // se o nível lógico da variável for 0, a fita de led recebe metade da intensidade
+      analogWrite(LEDstripRED,   color1*intensityFraction);
+      analogWrite(LEDstripGREEN, color2*intensityFraction);
+      analogWrite(LEDstripBLUE,  color3*intensityFraction);
+      delay(offDelay);
+    }
+
+  }
+  color1 = random(255);  // Variam randomicamente a cor da fita de leds
+  color2 = random(255);
+  color3 = random(255);
+  //soundState=0;
+}
+
+void soundEvent () { // função de tratamento de interrupção
+  soundState = !soundState; // inverte sinal lógico
+  // Serial.println("int"); // DEBUG SERIAL
+  delay(debouncingDelay);
+}

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