Initial commit

.gitignore

@@ -1,14 +1,7 @@
-# ---> VisualStudioCode
+.pio
-.vscode/*
+.venv
-!.vscode/settings.json
+.vscode/.browse.c_cpp.db*
-!.vscode/tasks.json
+.vscode/c_cpp_properties.json
-!.vscode/launch.json
+.vscode/launch.json
-!.vscode/extensions.json
+.vscode/ipch
-!.vscode/*.code-snippets
-
-# Local History for Visual Studio Code
-.history/
-
-# Built Visual Studio Code Extensions
-*.vsix
 

.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,37 @@
+
+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

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

platformio.ini

@@ -0,0 +1,24 @@
+; 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-s3-devkitc-1]
+platform = https://github.com/pioarduino/platform-espressif32/releases/download/stable/platform-espressif32.zip
+board = esp32-s3-devkitc-1
+framework = arduino
+monitor_speed = 230400
+board_build.arduino.memory_type = qio_opi
+board_build.flash_mode = qio
+board_build.psram_type = opi
+board_upload.flash_size = 16MB
+board_upload.maximum_size = 16777216
+board_build.partitions = default_16MB.csv
+board_build.extra_flags = 
+	-DBOARD_HAS_PSRAM
+lib_deps = links2004/WebSockets@^2.7.3

src/main.cpp

@@ -0,0 +1,73 @@
+#include "Arduino.h"
+#include "Network.h"
+#include <WiFi.h>
+
+#define MAX_PACKAGES 100
+#define TICKS 1000
+
+const char* SSID="Tenda_32C850";
+const char* PASSWD="rhLcrMEcY^Xjvq66";
+// COnfigurar direcciones fijas
+IPAddress local_ip(192,168,0,150);
+IPAddress gateway(192,168,0,1);
+IPAddress subnet(255,255,255,0);
+IPAddress dns1(192,168,0,100);
+IPAddress dns2(1,1,1,1);
+
+NetworkServer server(8080);
+NetworkClient client = server.accept();
+
+uint8_t i=0;
+
+hw_timer_t *timer = NULL;
+volatile SemaphoreHandle_t timerSemaphore;
+
+
+void ARDUINO_ISR_ATTR onTimer() {
+  i = (i>=MAX_PACKAGES) ? 0 : i+1;
+  xSemaphoreGiveFromISR(timerSemaphore, NULL);
+}
+
+void setup() {
+
+  Serial.begin(230400);
+
+  Network.begin();
+  WiFi.STA.begin();
+  WiFi.STA.config(local_ip,gateway,subnet,dns1,dns2);
+  WiFi.STA.connect(SSID, PASSWD);
+  while (WiFi.STA.status() != WL_CONNECTED) {
+    delay(500);
+    Serial.print(".");
+  }
+
+  Serial.println("");
+  Serial.println("WiFi connected");
+  Serial.println("IP address: ");
+  Serial.println(WiFi.localIP());
+
+  server.begin();
+
+  // Iniciar y desbloquear la bandera
+  timerSemaphore = xSemaphoreCreateBinary();
+  xSemaphoreGive(timerSemaphore);
+
+  // Configurar la interrupcion ISR
+  timer = timerBegin(1000000);
+  timerAttachInterrupt(timer, &onTimer);
+  timerAlarm(timer, TICKS, true, 0);
+
+}
+
+void loop() {
+  if (!client || !client.connected()) {
+    client = server.accept();
+  }
+
+  if (xSemaphoreTake(timerSemaphore, portMAX_DELAY) == pdTRUE) {
+    if (client && client.connected()) {
+      uint8_t imagen=i;
+      client.printf("%03u",imagen);
+    }
+  }
+}

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