Resolve nRF52 carrier bootloader links and explain audited coverage gaps

docs/_data/bootloader_manifest.json

@@ -536,7 +536,9 @@
       "id": "wio_tracker_l1",
       "label": "Seeed Wio Tracker L1",
       "meshcoreHardware": [
-        "WioTrackerL1"
+        "WioTrackerL1",
+        "WioTrackerL1-1W",
+        "WioTrackerL1Eink"
       ],
       "deviceName": "WTL1_DFU",
       "storage": "qspi",
@@ -653,7 +655,17 @@
       "id": "xiao_nrf52840_ble",
       "label": "Seeed XIAO nRF52840 BLE",
       "meshcoreHardware": [
-        "Xiao_nrf52"
+        "Xiao_nrf52",
+        "ikoka_handheld_nrf_e22_30dbm",
+        "ikoka_handheld_nrf_e22_30dbm_096",
+        "ikoka_nano_nrf_22dbm",
+        "ikoka_nano_nrf_30dbm",
+        "ikoka_nano_nrf_33dbm",
+        "ikoka_stick_nrf_22dbm",
+        "ikoka_stick_nrf_30dbm",
+        "ikoka_stick_nrf_33dbm",
+        "solarxiao_30S",
+        "solarxiao_33S"
       ],
       "deviceName": "XIAO_DFU",
       "storage": "qspi",
@@ -707,5 +719,98 @@
         }
       }
     }
+  ],
+  "unavailableProfiles": [
+    {
+      "id": "gat562_mesh_watch13",
+      "label": "GAT562 Mesh Watch13",
+      "meshcoreHardware": [
+        "GAT562_Mesh_Watch13"
+      ],
+      "reason": "The watch routes a GAT562 bootloader LED output to its vibration motor and has onboard flash. It needs a watch-specific profile."
+    },
+    {
+      "id": "heltec_mesh_solar",
+      "label": "Heltec Mesh Solar",
+      "meshcoreHardware": [
+        "Heltec_mesh_solar"
+      ],
+      "reason": "Mesh Solar has different LED and peripheral pins from the supported Heltec boards. It needs its own profile."
+    },
+    {
+      "id": "lilygo_t_impulse_plus",
+      "label": "LilyGo T-Impulse Plus",
+      "meshcoreHardware": [
+        "LilyGo_T_Impulse_Plus"
+      ],
+      "reason": "T-Impulse Plus has different flash data pins and LED wiring from T-Echo Lite. It needs its own profile."
+    },
+    {
+      "id": "lilygo_techo_card",
+      "label": "LilyGo T-Echo Card",
+      "meshcoreHardware": [
+        "LilyGo_T-Echo_Card"
+      ],
+      "reason": "T-Echo Card has its own NFC configuration, buttons and LED hardware. It needs a Card-specific profile."
+    },
+    {
+      "id": "meshtiny",
+      "label": "Meshtiny",
+      "meshcoreHardware": [
+        "Meshtiny"
+      ],
+      "reason": "Meshtiny has its own factory bootloader identity and controls. A dedicated Meshtiny profile has not been qualified."
+    },
+    {
+      "id": "meshtracker_x1",
+      "label": "MeshTracker X1",
+      "meshcoreHardware": [
+        "MeshTracker_X1"
+      ],
+      "reason": "MeshTracker X1 has different flash wiring, power control and button polarity from Wio Tracker L1. It needs its own profile."
+    },
+    {
+      "id": "muzi_base",
+      "label": "Muzi Base",
+      "meshcoreHardware": [
+        "muzi_base_duo",
+        "muzi_base_duo_superIO",
+        "muzi_base_uno",
+        "muzi_base_uno_superIO"
+      ],
+      "reason": "These four variants share Muzi Base hardware, which needs its own bootloader identity, LED polarity and flash configuration."
+    },
+    {
+      "id": "nano_g2_ultra",
+      "label": "Nano G2 Ultra",
+      "meshcoreHardware": [
+        "Nano_G2_Ultra"
+      ],
+      "reason": "Nano G2 Ultra has its own flash and button wiring. It needs a dedicated profile."
+    },
+    {
+      "id": "thinknode_m4",
+      "label": "ThinkNode M4",
+      "meshcoreHardware": [
+        "ThinkNode_M4"
+      ],
+      "reason": "ThinkNode M4 has different LED, button and power-control pins from the supported ThinkNodes. It needs its own profile."
+    },
+    {
+      "id": "thinknode_m8",
+      "label": "ThinkNode M8",
+      "meshcoreHardware": [
+        "ThinkNode_M8"
+      ],
+      "reason": "ThinkNode M8 shares some flash wiring with M1 but has different buttons and peripheral controls. It needs an M8-specific profile."
+    },
+    {
+      "id": "wio_wm1110",
+      "label": "Seeed Wio WM1110",
+      "meshcoreHardware": [
+        "wio_wm1110"
+      ],
+      "reason": "Wio WM1110 is a separate tracker board with different LED and peripheral pins. Its XIAO build setting does not make it XIAO hardware."
+    }
   ]
 }

docs/_javascript/firmware_picker.js

@@ -152,7 +152,21 @@
       });
       return Object.assign({}, profile, { files: files });
     }).filter(function (profile) { return Object.keys(profile.files).length === 3; });
-    return { tag: tag, version: tag.split("OTAFIX")[1], releaseUrl: releaseUrl, profiles: profiles };
+    const unavailableProfiles = (manifest.unavailableProfiles || []).map(function (profile) {
+      if (!/^[a-z0-9_]+$/.test(profile.id) || ids.has(profile.id) ||
+          !Array.isArray(profile.meshcoreHardware) || !profile.meshcoreHardware.length ||
+          typeof profile.reason !== "string" || !profile.reason.trim()) {
+        throw new Error("Invalid unavailable bootloader profile");
+      }
+      ids.add(profile.id);
+      profile.meshcoreHardware.forEach(function (hardware) {
+        if (!hardware || aliases.has(hardware)) throw new Error("Ambiguous bootloader hardware mapping");
+        aliases.add(hardware);
+      });
+      return profile;
+    });
+    return { tag: tag, version: tag.split("OTAFIX")[1], releaseUrl: releaseUrl,
+      profiles: profiles, unavailableProfiles: unavailableProfiles };
   }
 
   function bootloaderForHardware(catalog, hardware, chipFamily) {
@@ -163,6 +177,13 @@
     return matches.length === 1 ? matches[0] : null;
   }
 
+  function unavailableBootloaderForHardware(catalog, hardware, chipFamily) {
+    if (!catalog || chipFamily !== "nrf52" || !hardware) return null;
+    return catalog.unavailableProfiles.find(function (profile) {
+      return profile.meshcoreHardware.includes(hardware);
+    }) || null;
+  }
+
   const HARDWARE_ALIASES = Object.freeze({
     // Generated Full Companion artifact name. It uses the standard Heltec V4
     // board definition and auto-detects the V4.2 and V4.3 FEM hardware.
@@ -1995,7 +2016,10 @@
         content.appendChild(actions);
         content.appendChild(createElement("p", "UF2 updates an existing compatible bootloader. The DFU ZIP includes SoftDevice and bootloader; HEX is for SWD installation or recovery. Application firmware files do not install a bootloader. Follow the release's migration instructions if your installed identity needs a recovery bridge."));
       } else if (bootloaderCatalog) {
-        content.appendChild(createElement("p", "No verified bootloader download matches this exact hardware in the current catalog. Check the release notes for board support."));
+        const unavailable = unavailableBootloaderForHardware(bootloaderCatalog, hardware, chip);
+        content.appendChild(createElement("p", unavailable ?
+          "No OTAFIX " + bootloaderCatalog.version + " bootloader has been published for this board. " + unavailable.reason :
+          "No verified bootloader download matches this exact hardware in the current catalog. Check the release notes for board support."));
       }
       if (bootloaderNotice) content.appendChild(createElement("p", bootloaderNotice));
       const notes = createElement("a", "Bootloader release notes and migration instructions");
@@ -2159,6 +2183,7 @@
   const api = Object.freeze({
     buildBootloaderCatalog: buildBootloaderCatalog,
     bootloaderForHardware: bootloaderForHardware,
+    unavailableBootloaderForHardware: unavailableBootloaderForHardware,
     FILTER_FIELDS: FILTER_FIELDS,
     FACET_FIELDS: FACET_FIELDS,
     PROFILE_FIELDS: PROFILE_FIELDS,

docs/firmware_picker.md

@@ -20,7 +20,7 @@ The picker reads public release metadata from GitHub. It does not upload device
 information. Hardware names, target names, and download links come directly
 from the published firmware assets.
 
-<div class="firmware-picker" data-firmware-picker data-release-repo="mikecarper/MeshCore" data-controls-url="../_data/firmware_controls.json?v=1.17.1.7-runtime-2" data-bootloaders-url="../_data/bootloader_manifest.json?v=20260929-1" data-share-url="https://mikecarper.github.io/MeshCore/firmware_picker/">
+<div class="firmware-picker" data-firmware-picker data-release-repo="mikecarper/MeshCore" data-controls-url="../_data/firmware_controls.json?v=1.17.1.7-runtime-2" data-bootloaders-url="../_data/bootloader_manifest.json?v=20260929-2" data-share-url="https://mikecarper.github.io/MeshCore/firmware_picker/">
   <div class="firmware-picker-intro" role="note">
     <strong>Current release set</strong>
     <p data-role="release-set">Loading release information...</p>
@@ -398,6 +398,10 @@ includes the bootloader release named in its saved catalog. If a board has no
 verified mapping or a file is missing, the picker explains that instead of
 offering another board's bootloader. MeshTower internal and microSD remain
 separate; RAK3401 and RAK4631 each use their adaptive storage bootloader.
+Ikoka Stick, Nano and Handheld plus SolarXiao use the XIAO bootloader;
+Wio Tracker L1 1W and E-Ink use the L1 bootloader. See the
+[board coverage audit](https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/blob/feature/ota-delta-apply/docs/meshcore-hardware-coverage.md)
+for the source checks and boards still awaiting a dedicated, tested release.
 
 Board mappings and file names, URLs, sizes and SHA-256 hashes come from
 `bootloader-manifest.json` in the