Switch to esp32_4MB_V4_S_eth build with ESP32-POE ethernet config

Changed from esp32_4MB_M_eth to esp32_4MB_V4_S_eth as requested.
This is the V4 Sound Reactive build with ethernet support.

Changes:
- Use esp32_4MB_V4_S_eth build (V4 Sound Reactive + Ethernet)
- Added WLED_ETH_DEFAULT=2 (ESP32-POE board configuration)
- ESP32-POE config compatible with QEMU open_eth model
- Updated all workflow paths and cache keys

Ethernet Configuration (ESP32-POE, index 2):
- PHY Address: 0
- Power Pin: 12
- MDC Pin: 23
- MDIO Pin: 18
- PHY Type: LAN8720
- Clock Mode: GPIO17_OUT

This configuration works with QEMU's open_eth model which emulates
standard ESP32 RMII ethernet interface.

Updated documentation:
- docs/QEMU-ISSUES.md: Added ethernet pin configuration details
- e2e-tests/README.md: Updated to use esp32_4MB_V4_S_eth
- platformio.ini: Set WLED_ETH_DEFAULT=2 for the build

Co-authored-by: softhack007 <91616163+softhack007@users.noreply.github.com>

Author: Copilot

.github/workflows/qemu-e2e-test.yml

@@ -27,9 +27,9 @@ jobs:
         uses: actions/cache@v4
         with:
           path: ~/.platformio
-          key: ${{ runner.os }}-pio-esp32_4MB_M_eth-${{ hashFiles('**/platformio.ini') }}
+          key: ${{ runner.os }}-pio-esp32_4MB_V4_S_eth-${{ hashFiles('**/platformio.ini') }}
           restore-keys: |
-            ${{ runner.os }}-pio-esp32_4MB_M_eth-
+            ${{ runner.os }}-pio-esp32_4MB_V4_S_eth-
       
       - name: Set up Python
         uses: actions/setup-python@v5
@@ -52,13 +52,13 @@ jobs:
         run: npm run build
 
       - name: Build ESP32 firmware
-        run: pio run -e esp32_4MB_M_eth
+        run: pio run -e esp32_4MB_V4_S_eth
 
       - name: Upload firmware artifacts
         uses: actions/upload-artifact@v4
         with:
           name: esp32-firmware
-          path: .pio/build/esp32_4MB_M_eth/
+          path: .pio/build/esp32_4MB_V4_S_eth/
           retention-days: 1
 
   # Job 2: Test with QEMU ESP32
@@ -85,7 +85,7 @@ jobs:
         uses: actions/download-artifact@v4
         with:
           name: esp32-firmware
-          path: .pio/build/esp32_4MB_M_eth/
+          path: .pio/build/esp32_4MB_V4_S_eth/
 
       - name: Install Node.js dependencies
         run: npm ci
@@ -116,7 +116,7 @@ jobs:
       - name: Start QEMU with WLED firmware in background
         run: |
           chmod +x .github/scripts/run-qemu.sh
-          bash .github/scripts/run-qemu.sh .pio/build/esp32_4MB_M_eth qemu-esp32 8080 > qemu-output.log 2>&1 &
+          bash .github/scripts/run-qemu.sh .pio/build/esp32_4MB_V4_S_eth qemu-esp32 8080 > qemu-output.log 2>&1 &
           echo "Waiting for QEMU to start and WLED to boot..."
           sleep 45
       

docs/QEMU-ISSUES.md

@@ -2,16 +2,28 @@
 
 ## Build Configuration
 
-**Important**: QEMU testing uses the **ethernet build** (`esp32_4MB_M_eth`) instead of the default WiFi build.
+**Important**: QEMU testing uses the **V4 Sound Reactive ethernet build** (`esp32_4MB_V4_S_eth`).
 
-### Why Ethernet Build?
+### Why esp32_4MB_V4_S_eth Build?
 - WiFi hardware is not emulated in QEMU
 - WiFi initialization causes crashes in QEMU
 - Ethernet build uses `WLED_USE_ETHERNET` flag
 - Disables ESP-NOW with `WLED_DISABLE_ESPNOW` (requires WiFi)
+- Uses ESP32-POE board configuration (`WLED_ETH_DEFAULT=2`)
 - Allows network functionality without WiFi hardware
 - HTTP server works via emulated ethernet (open_eth model)
 
+### Ethernet Configuration for QEMU
+The build uses ESP32-POE board configuration (index 2):
+- **PHY Address**: 0
+- **Power Pin**: 12
+- **MDC Pin**: 23
+- **MDIO Pin**: 18
+- **PHY Type**: LAN8720
+- **Clock Mode**: GPIO17_OUT
+
+This configuration is compatible with QEMU's `open_eth` model, which emulates standard ESP32 RMII ethernet interface.
+
 ## QEMU Limitations
 
 ESP32 QEMU emulation is not perfect and has several known limitations:

e2e-tests/README.md

@@ -31,12 +31,12 @@ pip install -r requirements.txt
 
 Test the actual firmware running in QEMU ESP32 emulator:
 
-**Important**: Use the ethernet build for QEMU testing, as WiFi is not emulated and causes crashes.
+**Important**: Use the V4 Sound Reactive ethernet build for QEMU testing, as WiFi is not emulated and causes crashes.
 
 1. **Build the firmware**:
    ```bash
    npm run build  # Build web UI
-   pio run -e esp32_4MB_M_eth  # Build ethernet firmware (WiFi disabled, 15+ min first time)
+   pio run -e esp32_4MB_V4_S_eth  # Build V4 SR ethernet firmware (WiFi disabled, 15+ min first time)
    ```
 
 2. **Setup QEMU** (first time only):
@@ -46,7 +46,7 @@ Test the actual firmware running in QEMU ESP32 emulator:
 
 3. **Run firmware in QEMU** (in a separate terminal):
    ```bash
-   bash .github/scripts/run-qemu.sh .pio/build/esp32_4MB_M_eth qemu-esp32 8080
+   bash .github/scripts/run-qemu.sh .pio/build/esp32_4MB_V4_S_eth qemu-esp32 8080
    ```
 
    Wait ~30-45 seconds for ESP32 to boot and start the web server.

platformio.ini

@@ -1826,6 +1826,7 @@ build_flags = ${esp32_4MB_V4_S_base.esp32_build_flags}
   ${common_mm.HUB75_build_flags}
   -D SR_DMTYPE=254 ;; HUB75 driver needs the I2S unit - set AR default mode to 'Network Receive Only' to prevent driver conflicts.
   -D WLED_USE_ETHERNET
+  -D WLED_ETH_DEFAULT=2 ;; ESP32-POE board configuration (works with QEMU open_eth)
   -D WLED_DISABLE_ESPNOW ;; ESP-NOW requires wifi, may crash with ethernet only
 lib_deps = ${esp32_4MB_V4_S_base.esp32_lib_deps}
     ${common_mm.HUB75_lib_deps}