first version with mesaggepakc on the FE

Author: dido18

README.md

@@ -1,125 +1,6 @@
-# Linux Blink with UI (JavaScript)
+# Mange you board with Scratch
 
-The **Linux Blink** example shows a simple Linux application that changes the LED state on the board. It showcases basic event handling and UI updates through a web-based interface.
-
-![Linux Blink App](assets/docs_assets/linux-blink-banner.png)
-
-## Description
-
-This example toggles an LED on the board using a simple web user interface. The application listens for user input through a web browser and updates the LED state accordingly. It shows how to interact with hardware from a Linux environment and provides a basis for building more complex hardware-interfacing applications.
-
-The `assets` folder contains the **frontend** components of the application. Inside, you'll find the JavaScript source files along with the HTML and CSS files that make up the web user interface. The `python` folder instead includes the application **backend**.
-
-The interactive toggle switch UI is generated with JavaScript, while the Arduino sketch manages the LED hardware control. The Router Bridge enables communication between the web interface and the microcontroller.
-
-## Bricks Used
-
-The Linux blink example uses the following Bricks:
-
-- `web_ui`: Brick to create a web interface to display the LED control toggle switch.
-
-## Hardware and Software Requirements
-
-### Hardware
-
-- Arduino UNO Q (x1)
-- USB-C® cable (for power and programming) (x1)
-
-### Software
-
-- Arduino App Lab
-
-**Note:** You can run this example using your Arduino UNO Q as a Single Board Computer (SBC) using a [USB-C® hub](https://store.arduino.cc/products/usb-c-to-hdmi-multiport-adapter-with-ethernet-and-usb-hub) with a mouse, keyboard and display attached.
-
-## How to Use the Example
-
-1. Run the App
-   ![Arduino App Lab - Run App](assets/docs_assets/app-lab-run-app.png)
-2. Open the App in your browser at `<UNO-Q-IP-ADDRESS>:7000`
-3. Click on the circular switch to change the state of the LED
-
-## How it Works
-
-Once the application is running, the device performs the following operations:
-
-- **Serving the web interface and handling WebSocket communication.**
-
-The `web_ui` Brick provides the web server and WebSocket communication:
-
-```python
-from arduino.app_bricks.web_ui import WebUI
-
-ui = WebUI()
-ui.on_message('toggle_led', toggle_led_state)
-ui.on_message('get_initial_state', on_get_initial_state)
-```
-
-- **Communicating LED state to the Arduino.**
-
-The Router Bridge sends LED commands to the microcontroller:
-
-```python
-   Bridge.call("set_led_state", led_is_on)
-```
-
-- **Controlling the hardware LED.**
-
-The Arduino sketch handles the LED hardware control:
-
-```cpp
-   void set_led_state(bool state) {
-      digitalWrite(LED_BUILTIN, state ? LOW : HIGH);
-   }
-```
-
-The high-level data flow looks like this:
-
-```
-Web Browser Toggle → WebSocket → Python Backend → Router Bridge → Arduino LED Control
-```
-
-## Understanding the Code
-
-Here is a brief explanation of the application components:
-
-### 🔧 Backend (`main.py`)
-
-The Python code manages the web interface, handles user interactions, and communicates with the Arduino.
-
-- **`ui = WebUI()`:** Initializes the web server that serves the HTML interface and handles WebSocket communication.
-
-- **`ui.on_message('toggle_led', toggle_led_state)`:** Registers a WebSocket message handler that responds when the user clicks the toggle button in the web interface.
-
-- **`ui.send_message('led_status_update', get_led_status())`:** Sends LED status updates to all connected web clients in real-time.
-
-- **`Bridge.call("set_led_state", led_is_on)`:** Calls the Arduino function to physically control the LED hardware.
-
-- **`get_led_status()`:** Returns the current LED state as a dictionary for the web interface.
-
-### 🔧 Frontend (`index.html` + `app.js`)
-
-The web interface provides a simple toggle button for LED control.
-
-- **Socket.IO connection:** Establishes WebSocket communication with the Python backend through the `web_ui` Brick.
-
-- **`socket.emit('toggle_led', {})`:** Sends a toggle message to the backend when the user clicks the button.
-
-- **`socket.on('led_status_update', updateLedStatus)`:** Receives LED status updates and updates the button appearance accordingly.
-
-- **`updateLedStatus(status)`:** Changes the button's visual state (LED IS ON/OFF) based on the received status.
-
-### 🔧 Hardware (`sketch.ino`)
-
-The Arduino code handles LED hardware control and sets up Bridge communication.
-
-- **`pinMode(LED_BUILTIN, OUTPUT)`:** Configures the built-in LED pin as an output for controlling the LED state.
-
-- **`Bridge.begin()`:** Initializes the Router Bridge communication system for receiving commands from Python.
-
-- **`Bridge.provide(...)`:** Registers the `set_led_state` function to be callable from the Python web interface.
-
-- **`set_led_state(bool state)`:** Controls the LED hardware by setting the pin HIGH or LOW based on the received state parameter.
-
-- **Empty `loop()`:** The main loop remains empty since all LED control is event-driven through Bridge function calls.
-
-# scratch-arduino-app
+Scratch extension to:
+- control the board perhiperals (pins, matrix led)
+- mange the arduino Modulino connecte to the board
+- manage the python trigger

app.yaml

@@ -0,0 +1,5 @@
+name: scratch-arduino-app
+description: Controll the Uno-Q borad using Scractch blocks
+ports: []
+bricks: []
+icon: 💡

python/main.py

@@ -0,0 +1,7 @@
+from arduino.app_utils import App
+import time
+
+def loop():
+    time.sleep(1) # do nothing: only to keep the track the app status
+    
+App.run(user_loop=loop)

sketch/sketch.ino

@@ -0,0 +1,75 @@
+// SPDX-FileCopyrightText: Copyright (C) 2025 ARDUINO SA <http://www.arduino.cc>
+//
+// SPDX-License-Identifier: MPL-2.0
+
+#include <Arduino_RouterBridge.h>
+#include <Modulino.h>
+
+// TODO: those will go into an header file.
+extern "C" void matrixWrite(const uint32_t* buf);
+extern "C" void matrixBegin();
+
+ModulinoButtons buttons;
+
+void set_led_state(bool state) {
+  // LOW state means LED is ON
+  digitalWrite(LED_BUILTIN, state ? LOW : HIGH);
+}
+
+void setup() {
+  matrixBegin();
+  //Monitor.begin();
+  Modulino.begin(Wire1);
+
+ while(!buttons.begin()){
+   set_led_state(true);
+   delay(1000);
+   set_led_state(false);
+ }
+ buttons.setLeds(true, true, true);
+
+  pinMode(LED_BUILTIN, OUTPUT);
+  // Start with the LED OFF (HIGH state of the PIN)
+  digitalWrite(LED_BUILTIN, HIGH);
+
+  Bridge.begin();
+  Bridge.provide("set_led_state", set_led_state);
+  Bridge.provide("matrix_draw", matrix_draw);
+}
+
+void loop() {
+  
+if (buttons.update()) {
+    if (buttons.isPressed(0)) {
+      // Monitor.println("button a pressed");
+      // Serial.println("Button A pressed!");
+      Bridge.notify("button_pressed");
+      set_led_state(true);
+      delay(500);
+    } else if (buttons.isPressed(1)) {
+      // Serial.println("Button B pressed!");
+      // Monitor.println("button B pressed");
+      set_led_state(false);
+      Bridge.notify("button_pressed");
+      delay(500);
+    } else if (buttons.isPressed(1)) {
+      // Serial.println("Button C pressed!");
+      // Monitor.println("button C pressed");
+      Bridge.notify("button_pressed");
+      delay(500);
+    }
+ }
+}
+
+const uint32_t heart[] = {
+	0x1f88ffff,
+	0xe0fe03f0,
+	0xc1ef1e3d,
+	0x1f
+};
+
+void matrix_draw(){
+   matrixWrite(heart);
+}
+
+

sketch/sketch.yaml

@@ -0,0 +1,17 @@
+profiles:
+  default:
+    fqbn: arduino:zephyr:unoq
+    platforms:
+      - platform: arduino:zephyr
+    libraries:
+      - MsgPack (0.4.2)
+      - DebugLog (0.8.4)
+      - ArxContainer (0.7.0)
+      - ArxTypeTraits (0.3.1)
+      - Modulino (0.5.1)
+      - Arduino_HS300x (1.0.0)
+      - STM32duino VL53L4CD (1.0.5)
+      - STM32duino VL53L4ED (1.0.1)
+      - Arduino_LSM6DSOX (1.1.2)
+      - Arduino_LPS22HB (1.0.2)
+default_profile: default