diff --git a/DOCS/DEV_SETUP.md b/DOCS/DEV_SETUP.md
index b7f0602e..1e0399bd 100644
--- a/DOCS/DEV_SETUP.md
+++ b/DOCS/DEV_SETUP.md
@@ -18,6 +18,23 @@
 4. If you touch component metadata, run `idf.py lint` to validate the manifest
    files.
 
+### Wi-Fi remote firmware
+
+ESP-IDF 5.4.2 ships the ESP32 Wi-Fi remote project in
+`$IDF_PATH/components/espressif__esp_hosted/slave`. Build and flash it once so
+the Tab5 SDIO link negotiates correctly:
+
+```bash
+cd "$IDF_PATH/components/espressif__esp_hosted/slave"
+idf.py set-target esp32
+idf.py build
+idf.py -p <remote_port> flash
+```
+
+The build drops `build/network_adapter.bin` if you prefer flashing with
+`esptool.py`. Future ESP32-C6 variants should publish their binaries as external
+artifacts instead of committing them to the repo.
+
 ## Component manager notes
 
 - Managed component revisions are pinned in
diff --git a/README.md b/README.md
index 97c1d377..91d13201 100644
--- a/README.md
+++ b/README.md
@@ -177,6 +177,22 @@ Monitor logs:
 
 Exit with Ctrl+].
 
+### Wi-Fi remote firmware
+
+ESP-IDF 5.4.2 bundles the supported ESP32 Wi-Fi remote under
+`$IDF_PATH/components/espressif__esp_hosted/slave`. Flash that image once per
+Tab5 so the SDIO link comes up reliably:
+
+1. `cd $IDF_PATH/components/espressif__esp_hosted/slave`
+2. `idf.py set-target esp32`
+3. `idf.py build`
+4. `idf.py -p <remote_port> flash`
+
+The build output produces `build/network_adapter.bin` if you prefer to flash via
+`esptool.py`. Shipping units use `CONFIG_SLAVE_IDF_TARGET_ESP32`, so the ESP32-C6
+firmware is no longer stored in this repository. Host any experimental C6 image
+as an external download and link it from the docs instead of committing binaries.
+
 
 ------------
 
diff --git a/docs/DEV_SETUP.md b/docs/DEV_SETUP.md
index e696bc37..462bf0ed 100644
--- a/docs/DEV_SETUP.md
+++ b/docs/DEV_SETUP.md
@@ -17,3 +17,20 @@
    `clang-format` manually).
 4. If you touch component metadata, run `idf.py lint` to validate the manifest
    files.
+
+### Wi-Fi remote firmware
+
+ESP-IDF 5.4.2 ships the ESP32 Wi-Fi remote project in
+`$IDF_PATH/components/espressif__esp_hosted/slave`. Build and flash it once so
+the Tab5 SDIO link negotiates correctly:
+
+```bash
+cd "$IDF_PATH/components/espressif__esp_hosted/slave"
+idf.py set-target esp32
+idf.py build
+idf.py -p <remote_port> flash
+```
+
+The build drops `build/network_adapter.bin` if you prefer flashing with
+`esptool.py`. Future ESP32-C6 variants should publish their binaries as external
+artifacts instead of committing them to the repo.
diff --git a/platforms/tab5/wifi_c6_fw/ESP32C6-WiFi-SDIO-Interface-V1.4.1-96bea3a_0x0.bin b/platforms/tab5/wifi_c6_fw/ESP32C6-WiFi-SDIO-Interface-V1.4.1-96bea3a_0x0.bin
deleted file mode 100644
index f78dbc51..00000000
Binary files a/platforms/tab5/wifi_c6_fw/ESP32C6-WiFi-SDIO-Interface-V1.4.1-96bea3a_0x0.bin and /dev/null differ
diff --git a/platforms/tab5/wifi_c6_fw/flash.sh b/platforms/tab5/wifi_c6_fw/flash.sh
deleted file mode 100755
index 44b91a42..00000000
--- a/platforms/tab5/wifi_c6_fw/flash.sh
+++ /dev/null
@@ -1 +0,0 @@
-esptool.py write_flash 0x0 ESP32C6-WiFi-SDIO-Interface-V1.4.1-96bea3a_0x0.bin
\ No newline at end of file