embeddedci 0.2.2__tar.gz → 0.2.3__tar.gz

embeddedci-0.2.3/.gitignore

@@ -0,0 +1,20 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.pytest_cache/
+
+# Build artifacts
+build/
+dist/
+
+# Virtualenvs
+.venv/
+venv/
+
+# ADC FFT capture outputs (scripts/adc_fft_capture.py)
+adc_capture_*.csv
+adc_capture_*.json
+adc_capture_*.png
+
+.DS_Store

embeddedci-0.2.3/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

{embeddedci-0.2.2 → embeddedci-0.2.3}/PKG-INFO

@@ -1,16 +1,16 @@
 Metadata-Version: 2.4
 Name: embeddedci
-Version: 0.2.2
+Version: 0.2.3
 Summary: BenchPod pytest client for EmbeddedCI hardware-in-the-loop testing
 Project-URL: Homepage, https://embeddedci.com
 Project-URL: Repository, https://github.com/embeddedci-com/embeddedci-python
 Project-URL: Issues, https://github.com/embeddedci-com/embeddedci-python/issues
 Author: EmbeddedCI
-License: Apache-2.0
+License-Expression: Apache-2.0
+License-File: LICENSE
 Keywords: benchpod,embedded,hardware-in-the-loop,openocd,pytest,swd
 Classifier: Development Status :: 3 - Alpha
 Classifier: Framework :: Pytest
-Classifier: License :: OSI Approved :: Apache Software License
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.9
@@ -21,11 +21,15 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Software Development :: Testing
 Requires-Python: >=3.9
 Requires-Dist: pyserial>=3.5
+Provides-Extra: analysis
+Requires-Dist: numpy>=1.21; extra == 'analysis'
 Provides-Extra: cloud
 Requires-Dist: websocket-client>=1.6; extra == 'cloud'
 Provides-Extra: dev
 Requires-Dist: pytest>=7.0; extra == 'dev'
 Requires-Dist: websocket-client>=1.6; extra == 'dev'
+Provides-Extra: discovery
+Requires-Dist: zeroconf>=0.131; extra == 'discovery'
 Description-Content-Type: text/markdown
 
 # embeddedci (BenchPod pytest library)
@@ -66,23 +70,22 @@ with benchpod.BenchPod("192.168.1.213") as bp:   # or "/dev/ttyACM0", or "serial
 pip install embeddedci
 # for the cloud (embeddedci:<device>) destination, add the cloud extra:
 pip install "embeddedci[cloud]"
+# optional: numpy-backed FFT helpers on captures (Capture.fft / dominant_frequency)
+pip install "embeddedci[analysis]"
 ```
 
 The `[cloud]` extra pulls in a WebSocket client used only by the `embeddedci:` destination;
-local wifi/serial use needs nothing extra.
+local wifi/serial use needs nothing extra. The `[analysis]` extra adds numpy for the FFT helpers
+— the mean/rms/peak-to-peak reductions are pure-Python and always available.
 
 ### OpenOCD (required for flashing)
 
-Flashing shells out to **OpenOCD**, which must be on your `PATH`. It drives the pod's SWD probe
-through OpenOCD's `remote_bitbang` adapter in **SWD** mode — and **SWD support for `remote_bitbang`
-only exists in OpenOCD *master* (post‑0.12.0)**. The stock packages (`apt install openocd`,
-`brew install open-ocd`) are **0.12.0**, whose `remote_bitbang` is `jtag_only`; flashing with them
-fails immediately:
-
-```
-Info : only one transport option; autoselect 'jtag'
-Error: Can't change session's transport after the initial selection was made
-```
+Flashing shells out to **OpenOCD**, which must be on your `PATH`. The pod runs a **CMSIS-DAP**
+processor locally; the library drives it through OpenOCD's `cmsis-dap` adapter using its **TCP
+backend** (`cmsis_dap_tcp`), shipping whole DAP transfers rather than per-bit toggles. That backend
+**only exists in OpenOCD *master* (post‑0.12.0)**. The stock packages (`apt install openocd`,
+`brew install open-ocd`) are **0.12.0** and lack it; flashing with them fails up front with a clear
+message.
 
 Install a master snapshot instead — the easiest is **xPack OpenOCD**:
 
@@ -92,11 +95,11 @@ npm install -g @xpack-dev-tools/openocd
 # or: https://github.com/xpack-dev-tools/openocd-xpack/releases  (extract, add bin/ to PATH)
 ```
 
-Verify your OpenOCD can do SWD over `remote_bitbang`:
+Verify your OpenOCD has the CMSIS-DAP TCP backend:
 
 ```bash
-openocd -c "adapter driver remote_bitbang" -c "transport list" -c "exit"
-# must list:  jtag  swd     (if only 'jtag', it's too old)
+openocd -c "adapter driver cmsis-dap" -c "cmsis-dap backend tcp" -c "exit"
+# must NOT error on the 'backend tcp' line (if it errors, the build is too old)
 ```
 
 ## Named constants (no magic numbers)
@@ -200,11 +203,113 @@ the **token request itself failed**.
 | Connect (wifi + serial) | ✅ |
 | Connect (cloud via GitHub OIDC) | ✅ server + SDK; device firmware tunnel pending on-hardware bring-up |
 | Power on/off (+ scheduled delay) | ✅ |
-| Flash + assert ok/not ok | ✅ (pure-Python OpenOCD `remote_bitbang` bridge) |
+| Flash + assert ok/not ok | ✅ (pure-Python OpenOCD `cmsis-dap` TCP bridge) |
 | Emulated I2C sensor (BMP280) | ✅ wifi + serial (serial via `json` console mode) |
 | I2C bus decode (`benchpod.i2c`) | ✅ START/STOP, R/W, ACK, register reads |
+| Protocol decode I2C / UART / SPI (`bp.decode`) | ✅ off-device, parity-checked vs the server |
 | UART capture (`capture_uart`) | ✅ wifi + serial |
-| Signal helpers (`capture`, `gpio_set`) | ✅ minimal, TCP transport only |
+| ADC scope capture → calibrated volts (`scope_capture`) | ✅ LAN + cloud tunnel |
+| Raw 12-ch LA capture (`capture_la`) | ✅ LAN + cloud tunnel |
+| Correlated ADC + LA capture (`capture_analog`) | ✅ one hardware trigger, aligned |
+| DAC generate / DC / replay (`generate`, `dac_set`, `replay`) | ✅ looping, concurrent-with-capture (gw v18) |
+| Cloud waveform library + replay (`bp.waveforms`, `replay_waveform`) | ✅ cloud (OIDC) or an API key on LAN (see below) |
+| DAC↔capture co-trigger + auto-stop (`replay(..., on_capture=True)`, `capture_*(stop_dac_after_us=…)`) | ✅ phase-locked to capture t0 (gw v27 / v21) |
+| Closed-loop DAC control — panel/MPPT emulator (`control_loop`, `loop_probe`) | ✅ needs the loop gateware image (`fpga_image`) |
+| Runtime gateware image swap (`fpga_image`) | ✅ loop ↔ deep-replay, no reflash |
+| Signal helpers (`la_step`) | ✅ minimal, TCP transport only |
+
+## Scope, logic analyzer, and DAC replay
+
+Every capture returns data with the scaling already applied — an ADC `scope_capture` gives you
+**calibrated volts** (the same affine front-end model the web UI uses), so you assert on real
+voltages, not raw counts. It all works over any transport: a LAN/serial pod **or** a cloud device
+over the byte tunnel.
+
+```python
+from embeddedci import benchpod
+
+with benchpod.BenchPod("embeddedci:my-bench") as bp:
+    # ADC scope — calibrated volts + summary helpers
+    cap = bp.scope_capture(4096, sample_rate_mhz=1)
+    assert 3.2 < cap.mean() < 3.4          # a 3.3 V rail
+    print(cap.rms(), cap.peak_to_peak(), cap.dominant_frequency())   # fft needs the [analysis] extra
+
+    # Raw logic analyzer + off-device decode (i2c / uart / spi)
+    la = bp.capture_la(8192, sample_rate_mhz=1)
+    txns = la.decode("i2c", sda=2, scl=1)
+    frames = bp.decode(la, "uart", rx=5, baud=115200)
+
+    # Correlated ADC + LA from one trigger (aligned timebases)
+    both = bp.capture_analog(adc_samples=2048, adc_rate_mhz=0.4, la_samples=2048, la_rate_mhz=1)
+
+    # DAC replay — loops until stopped, and (gateware v18) can run *while* you capture
+    with bp.replay(cap, dac_path="5v"):            # replay the captured waveform back out
+        alongside = bp.capture_la(8192, sample_rate_mhz=1)   # DAC + LA at the same time
+```
+
+`bp.replay(...)` accepts a `Capture` (its volts are replayed), a list of volts, or raw DAC codes
+(`are_codes=True`); `mapping="faithful"` reproduces the voltage (clipping outside the path range),
+`"fit"` auto-scales. Inject a fault with `fault=benchpod.Fault("flatline", start=…, width=…)`.
+
+### DAC ↔ capture co-trigger and auto-stop
+
+For a *deterministic* stimulus→response run, phase-lock the DAC to the capture instead of racing
+them from the host. `on_capture=True` arms the DAC to fire on the next capture's hardware t0, and
+`stop_dac_after_us=` cuts it at a sample-precise offset from that same t0:
+
+```python
+    # armed, not yet driving — the following capture starts it at t0 and cuts it at 2 ms
+    with bp.replay(cap, dac_path="5v", on_capture=True) as r:
+        assert r.cotrig                                    # device armed the co-trigger (gw v27)
+        a = bp.capture_analog(adc_samples=4096, adc_rate_mhz=0.4,
+                              la_samples=0, stop_dac_after_us=2000)   # DAC fires at t0, off at 2 ms
+```
+
+### Closed-loop DAC control (solar-panel / MPPT emulator)
+
+On the **loop gateware image**, the iCE40 runs a control loop in fabric: each tick it reads the ADC
+(a load "current"), looks it up in a panel I-V curve, damps and clamps, then drives the DAC — no
+host in the loop. Switch to that image with `fpga_image(0)` (deep-replay is `fpga_image(1)`):
+
+```python
+    if not bp.capabilities.dac_control_loop:
+        bp.fpga_image(0)                                   # swap to the loop image (~10 ms, no reflash)
+
+    curve = benchpod.build_panel_curve(voc_code=52000, sharpness=6)   # a solar panel I-V table
+    with bp.control_loop(curve=curve, vmax=52000) as loop:            # or voc_code=… to synthesise
+        pt = loop.probe()                                  # IVPoint(i=<ADC current>, v=<DAC voltage>)
+        print(pt.i, pt.v)
+```
+
+## Cloud waveform library (load + replay stored recordings)
+
+Save a captured waveform to the cloud library and replay it later — on this pod or another:
+
+```python
+with benchpod.BenchPod("embeddedci:my-bench", api_key="eci_…") as bp:
+    cap = bp.scope_capture(8192, sample_rate_mhz=0.4)
+    wf = bp.save_capture_as_recording(cap, "golden-startup")   # stored raw in S3
+
+    for w in bp.waveforms.list():
+        print(w.id, w.name, w.kind)
+
+    handle = bp.replay_waveform(wf.id, dac_path="5v", mapping="faithful")
+    ...
+    handle.stop()
+```
+
+> **Auth note.** The cloud waveform library and server-side replay carry the `benchpod:control`
+> capability. Over the cloud destination (`embeddedci:<device>`) the SDK reuses the connection's
+> session token — including the **GitHub Actions OIDC** token minted in CI — so no API key is
+> needed: a workflow that already drives the device can also load/save library waveforms and run
+> server-side replay, scoped to the devices/org the OIDC token is allowed to drive. On a
+> **LAN/serial** connection there is no session token, so pass an API key (`api_key=` /
+> `--benchpod-api-key` / `BENCHPOD_API_KEY`) to reach the shared library. Capture and direct
+> `replay(...)` never need one — they run over the device transport.
+
+In pytest, the `benchpod_waveforms` fixture gives you the library with automatic cleanup of
+anything created during the test, and `@pytest.mark.benchpod_capability("dac_deep_replay")` skips a
+test when the device doesn't advertise a capability.
 
 ## Emulated I2C sensor + UART capture (HIL)
 

{embeddedci-0.2.2 → embeddedci-0.2.3}/README.md

@@ -36,23 +36,22 @@ with benchpod.BenchPod("192.168.1.213") as bp:   # or "/dev/ttyACM0", or "serial
 pip install embeddedci
 # for the cloud (embeddedci:<device>) destination, add the cloud extra:
 pip install "embeddedci[cloud]"
+# optional: numpy-backed FFT helpers on captures (Capture.fft / dominant_frequency)
+pip install "embeddedci[analysis]"
 ```
 
 The `[cloud]` extra pulls in a WebSocket client used only by the `embeddedci:` destination;
-local wifi/serial use needs nothing extra.
+local wifi/serial use needs nothing extra. The `[analysis]` extra adds numpy for the FFT helpers
+— the mean/rms/peak-to-peak reductions are pure-Python and always available.
 
 ### OpenOCD (required for flashing)
 
-Flashing shells out to **OpenOCD**, which must be on your `PATH`. It drives the pod's SWD probe
-through OpenOCD's `remote_bitbang` adapter in **SWD** mode — and **SWD support for `remote_bitbang`
-only exists in OpenOCD *master* (post‑0.12.0)**. The stock packages (`apt install openocd`,
-`brew install open-ocd`) are **0.12.0**, whose `remote_bitbang` is `jtag_only`; flashing with them
-fails immediately:
-
-```
-Info : only one transport option; autoselect 'jtag'
-Error: Can't change session's transport after the initial selection was made
-```
+Flashing shells out to **OpenOCD**, which must be on your `PATH`. The pod runs a **CMSIS-DAP**
+processor locally; the library drives it through OpenOCD's `cmsis-dap` adapter using its **TCP
+backend** (`cmsis_dap_tcp`), shipping whole DAP transfers rather than per-bit toggles. That backend
+**only exists in OpenOCD *master* (post‑0.12.0)**. The stock packages (`apt install openocd`,
+`brew install open-ocd`) are **0.12.0** and lack it; flashing with them fails up front with a clear
+message.
 
 Install a master snapshot instead — the easiest is **xPack OpenOCD**:
 
@@ -62,11 +61,11 @@ npm install -g @xpack-dev-tools/openocd
 # or: https://github.com/xpack-dev-tools/openocd-xpack/releases  (extract, add bin/ to PATH)
 ```
 
-Verify your OpenOCD can do SWD over `remote_bitbang`:
+Verify your OpenOCD has the CMSIS-DAP TCP backend:
 
 ```bash
-openocd -c "adapter driver remote_bitbang" -c "transport list" -c "exit"
-# must list:  jtag  swd     (if only 'jtag', it's too old)
+openocd -c "adapter driver cmsis-dap" -c "cmsis-dap backend tcp" -c "exit"
+# must NOT error on the 'backend tcp' line (if it errors, the build is too old)
 ```
 
 ## Named constants (no magic numbers)
@@ -170,11 +169,113 @@ the **token request itself failed**.
 | Connect (wifi + serial) | ✅ |
 | Connect (cloud via GitHub OIDC) | ✅ server + SDK; device firmware tunnel pending on-hardware bring-up |
 | Power on/off (+ scheduled delay) | ✅ |
-| Flash + assert ok/not ok | ✅ (pure-Python OpenOCD `remote_bitbang` bridge) |
+| Flash + assert ok/not ok | ✅ (pure-Python OpenOCD `cmsis-dap` TCP bridge) |
 | Emulated I2C sensor (BMP280) | ✅ wifi + serial (serial via `json` console mode) |
 | I2C bus decode (`benchpod.i2c`) | ✅ START/STOP, R/W, ACK, register reads |
+| Protocol decode I2C / UART / SPI (`bp.decode`) | ✅ off-device, parity-checked vs the server |
 | UART capture (`capture_uart`) | ✅ wifi + serial |
-| Signal helpers (`capture`, `gpio_set`) | ✅ minimal, TCP transport only |
+| ADC scope capture → calibrated volts (`scope_capture`) | ✅ LAN + cloud tunnel |
+| Raw 12-ch LA capture (`capture_la`) | ✅ LAN + cloud tunnel |
+| Correlated ADC + LA capture (`capture_analog`) | ✅ one hardware trigger, aligned |
+| DAC generate / DC / replay (`generate`, `dac_set`, `replay`) | ✅ looping, concurrent-with-capture (gw v18) |
+| Cloud waveform library + replay (`bp.waveforms`, `replay_waveform`) | ✅ cloud (OIDC) or an API key on LAN (see below) |
+| DAC↔capture co-trigger + auto-stop (`replay(..., on_capture=True)`, `capture_*(stop_dac_after_us=…)`) | ✅ phase-locked to capture t0 (gw v27 / v21) |
+| Closed-loop DAC control — panel/MPPT emulator (`control_loop`, `loop_probe`) | ✅ needs the loop gateware image (`fpga_image`) |
+| Runtime gateware image swap (`fpga_image`) | ✅ loop ↔ deep-replay, no reflash |
+| Signal helpers (`la_step`) | ✅ minimal, TCP transport only |
+
+## Scope, logic analyzer, and DAC replay
+
+Every capture returns data with the scaling already applied — an ADC `scope_capture` gives you
+**calibrated volts** (the same affine front-end model the web UI uses), so you assert on real
+voltages, not raw counts. It all works over any transport: a LAN/serial pod **or** a cloud device
+over the byte tunnel.
+
+```python
+from embeddedci import benchpod
+
+with benchpod.BenchPod("embeddedci:my-bench") as bp:
+    # ADC scope — calibrated volts + summary helpers
+    cap = bp.scope_capture(4096, sample_rate_mhz=1)
+    assert 3.2 < cap.mean() < 3.4          # a 3.3 V rail
+    print(cap.rms(), cap.peak_to_peak(), cap.dominant_frequency())   # fft needs the [analysis] extra
+
+    # Raw logic analyzer + off-device decode (i2c / uart / spi)
+    la = bp.capture_la(8192, sample_rate_mhz=1)
+    txns = la.decode("i2c", sda=2, scl=1)
+    frames = bp.decode(la, "uart", rx=5, baud=115200)
+
+    # Correlated ADC + LA from one trigger (aligned timebases)
+    both = bp.capture_analog(adc_samples=2048, adc_rate_mhz=0.4, la_samples=2048, la_rate_mhz=1)
+
+    # DAC replay — loops until stopped, and (gateware v18) can run *while* you capture
+    with bp.replay(cap, dac_path="5v"):            # replay the captured waveform back out
+        alongside = bp.capture_la(8192, sample_rate_mhz=1)   # DAC + LA at the same time
+```
+
+`bp.replay(...)` accepts a `Capture` (its volts are replayed), a list of volts, or raw DAC codes
+(`are_codes=True`); `mapping="faithful"` reproduces the voltage (clipping outside the path range),
+`"fit"` auto-scales. Inject a fault with `fault=benchpod.Fault("flatline", start=…, width=…)`.
+
+### DAC ↔ capture co-trigger and auto-stop
+
+For a *deterministic* stimulus→response run, phase-lock the DAC to the capture instead of racing
+them from the host. `on_capture=True` arms the DAC to fire on the next capture's hardware t0, and
+`stop_dac_after_us=` cuts it at a sample-precise offset from that same t0:
+
+```python
+    # armed, not yet driving — the following capture starts it at t0 and cuts it at 2 ms
+    with bp.replay(cap, dac_path="5v", on_capture=True) as r:
+        assert r.cotrig                                    # device armed the co-trigger (gw v27)
+        a = bp.capture_analog(adc_samples=4096, adc_rate_mhz=0.4,
+                              la_samples=0, stop_dac_after_us=2000)   # DAC fires at t0, off at 2 ms
+```
+
+### Closed-loop DAC control (solar-panel / MPPT emulator)
+
+On the **loop gateware image**, the iCE40 runs a control loop in fabric: each tick it reads the ADC
+(a load "current"), looks it up in a panel I-V curve, damps and clamps, then drives the DAC — no
+host in the loop. Switch to that image with `fpga_image(0)` (deep-replay is `fpga_image(1)`):
+
+```python
+    if not bp.capabilities.dac_control_loop:
+        bp.fpga_image(0)                                   # swap to the loop image (~10 ms, no reflash)
+
+    curve = benchpod.build_panel_curve(voc_code=52000, sharpness=6)   # a solar panel I-V table
+    with bp.control_loop(curve=curve, vmax=52000) as loop:            # or voc_code=… to synthesise
+        pt = loop.probe()                                  # IVPoint(i=<ADC current>, v=<DAC voltage>)
+        print(pt.i, pt.v)
+```
+
+## Cloud waveform library (load + replay stored recordings)
+
+Save a captured waveform to the cloud library and replay it later — on this pod or another:
+
+```python
+with benchpod.BenchPod("embeddedci:my-bench", api_key="eci_…") as bp:
+    cap = bp.scope_capture(8192, sample_rate_mhz=0.4)
+    wf = bp.save_capture_as_recording(cap, "golden-startup")   # stored raw in S3
+
+    for w in bp.waveforms.list():
+        print(w.id, w.name, w.kind)
+
+    handle = bp.replay_waveform(wf.id, dac_path="5v", mapping="faithful")
+    ...
+    handle.stop()
+```
+
+> **Auth note.** The cloud waveform library and server-side replay carry the `benchpod:control`
+> capability. Over the cloud destination (`embeddedci:<device>`) the SDK reuses the connection's
+> session token — including the **GitHub Actions OIDC** token minted in CI — so no API key is
+> needed: a workflow that already drives the device can also load/save library waveforms and run
+> server-side replay, scoped to the devices/org the OIDC token is allowed to drive. On a
+> **LAN/serial** connection there is no session token, so pass an API key (`api_key=` /
+> `--benchpod-api-key` / `BENCHPOD_API_KEY`) to reach the shared library. Capture and direct
+> `replay(...)` never need one — they run over the device transport.
+
+In pytest, the `benchpod_waveforms` fixture gives you the library with automatic cleanup of
+anything created during the test, and `@pytest.mark.benchpod_capability("dac_deep_replay")` skips a
+test when the device doesn't advertise a capability.
 
 ## Emulated I2C sensor + UART capture (HIL)
 

{embeddedci-0.2.2 → embeddedci-0.2.3}/docs/event-uart-design.md

@@ -135,7 +135,7 @@ backward-compatible.
   `command.request`/`command.response`) instead of dialing a second byte tunnel.
   The firmware services the command channel (`CH_CLOUD_CONN`) and the byte tunnel
   (`CH_CLOUD_TUNNEL_CONN`) as independent connections and announces
-  `"command":true` in its capabilities, so `power_on`/`power_off`/`gpio_set`/etc.
+  `"command":true` in its capabilities, so `power_on`/`power_off`/`la`/etc.
   run *while* `uart_proxy_start` holds the tunnel. Streaming modes
   (`dap_start`/`uart_proxy_start`) still use the tunnel via `_dial`. This both
   removes the two-concurrent-tunnels requirement and makes every command faster

{embeddedci-0.2.2 → embeddedci-0.2.3}/pyproject.toml

@@ -4,17 +4,17 @@ build-backend = "hatchling.build"
 
 [project]
 name = "embeddedci"
-version = "0.2.2"
+version = "0.2.3"
 description = "BenchPod pytest client for EmbeddedCI hardware-in-the-loop testing"
 readme = "README.md"
 requires-python = ">=3.9"
-license = { text = "Apache-2.0" }
+license = "Apache-2.0"
+license-files = ["LICENSE"]
 authors = [{ name = "EmbeddedCI" }]
 keywords = ["embedded", "hardware-in-the-loop", "pytest", "benchpod", "swd", "openocd"]
 classifiers = [
     "Development Status :: 3 - Alpha",
     "Framework :: Pytest",
-    "License :: OSI Approved :: Apache Software License",
     "Operating System :: OS Independent",
     "Programming Language :: Python :: 3",
     "Programming Language :: Python :: 3.9",
@@ -33,6 +33,12 @@ dev = ["pytest>=7.0", "websocket-client>=1.6"]
 # Cloud destination (embeddedci:<device>): a synchronous WebSocket client for the byte tunnel.
 # OIDC mint + token exchange use the stdlib (urllib), so no extra HTTP dependency is needed.
 cloud = ["websocket-client>=1.6"]
+# LAN auto-discovery (connection="discover" / --benchpod-discover): browse mDNS for pods.
+# Kept optional so headless CI (cloud/explicit path, multicast often blocked) stays lean.
+discovery = ["zeroconf>=0.131"]
+# Signal analysis helpers on capture results (Capture.fft / dominant_frequency). The core
+# reductions (mean/rms/peak-to-peak) are pure-Python and need no extra; only the FFT uses numpy.
+analysis = ["numpy>=1.21"]
 
 [project.entry-points.pytest11]
 benchpod = "embeddedci.benchpod.pytest_plugin"