This commit is contained in:
PaulVua
2025-11-03 16:49:54 +01:00
commit 818859eb6c
7 changed files with 215 additions and 0 deletions

5
.gitignore vendored Normal file
View File

@@ -0,0 +1,5 @@
.pio
.vscode/.browse.c_cpp.db*
.vscode/c_cpp_properties.json
.vscode/launch.json
.vscode/ipch

10
.vscode/extensions.json vendored Normal file
View File

@@ -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"
]
}

37
include/README Normal file
View File

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

46
lib/README Normal file
View File

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

19
platformio.ini Normal file
View File

@@ -0,0 +1,19 @@
; 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:ModuleAir]
platform = espressif32
board = esp32dev
lib_deps =
2dom/PxMatrix LED MATRIX library@^1.8.2
adafruit/Adafruit GFX Library@^1.10.12
monitor_speed = 115200
framework = arduino

87
src/main.cpp Normal file
View File

@@ -0,0 +1,87 @@
/*
Script de base pour afficher un message sur une matrice LED 64x32
*/
#include <Arduino.h>
#include <PxMatrix.h>
// Define Matrix pins for ESP32 (voir https://github.com/aircarto/ModuleAir_V2.1/blob/main/pinMap.md)
#define P_LAT 25
#define P_A 17
#define P_B 33
#define P_C 4
#define P_D 12
#define P_E 15
#define P_OE 16
hw_timer_t * timer = NULL;
portMUX_TYPE timerMux = portMUX_INITIALIZER_UNLOCKED;
//define matrix size
#define matrix_width 64
#define matrix_height 32
uint8_t display_draw_time = 30; //10-50 is usually fine
PxMATRIX display(64, 32, P_LAT, P_OE, P_A, P_B, P_C, P_D, P_E);
//Need this two functions for ESP32 to refresh display
void IRAM_ATTR display_updater()
{
// Increment the counter and set the time of ISR
portENTER_CRITICAL_ISR(&timerMux);
display.display(display_draw_time);
portEXIT_CRITICAL_ISR(&timerMux);
}
void display_update_enable(bool is_enable)
{
Serial.print("Call display_update_enable function with:");
if (is_enable)
{
Serial.println("true");
//timer = timerBegin(0, 80, true);
timerAttachInterrupt(timer, &display_updater, true);
timerAlarmWrite(timer, 4000, true);
timerAlarmEnable(timer);
}
else
{
Serial.println("false");
timerDetachInterrupt(timer);
timerAlarmDisable(timer);
}
}
/*
SETUP AND LOOP
*/
void setup() {
// put your setup code here, to run once:
Serial.begin(115200);
Serial.println("Hello, Arduino!");
display.begin(8);
display.setFastUpdate(true);
// ⭐ INITIALISER LE TIMER ICI ⭐
timer = timerBegin(0, 80, true); // Timer 0, prescaler 80, count up
timerAlarmWrite(timer, 4000, true); // Interruption toutes les 4ms
// Activer le rafraîchissement
display_update_enable(true);
}
void loop() {
// put your main code here, to run repeatedly:
Serial.println("Showing message on LED matrix");
display.fillScreen(0); // Clear the display
display.setCursor(1, 1);
display.setTextColor(display.color565(0, 255, 0));
display.setTextSize(1);
display.print("Hello");
delay(1000);
}

11
test/README Normal file
View File

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