Add GAT562 UF2 release packaging

.github/workflows/ci.yml

@@ -121,8 +121,8 @@ jobs:
             fi
           fi
 
-      - name: Prepare and verify T-Echo-Lite UF2
-        if: matrix.env == 't-echo-lite'
+      - name: Prepare and verify nRF52840 UF2
+        if: matrix.env == 'gat562_mesh_evb_pro' || matrix.env == 't-echo-lite'
         run: |
           python scripts/prepare_nrf52_uf2.py \
             --env ${{ matrix.env }} \

README.md

@@ -231,7 +231,7 @@ The table below describes the **real build targets that exist in the repository
 - If you are working on the newer large-screen ESP-IDF path, start with **`tab5`**
 - **`tdeck_pro_*`**, **`lilygo_twatch_s3`**, **`t_display_p4_tft`**, and **`t_display_p4_amoled`** are better treated as bring-up, layout, or device-adaptation targets than as the highest-maturity feature-validation path
 - “The repository has a build target” does not mean every page or capability is equally mature on that device; some features are enabled or hidden dynamically based on capabilities, RAM budget, and input hardware
-- GitHub Actions currently keeps building the main path through **`tlora_pager_sx1262`**, **`tlora_pager_lr1121`**, **`tdeck`**, **`lilygo_twatch_s3`**, **`gat562_mesh_evb_pro`**, and the nRF52 wrapper target **`t-echo-lite`**; T-Echo-Lite release artifacts include a UF2 file for manual flashing, verified with the nRF52840 UF2 family ID `0xADA52840`
+- GitHub Actions currently keeps building the main path through **`tlora_pager_sx1262`**, **`tlora_pager_lr1121`**, **`tdeck`**, **`lilygo_twatch_s3`**, **`gat562_mesh_evb_pro`**, and the nRF52 wrapper target **`t-echo-lite`**; GAT562 and T-Echo-Lite release artifacts include UF2 files for manual flashing, verified with the nRF52840 UF2 family ID `0xADA52840`
 
 ---
 

builds/pio_nrf52/README.md

@@ -34,10 +34,10 @@ platformio run -d builds/pio_nrf52 -e t-echo-lite
 platformio run -d builds/pio_nrf52 -e gat562_mesh_evb_pro
 ```
 
-Release artifacts for `t-echo-lite` prefer the generated `firmware.uf2` for
-manual flashing. CI verifies that this UF2 uses the nRF52840 family ID
-`0xADA52840`. The `.hex` and `.zip` outputs remain useful for diagnostics and
-toolchain-specific fallback paths.
+Release artifacts for the nRF52840 manual-flash targets prefer generated
+`firmware.uf2` files. CI verifies that these UF2 files use the nRF52840 family
+ID `0xADA52840`. The `.hex` and `.zip` outputs remain useful for diagnostics
+and toolchain-specific fallback paths.
 
 Rules:
 

site/main.js

@@ -525,12 +525,12 @@ const DEVICES = [
     },
     interactions: {
       en: [
-        "Use the downloaded firmware file instead of the browser flasher.",
+        "Use the GAT562 nRF52840 UF2 release file instead of the browser flasher.",
         "This board follows a different flashing model than the ESP32-S3 devices above.",
         "Screenshots will be added when this target has its own captured UI set.",
       ],
       zh: [
-        "请使用 GitHub Release 中的发布包，不要使用网页刷机。",
+        "请优先使用 GitHub Release 中的 GAT562 nRF52840 UF2 发布文件，不要使用网页刷机。",
         "这个设备的刷写方式和上面的 ESP32-S3 设备不同。",
         "后续有独立截图后，会补充该目标自己的界面展示。",
       ],