embeddedci 3.0.0__tar.gz → 3.0.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (191) hide show
  1. {embeddedci-3.0.0 → embeddedci-3.0.2}/CHANGELOG.md +53 -0
  2. {embeddedci-3.0.0 → embeddedci-3.0.2}/PKG-INFO +101 -22
  3. {embeddedci-3.0.0 → embeddedci-3.0.2}/README.md +100 -21
  4. {embeddedci-3.0.0 → embeddedci-3.0.2}/pyproject.toml +1 -1
  5. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/__init__.py +4 -1
  6. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/capabilities.py +61 -1
  7. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/client.py +242 -32
  8. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/errors.py +5 -4
  9. embeddedci-3.0.2/src/embeddedci/benchpod/feature_map.json +641 -0
  10. embeddedci-3.0.2/src/embeddedci/benchpod/feature_map.py +112 -0
  11. embeddedci-3.0.2/src/embeddedci/benchpod/header.py +142 -0
  12. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/transport/base.py +14 -2
  13. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/transport/serial.py +14 -1
  14. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/transport/tcp.py +16 -1
  15. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/uart.py +48 -0
  16. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/wiring.py +37 -4
  17. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/api_surface.json +28 -4
  18. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/conftest.py +5 -1
  19. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_e2e_cloud.py +15 -4
  20. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_e2e_rev3.py +2 -1
  21. embeddedci-3.0.2/tests/test_feature_map.py +143 -0
  22. embeddedci-3.0.2/tests/test_header.py +83 -0
  23. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_image_switching.py +50 -0
  24. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_refusal_errors.py +4 -3
  25. embeddedci-3.0.2/tests/test_status_diag.py +124 -0
  26. embeddedci-3.0.2/tests/test_uart_de.py +102 -0
  27. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_uart_frame.py +17 -2
  28. embeddedci-3.0.2/tests/test_uart_half_duplex.py +90 -0
  29. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_wiring_profiles.py +57 -0
  30. {embeddedci-3.0.0 → embeddedci-3.0.2}/.gitignore +0 -0
  31. {embeddedci-3.0.0 → embeddedci-3.0.2}/LICENSE +0 -0
  32. {embeddedci-3.0.0 → embeddedci-3.0.2}/docs/aivision.md +0 -0
  33. {embeddedci-3.0.0 → embeddedci-3.0.2}/docs/event-uart-design.md +0 -0
  34. {embeddedci-3.0.0 → embeddedci-3.0.2}/examples/README.md +0 -0
  35. {embeddedci-3.0.0 → embeddedci-3.0.2}/examples/test_bmp280.py +0 -0
  36. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/__init__.py +0 -0
  37. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/_http.py +0 -0
  38. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/aivision/__init__.py +0 -0
  39. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/aivision/client.py +0 -0
  40. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/aivision/cloud.py +0 -0
  41. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/aivision/discovery.py +0 -0
  42. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/aivision/errors.py +0 -0
  43. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/aivision/pytest_plugin.py +0 -0
  44. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/aivision/results.py +0 -0
  45. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/can.py +0 -0
  46. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/capture.py +0 -0
  47. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/ci.py +0 -0
  48. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/cli_config.py +0 -0
  49. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/cli_login.py +0 -0
  50. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/cloud_auth.py +0 -0
  51. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/connection.py +0 -0
  52. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/constants.py +0 -0
  53. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/control_loop.py +0 -0
  54. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/decode.py +0 -0
  55. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/discovery.py +0 -0
  56. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/dsp.py +0 -0
  57. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/error_catalog.json +0 -0
  58. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/esp.py +0 -0
  59. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/expansion.py +0 -0
  60. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/flash.py +0 -0
  61. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/gpio.py +0 -0
  62. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/i2c.py +0 -0
  63. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/i2c_master.py +0 -0
  64. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/lease.py +0 -0
  65. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/lowlevel.py +0 -0
  66. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/main.c +0 -0
  67. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/motor_emulator.py +0 -0
  68. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/power.py +0 -0
  69. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/protocol.py +0 -0
  70. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/pytest_plugin.py +0 -0
  71. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/replay.py +0 -0
  72. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/results.py +0 -0
  73. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/__init__.py +0 -0
  74. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/README.md +0 -0
  75. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/docs/format.md +0 -0
  76. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/library.json +0 -0
  77. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/analog/ntc_10k_divider.yaml +0 -0
  78. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/analog/pressure_4_20ma.yaml +0 -0
  79. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/bme280.yaml +0 -0
  80. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/bmp280.yaml +0 -0
  81. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/ina219.yaml +0 -0
  82. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/mpu6050.yaml +0 -0
  83. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/scd4x.yaml +0 -0
  84. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/sht3x.yaml +0 -0
  85. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/sht4x.yaml +0 -0
  86. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/tmp117.yaml +0 -0
  87. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/spi/lis3dh.yaml +0 -0
  88. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/spi/lis3dh_fifo.yaml +0 -0
  89. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/uart/gps_nmea.yaml +0 -0
  90. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/sensors/uart/mhz19b.yaml +0 -0
  91. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/stimuli/gps_drive.yaml +0 -0
  92. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/stimuli/pressure_drop.yaml +0 -0
  93. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/bundled/stimuli/temperature_ramp_fault.yaml +0 -0
  94. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/definition.py +0 -0
  95. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/emulation.py +0 -0
  96. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/library.py +0 -0
  97. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/sensors/yaml12.py +0 -0
  98. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/server_api.py +0 -0
  99. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/spi.py +0 -0
  100. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/state.py +0 -0
  101. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/transport/__init__.py +0 -0
  102. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/transport/cloud.py +0 -0
  103. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/transport/tls.py +0 -0
  104. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/transport/usblink.py +0 -0
  105. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/benchpod/waveforms.py +0 -0
  106. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/py.typed +0 -0
  107. {embeddedci-3.0.0 → embeddedci-3.0.2}/src/embeddedci/upload_build.py +0 -0
  108. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/conftest.py +0 -0
  109. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/README.md +0 -0
  110. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/e2e_bench.py +0 -0
  111. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/e2e_helpers.py +0 -0
  112. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_bench_profile.py +0 -0
  113. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_e2e_digital.py +0 -0
  114. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_e2e_dut.py +0 -0
  115. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_e2e_gpio.py +0 -0
  116. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_e2e_la13_14.py +0 -0
  117. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_e2e_pod.py +0 -0
  118. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_e2e_spi.py +0 -0
  119. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/e2e/test_e2e_usb.py +0 -0
  120. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/examples/test_bmp280_hil.py +0 -0
  121. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/examples/test_can_ecu_demo.py +0 -0
  122. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/examples/test_can_loopback_hil.py +0 -0
  123. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/examples/test_smoke.py +0 -0
  124. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_adc_fft_hw.py +0 -0
  125. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_adc_oversample.py +0 -0
  126. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_adc_range.py +0 -0
  127. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_aivision.py +0 -0
  128. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_aivision_cloud.py +0 -0
  129. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_aivision_live.py +0 -0
  130. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_api_surface.py +0 -0
  131. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_can.py +0 -0
  132. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_capabilities.py +0 -0
  133. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_capabilities_scope.py +0 -0
  134. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_capture.py +0 -0
  135. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_capture_replay_hw.py +0 -0
  136. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_ci.py +0 -0
  137. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_client_v2.py +0 -0
  138. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_cloud.py +0 -0
  139. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_connection.py +0 -0
  140. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_control_loop.py +0 -0
  141. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_control_loop_hw.py +0 -0
  142. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_current_out_waveforms.py +0 -0
  143. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_dac_limits_fixture.py +0 -0
  144. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_dac_path_default.py +0 -0
  145. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_dac_path_ranges.py +0 -0
  146. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_decode.py +0 -0
  147. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_decode_parity.py +0 -0
  148. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_docs_coverage.py +0 -0
  149. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_dsp.py +0 -0
  150. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_esp_flash.py +0 -0
  151. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_expansion.py +0 -0
  152. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_flash_bridge.py +0 -0
  153. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_flash_build.py +0 -0
  154. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_generate16.py +0 -0
  155. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_gpio.py +0 -0
  156. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_http_redirect_auth.py +0 -0
  157. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_i2c_decode.py +0 -0
  158. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_i2c_master.py +0 -0
  159. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_i2c_parity.py +0 -0
  160. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_i2c_timed.py +0 -0
  161. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_integration.py +0 -0
  162. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_la_voltage_fixture.py +0 -0
  163. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_lan_tls.py +0 -0
  164. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_lease.py +0 -0
  165. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_module.py +0 -0
  166. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_motor_emulator.py +0 -0
  167. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_one_source.py +0 -0
  168. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_pin_directions.py +0 -0
  169. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_pins_bias.py +0 -0
  170. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_protocol.py +0 -0
  171. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_replay.py +0 -0
  172. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_sensor_library.py +0 -0
  173. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_sensors.py +0 -0
  174. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_serial_autodetect.py +0 -0
  175. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_serial_text_console.py +0 -0
  176. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_spi.py +0 -0
  177. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_tcp_transport.py +0 -0
  178. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_timed_power.py +0 -0
  179. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_timing.py +0 -0
  180. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_transport_failures.py +0 -0
  181. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_trigger_power.py +0 -0
  182. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_uart_capture.py +0 -0
  183. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_uart_session.py +0 -0
  184. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_unsupported_feature.py +0 -0
  185. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_upload_build.py +0 -0
  186. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_usb_net.py +0 -0
  187. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_waveforms.py +0 -0
  188. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/test_wiring.py +0 -0
  189. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/testdata/i2c_decode_vectors.json +0 -0
  190. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/testdata/spi_decode_vectors.json +0 -0
  191. {embeddedci-3.0.0 → embeddedci-3.0.2}/tests/testdata/uart_decode_vectors.json +0 -0
@@ -1,5 +1,58 @@
1
1
  # Changelog — `embeddedci`
2
2
 
3
+ ## 3.0.2
4
+
5
+ - **The profile on the pod's header:** `BenchPod.board_header()` says which I/O header the pod has
6
+ (`"j1"`, the 2x11 pin headers up to v3-r2, or `"front"`, the 2x13 front connector of digital v3r3
7
+ and later; asked once per connection with the read-only `module` command), and
8
+ `header_map(wiring, header)` writes the profile on it as text: every pin in its place, then what
9
+ to connect to it.
10
+ - **UART frame in the wiring profile:** `Wiring.uart_parity` (`"none"`, `"even"`, `"odd"`) and
11
+ `Wiring.uart_stop_bits` (1, 2), next to `uart_baud`. `open_uart`, `capture_uart` and
12
+ `power_cycle_and_capture` take them from the profile when `parity` / `stop_bits` are omitted
13
+ (8N1 unless the profile says otherwise). The web app and the desktop app set them in Pins.
14
+ - `flash(target="esp32...")` switches the FPGA to the deep-replay image before staging the image,
15
+ so a pod left on the emulation or loop image no longer refuses with `load_bin: deep replay is
16
+ not in the emulation image`.
17
+ - **One-wire UART and boot-mode entry:** `open_uart` and `capture_uart` take `half_duplex=True`
18
+ (rx and tx on one LA pin; the pod only pulls the line low and does not read back its own bytes)
19
+ and `entry=UartEntry(...)`, a reset with TX held low, its release and the first bytes, all timed
20
+ on the pod. Needs gateware v57 (capability `uart_hd`); the entry also needs the reset pin.
21
+ - **RS-485 direction driven by the pod:** `open_uart` and `capture_uart` take `de=` (the LA channel
22
+ on a transceiver's DE + /RE) and `de_active_low=`. The pod switches DE itself, from before the
23
+ first start bit to the end of the last stop bit, so a device that answers within a millisecond
24
+ is heard (DE switched from the host with GPIO calls drops about 25 ms after the request over
25
+ LAN). Needs gateware v58 (feature `uart_de`, features table revision 2).
26
+
27
+ - **Features from the firmware's features table:** the SDK ships benchpod-firmware's
28
+ `features/features.json` (`embeddedci.benchpod.feature_map`) and reads the pod's status with
29
+ `"caps":false`. Firmware after 3.10.10 answers with `features_rev` instead of its `caps` list,
30
+ and `Capabilities` takes the features from the table (`capabilities.features`,
31
+ `capabilities.fpga_image`, `Capabilities.has()`); older firmware sends its list as before.
32
+ `bp.supports()` also takes table names without a flag of their own (`"la_dir"`, `"i2c_master"`,
33
+ `"diag"`, ...). A pod whose firmware has a newer table than the SDK logs one warning to update it.
34
+
35
+ ## 3.0.1
36
+
37
+ - **Pull resistors in the wiring profile:** `Wiring.pulls` lists the LA channels whose pull
38
+ resistor is on (`{"pulls": [1, 2]}`). `power_on()` switches exactly those on and the others off,
39
+ after the I/O voltage and before the rail; at 1.8 V, over the serial console, or without the key
40
+ it leaves them alone. The LA7/LA8 pull-down warnings only fire while that pull-down may be on.
41
+ - **The I/O voltage comes from the profile:** on connect the SDK sets the pod's I/O voltage from
42
+ the pod's profile (`la_mv`) when the pod has none (no extra reads, never fails the connection,
43
+ never changes a voltage the pod has). Firmware 3.10.10+ also takes it from the profile itself on
44
+ the first LA operation. `la voltage not set` now says the profile sets no voltage and how to set
45
+ it there.
46
+ - A pin's direction follows from what it is used for (a signal's `direction`); `dut_dirs` is still
47
+ honored for older profiles, but the web and desktop editors no longer write it.
48
+ - `bp.diag()`: the pod's heap, per-task stacks, network-stack and console counters. Firmware 3.10.9
49
+ moved them from `status` to the new `diag` command, so the full status keeps room under the
50
+ 2047 bytes a LAN connection takes in one reply; with older firmware `diag()` reads them from
51
+ `status`.
52
+ - When a LAN or USB-network status comes back as the short form (the full one did not fit the
53
+ connection), the SDK reads it once more and, when it is still short, logs a warning: the ADC
54
+ calibration and feature flags then come from embeddedci.com, else the board's defaults.
55
+
3
56
  ## 3.0.0
4
57
 
5
58
  A major release: wiring profiles live on the pod, nothing is wired by default, and refusals carry
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: embeddedci
3
- Version: 3.0.0
3
+ Version: 3.0.2
4
4
  Summary: BenchPod SDK and pytest plugin for EmbeddedCI hardware-in-the-loop testing
5
5
  Project-URL: Homepage, https://embeddedci.com
6
6
  Project-URL: Repository, https://github.com/embeddedci-com/embeddedci-python
@@ -196,15 +196,20 @@ with BenchPod("192.168.1.213", la_voltage=3.3) as bp:
196
196
  bp.power_on(INTERNAL)
197
197
  ```
198
198
 
199
- `BenchPod` is a context manager; `close()` is idempotent. `la_voltage` (1.8 or 3.3) selects the
200
- **LA I/O-bank voltage** right after connecting — match it to the DUT's I/O voltage. The pod refuses
201
- every LA-bank operation (flashing, UART, LA capture, pull resistors, sensor emulation) until one
202
- is selected. You can also call `bp.set_la_voltage(3.3)` later; `bp.get_la_voltage()` returns a
203
- `LaVoltage` whose `voltage` is `None` until one is chosen. 1.8 V needs a rev3 pod. Until then a
204
- refused command raises `FirmwareError` with the message `la voltage not set; set the board's I/O
205
- voltage first: BenchPod(conn, la_voltage=3.3) (1.8 for a 1.8 V target), the benchpod_la_voltage
206
- fixture in conftest.py, or bp.set_la_voltage(3.3)` (prefixed with the command, as every
207
- `FirmwareError` is).
199
+ `BenchPod` is a context manager; `close()` is idempotent.
200
+
201
+ **The I/O voltage comes from the wiring profile.** The pod refuses every LA-bank operation
202
+ (flashing, UART, LA capture, pull resistors, sensor emulation) until its LA I/O-bank voltage is
203
+ selected, and it forgets it on every reboot. The profile's `la_mv` (`3300` or `1800`, the board's
204
+ I/O voltage) fills it in: on connect the SDK sets it from the pod's profile when the pod has none,
205
+ and firmware 3.10.10+ takes it from the active profile itself on the first LA operation. So a
206
+ profile that sets its I/O voltage needs nothing else. `la_voltage` (1.8 or 3.3) still sets it right
207
+ after connecting for this session, and `bp.set_la_voltage(3.3)` at any time; `bp.get_la_voltage()`
208
+ returns a `LaVoltage` whose `voltage` is `None` until one is chosen. 1.8 V needs a rev3 pod. With
209
+ no voltage anywhere, a refused command raises `FirmwareError` with the message `la voltage not set;
210
+ the wiring profile sets no I/O voltage: set la_mv in it (bp.save_wiring(bp.wiring.with_changes(la_mv=3300)),
211
+ 1800 for a 1.8 V board), or pass BenchPod(conn, la_voltage=3.3), or call bp.set_la_voltage(3.3)`
212
+ (prefixed with the command, as every `FirmwareError` is).
208
213
 
209
214
  Other constructor arguments: `timeout` (seconds, default 30), `api_key`, `api_base`,
210
215
  `cloud_token`, `cloud_audience`, `cloud_user_token`, `lease`, `lease_wait`, `lease_ttl` (see [Cloud](#cloud-embeddedcidevice-name)),
@@ -410,7 +415,18 @@ properties `can_gpio`, `can_trigger`, `can_spi`, `can_profile_power`, `can_calib
410
415
  `can_current_out`, `can_reset_target` and `can_analog` name the common ones (`can_config` …
411
416
  `can_disable` stay the CAN bus commands). A call the pod cannot serve raises
412
417
  `UnsupportedFeatureError` (see [Errors](#errors)), before anything is sent when the capabilities
413
- already say so:
418
+ already say so.
419
+
420
+ Where those come from: firmware after 3.10.10 no longer lists its features. The SDK asks for its
421
+ `status` without the list (`"caps":false`) and gets `capabilities.features_rev`, the revision of
422
+ the features table the firmware is built from, plus the running image (`capabilities.fpga_image`)
423
+ and a few hardware facts. The SDK ships that table (`embeddedci.benchpod.feature_map`, a copy of
424
+ benchpod-firmware's `features/features.json`), so this needs no network: `capabilities.features`
425
+ is every feature the table gives the pod, and `bp.supports()` also takes table names without a
426
+ flag of their own (`"la_dir"`, `"i2c_master"`, `"diag"`, `"wiring_store"`, ...). Older firmware
427
+ sends its list as before and gets the same answers. A pod with a higher `features_rev` than the
428
+ SDK knows logs a warning once: update the SDK (`pip install -U embeddedci`) to use those features.
429
+
414
430
 
415
431
  ```python
416
432
  import pytest
@@ -430,9 +446,10 @@ has a complete old → new table.
430
446
 
431
447
  ## pytest plugin
432
448
 
433
- Installing the package registers a pytest plugin (options, fixtures and markers). Set the board's
434
- I/O voltage **once** for the whole suite in `conftest.py` — the pod refuses flashing, UART, LA
435
- capture, pull resistors and sensor emulation until an LA bank voltage is selected:
449
+ Installing the package registers a pytest plugin (options, fixtures and markers). The board's I/O
450
+ voltage normally comes from the pod's wiring profile (`la_mv`); when the profile sets none, or a
451
+ suite must not depend on it, set it **once** for the whole suite in `conftest.py`. The pod refuses
452
+ flashing, UART, LA capture, pull resistors and sensor emulation until a voltage is selected:
436
453
 
437
454
  ```python
438
455
  # conftest.py
@@ -593,6 +610,7 @@ print(wiring.describe()) # a pin table: bias resistor and
593
610
  | `la_mv` | not set | LA I/O-bank voltage in mV (1800 or 3300); `wiring.la_voltage` in volts |
594
611
  | `efuse` | not set (pass `efuse=`) | target-power rail: 1 internal 5 V, 2 external |
595
612
  | `uart_rx`, `uart_tx`, `uart_baud` | not wired, not wired, `115200` | `rx` samples the DUT's TX; `tx` drives the DUT's RX |
613
+ | `uart_parity`, `uart_stop_bits` | `"none"`, `1` | The UART frame after the 8 data bits (`"even"`, `"odd"`; 2 stop bits). `open_uart`, `capture_uart` and `power_cycle_and_capture` use it when `parity` / `stop_bits` are omitted; anything but 8N1 needs firmware 3.10.8+ |
596
614
  | `i2c_sda`, `i2c_scl`, `i2c_addr` | not wired, not wired, not set | the I2C bus (emulated sensors default to it; put I2C on LA1-LA6, which have pull-ups) |
597
615
  | `swd_swclk`, `swd_swdio`, `swd_nreset`, `swd_target` | not wired, not wired, `False`, `""` (auto-detect) | flashing |
598
616
  | `spi_sclk`, `spi_mosi`, `spi_miso`, `spi_cs` | not wired | decoder channels |
@@ -658,8 +676,11 @@ pod's bus; reading never touches it. Firmware that stores no profiles: `save_wir
658
676
  cloud device's single profile on embeddedci.com, and raises over the LAN or USB.
659
677
 
660
678
  **Power-on applies the profile.** `bp.power_on()` (or `bp.power_on(wiring_profile="k66")`) sets the
661
- profile's I/O voltage when the pod has none or another one, then switches the profile's rail on and
662
- records on the pod which profile powered the board (`target_status`). It never changes the I/O
679
+ profile's I/O voltage when the pod has none or another one, sets its pull resistors, then switches
680
+ the profile's rail on and records on the pod which profile powered the board (`target_status`).
681
+ `Wiring.pulls` lists the LA channels whose pull resistor is on (`{"pulls": [1, 2]}` in the JSON):
682
+ `power_on` switches exactly those on and the others off. They work at 3.3 V only, so at 1.8 V nothing
683
+ is sent, and a profile without `pulls` (`None`) leaves them as they are. It never changes the I/O
663
684
  voltage under a board that is already powered: that raises, and `bp.set_la_voltage()` does it if you
664
685
  mean it.
665
686
 
@@ -673,6 +694,19 @@ A file holds the same JSON object the pod stores:
673
694
  `bp.signal(name)` returns a GPIO handle for a signal (see [GPIO on the LA pins](#gpio-on-the-la-pins));
674
695
  channel arguments accept a role or signal name too (`bp.open_uart(rx="uart_rx", tx=4)`).
675
696
 
697
+ **The profile on the pod's header.** `bp.board_header()` says which I/O header the pod has:
698
+ `"j1"` (the 2x11 pin headers of the one-piece boards up to v3-r2) or `"front"` (the 2x13 connector
699
+ on the front of digital v3r3 and later), None when the pod cannot tell. `header_map(wiring, header)`
700
+ writes the profile on that header as text: every pin in its physical place, then what to connect
701
+ to each pin on your board (header None writes both headers). The web and desktop apps draw the same
702
+ thing from the Pins pane's Visualize button.
703
+
704
+ ```python
705
+ from embeddedci.benchpod import header_map
706
+
707
+ print(header_map(bp.wiring, bp.board_header()))
708
+ ```
709
+
676
710
  ## Power, reset and power monitoring
677
711
 
678
712
  ```python
@@ -996,12 +1030,53 @@ The LA pins are 1.8 V or 3.3 V only: the pod has no 5 V I/O and no RS-485 port.
996
1030
  level shifter, and Modbus RTU on RS-485 an external RS-485 transceiver powered at 3.3 V (or a 5 V
997
1031
  transceiver behind a level shifter), between the pod and the device.
998
1032
 
1033
+ **One wire (half duplex).** Some parts talk UART on a single pin, for example a boot ROM's
1034
+ programming pin. `half_duplex=True` runs the session on `rx` alone (`tx` defaults to the same
1035
+ channel): the pod only pulls the line low and lets the pull-up hold it high, so the device answers
1036
+ on the same wire, and the pod does not read back its own bytes. Use LA1 to LA6, whose pull-up the
1037
+ pod turns on for the session, or a pull-up on the board.
1038
+
1039
+ **Boot-mode entry.** A boot ROM that picks its mode from the UART pin at reset needs the pin held
1040
+ low while the chip leaves reset, then a byte soon after. `entry=UartEntry(...)` has the pod run that
1041
+ sequence before the session starts, timed on the pod so no network delay sits in between: TX
1042
+ low (`tx_low`), reset for `reset_ms`, release, wait `hold_ms`, release TX, wait `idle_ms`, then send
1043
+ `data` (at most 32 bytes). Times are whole milliseconds, 0 to 1000:
1044
+
1045
+ ```python
1046
+ from embeddedci.benchpod import UartEntry
1047
+
1048
+ entry = UartEntry(reset_ms=5, hold_ms=3, idle_ms=2, data=b"\x00")
1049
+ with bp.open_uart(rx=PIN3, half_duplex=True, entry=entry, encoding="latin-1") as uart:
1050
+ reply = uart.read(timeout=0.5)
1051
+ ```
1052
+
1053
+ Both need gateware v57 (`bp.supports("uart_hd")`), and `entry` also the pod's reset pin
1054
+ (`bp.supports("nrst_pin")`); older pods raise `UnsupportedFeatureError` before anything is sent.
1055
+ The USB console has neither.
1056
+
999
1057
  **Binary protocols.** A session decodes what it receives as UTF-8, which suits a console. For bytes
1000
1058
  that are not text (a binary protocol's frames), open it with `encoding="latin-1"`: every byte is one
1001
1059
  character, so `uart.read().encode("latin-1")` gives the bytes back unchanged, and a `bytes` write is
1002
1060
  sent as is. For the adapter wiring and a Modbus RTU test through a transceiver, see
1003
1061
  [5 V logic and RS-485](https://www.embeddedci.com/docs/benchpod-targets/5v-rs485).
1004
1062
 
1063
+ **RS-485 direction (DE).** A half-duplex RS-485 transceiver sends while its DE (tied to /RE) is
1064
+ high and listens while it is low. `de=` names the LA channel wired to DE, and the pod switches it
1065
+ itself: high from before the first start bit of what it sends to the end of the last stop bit, low
1066
+ otherwise. Nothing on the host times it, so a device that answers within a millisecond is still
1067
+ heard (switching DE with `gpio` calls from the host takes tens of milliseconds over the network,
1068
+ and the reply of a fast device is lost meanwhile). `de_active_low=True` inverts it:
1069
+
1070
+ ```python
1071
+ with bp.open_uart(rx=PIN5, tx=PIN4, de=PIN9, baud=19200, parity="even",
1072
+ encoding="latin-1") as uart:
1073
+ uart.write(request) # DE goes high and low with the bytes
1074
+ reply = uart.read(timeout=0.2)
1075
+ ```
1076
+
1077
+ `de` needs gateware v58 (`bp.supports("uart_de")`); older pods raise `UnsupportedFeatureError`
1078
+ before anything is sent. The USB console has no DE.
1079
+
1005
1080
  ## LA bias resistors
1006
1081
 
1007
1082
  Eight LA channels carry a fixed, switchable bias resistor. They are referenced to 3V3, so the pod
@@ -1111,10 +1186,13 @@ sends them again.
1111
1186
  Every wired role and signal has a direction. The defaults: `uart_rx` and `spi_miso` are DUT
1112
1187
  outputs (the DUT drives them); `uart_tx`, `spi_sclk`, `spi_mosi`, `spi_cs` and `swd_swclk` DUT
1113
1188
  inputs; the I2C pins and `swd_swdio` `bidir`; a signal with direction `input` (the pod watches it)
1114
- is a DUT output, `output` a DUT input, `open_drain` and `bidir` are `bidir`. The profile's
1115
- `dut_dirs` overrides any of them (`wiring.dut_dir(name)` is one role's or signal's direction,
1116
- `wiring.pin_dut_dirs()` the per-channel map). Note the point of view: `la_dir` and `dut_dirs`
1117
- describe the DUT's signal, while a signal's `direction` is seen from the pod.
1189
+ is a DUT output, `output` a DUT input, `open_drain` and `bidir` are `bidir`. So a pin's direction
1190
+ follows from what it is used for: set a signal's `direction` to change it. `wiring.dut_dir(name)` is
1191
+ one role's or signal's direction, `wiring.pin_dut_dirs()` the per-channel map. Profiles from older
1192
+ versions may carry `dut_dirs` (role key or signal name -> `dut_input`, `dut_output`, `bidir`), which
1193
+ still overrides the defaults; the web and desktop editors no longer write it. Note the point of
1194
+ view: `la_dir` and `dut_dirs` describe the DUT's signal, while a signal's `direction` is seen from the
1195
+ pod.
1118
1196
  `LaPinState.dir` is a pin's direction (`None` when unknown), and `LaPinState.warn` holds warning
1119
1197
  bits that `LaPinState.warnings` spells out: a pull-up under a push-pull output, and a pin driven high
1120
1198
  or pulled up while the target power is off (it powers an unpowered DUT through its I/O pins).
@@ -2235,7 +2313,7 @@ lease_wait=600.0, lease_ttl=120, wiring=None)`. A context manager; `close()` is
2235
2313
 
2236
2314
  | Area | Methods and properties |
2237
2315
  |---|---|
2238
- | Connection and device | `ping()`, `status()`, `mac_addresses(status=None)` (the Ethernet and Wi-Fi MACs, see [MAC addresses](#mac-addresses-managed-networks)), `capabilities`, `refresh_capabilities()` (drop the cached capabilities and read them again), `close()`, `leased` (true while this client holds the cloud lease), `wiring`, `save_wiring(wiring=None)` (store a cloud device's profile on embeddedci.com), `signal(name)`, `fpga_image(image)`, `usb_cc()`, `usb_network(on=None)` (the USB network setting; `False` turns the adapter off over the USB link), `lan_tls()`, `set_lan_tls_https_only(on)`, `regenerate_lan_tls()`, `set_lan_tls_cert(cert_pem, key_pem)` (the LAN API over TLS, see [TLS on the LAN](#tls-on-the-lan)) |
2316
+ | Connection and device | `ping()`, `status()`, `diag()` (heap, per-task stacks, network-stack and console counters: the `diag` command on firmware 3.10.9+, else the full `status`), `mac_addresses(status=None)` (the Ethernet and Wi-Fi MACs, see [MAC addresses](#mac-addresses-managed-networks)), `capabilities`, `refresh_capabilities()` (drop the cached capabilities and read them again), `close()`, `leased` (true while this client holds the cloud lease), `wiring`, `save_wiring(wiring=None, name=None)` (store a wiring profile on the pod; firmware before 3.10.8: on embeddedci.com), `signal(name)`, `fpga_image(image)`, `usb_cc()`, `usb_network(on=None)` (the USB network setting; `False` turns the adapter off over the USB link), `lan_tls()`, `set_lan_tls_https_only(on)`, `regenerate_lan_tls()`, `set_lan_tls_cert(cert_pem, key_pem)` (the LAN API over TLS, see [TLS on the LAN](#tls-on-the-lan)) |
2239
2317
  | LA voltage | `set_la_voltage(volts)`, `get_la_voltage()` |
2240
2318
  | Power and reset | `power_on(efuse=None, *, delay=None)`, `power_off(efuse=None, *, delay=None)`, `target_power(efuse=None, *, on, delay=None)`, `target_status()`, `power_status()`, `measure_power(duration, *, efuse=None, rate_hz=500.0, keep_samples=0)`, `power_profile(*, efuse=None, rate_hz=500.0, keep_samples=4096, max_duration=60.0)`, `reset_target(*, pulse=0.1)`, `set_reset(asserted)`, `reset_state()` |
2241
2319
  | Flashing | `flash(...)`, `spi_flash(image, addr=0, *, erase=True, verify=True, hold_reset=False, sck=, mosi=, miso=, cs=)`, `open_spi(...)`, `open_motor_emulator(...)` |
@@ -2285,6 +2363,7 @@ few built from other shapes); `to_dict()` goes the other way where a type is sen
2285
2363
  | `SpiFlashResult` | `spi_flash`, `SpiSession.flash_program` | `jedec_id`, `addr`, `length`, `erased`, `verified`, `seconds` |
2286
2364
  | `SpiStreamResult` | `SpiSession.stream` | `sent`, `seconds` |
2287
2365
  | `UartCapture` | `capture_uart`, `power_cycle_and_capture` | `text`, `lines`, `matched`, `match(pattern)`, `contains(needle)` (also `needle in capture`) |
2366
+ | `UartEntry` (frozen dataclass) | passed to `open_uart` / `capture_uart` as `entry` | `reset_ms`, `tx_low`, `hold_ms`, `idle_ms`, `data`, `to_request()` |
2288
2367
  | `UartSession` (class) | `open_uart` (a context manager) | `write(data)`, `read(*, timeout=0.0)`, `read_until(pattern, *, timeout)`, `expect(pattern, *, timeout)`, `text`, `lines`, `closed`, `error`, `close()` |
2289
2368
  | `Sensor` (class) | `sensors.start`, `sensors.sensor` | `instance`, `kind`, `name`, `params`, `info`, `started`, `set(**values)`, `fault(type, *, duration_s=None, **fields)`, `clear_fault()`, `status()`, `regs(start=0, length=None)`, `capture(samples, sample_rate_hz, *, timeout_s, wait_for_traffic)`, `i2c_transactions(...)`, `stop()` |
2290
2369
  | `SensorEmulation` (class) | `BenchPod.sensors` | see [Emulated sensors](#emulated-sensors) |
@@ -2347,7 +2426,7 @@ reported keeps its default (`False`, `0` or `""`), so a feature check is just
2347
2426
  | Identity | `board`, `firmware_version`, `board_rev` (`"v2"`, `"v3"`, `"unknown"`, or `""`), `la_vccio_mv` (the LA bank voltage the pod reports) |
2348
2427
  | ADC | `adc_bits`, `adc_fullscale_mv`, `adc_channels`, `adc_offset_counts`, `adc_affine` (the front-end fit, of the range in use), `adc_low_range` (analog module v3r4+: the low range), `adc_range` (`"normal"`, `"low"`, or `""` before firmware 3.9.5), `adc_range_fullscale` (volts, ±), `adc_max_count`, `counts_to_volts(count)` |
2349
2428
  | DAC and replay | `dac`, `dac_dc`, `dac_replay`, `dac_deep_replay`, `dac_control_loop`, `dac_loop_sources` (gateware v29+), `dac_loop_input_map` (v30+), `dac_cotrig` (v27+), `generate16` (firmware 3.9.1+: `generate` in calibrated 16-bit volts), `dac_bits`, `dac_replay_bits`, `dac_replay_max_samples`, `dac_fullscale_mv`, `dac_channels`, `dac_limits` (output limits on the DAC paths) |
2350
- | Features | `scope`, `analyzer`, `serial`, `tunnel`, `command`, `ota`, `la_pins`, `gpio_read` (direct pin reads, v35+), `capture_trigger` (v35+), `power_profile`, `capture_b64` (faster ADC read-back, used automatically), `nrst_pin` (the dedicated reset pin, rev3), `usb_cc` (rev3), `spi_master` (v45+), `spi_stream`, `uart_frame` (UART parity and stop bits, gateware v56+), `calibrate`, `cal_dmm` (firmware 3.9.4+: `calibrate_dac`, `calibrate_adc_gain`), `current_out`, `can`, `pod_current` (`PowerStatus.pod`), `sensors` (sensor emulation from definitions, with `sensors_format` the format the pod reads), `analog` (`False` on the digital-only board, `None` when not announced) |
2429
+ | Features | `scope`, `analyzer`, `serial`, `tunnel`, `command`, `ota`, `la_pins`, `gpio_read` (direct pin reads, v35+), `capture_trigger` (v35+), `power_profile`, `capture_b64` (faster ADC read-back, used automatically), `nrst_pin` (the dedicated reset pin, rev3), `usb_cc` (rev3), `spi_master` (v45+), `spi_stream`, `uart_frame` (UART parity and stop bits, gateware v56+), `uart_hd` (one-wire UART and boot-mode entry, gateware v57+), `calibrate`, `cal_dmm` (firmware 3.9.4+: `calibrate_dac`, `calibrate_adc_gain`), `current_out`, `can`, `pod_current` (`PowerStatus.pod`), `sensors` (sensor emulation from definitions, with `sensors_format` the format the pod reads), `analog` (`False` on the digital-only board, `None` when not announced) |
2351
2430
  | Firmware updates and policies | `flash_kb` (MCU flash in KiB, 0 when not reported), `blob_slots`, `ota_sig`, `sig_policy` (`"audit"`, `"required"`, ...), `sig_keys`, `sig_policy_cmd`, `lan_policy` (`"open"`, `"locked"`, `"off"`), `lan_policy_cmd`, `tunnel_max_tier`, `lease_state` (the pod refuses LAN writes while a cloud job holds it), `cloud_ca`, `cloud_proxy`, `ws_auth_v2` (server only) |
2352
2431
  | Boot health | `safe_mode`, `safe_reason`, `last_crash`, `reset_cause`, `boot_warning()` (a one-line warning after safe mode or a crash, else `None`) |
2353
2432
  | Source | `raw` (the map it was parsed from) |
@@ -155,15 +155,20 @@ with BenchPod("192.168.1.213", la_voltage=3.3) as bp:
155
155
  bp.power_on(INTERNAL)
156
156
  ```
157
157
 
158
- `BenchPod` is a context manager; `close()` is idempotent. `la_voltage` (1.8 or 3.3) selects the
159
- **LA I/O-bank voltage** right after connecting — match it to the DUT's I/O voltage. The pod refuses
160
- every LA-bank operation (flashing, UART, LA capture, pull resistors, sensor emulation) until one
161
- is selected. You can also call `bp.set_la_voltage(3.3)` later; `bp.get_la_voltage()` returns a
162
- `LaVoltage` whose `voltage` is `None` until one is chosen. 1.8 V needs a rev3 pod. Until then a
163
- refused command raises `FirmwareError` with the message `la voltage not set; set the board's I/O
164
- voltage first: BenchPod(conn, la_voltage=3.3) (1.8 for a 1.8 V target), the benchpod_la_voltage
165
- fixture in conftest.py, or bp.set_la_voltage(3.3)` (prefixed with the command, as every
166
- `FirmwareError` is).
158
+ `BenchPod` is a context manager; `close()` is idempotent.
159
+
160
+ **The I/O voltage comes from the wiring profile.** The pod refuses every LA-bank operation
161
+ (flashing, UART, LA capture, pull resistors, sensor emulation) until its LA I/O-bank voltage is
162
+ selected, and it forgets it on every reboot. The profile's `la_mv` (`3300` or `1800`, the board's
163
+ I/O voltage) fills it in: on connect the SDK sets it from the pod's profile when the pod has none,
164
+ and firmware 3.10.10+ takes it from the active profile itself on the first LA operation. So a
165
+ profile that sets its I/O voltage needs nothing else. `la_voltage` (1.8 or 3.3) still sets it right
166
+ after connecting for this session, and `bp.set_la_voltage(3.3)` at any time; `bp.get_la_voltage()`
167
+ returns a `LaVoltage` whose `voltage` is `None` until one is chosen. 1.8 V needs a rev3 pod. With
168
+ no voltage anywhere, a refused command raises `FirmwareError` with the message `la voltage not set;
169
+ the wiring profile sets no I/O voltage: set la_mv in it (bp.save_wiring(bp.wiring.with_changes(la_mv=3300)),
170
+ 1800 for a 1.8 V board), or pass BenchPod(conn, la_voltage=3.3), or call bp.set_la_voltage(3.3)`
171
+ (prefixed with the command, as every `FirmwareError` is).
167
172
 
168
173
  Other constructor arguments: `timeout` (seconds, default 30), `api_key`, `api_base`,
169
174
  `cloud_token`, `cloud_audience`, `cloud_user_token`, `lease`, `lease_wait`, `lease_ttl` (see [Cloud](#cloud-embeddedcidevice-name)),
@@ -369,7 +374,18 @@ properties `can_gpio`, `can_trigger`, `can_spi`, `can_profile_power`, `can_calib
369
374
  `can_current_out`, `can_reset_target` and `can_analog` name the common ones (`can_config` …
370
375
  `can_disable` stay the CAN bus commands). A call the pod cannot serve raises
371
376
  `UnsupportedFeatureError` (see [Errors](#errors)), before anything is sent when the capabilities
372
- already say so:
377
+ already say so.
378
+
379
+ Where those come from: firmware after 3.10.10 no longer lists its features. The SDK asks for its
380
+ `status` without the list (`"caps":false`) and gets `capabilities.features_rev`, the revision of
381
+ the features table the firmware is built from, plus the running image (`capabilities.fpga_image`)
382
+ and a few hardware facts. The SDK ships that table (`embeddedci.benchpod.feature_map`, a copy of
383
+ benchpod-firmware's `features/features.json`), so this needs no network: `capabilities.features`
384
+ is every feature the table gives the pod, and `bp.supports()` also takes table names without a
385
+ flag of their own (`"la_dir"`, `"i2c_master"`, `"diag"`, `"wiring_store"`, ...). Older firmware
386
+ sends its list as before and gets the same answers. A pod with a higher `features_rev` than the
387
+ SDK knows logs a warning once: update the SDK (`pip install -U embeddedci`) to use those features.
388
+
373
389
 
374
390
  ```python
375
391
  import pytest
@@ -389,9 +405,10 @@ has a complete old → new table.
389
405
 
390
406
  ## pytest plugin
391
407
 
392
- Installing the package registers a pytest plugin (options, fixtures and markers). Set the board's
393
- I/O voltage **once** for the whole suite in `conftest.py` — the pod refuses flashing, UART, LA
394
- capture, pull resistors and sensor emulation until an LA bank voltage is selected:
408
+ Installing the package registers a pytest plugin (options, fixtures and markers). The board's I/O
409
+ voltage normally comes from the pod's wiring profile (`la_mv`); when the profile sets none, or a
410
+ suite must not depend on it, set it **once** for the whole suite in `conftest.py`. The pod refuses
411
+ flashing, UART, LA capture, pull resistors and sensor emulation until a voltage is selected:
395
412
 
396
413
  ```python
397
414
  # conftest.py
@@ -552,6 +569,7 @@ print(wiring.describe()) # a pin table: bias resistor and
552
569
  | `la_mv` | not set | LA I/O-bank voltage in mV (1800 or 3300); `wiring.la_voltage` in volts |
553
570
  | `efuse` | not set (pass `efuse=`) | target-power rail: 1 internal 5 V, 2 external |
554
571
  | `uart_rx`, `uart_tx`, `uart_baud` | not wired, not wired, `115200` | `rx` samples the DUT's TX; `tx` drives the DUT's RX |
572
+ | `uart_parity`, `uart_stop_bits` | `"none"`, `1` | The UART frame after the 8 data bits (`"even"`, `"odd"`; 2 stop bits). `open_uart`, `capture_uart` and `power_cycle_and_capture` use it when `parity` / `stop_bits` are omitted; anything but 8N1 needs firmware 3.10.8+ |
555
573
  | `i2c_sda`, `i2c_scl`, `i2c_addr` | not wired, not wired, not set | the I2C bus (emulated sensors default to it; put I2C on LA1-LA6, which have pull-ups) |
556
574
  | `swd_swclk`, `swd_swdio`, `swd_nreset`, `swd_target` | not wired, not wired, `False`, `""` (auto-detect) | flashing |
557
575
  | `spi_sclk`, `spi_mosi`, `spi_miso`, `spi_cs` | not wired | decoder channels |
@@ -617,8 +635,11 @@ pod's bus; reading never touches it. Firmware that stores no profiles: `save_wir
617
635
  cloud device's single profile on embeddedci.com, and raises over the LAN or USB.
618
636
 
619
637
  **Power-on applies the profile.** `bp.power_on()` (or `bp.power_on(wiring_profile="k66")`) sets the
620
- profile's I/O voltage when the pod has none or another one, then switches the profile's rail on and
621
- records on the pod which profile powered the board (`target_status`). It never changes the I/O
638
+ profile's I/O voltage when the pod has none or another one, sets its pull resistors, then switches
639
+ the profile's rail on and records on the pod which profile powered the board (`target_status`).
640
+ `Wiring.pulls` lists the LA channels whose pull resistor is on (`{"pulls": [1, 2]}` in the JSON):
641
+ `power_on` switches exactly those on and the others off. They work at 3.3 V only, so at 1.8 V nothing
642
+ is sent, and a profile without `pulls` (`None`) leaves them as they are. It never changes the I/O
622
643
  voltage under a board that is already powered: that raises, and `bp.set_la_voltage()` does it if you
623
644
  mean it.
624
645
 
@@ -632,6 +653,19 @@ A file holds the same JSON object the pod stores:
632
653
  `bp.signal(name)` returns a GPIO handle for a signal (see [GPIO on the LA pins](#gpio-on-the-la-pins));
633
654
  channel arguments accept a role or signal name too (`bp.open_uart(rx="uart_rx", tx=4)`).
634
655
 
656
+ **The profile on the pod's header.** `bp.board_header()` says which I/O header the pod has:
657
+ `"j1"` (the 2x11 pin headers of the one-piece boards up to v3-r2) or `"front"` (the 2x13 connector
658
+ on the front of digital v3r3 and later), None when the pod cannot tell. `header_map(wiring, header)`
659
+ writes the profile on that header as text: every pin in its physical place, then what to connect
660
+ to each pin on your board (header None writes both headers). The web and desktop apps draw the same
661
+ thing from the Pins pane's Visualize button.
662
+
663
+ ```python
664
+ from embeddedci.benchpod import header_map
665
+
666
+ print(header_map(bp.wiring, bp.board_header()))
667
+ ```
668
+
635
669
  ## Power, reset and power monitoring
636
670
 
637
671
  ```python
@@ -955,12 +989,53 @@ The LA pins are 1.8 V or 3.3 V only: the pod has no 5 V I/O and no RS-485 port.
955
989
  level shifter, and Modbus RTU on RS-485 an external RS-485 transceiver powered at 3.3 V (or a 5 V
956
990
  transceiver behind a level shifter), between the pod and the device.
957
991
 
992
+ **One wire (half duplex).** Some parts talk UART on a single pin, for example a boot ROM's
993
+ programming pin. `half_duplex=True` runs the session on `rx` alone (`tx` defaults to the same
994
+ channel): the pod only pulls the line low and lets the pull-up hold it high, so the device answers
995
+ on the same wire, and the pod does not read back its own bytes. Use LA1 to LA6, whose pull-up the
996
+ pod turns on for the session, or a pull-up on the board.
997
+
998
+ **Boot-mode entry.** A boot ROM that picks its mode from the UART pin at reset needs the pin held
999
+ low while the chip leaves reset, then a byte soon after. `entry=UartEntry(...)` has the pod run that
1000
+ sequence before the session starts, timed on the pod so no network delay sits in between: TX
1001
+ low (`tx_low`), reset for `reset_ms`, release, wait `hold_ms`, release TX, wait `idle_ms`, then send
1002
+ `data` (at most 32 bytes). Times are whole milliseconds, 0 to 1000:
1003
+
1004
+ ```python
1005
+ from embeddedci.benchpod import UartEntry
1006
+
1007
+ entry = UartEntry(reset_ms=5, hold_ms=3, idle_ms=2, data=b"\x00")
1008
+ with bp.open_uart(rx=PIN3, half_duplex=True, entry=entry, encoding="latin-1") as uart:
1009
+ reply = uart.read(timeout=0.5)
1010
+ ```
1011
+
1012
+ Both need gateware v57 (`bp.supports("uart_hd")`), and `entry` also the pod's reset pin
1013
+ (`bp.supports("nrst_pin")`); older pods raise `UnsupportedFeatureError` before anything is sent.
1014
+ The USB console has neither.
1015
+
958
1016
  **Binary protocols.** A session decodes what it receives as UTF-8, which suits a console. For bytes
959
1017
  that are not text (a binary protocol's frames), open it with `encoding="latin-1"`: every byte is one
960
1018
  character, so `uart.read().encode("latin-1")` gives the bytes back unchanged, and a `bytes` write is
961
1019
  sent as is. For the adapter wiring and a Modbus RTU test through a transceiver, see
962
1020
  [5 V logic and RS-485](https://www.embeddedci.com/docs/benchpod-targets/5v-rs485).
963
1021
 
1022
+ **RS-485 direction (DE).** A half-duplex RS-485 transceiver sends while its DE (tied to /RE) is
1023
+ high and listens while it is low. `de=` names the LA channel wired to DE, and the pod switches it
1024
+ itself: high from before the first start bit of what it sends to the end of the last stop bit, low
1025
+ otherwise. Nothing on the host times it, so a device that answers within a millisecond is still
1026
+ heard (switching DE with `gpio` calls from the host takes tens of milliseconds over the network,
1027
+ and the reply of a fast device is lost meanwhile). `de_active_low=True` inverts it:
1028
+
1029
+ ```python
1030
+ with bp.open_uart(rx=PIN5, tx=PIN4, de=PIN9, baud=19200, parity="even",
1031
+ encoding="latin-1") as uart:
1032
+ uart.write(request) # DE goes high and low with the bytes
1033
+ reply = uart.read(timeout=0.2)
1034
+ ```
1035
+
1036
+ `de` needs gateware v58 (`bp.supports("uart_de")`); older pods raise `UnsupportedFeatureError`
1037
+ before anything is sent. The USB console has no DE.
1038
+
964
1039
  ## LA bias resistors
965
1040
 
966
1041
  Eight LA channels carry a fixed, switchable bias resistor. They are referenced to 3V3, so the pod
@@ -1070,10 +1145,13 @@ sends them again.
1070
1145
  Every wired role and signal has a direction. The defaults: `uart_rx` and `spi_miso` are DUT
1071
1146
  outputs (the DUT drives them); `uart_tx`, `spi_sclk`, `spi_mosi`, `spi_cs` and `swd_swclk` DUT
1072
1147
  inputs; the I2C pins and `swd_swdio` `bidir`; a signal with direction `input` (the pod watches it)
1073
- is a DUT output, `output` a DUT input, `open_drain` and `bidir` are `bidir`. The profile's
1074
- `dut_dirs` overrides any of them (`wiring.dut_dir(name)` is one role's or signal's direction,
1075
- `wiring.pin_dut_dirs()` the per-channel map). Note the point of view: `la_dir` and `dut_dirs`
1076
- describe the DUT's signal, while a signal's `direction` is seen from the pod.
1148
+ is a DUT output, `output` a DUT input, `open_drain` and `bidir` are `bidir`. So a pin's direction
1149
+ follows from what it is used for: set a signal's `direction` to change it. `wiring.dut_dir(name)` is
1150
+ one role's or signal's direction, `wiring.pin_dut_dirs()` the per-channel map. Profiles from older
1151
+ versions may carry `dut_dirs` (role key or signal name -> `dut_input`, `dut_output`, `bidir`), which
1152
+ still overrides the defaults; the web and desktop editors no longer write it. Note the point of
1153
+ view: `la_dir` and `dut_dirs` describe the DUT's signal, while a signal's `direction` is seen from the
1154
+ pod.
1077
1155
  `LaPinState.dir` is a pin's direction (`None` when unknown), and `LaPinState.warn` holds warning
1078
1156
  bits that `LaPinState.warnings` spells out: a pull-up under a push-pull output, and a pin driven high
1079
1157
  or pulled up while the target power is off (it powers an unpowered DUT through its I/O pins).
@@ -2194,7 +2272,7 @@ lease_wait=600.0, lease_ttl=120, wiring=None)`. A context manager; `close()` is
2194
2272
 
2195
2273
  | Area | Methods and properties |
2196
2274
  |---|---|
2197
- | Connection and device | `ping()`, `status()`, `mac_addresses(status=None)` (the Ethernet and Wi-Fi MACs, see [MAC addresses](#mac-addresses-managed-networks)), `capabilities`, `refresh_capabilities()` (drop the cached capabilities and read them again), `close()`, `leased` (true while this client holds the cloud lease), `wiring`, `save_wiring(wiring=None)` (store a cloud device's profile on embeddedci.com), `signal(name)`, `fpga_image(image)`, `usb_cc()`, `usb_network(on=None)` (the USB network setting; `False` turns the adapter off over the USB link), `lan_tls()`, `set_lan_tls_https_only(on)`, `regenerate_lan_tls()`, `set_lan_tls_cert(cert_pem, key_pem)` (the LAN API over TLS, see [TLS on the LAN](#tls-on-the-lan)) |
2275
+ | Connection and device | `ping()`, `status()`, `diag()` (heap, per-task stacks, network-stack and console counters: the `diag` command on firmware 3.10.9+, else the full `status`), `mac_addresses(status=None)` (the Ethernet and Wi-Fi MACs, see [MAC addresses](#mac-addresses-managed-networks)), `capabilities`, `refresh_capabilities()` (drop the cached capabilities and read them again), `close()`, `leased` (true while this client holds the cloud lease), `wiring`, `save_wiring(wiring=None, name=None)` (store a wiring profile on the pod; firmware before 3.10.8: on embeddedci.com), `signal(name)`, `fpga_image(image)`, `usb_cc()`, `usb_network(on=None)` (the USB network setting; `False` turns the adapter off over the USB link), `lan_tls()`, `set_lan_tls_https_only(on)`, `regenerate_lan_tls()`, `set_lan_tls_cert(cert_pem, key_pem)` (the LAN API over TLS, see [TLS on the LAN](#tls-on-the-lan)) |
2198
2276
  | LA voltage | `set_la_voltage(volts)`, `get_la_voltage()` |
2199
2277
  | Power and reset | `power_on(efuse=None, *, delay=None)`, `power_off(efuse=None, *, delay=None)`, `target_power(efuse=None, *, on, delay=None)`, `target_status()`, `power_status()`, `measure_power(duration, *, efuse=None, rate_hz=500.0, keep_samples=0)`, `power_profile(*, efuse=None, rate_hz=500.0, keep_samples=4096, max_duration=60.0)`, `reset_target(*, pulse=0.1)`, `set_reset(asserted)`, `reset_state()` |
2200
2278
  | Flashing | `flash(...)`, `spi_flash(image, addr=0, *, erase=True, verify=True, hold_reset=False, sck=, mosi=, miso=, cs=)`, `open_spi(...)`, `open_motor_emulator(...)` |
@@ -2244,6 +2322,7 @@ few built from other shapes); `to_dict()` goes the other way where a type is sen
2244
2322
  | `SpiFlashResult` | `spi_flash`, `SpiSession.flash_program` | `jedec_id`, `addr`, `length`, `erased`, `verified`, `seconds` |
2245
2323
  | `SpiStreamResult` | `SpiSession.stream` | `sent`, `seconds` |
2246
2324
  | `UartCapture` | `capture_uart`, `power_cycle_and_capture` | `text`, `lines`, `matched`, `match(pattern)`, `contains(needle)` (also `needle in capture`) |
2325
+ | `UartEntry` (frozen dataclass) | passed to `open_uart` / `capture_uart` as `entry` | `reset_ms`, `tx_low`, `hold_ms`, `idle_ms`, `data`, `to_request()` |
2247
2326
  | `UartSession` (class) | `open_uart` (a context manager) | `write(data)`, `read(*, timeout=0.0)`, `read_until(pattern, *, timeout)`, `expect(pattern, *, timeout)`, `text`, `lines`, `closed`, `error`, `close()` |
2248
2327
  | `Sensor` (class) | `sensors.start`, `sensors.sensor` | `instance`, `kind`, `name`, `params`, `info`, `started`, `set(**values)`, `fault(type, *, duration_s=None, **fields)`, `clear_fault()`, `status()`, `regs(start=0, length=None)`, `capture(samples, sample_rate_hz, *, timeout_s, wait_for_traffic)`, `i2c_transactions(...)`, `stop()` |
2249
2328
  | `SensorEmulation` (class) | `BenchPod.sensors` | see [Emulated sensors](#emulated-sensors) |
@@ -2306,7 +2385,7 @@ reported keeps its default (`False`, `0` or `""`), so a feature check is just
2306
2385
  | Identity | `board`, `firmware_version`, `board_rev` (`"v2"`, `"v3"`, `"unknown"`, or `""`), `la_vccio_mv` (the LA bank voltage the pod reports) |
2307
2386
  | ADC | `adc_bits`, `adc_fullscale_mv`, `adc_channels`, `adc_offset_counts`, `adc_affine` (the front-end fit, of the range in use), `adc_low_range` (analog module v3r4+: the low range), `adc_range` (`"normal"`, `"low"`, or `""` before firmware 3.9.5), `adc_range_fullscale` (volts, ±), `adc_max_count`, `counts_to_volts(count)` |
2308
2387
  | DAC and replay | `dac`, `dac_dc`, `dac_replay`, `dac_deep_replay`, `dac_control_loop`, `dac_loop_sources` (gateware v29+), `dac_loop_input_map` (v30+), `dac_cotrig` (v27+), `generate16` (firmware 3.9.1+: `generate` in calibrated 16-bit volts), `dac_bits`, `dac_replay_bits`, `dac_replay_max_samples`, `dac_fullscale_mv`, `dac_channels`, `dac_limits` (output limits on the DAC paths) |
2309
- | Features | `scope`, `analyzer`, `serial`, `tunnel`, `command`, `ota`, `la_pins`, `gpio_read` (direct pin reads, v35+), `capture_trigger` (v35+), `power_profile`, `capture_b64` (faster ADC read-back, used automatically), `nrst_pin` (the dedicated reset pin, rev3), `usb_cc` (rev3), `spi_master` (v45+), `spi_stream`, `uart_frame` (UART parity and stop bits, gateware v56+), `calibrate`, `cal_dmm` (firmware 3.9.4+: `calibrate_dac`, `calibrate_adc_gain`), `current_out`, `can`, `pod_current` (`PowerStatus.pod`), `sensors` (sensor emulation from definitions, with `sensors_format` the format the pod reads), `analog` (`False` on the digital-only board, `None` when not announced) |
2388
+ | Features | `scope`, `analyzer`, `serial`, `tunnel`, `command`, `ota`, `la_pins`, `gpio_read` (direct pin reads, v35+), `capture_trigger` (v35+), `power_profile`, `capture_b64` (faster ADC read-back, used automatically), `nrst_pin` (the dedicated reset pin, rev3), `usb_cc` (rev3), `spi_master` (v45+), `spi_stream`, `uart_frame` (UART parity and stop bits, gateware v56+), `uart_hd` (one-wire UART and boot-mode entry, gateware v57+), `calibrate`, `cal_dmm` (firmware 3.9.4+: `calibrate_dac`, `calibrate_adc_gain`), `current_out`, `can`, `pod_current` (`PowerStatus.pod`), `sensors` (sensor emulation from definitions, with `sensors_format` the format the pod reads), `analog` (`False` on the digital-only board, `None` when not announced) |
2310
2389
  | Firmware updates and policies | `flash_kb` (MCU flash in KiB, 0 when not reported), `blob_slots`, `ota_sig`, `sig_policy` (`"audit"`, `"required"`, ...), `sig_keys`, `sig_policy_cmd`, `lan_policy` (`"open"`, `"locked"`, `"off"`), `lan_policy_cmd`, `tunnel_max_tier`, `lease_state` (the pod refuses LAN writes while a cloud job holds it), `cloud_ca`, `cloud_proxy`, `ws_auth_v2` (server only) |
2311
2390
  | Boot health | `safe_mode`, `safe_reason`, `last_crash`, `reset_cause`, `boot_warning()` (a one-line warning after safe mode or a crash, else `None`) |
2312
2391
  | Source | `raw` (the map it was parsed from) |
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "embeddedci"
7
- version = "3.0.0"
7
+ version = "3.0.2"
8
8
  description = "BenchPod SDK and pytest plugin for EmbeddedCI hardware-in-the-loop testing"
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.10"
@@ -161,17 +161,19 @@ from .state import (
161
161
  TargetStatus,
162
162
  UsbCcStatus,
163
163
  )
164
- from .uart import UartCapture, UartSession
164
+ from .uart import UartCapture, UartEntry, UartSession
165
165
  from .spi import SpiFlashInfo, SpiFlashResult, SpiSession, SpiStreamResult
166
166
  from . import motor_emulator
167
167
  from .motor_emulator import BatteryModel, EmulatorCalibration, MotorEmulator
168
168
  from .waveforms import Waveform, WaveformLibrary
169
169
  from .wiring import Signal, Wiring
170
+ from .header import header_map
170
171
 
171
172
  __all__ = [
172
173
  "BenchPod",
173
174
  # wiring profile
174
175
  "Wiring",
176
+ "header_map",
175
177
  "Signal",
176
178
  # LA pin modes + GPIO
177
179
  "GpioPin",
@@ -212,6 +214,7 @@ __all__ = [
212
214
  # flash + UART
213
215
  "FlashResult",
214
216
  "UartCapture",
217
+ "UartEntry",
215
218
  "UartSession",
216
219
  "SpiSession",
217
220
  "SpiFlashInfo",