Merge branch 'main' of https://gitlab-df.imt-atlantique.fr/pronto-3/capteur-autonome-penn-avel

Capteur-autonome/Projects/Archives/Modes Veilles/Test_Veille_ESP8266/.gitignore

+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

Capteur-autonome/Projects/Archives/Modes Veilles/Test_Veille_ESP8266/.vscode/extensions.json

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

Capteur-autonome/Projects/Archives/Modes Veilles/Test_Veille_ESP8266/include/README

+
+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 convention is to give header files names that end with `.h'.
+
+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

Capteur-autonome/Projects/Archives/Modes Veilles/Test_Veille_ESP8266/lib/README

+
+This directory is intended for project specific (private) libraries.
+PlatformIO will compile them to static libraries and link into the executable file.
+
+The source code of each library should be placed in a separate directory
+("lib/your_library_name/[Code]").
+
+For example, see the structure of the following example libraries `Foo` and `Bar`:
+
+|--lib
+|  |
+|  |--Bar
+|  |  |--docs
+|  |  |--examples
+|  |  |--src
+|  |     |- Bar.c
+|  |     |- Bar.h
+|  |  |- library.json (optional. for 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
+
+Example contents of `src/main.c` using Foo and Bar:
+```
+#include <Foo.h>
+#include <Bar.h>
+
+int main (void)
+{
+  ...
+}
+
+```
+
+The PlatformIO Library Dependency Finder will find automatically dependent
+libraries by scanning project source files.
+
+More information about PlatformIO Library Dependency Finder
+- https://docs.platformio.org/page/librarymanager/ldf.html

Capteur-autonome/Projects/Archives/Modes Veilles/Test_Veille_ESP8266/platformio.ini

+; 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:nodemcuv2]
+platform = espressif8266
+board = nodemcuv2
+framework = arduino
+monitor_speed = 115200
+upload_speed = 921600
\ No newline at end of file

Capteur-autonome/Projects/Archives/Modes Veilles/Test_Veille_ESP8266/src/main.cpp

+#include <Arduino.h>
+extern "C" {
+  #include <user_interface.h>
+}
+
+#define ets_wdt_disable ((void (*)(void))0x400030f0)
+#define ets_delay_us ((void (*)(int))0x40002ecc)
+
+#define _R (uint32_t *)0x60000700
+void nk_deep_sleep(uint64_t time)
+{
+	ets_wdt_disable();
+	*(_R + 4) = 0;
+	*(_R + 17) = 4;
+	*(_R + 1) = *(_R + 7) + 5;
+	*(_R + 6) = 8;
+	*(_R + 2) = 1 << 20;
+	ets_delay_us(10);
+	*(_R + 39) = 0x11;
+	*(_R + 40) = 3;
+	*(_R) &= 0xFCF;
+	*(_R + 1) = *(_R + 7) + (45*(time >> 8));
+	*(_R + 16) = 0x7F;
+	*(_R + 2) = 1 << 20;
+	__asm volatile ("waiti 0");
+}
+void setup() {
+  Serial.begin(115200);
+  delay(1000);
+  Serial.println("Wakeup OK!");
+  delay(100);
+  nk_deep_sleep(5e6); // 5 secondes
+}
+
+void loop() {}
\ No newline at end of file

Capteur-autonome/Projects/Archives/Modes Veilles/Test_Veille_ESP8266/test/README

+
+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

Capteur-autonome/Projects/Archives/Tests de capteurs simples/SDS011_TEST_ESP8266/src/main.cpp

@@ -3,8 +3,8 @@
 #include "SdsDustSensor.h"
 
 // Définition des broches pour le SDS011 (sur ESP8266)
-#define RX_PIN 14  // GPIO14 = D5 (RX de l'ESP, donc relié au TX du SDS011)
-#define TX_PIN 12  // GPIO12 = D6 (TX de l'ESP, donc relié au RX du SDS011)
+#define RX_PIN 5  // GPIO14 = D5 (RX de l'ESP, donc relié au TX du SDS011)
+#define TX_PIN 4  // GPIO12 = D6 (TX de l'ESP, donc relié au RX du SDS011)
 
 // Création du port série logiciel pour le capteur SDS011
 SoftwareSerial SDS_Serial(RX_PIN, TX_PIN);  // RX, TX