back to dio flash mode, changed S3 bootloader position

PPUC · Nov 7, 2024 · 8f1eb82 · 8f1eb82
1 parent 0934b42
commit 8f1eb82
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 3 deletions.
diff --git a/.github/workflows/ZeDMD.yml b/.github/workflows/ZeDMD.yml
@@ -57,7 +57,7 @@ jobs:
         run: |
           pio run -e ${{ matrix.panels }}
           pio run -e ${{ matrix.panels }} -t buildfs
-          python ~/.platformio/packages/tool-esptoolpy/esptool.py --chip esp32 merge_bin -o ZeDMD.bin --flash_mode qio --flash_size 4MB \
+          python ~/.platformio/packages/tool-esptoolpy/esptool.py --chip esp32 merge_bin -o ZeDMD.bin --flash_mode dio --flash_size 4MB \
             0x1000 .pio/build/${{ matrix.panels }}/bootloader.bin \
             0x8000 .pio/build/${{ matrix.panels }}/partitions.bin \
             0xe000 ~/.platformio/packages/framework-arduinoespressif32/tools/partitions/boot_app0.bin \
@@ -69,8 +69,8 @@ jobs:
         run: |
           pio run -e ${{ matrix.panels }}
           pio run -e ${{ matrix.panels }} -t buildfs
-          python ~/.platformio/packages/tool-esptoolpy/esptool.py --chip esp32s3 merge_bin -o ZeDMD.bin --flash_mode qio --flash_size 16MB \
-            0x1000 .pio/build/${{ matrix.panels }}/bootloader.bin \
+          python ~/.platformio/packages/tool-esptoolpy/esptool.py --chip esp32s3 merge_bin -o ZeDMD.bin --flash_mode dio --flash_size 16MB \
+            0x0000 .pio/build/${{ matrix.panels }}/bootloader.bin \
             0x8000 .pio/build/${{ matrix.panels }}/partitions.bin \
             0xe000 ~/.platformio/packages/framework-arduinoespressif32/tools/partitions/boot_app0.bin \
             0x10000 .pio/build/${{ matrix.panels }}/firmware.bin \

diff --git a/README.md b/README.md
@@ -16,11 +16,15 @@ A full tutorial of its installation is available in [English](https://www.pincab
 Meanwhile, there're different "flavours" of the ZeDMD firmware. Because it pushes the cheap ESP32 to its limits, we can't provide a unified firmware, so you have to pick the appropriate one:
 * ZeDMD: using two 64x32 panels driven by an ESP32 connected over USB
 * ZeDMD HD: using four 64x64 or two 128x64 panels driven by an ESP32 connected over USB
+* ZeDMD HALF: using one 128x64 panel driven by an ESP32 connected over USB
 * ZeDMD WiFi: using two 64x32 panels driven by an ESP32 connected over WiFi
+* ZeDMD HALF WiFi: using one 128x64 panel driven by an ESP32 connected over WiFi
 * ZeDMD S3: using two 64x32 panels driven by an ESP32 S3 N16R8 connected over USB
 * ZeDMD S3 HD: using four 64x64 or two 128x64 panels  driven by an ESP32 S3 N16R8 connected over USB
+* ZeDMD S3 HALF: using one 128x64 panel driven by an ESP32 S3 N16R8 connected over USB
 * ZeDMD S3 WiFi: using two 64x32 panels  driven by an ESP32 S3 N16R8 connected over WiFi
 * ZeDMD S3 HD WiFi: using four 64x64 or two 128x64 panels driven by an ESP32 S3 N16R8 connected over WiFi
+* ZeDMD S3 HALF WiFi: using one 128x64 panel driven by an ESP32 S3 N16R8 connected over WiFi
 * ZeDMD S3 AMOLED: using a small OLED driven by a LilyGo AMOLED T-Display-S3 ESP32-S3 connected via USB
 * ZeDMD S3 AMOLED WiFi: using a small OLED driven by a LilyGo AMOLED T-Display-S3 ESP32-S3 connected via WiFi