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,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,3 @@
+Animation a base de LED WS2812B et ATtiny85
+
+IDE platformio

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,27 @@
+; 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:attiny85]
+platform = atmelavr
+board = attiny85
+framework = arduino
+lib_deps = 
+	fastled/FastLED @ ^3.3.3
+; upload by USBasp stick
+upload_protocol = custom
+upload_flags =
+    -C
+    ${platformio.packages_dir}/tool-avrdude/avrdude.conf
+    -p
+    t85
+    -Pusb
+    -c
+    usbasp
+upload_command = avrdude $UPLOAD_FLAGS -U flash:w:$SOURCE:i

src/.gitignore

@@ -0,0 +1 @@
+build-*

src/CycloTiny85.ino

@@ -0,0 +1,75 @@
+#include <FastLED.h>
+
+// How many leds in your strip?
+#define BRIGHTNESS    96
+#define NUM_LEDS      12
+#define TEMPO         100
+
+#define DATA_PIN 0
+
+CRGB leds[NUM_LEDS];
+float tcount = 0.0;          //-INC VAR FOR SIN LOOPS 
+int ibright = 0;             //-BRIGHTNESS (0-255)
+int tempo_anim = TEMPO;
+uint8_t gHue = 0; // rotating "base color" 
+
+void colorWipe_up (struct CRGB rgb, uint8_t wait) {
+
+    for (int i=0; i < NUM_LEDS; i++) {
+        leds[i]=rgb;
+        FastSPI_LED.show();
+        delay(wait);
+    }
+}
+void colorWipe_down (struct CRGB rgb, uint8_t wait) {
+
+    for (int i =  NUM_LEDS-1 ; i >= 0;  i--) {
+        leds[i]=rgb;
+        FastSPI_LED.show();
+        delay(wait);
+    }
+}
+void black_out(){
+  // all leds off
+  memset(leds, 0, NUM_LEDS * 3); // all leds off
+  FastSPI_LED.show();
+}
+void dual_color(struct CRGB color1, struct CRGB color2,uint8_t wait) {
+  for (int i=0; i < NUM_LEDS; i++) {
+    memset(leds, 0, NUM_LEDS * 3); // all leds off
+    leds[i]=color1;
+    leds[NUM_LEDS-(i+1)]=color2;
+    FastSPI_LED.show();
+    delay(wait);
+  }
+}
+
+void setup() {
+  // put your setup code here, to run once:
+  FastLED.addLeds<WS2812B, DATA_PIN, GRB>(leds, NUM_LEDS);
+  FastLED.setBrightness(BRIGHTNESS);
+}
+
+void loop() {
+  // put your main code here, to run repeatedly:
+    colorWipe_up ( CRGB::Red,tempo_anim); 
+    delay(100);
+    colorWipe_down ( CRGB::Green,tempo_anim); 
+    delay(100);
+    colorWipe_up ( CRGB::Purple,tempo_anim); 
+    delay(100);
+    colorWipe_down ( CRGB::Blue,tempo_anim); 
+    delay(100);
+    colorWipe_up ( CRGB::Black,tempo_anim); 
+    delay(100);
+    //dual_color( CRGB::LightGreen,CRGB::Aqua,tempo_anim);
+    // dual_color( CRGB::Aqua,CRGB::LightGreen,tempo_anim);    
+    dual_color( CRGB::AliceBlue,CRGB::OrangeRed,tempo_anim);
+    dual_color( CRGB::AliceBlue,CRGB::OrangeRed,tempo_anim);
+    black_out();
+    delay(100);
+
+ }
+
+
+ 

src/README.md

@@ -0,0 +1,3 @@
+Annimation a base de LED WS2812B et ATtiny85
+
+IDE platformio

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