@typecad/framework-zephyr 1.0.0-alpha.15 → 1.0.0-alpha.18

package/src/toolchain/west-discover.ts

@@ -11,7 +11,7 @@
 //   1. `west` already on PATH (env already activated / global install).
 //   2. $ZEPHYR_BASE venv: ${ZEPHYR_BASE}/../.venv/<python> -m west.
 //   3. micromamba env from @typecad/zephyr-installer (invoked via `micromamba run`,
-//      so cuttlefish builds work with NO manual activation).
+//      so typecad-hal builds work with NO manual activation).
 //   4. Well-known workspace layouts: ~/zephyrproject/.venv, /opt/zephyrproject/.
 //      venv, etc.
 //   5. System pythons (`python`, `python3`, `py`) via `-m west`.
@@ -142,6 +142,33 @@ export function discoverFromZephyrBase(): WestInstall | null {
   };
 }
 
+/** The installer-written SDK dir for the default micromamba env, when the
+ *  installer has run on this machine. Read WITHOUT requiring micromamba
+ *  mode — a PATH/venv west install is enriched with it so builds spawned
+ *  through it still pin the installer's SDK (otherwise Zephyr's CMake
+ *  searches $HOME and can pick up a stray, older SDK). */
+export function installerSdkDir(): string | undefined {
+  const mm = findMicromamba();
+  if (!mm) return undefined;
+  const envName = process.env.TYPECAD_ZEPHYR_ENV || 'zephyr';
+  const envDir = join(mm.rootPrefix, 'envs', envName);
+  if (!existsSync(envDir)) return undefined;
+  const sdk = readMicromambaEnvVar(envDir, 'TYPECAD_ZEPHYR_SDK_INSTALL_DIR');
+  return sdk && existsSync(sdk) ? sdk : undefined;
+}
+
+/**
+ * The micromamba env created by `@typecad/zephyr-installer`. The env's west
+ * lives at envs/<name>/bin/west (POSIX) or Scripts/west.exe (Windows). Found
+ * installs are invoked via `micromamba run -n <name> west …` (see
+ * west-spawn.ts), which sets up the env's full PATH (cmake/ninja/dtc) AND runs
+ * the activation hook (ZEPHYR_BASE / ZEPHYR_SDK_INSTALL_DIR) — so builds work
+ * with NO manual `micromamba activate`. This is what makes a fresh
+ * `typecad-hal build` succeed in any project without the user activating.
+ *
+ * Env name defaults to "zephyr"; override via TYPECAD_ZEPHYR_ENV. File-check
+ * based (no spawn) so it's cheap to run on every invocation.
+ */
 // ── Strategy 3: micromamba env (the @typecad/zephyr-installer install) ─────
 
 // Locate the micromamba binary + root prefix. The installer downloads
@@ -156,18 +183,6 @@ function findMicromamba(): { exe: string; rootPrefix: string } | null {
   return existsSync(exe) ? { exe, rootPrefix: root } : null;
 }
 
-/**
- * The micromamba env created by `@typecad/zephyr-installer`. The env's west
- * lives at envs/<name>/bin/west (POSIX) or Scripts/west.exe (Windows). Found
- * installs are invoked via `micromamba run -n <name> west …` (see
- * west-spawn.ts), which sets up the env's full PATH (cmake/ninja/dtc) AND runs
- * the activation hook (ZEPHYR_BASE / ZEPHYR_SDK_INSTALL_DIR) — so cuttlefish
- * builds work with NO manual `micromamba activate`. This is what makes a fresh
- * `cuttlefish build` succeed in any project without the user activating.
- *
- * Env name defaults to "zephyr"; override via TYPECAD_ZEPHYR_ENV. File-check
- * based (no spawn) so it's cheap to run on every cuttlefish invocation.
- */
 /** Read a TYPECAD_ZEPHYR_* value from the installer-written env-vars file in
  *  a micromamba env. Handles .sh (export VAR="val"), .bat (set "VAR=val"),
  *  and .ps1 ($env:VAR = "val"). Returns undefined if absent/unreadable. */
@@ -325,6 +340,13 @@ export function discoverWest(): WestInstall | null {
       install = null;
     }
     if (install) {
+      // A PATH/venv west install knows nothing about the installer's SDK.
+      // Enrich it: west-spawn pins the child's ZEPHYR_SDK_INSTALL_DIR to the
+      // installer dir, so Zephyr's CMake cannot pick up a stray SDK from
+      // $HOME (a version mismatch that only surfaces at configure time).
+      if (!install.sdkInstallDir) {
+        install.sdkInstallDir = installerSdkDir();
+      }
       cachedDiscover = install;
       return install;
     }

package/src/toolchain/west-spawn.ts

@@ -1,168 +1,174 @@
-// ---------------------------------------------------------------------------
-// west spawn helper — build a spawnSync invocation for `west <args>`
-//
-// Mirrors framework-esp32's idfSpawn(): given the discovered WestInstall,
-// produce {command, args, env} that the toolchain destructures into spawnSync.
-//
-// Two modes:
-//   - 'launcher': spawn the `west` launcher directly (mode 'launcher').
-//   - 'module'  : spawn `<python> -m west ...` (mode 'module'). This is the
-//                 robust cross-platform form — it activates the venv's
-//                 interpreter for the one process without sourcing anything.
-//
-// ZEPHYR_BASE is injected into the spawn env when a SDK root was discovered
-// (find_package(Zephyr) needs it). west's prj.conf/CMakeLists are found via
-// the project dir regardless.
-// ---------------------------------------------------------------------------
-
-import type { SpawnSyncOptions } from 'node:child_process';
-import { dirname, join } from 'node:path';
-import { existsSync } from 'node:fs';
-import { type WestInstall, discoverWest } from './west-discover.js';
-
-export interface WestInvocation {
-  /** The command to spawnSync: a `west` launcher or a Python interpreter. */
-  command: string;
-  /** Args for the command (includes `-m west` when in module mode). */
-  args: string[];
-  /** Base spawn options with cwd/timeout/encoding/stdio, plus the env carrying
-   *  ZEPHYR_BASE when discovered. */
-  options: SpawnSyncOptions;
-  /** The install the invocation was built from, for surfacing to the user. */
-  install: WestInstall;
-}
-
-/**
- * The Scripts/ (Windows) or bin/ (POSIX) directory of the venv the discovered
- * west runs under. `pythonExecutable` lives in that directory, so it is its
- * dirname. Returns undefined for launcher-mode installs where no venv is known.
- */
-function venvBinDir(install: WestInstall): string | undefined {
-  return install.pythonExecutable ? dirname(install.pythonExecutable) : undefined;
-}
-
-/**
- * The env to pass to the west spawn: the process env, with ZEPHYR_BASE injected
- * when a SDK root was discovered, AND the venv's bin/Scripts dir prepended to
- * PATH when west was found via a venv Python.
- *
- * The PATH prepend matters: `west flash` shells out to bare runner tools
- * (`esptool`, `openocd`, `nrfjprog`, …) via check_call, so they resolve from
- * PATH. Without the prepend, the user's PATH may surface a *different* tool
- * ahead of the venv's — e.g. an older esptool whose argument spelling is
- * incompatible with the runner. Putting the venv's bin first makes west's
- * delegated subprocesses resolve to the same versions west itself runs under.
- */
-export function buildEnv(install: WestInstall): NodeJS.ProcessEnv {
-  const env = { ...process.env };
-  if (install.zephyrBase && !env.ZEPHYR_BASE) {
-    env.ZEPHYR_BASE = install.zephyrBase;
-  }
-  // SWD flashing (`zephyr.runner: 'openocd'`): west's openocd runner resolves
-  // a bare `openocd` from PATH. The Zephyr SDK ships it under
-  // hosttools/openocd/bin (the SDK's own setup.cmd puts that dir on PATH for
-  // activated terminals) — do the same for spawned west processes so ST-Link
-  // flashing works without activation. $ZEPHYR_SDK_INSTALL_DIR (set by an
-  // activated env) wins over the discovered install dir.
-  const sdkRoot = env.ZEPHYR_SDK_INSTALL_DIR || install.sdkInstallDir;
-  const openocdBin = sdkRoot ? join(sdkRoot, 'hosttools', 'openocd', 'bin') : undefined;
-  const prepend = [
-    openocdBin !== undefined && existsSync(openocdBin) ? openocdBin : undefined,
-    venvBinDir(install),
-  ].filter((d): d is string => d !== undefined);
-  if (prepend.length > 0) {
-    const sep = process.platform === 'win32' ? ';' : ':';
-    // On Windows the PATH environment variable may be cased as `Path` (the
-    // registry-native form, the only one populated when node is launched from
-    // PowerShell/cmd) or `PATH` (POSIX form, set by Git Bash). Writing only one
-    // casing can leave the other stale/empty, which under PowerShell would drop
-    // the user's real PATH (cmake, ninja, …) — breaking `west` configure. Read
-    // whichever casing is populated and write that same casing back, preserving
-    // the full existing value with the discovered dirs prepended.
-    const existing = env.Path ?? env.PATH ?? '';
-    const updated = prepend.join(sep) + sep + existing;
-    if (env.Path !== undefined || (env.PATH === undefined && process.platform === 'win32')) {
-      env.Path = updated;
-    } else {
-      env.PATH = updated;
-    }
-  }
-  return env;
-}
-
-/**
- * Build a spawn invocation that runs `west <westArgs>`.
- *
- * `baseOptions` carries the cwd/timeout/stdio settings the caller wants;
- * westSpawn preserves them and injects the discovery env. The returned object
- * destructures directly into spawnSync:
- *
- *   const inv = westSpawn(['build', '-b', 'xiao_ble', projectRoot], { cwd, timeout });
- *   spawnSync(inv.command, inv.args, inv.options);
- *
- * Throws a clear, actionable error when no usable west install is discovered.
- */
-export function westSpawn(
-  westArgs: string[],
-  baseOptions: SpawnSyncOptions,
-): WestInvocation {
-  const install = discoverWest();
-  if (!install) {
-    throw new Error(
-      [
-        'west (the Zephyr build tool) was not found.',
-        '',
-        'cuttlefish looked for it on PATH, in $ZEPHYR_BASE/.venv, in common',
-        'Zephyr workspace dirs (~/zephyrproject/.venv), and as a system',
-        "Python module (`python -m west`). To fix:",
-        '',
-        '  • Run the typeCAD Zephyr installer (one command, any OS — needs Node ≥18):',
-        '      node packages/zephyr-installer/install.mjs',
-        '    then `micromamba activate zephyr` and retry.',
-        '  • Or activate an existing Zephyr venv in this shell, or',
-        '  • Or set ZEPHYR_BASE to your Zephyr SDK root (the venv at $ZEPHYR_BASE/../.venv is then used), or',
-        '  • Or install west into a discoverable Python: pip install west',
-        '',
-        'See https://docs.zephyrproject.org/latest/develop/getting_started/index.html',
-      ].join('\n'),
-    );
-  }
-
-  const env = buildEnv(install);
-  // Strip `shell` if present — we pass absolute paths / known commands, and
-  // an explicit shell changes arg-quoting semantics on Windows.
-  const { shell: _drop, ...optsWithoutShell } = baseOptions as any;
-
-  if (install.mode === 'micromamba' && install.micromambaExe) {
-    // `micromamba run -n <env> west …` sets up the env's full PATH
-    // (cmake/ninja/dtc) and runs the activation hook (ZEPHYR_BASE /
-    // ZEPHYR_SDK_INSTALL_DIR), so cuttlefish builds work WITHOUT the user
-    // activating the env. Inject MAMBA_ROOT_PREFIX so micromamba finds envs.
-    const mmEnv = { ...env };
-    if (install.mambaRootPrefix) mmEnv.MAMBA_ROOT_PREFIX = install.mambaRootPrefix;
-    return {
-      command: install.micromambaExe,
-      args: ['run', '-n', install.envName ?? 'zephyr', 'west', ...westArgs],
-      options: { ...optsWithoutShell, env: mmEnv },
-      install,
-    };
-  }
-
-  if (install.mode === 'launcher' && install.westExecutable) {
-    return {
-      command: install.westExecutable,
-      args: westArgs,
-      options: { ...optsWithoutShell, env },
-      install,
-    };
-  }
-
-  // module mode: <python> -m west <args>
-  const py = install.pythonExecutable!;
-  return {
-    command: py,
-    args: ['-m', 'west', ...westArgs],
-    options: { ...optsWithoutShell, env },
-    install,
-  };
-}
+// ---------------------------------------------------------------------------
+// west spawn helper — build a spawnSync invocation for `west <args>`
+//
+// Mirrors framework-esp32's idfSpawn(): given the discovered WestInstall,
+// produce {command, args, env} that the toolchain destructures into spawnSync.
+//
+// Two modes:
+//   - 'launcher': spawn the `west` launcher directly (mode 'launcher').
+//   - 'module'  : spawn `<python> -m west ...` (mode 'module'). This is the
+//                 robust cross-platform form — it activates the venv's
+//                 interpreter for the one process without sourcing anything.
+//
+// ZEPHYR_BASE is injected into the spawn env when a SDK root was discovered
+// (find_package(Zephyr) needs it). west's prj.conf/CMakeLists are found via
+// the project dir regardless.
+// ---------------------------------------------------------------------------
+
+import type { SpawnSyncOptions } from 'node:child_process';
+import { dirname, join } from 'node:path';
+import { existsSync } from 'node:fs';
+import { type WestInstall, discoverWest } from './west-discover.js';
+
+export interface WestInvocation {
+  /** The command to spawnSync: a `west` launcher or a Python interpreter. */
+  command: string;
+  /** Args for the command (includes `-m west` when in module mode). */
+  args: string[];
+  /** Base spawn options with cwd/timeout/encoding/stdio, plus the env carrying
+   *  ZEPHYR_BASE when discovered. */
+  options: SpawnSyncOptions;
+  /** The install the invocation was built from, for surfacing to the user. */
+  install: WestInstall;
+}
+
+/**
+ * The Scripts/ (Windows) or bin/ (POSIX) directory of the venv the discovered
+ * west runs under. `pythonExecutable` lives in that directory, so it is its
+ * dirname. Returns undefined for launcher-mode installs where no venv is known.
+ */
+function venvBinDir(install: WestInstall): string | undefined {
+  return install.pythonExecutable ? dirname(install.pythonExecutable) : undefined;
+}
+
+/**
+ * The env to pass to the west spawn: the process env, with ZEPHYR_BASE injected
+ * when a SDK root was discovered, AND the venv's bin/Scripts dir prepended to
+ * PATH when west was found via a venv Python.
+ *
+ * The PATH prepend matters: `west flash` shells out to bare runner tools
+ * (`esptool`, `openocd`, `nrfjprog`, …) via check_call, so they resolve from
+ * PATH. Without the prepend, the user's PATH may surface a *different* tool
+ * ahead of the venv's — e.g. an older esptool whose argument spelling is
+ * incompatible with the runner. Putting the venv's bin first makes west's
+ * delegated subprocesses resolve to the same versions west itself runs under.
+ */
+export function buildEnv(install: WestInstall): NodeJS.ProcessEnv {
+  const env = { ...process.env };
+  if (install.zephyrBase && !env.ZEPHYR_BASE) {
+    env.ZEPHYR_BASE = install.zephyrBase;
+  }
+  // SWD flashing (`zephyr.runner: 'openocd'`): west's openocd runner resolves
+  // a bare `openocd` from PATH. The Zephyr SDK ships it under
+  // hosttools/openocd/bin (the SDK's own setup.cmd puts that dir on PATH for
+  // activated terminals) — do the same for spawned west processes so ST-Link
+  // flashing works without activation. $ZEPHYR_SDK_INSTALL_DIR (set by an
+  // activated env) wins over the discovered install dir.
+  const sdkRoot = env.ZEPHYR_SDK_INSTALL_DIR || install.sdkInstallDir;
+  // Pin the west/cmake child to the discovered SDK: without this, Zephyr's
+  // FindZephyr-sdk searches $HOME and can latch onto a stray, older SDK —
+  // a configure-time version failure that only surfaces in the build log.
+  if (!env.ZEPHYR_SDK_INSTALL_DIR && install.sdkInstallDir) {
+    env.ZEPHYR_SDK_INSTALL_DIR = install.sdkInstallDir;
+  }
+  const openocdBin = sdkRoot ? join(sdkRoot, 'hosttools', 'openocd', 'bin') : undefined;
+  const prepend = [
+    openocdBin !== undefined && existsSync(openocdBin) ? openocdBin : undefined,
+    venvBinDir(install),
+  ].filter((d): d is string => d !== undefined);
+  if (prepend.length > 0) {
+    const sep = process.platform === 'win32' ? ';' : ':';
+    // On Windows the PATH environment variable may be cased as `Path` (the
+    // registry-native form, the only one populated when node is launched from
+    // PowerShell/cmd) or `PATH` (POSIX form, set by Git Bash). Writing only one
+    // casing can leave the other stale/empty, which under PowerShell would drop
+    // the user's real PATH (cmake, ninja, …) — breaking `west` configure. Read
+    // whichever casing is populated and write that same casing back, preserving
+    // the full existing value with the discovered dirs prepended.
+    const existing = env.Path ?? env.PATH ?? '';
+    const updated = prepend.join(sep) + sep + existing;
+    if (env.Path !== undefined || (env.PATH === undefined && process.platform === 'win32')) {
+      env.Path = updated;
+    } else {
+      env.PATH = updated;
+    }
+  }
+  return env;
+}
+
+/**
+ * Build a spawn invocation that runs `west <westArgs>`.
+ *
+ * `baseOptions` carries the cwd/timeout/stdio settings the caller wants;
+ * westSpawn preserves them and injects the discovery env. The returned object
+ * destructures directly into spawnSync:
+ *
+ *   const inv = westSpawn(['build', '-b', 'xiao_ble', projectRoot], { cwd, timeout });
+ *   spawnSync(inv.command, inv.args, inv.options);
+ *
+ * Throws a clear, actionable error when no usable west install is discovered.
+ */
+export function westSpawn(
+  westArgs: string[],
+  baseOptions: SpawnSyncOptions,
+): WestInvocation {
+  const install = discoverWest();
+  if (!install) {
+    throw new Error(
+      [
+        'west (the Zephyr build tool) was not found.',
+        '',
+        'typecad-hal looked for it on PATH, in $ZEPHYR_BASE/.venv, in common',
+        'Zephyr workspace dirs (~/zephyrproject/.venv), and as a system',
+        "Python module (`python -m west`). To fix:",
+        '',
+        '  • Run the typeCAD Zephyr installer (one command, any OS — needs Node ≥18):',
+        '      node packages/zephyr-installer/install.mjs',
+        '    then `micromamba activate zephyr` and retry.',
+        '  • Or activate an existing Zephyr venv in this shell, or',
+        '  • Or set ZEPHYR_BASE to your Zephyr SDK root (the venv at $ZEPHYR_BASE/../.venv is then used), or',
+        '  • Or install west into a discoverable Python: pip install west',
+        '',
+        'See https://docs.zephyrproject.org/latest/develop/getting_started/index.html',
+      ].join('\n'),
+    );
+  }
+
+  const env = buildEnv(install);
+  // Strip `shell` if present — we pass absolute paths / known commands, and
+  // an explicit shell changes arg-quoting semantics on Windows.
+  const { shell: _drop, ...optsWithoutShell } = baseOptions as any;
+
+  if (install.mode === 'micromamba' && install.micromambaExe) {
+    // `micromamba run -n <env> west …` sets up the env's full PATH
+    // (cmake/ninja/dtc) and runs the activation hook (ZEPHYR_BASE /
+    // ZEPHYR_SDK_INSTALL_DIR), so typecad-hal builds work WITHOUT the user
+    // activating the env. Inject MAMBA_ROOT_PREFIX so micromamba finds envs.
+    const mmEnv = { ...env };
+    if (install.mambaRootPrefix) mmEnv.MAMBA_ROOT_PREFIX = install.mambaRootPrefix;
+    return {
+      command: install.micromambaExe,
+      args: ['run', '-n', install.envName ?? 'zephyr', 'west', ...westArgs],
+      options: { ...optsWithoutShell, env: mmEnv },
+      install,
+    };
+  }
+
+  if (install.mode === 'launcher' && install.westExecutable) {
+    return {
+      command: install.westExecutable,
+      args: westArgs,
+      options: { ...optsWithoutShell, env },
+      install,
+    };
+  }
+
+  // module mode: <python> -m west <args>
+  const py = install.pythonExecutable!;
+  return {
+    command: py,
+    args: ['-m', 'west', ...westArgs],
+    options: { ...optsWithoutShell, env },
+    install,
+  };
+}

package/dist/async/timer-polyfill.d.ts

@@ -1,10 +0,0 @@
-import type { RuntimePolyfillIR } from '@typecad/cuttlefish/api/shared';
-export interface TimerPolyfillIR extends RuntimePolyfillIR {
-    /** The clamped pool size the C++ was generated with. */
-    maxTimers: number;
-}
-/**
- * Build the timer_methods polyfill IR. `requestedTimers` is sized from
- * ctx.analysis.timerCallCount; it is clamped to [1, 16].
- */
-export declare function buildTimerPolyfill(requestedTimers: number): TimerPolyfillIR;

package/dist/async/timer-polyfill.js

@@ -1,95 +0,0 @@
-// ---------------------------------------------------------------------------
-// Timer methods polyfill — Zephyr k_timer + k_work (heap-free)
-//
-// setInterval / setTimeout / clearInterval / clearTimeout backed by a fixed
-// pool of k_timer + k_work pairs. The timer's expiry function (ISR context)
-// submits a k_work item to the system workqueue; the work handler runs the
-// user callback in thread context. This split keeps the ISR cheap and lets the
-// callback run on a real thread (so it can do real work — but must not block,
-// since the system workqueue is shared).
-//
-// EMIT BOUNDARY: emitted bytes land in user firmware. Covered by the TypeCAD
-// Runtime Exception (RUNTIME_EXCEPTION.md at the repo root).
-// ---------------------------------------------------------------------------
-const MIN_TIMERS = 1;
-const MAX_TIMERS_CAP = 16;
-/**
- * Build the timer_methods polyfill IR. `requestedTimers` is sized from
- * ctx.analysis.timerCallCount; it is clamped to [1, 16].
- */
-export function buildTimerPolyfill(requestedTimers) {
-    const maxTimers = Math.min(MAX_TIMERS_CAP, Math.max(MIN_TIMERS, requestedTimers));
-    const helperStructs = [`
-// cuttlefish timer runtime — k_timer + k_work pool (heap-free).
-struct __tc_TimerSlot {
-    struct k_timer timer;
-    struct k_work work;
-    void (*callback)(void);
-    bool active;
-};
-
-static struct __tc_TimerSlot __tc_timer_slots[${maxTimers}];
-
-static void __tc_timer_work_handler(struct k_work* w) {
-    // Runs on the system workqueue thread (NOT ISR). Find the owning slot by
-    // address and invoke the callback. Must not block.
-    for (int32_t i = 0; i < ${maxTimers}; i++) {
-        if (&__tc_timer_slots[i].work == w) {
-            if (__tc_timer_slots[i].callback != nullptr) { __tc_timer_slots[i].callback(); }
-            return;
-        }
-    }
-}
-
-static void __tc_timer_expiry_fn(struct k_timer* t) {
-    // ISR context: submit the work item, do NOT run the callback here.
-    for (int32_t i = 0; i < ${maxTimers}; i++) {
-        if (&__tc_timer_slots[i].timer == t) {
-            (void)k_work_submit(&__tc_timer_slots[i].work);
-            return;
-        }
-    }
-}
-
-static int32_t __tc_timer_add(void (*cb)(void), int32_t ms, bool repeat) {
-    for (int32_t i = 0; i < ${maxTimers}; i++) {
-        if (!__tc_timer_slots[i].active) {
-            __tc_timer_slots[i].callback = cb;
-            __tc_timer_slots[i].active = true;
-            k_timer_init(&__tc_timer_slots[i].timer, __tc_timer_expiry_fn, nullptr);
-            k_work_init(&__tc_timer_slots[i].work, __tc_timer_work_handler);
-            k_timer_start(&__tc_timer_slots[i].timer, K_MSEC(ms), repeat ? K_MSEC(ms) : K_FOREVER);
-            return i + 1;  // 1-based id
-        }
-    }
-    return 0;  // pool full
-}
-
-static void __tc_timer_clear(int32_t id) {
-    if (id > 0 && id <= ${maxTimers}) {
-        int32_t i = id - 1;
-        k_timer_stop(&__tc_timer_slots[i].timer);
-        __tc_timer_slots[i].active = false;
-        __tc_timer_slots[i].callback = nullptr;
-    }
-}
-`];
-    const helperFunctions = [`
-int32_t __tc_setInterval(void (*cb)(), int32_t ms) { return __tc_timer_add(cb, ms, true); }
-int32_t __tc_setTimeout(void (*cb)(), int32_t ms) { return __tc_timer_add(cb, ms, false); }
-void __tc_clearInterval(int32_t id) { __tc_timer_clear(id); }
-void __tc_clearTimeout(int32_t id) { __tc_timer_clear(id); }
-`];
-    return {
-        kind: 'polyfill',
-        id: 'timer_methods',
-        domain: 'embedded',
-        requiredIncludes: [],
-        forwardDeclarations: [],
-        helperStructs,
-        helperFunctions,
-        shimMacros: [],
-        dependencies: [],
-        maxTimers,
-    };
-}

package/dist/chips/board-overrides.d.ts

@@ -1,7 +0,0 @@
-export interface BoardOverride {
-    /** LED pin name for boards whose user LED is not a gpio-leds node (the
-     *  ESP32-S3 DevKitC's addressable RGB on GPIO48 — driven as plain GPIO,
-     *  same as the deleted board package did). */
-    readonly led?: string;
-}
-export declare const BOARD_OVERRIDES: Readonly<Record<string, BoardOverride>>;

package/dist/chips/board-overrides.js

@@ -1,11 +0,0 @@
-// ---------------------------------------------------------------------------
-// board-overrides.ts — curated board-level facts the devicetree cannot
-// express. The honest residue of the board-package deletion: things a board
-// vendor documents in a datasheet but never encodes in DTS.
-//
-// Keyed by the bare board id (the first segment of the qualified target, so
-// every variant/qualifier of the board inherits the override).
-// ----------------------------------------------------------------------------
-export const BOARD_OVERRIDES = {
-    esp32s3_devkitc: { led: 'GPIO48' },
-};

package/dist/chips/esp32.d.ts

@@ -1,2 +0,0 @@
-import type { ZephyrChipDescriptor } from './types.js';
-export declare const ESP32_DEVKITC: ZephyrChipDescriptor;

package/dist/chips/esp32.js

@@ -1,71 +0,0 @@
-// ---------------------------------------------------------------------------
-// Espressif ESP32 (esp32_devkitc) — Zephyr board descriptor
-//
-// Board target: `esp32_devkitc` (mainline Zephyr,
-// boards/espressif/esp32_devkitc). Programmed over USB via the esptool runner
-// (see toolchain/index.ts), the same flash path as the ESP32-S3.
-//
-// GPIO is split across TWO devicetree controllers — `gpio0` (pins 0–31) and
-// `gpio1` (pins 32–39) — so this descriptor lists both in `gpioControllers`.
-// The lowering routes each HAL pin to its owning controller at runtime; see
-// chips/controllers.ts. (Same shape as the S3, but the ESP32's highest GPIO is
-// 39, not 48 — `gpio1` has ngpios=8, not 17.)
-//
-// Minimal-by-design: the only DT facts carried here are the ones a compile-time
-// DT macro cannot reach — the runtime pin→controller split, plus the `sw0`
-// alias for the BOOT button (used by the devicetree-spec GPIO path). Every other
-// DT fact (UART/I2C/SPI/`wdt` nodelabels) is resolved by Zephyr's own
-// devicetree via emitted DT_NODELABEL macros, not hand-copied here.
-//
-// Verified against the Zephyr board DTS:
-//   boards/espressif/esp32_devkitc/esp32_devkitc_procpu.dts
-//   aliases { sw0 = &button0; } → button_0: pin 0 on gpio0, active-low + pull-up
-//   &gpio0/&gpio1 { status = "okay" }   (esp32_devkitc_procpu.dts:64-70)
-//   &wifi { status = "okay" }            (esp32_devkitc_procpu.dts:143-145)
-// GPIO controller coverage:
-//   dts/xtensa/espressif/esp32/esp32_common.dtsi:314-337
-//   gpio0: ngpios = <32>  (pins 0–31)
-//   gpio1: ngpios = <8>   (pins 32–39)
-//
-// Note: GPIO 34–39 are input-only pads on ESP32 silicon (not modeled here —
-// the DT does not encode output restrictions per pin; an output config on those
-// pins fails at runtime against the raw controller, which is the expected
-// silicon-accurate behavior).
-// ---------------------------------------------------------------------------
-export const ESP32_DEVKITC = {
-    id: 'esp32_devkitc',
-    soc: 'esp32',
-    gpioController: 'gpio0',
-    gpioControllers: [
-        { nodelabel: 'gpio0', minPin: 0, maxPin: 31 },
-        { nodelabel: 'gpio1', minPin: 32, maxPin: 39 },
-    ],
-    gpio: {
-        // The BOOT button (GPIO0) is the board's only DT-aliased GPIO. Listed so a
-        // program reading/interrupting pin 0 goes through the polarity-correct
-        // devicetree-spec path (GPIO_ACTIVE_LOW honored by the DT flags).
-        dtSpecs: [
-            { pin: 0, dtSpec: 'sw0' }, // BOOT button (GPIO0)
-        ],
-        interruptPins: [
-            { pin: 0, dtSpec: 'sw0' }, // BOOT button (GPIO0)
-        ],
-    },
-    // WiFi: the ESP32 has a 2.4GHz radio; conn_mgr + the esp32 wifi driver
-    // (CONFIG_WIFI_ESP32) provide connectivity. WIFI_ESP32 depends on !SMP, and
-    // the ESP32 is AMP (dual-image procpu/appcpu), not SMP, by default — so the
-    // dependency is satisfied. Omitted on radioless targets.
-    wifi: { supported: true },
-    // DAC: the ESP32 has two 8-bit DAC channels on GPIO25 (channel 1) and GPIO26
-    // (channel 2). The Zephyr esp32 DAC driver (drivers/dac/dac_esp32.c) exposes
-    // them via the `dac0` node; the lowering emits dac_channel_setup +
-    // dac_write_value against DEVICE_DT_GET(DT_NODELABEL(dac0)). The overlay
-    // enables the node when the program uses dac.*. ESP32-S3 has no DAC.
-    dac: {
-        device: 'dac0',
-        channels: [
-            { pin: 25, channel: 1, resolution: 8 },
-            { pin: 26, channel: 2, resolution: 8 },
-        ],
-    },
-};

package/dist/chips/esp32s3.d.ts

@@ -1,2 +0,0 @@
-import type { ZephyrChipDescriptor } from './types.js';
-export declare const ESP32S3_DEVKITC: ZephyrChipDescriptor;