embeddedci 3.0.1__tar.gz → 3.0.3__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.
- {embeddedci-3.0.1 → embeddedci-3.0.3}/CHANGELOG.md +55 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/PKG-INFO +114 -25
- {embeddedci-3.0.1 → embeddedci-3.0.3}/README.md +113 -24
- {embeddedci-3.0.1 → embeddedci-3.0.3}/pyproject.toml +1 -1
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/__init__.py +6 -1
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/capabilities.py +61 -1
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/client.py +268 -63
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/constants.py +30 -8
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/error_catalog.json +132 -1
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/errors.py +23 -3
- embeddedci-3.0.3/src/embeddedci/benchpod/feature_map.json +657 -0
- embeddedci-3.0.3/src/embeddedci/benchpod/feature_map.py +112 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/gpio.py +11 -3
- embeddedci-3.0.3/src/embeddedci/benchpod/header.py +143 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/state.py +38 -12
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/transport/base.py +14 -2
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/transport/serial.py +14 -1
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/transport/tcp.py +16 -1
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/uart.py +48 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/wiring.py +99 -32
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/api_surface.json +37 -6
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_e2e_cloud.py +15 -4
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_e2e_gpio.py +41 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/examples/test_bmp280_hil.py +3 -2
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_client_v2.py +4 -3
- embeddedci-3.0.3/tests/test_feature_map.py +143 -0
- embeddedci-3.0.3/tests/test_header.py +83 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_image_switching.py +50 -0
- embeddedci-3.0.3/tests/test_pull_direction.py +196 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_refusal_errors.py +1 -1
- embeddedci-3.0.3/tests/test_uart_de.py +102 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_uart_frame.py +17 -2
- embeddedci-3.0.3/tests/test_uart_half_duplex.py +90 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_wiring.py +6 -4
- {embeddedci-3.0.1 → embeddedci-3.0.3}/.gitignore +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/LICENSE +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/docs/aivision.md +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/docs/event-uart-design.md +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/examples/README.md +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/examples/test_bmp280.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/__init__.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/_http.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/aivision/__init__.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/aivision/client.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/aivision/cloud.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/aivision/discovery.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/aivision/errors.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/aivision/pytest_plugin.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/aivision/results.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/can.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/capture.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/ci.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/cli_config.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/cli_login.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/cloud_auth.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/connection.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/control_loop.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/decode.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/discovery.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/dsp.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/esp.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/expansion.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/flash.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/i2c.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/i2c_master.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/lease.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/lowlevel.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/main.c +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/motor_emulator.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/power.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/protocol.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/pytest_plugin.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/replay.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/results.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/__init__.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/README.md +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/docs/format.md +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/library.json +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/analog/ntc_10k_divider.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/analog/pressure_4_20ma.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/bme280.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/bmp280.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/ina219.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/mpu6050.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/scd4x.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/sht3x.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/sht4x.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/i2c/tmp117.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/spi/lis3dh.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/spi/lis3dh_fifo.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/uart/gps_nmea.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/sensors/uart/mhz19b.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/stimuli/gps_drive.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/stimuli/pressure_drop.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/bundled/stimuli/temperature_ramp_fault.yaml +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/definition.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/emulation.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/library.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/sensors/yaml12.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/server_api.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/spi.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/transport/__init__.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/transport/cloud.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/transport/tls.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/transport/usblink.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/benchpod/waveforms.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/py.typed +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/src/embeddedci/upload_build.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/conftest.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/README.md +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/conftest.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/e2e_bench.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/e2e_helpers.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_bench_profile.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_e2e_digital.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_e2e_dut.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_e2e_la13_14.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_e2e_pod.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_e2e_rev3.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_e2e_spi.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/e2e/test_e2e_usb.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/examples/test_can_ecu_demo.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/examples/test_can_loopback_hil.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/examples/test_smoke.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_adc_fft_hw.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_adc_oversample.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_adc_range.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_aivision.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_aivision_cloud.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_aivision_live.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_api_surface.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_can.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_capabilities.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_capabilities_scope.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_capture.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_capture_replay_hw.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_ci.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_cloud.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_connection.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_control_loop.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_control_loop_hw.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_current_out_waveforms.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_dac_limits_fixture.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_dac_path_default.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_dac_path_ranges.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_decode.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_decode_parity.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_docs_coverage.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_dsp.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_esp_flash.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_expansion.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_flash_bridge.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_flash_build.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_generate16.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_gpio.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_http_redirect_auth.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_i2c_decode.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_i2c_master.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_i2c_parity.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_i2c_timed.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_integration.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_la_voltage_fixture.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_lan_tls.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_lease.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_module.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_motor_emulator.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_one_source.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_pin_directions.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_pins_bias.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_protocol.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_replay.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_sensor_library.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_sensors.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_serial_autodetect.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_serial_text_console.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_spi.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_status_diag.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_tcp_transport.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_timed_power.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_timing.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_transport_failures.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_trigger_power.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_uart_capture.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_uart_session.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_unsupported_feature.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_upload_build.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_usb_net.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_waveforms.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/test_wiring_profiles.py +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/testdata/i2c_decode_vectors.json +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/testdata/spi_decode_vectors.json +0 -0
- {embeddedci-3.0.1 → embeddedci-3.0.3}/tests/testdata/uart_decode_vectors.json +0 -0
|
@@ -1,5 +1,60 @@
|
|
|
1
1
|
# Changelog — `embeddedci`
|
|
2
2
|
|
|
3
|
+
## 3.0.3
|
|
4
|
+
|
|
5
|
+
- The preset of the default pins is now `Wiring.preset("embeddedci-default")` (also the default of
|
|
6
|
+
`Wiring.preset()`), and `wiring.DEFAULT_PINS` is its values: they are the pins the pod used to
|
|
7
|
+
assume, not the wiring of a particular bench. The old names `"embeddedci-reference"` and
|
|
8
|
+
`REFERENCE_BENCH` still work. The values are unchanged, so version 1 profiles mean what they did.
|
|
9
|
+
- **Pull resistors by direction:** `BenchPod.set_pull(la, "up" | "down" | "off")` (None is off)
|
|
10
|
+
returns a `PullState` with `state`, `supported` (the directions the channel can pull) and `ohms`;
|
|
11
|
+
the pod picks the resistor. `enable_pullup` / `disable_pullup` / `enable_pulldown` /
|
|
12
|
+
`disable_pulldown` stay as shortcuts. `set_pull(la, True/False)` and `enabled=` still work
|
|
13
|
+
(deprecated: True pulls the channel's own direction). A direction the channel can't pull raises
|
|
14
|
+
`PullDirectionError` (code `BP0024`, also a `ValueError`), up/down on a channel without a resistor
|
|
15
|
+
`BP0023`. Firmware with the `la_pull_dir` feature gets `pull`; older firmware gets `pullup` and the
|
|
16
|
+
SDK checks the direction itself. `pull_state` and `enabled_pulls` cover LA1-LA14.
|
|
17
|
+
- **Wiring `pulls` map:** `Wiring.pulls` also takes `{"1": "up", "8": "down"}`; the list of channels
|
|
18
|
+
stays valid and means each channel's own direction. `Wiring.pull_directions()` gives either as
|
|
19
|
+
the map, and `power_on` applies it. `to_dict()` writes the list whenever every pull is its
|
|
20
|
+
channel's own direction, so older readers keep taking it.
|
|
21
|
+
- `LaPinState.pull_dirs`: every direction the channel's pull resistor can pull.
|
|
22
|
+
- The board's pull resistors are one table, `constants.PULL_TABLE` (`PullHw`: dirs, default,
|
|
23
|
+
ohms); `PULL_OHMS`, `PULLUP_CHANNELS` and `PULLDOWN_CHANNELS` come from it.
|
|
24
|
+
- Error catalog and features table synced from benchpod-firmware (BP0023, BP0024, `la_pull_dir`).
|
|
25
|
+
|
|
26
|
+
## 3.0.2
|
|
27
|
+
|
|
28
|
+
- **The profile on the pod's header:** `BenchPod.board_header()` says which I/O header the pod has
|
|
29
|
+
(`"j1"`, the 2x11 pin headers up to v3-r2, or `"front"`, the 2x13 front connector of digital v3r3
|
|
30
|
+
and later; asked once per connection with the read-only `module` command), and
|
|
31
|
+
`header_map(wiring, header)` writes the profile on it as text: every pin in its place, then what
|
|
32
|
+
to connect to it.
|
|
33
|
+
- **UART frame in the wiring profile:** `Wiring.uart_parity` (`"none"`, `"even"`, `"odd"`) and
|
|
34
|
+
`Wiring.uart_stop_bits` (1, 2), next to `uart_baud`. `open_uart`, `capture_uart` and
|
|
35
|
+
`power_cycle_and_capture` take them from the profile when `parity` / `stop_bits` are omitted
|
|
36
|
+
(8N1 unless the profile says otherwise). The web app and the desktop app set them in Pins.
|
|
37
|
+
- `flash(target="esp32...")` switches the FPGA to the deep-replay image before staging the image,
|
|
38
|
+
so a pod left on the emulation or loop image no longer refuses with `load_bin: deep replay is
|
|
39
|
+
not in the emulation image`.
|
|
40
|
+
- **One-wire UART and boot-mode entry:** `open_uart` and `capture_uart` take `half_duplex=True`
|
|
41
|
+
(rx and tx on one LA pin; the pod only pulls the line low and does not read back its own bytes)
|
|
42
|
+
and `entry=UartEntry(...)`, a reset with TX held low, its release and the first bytes, all timed
|
|
43
|
+
on the pod. Needs gateware v57 (capability `uart_hd`); the entry also needs the reset pin.
|
|
44
|
+
- **RS-485 direction driven by the pod:** `open_uart` and `capture_uart` take `de=` (the LA channel
|
|
45
|
+
on a transceiver's DE + /RE) and `de_active_low=`. The pod switches DE itself, from before the
|
|
46
|
+
first start bit to the end of the last stop bit, so a device that answers within a millisecond
|
|
47
|
+
is heard (DE switched from the host with GPIO calls drops about 25 ms after the request over
|
|
48
|
+
LAN). Needs gateware v58 (feature `uart_de`, features table revision 2).
|
|
49
|
+
|
|
50
|
+
- **Features from the firmware's features table:** the SDK ships benchpod-firmware's
|
|
51
|
+
`features/features.json` (`embeddedci.benchpod.feature_map`) and reads the pod's status with
|
|
52
|
+
`"caps":false`. Firmware after 3.10.10 answers with `features_rev` instead of its `caps` list,
|
|
53
|
+
and `Capabilities` takes the features from the table (`capabilities.features`,
|
|
54
|
+
`capabilities.fpga_image`, `Capabilities.has()`); older firmware sends its list as before.
|
|
55
|
+
`bp.supports()` also takes table names without a flag of their own (`"la_dir"`, `"i2c_master"`,
|
|
56
|
+
`"diag"`, ...). A pod whose firmware has a newer table than the SDK logs one warning to update it.
|
|
57
|
+
|
|
3
58
|
## 3.0.1
|
|
4
59
|
|
|
5
60
|
- **Pull resistors in the wiring profile:** `Wiring.pulls` lists the LA channels whose pull
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: embeddedci
|
|
3
|
-
Version: 3.0.
|
|
3
|
+
Version: 3.0.3
|
|
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
|
|
@@ -75,7 +75,7 @@ No pin numbers: the SWD channels, the UART pair, the baud and the power rail com
|
|
|
75
75
|
**Contents:** [Install](#install) · [Quick start](#quick-start) ·
|
|
76
76
|
[API conventions](#api-conventions-and-stability) · [pytest plugin](#pytest-plugin) ·
|
|
77
77
|
[Power and reset](#power-reset-and-power-monitoring) · [Flashing](#flashing) · [UART](#uart) ·
|
|
78
|
-
[
|
|
78
|
+
[Pull resistors](#la-pull-resistors) · [Emulated sensors](#emulated-sensors) ·
|
|
79
79
|
[Analog paths](#analog-paths-dc-output-and-single-readings) · [Captures](#captures) ·
|
|
80
80
|
[DAC](#dac-generator-replay-and-faults) · [Control loop](#in-fabric-dac-control-loop) ·
|
|
81
81
|
[CAN](#can) · [AI Vision](#ai-vision-board) · [Cloud](#cloud-embeddedcidevice-name) · [Build reporting](#build-reporting) ·
|
|
@@ -415,7 +415,18 @@ properties `can_gpio`, `can_trigger`, `can_spi`, `can_profile_power`, `can_calib
|
|
|
415
415
|
`can_current_out`, `can_reset_target` and `can_analog` name the common ones (`can_config` …
|
|
416
416
|
`can_disable` stay the CAN bus commands). A call the pod cannot serve raises
|
|
417
417
|
`UnsupportedFeatureError` (see [Errors](#errors)), before anything is sent when the capabilities
|
|
418
|
-
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
|
+
|
|
419
430
|
|
|
420
431
|
```python
|
|
421
432
|
import pytest
|
|
@@ -599,6 +610,7 @@ print(wiring.describe()) # a pin table: bias resistor and
|
|
|
599
610
|
| `la_mv` | not set | LA I/O-bank voltage in mV (1800 or 3300); `wiring.la_voltage` in volts |
|
|
600
611
|
| `efuse` | not set (pass `efuse=`) | target-power rail: 1 internal 5 V, 2 external |
|
|
601
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+ |
|
|
602
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) |
|
|
603
615
|
| `swd_swclk`, `swd_swdio`, `swd_nreset`, `swd_target` | not wired, not wired, `False`, `""` (auto-detect) | flashing |
|
|
604
616
|
| `spi_sclk`, `spi_mosi`, `spi_miso`, `spi_cs` | not wired | decoder channels |
|
|
@@ -608,10 +620,14 @@ print(wiring.describe()) # a pin table: bias resistor and
|
|
|
608
620
|
**Nothing is wired unless the profile says so** (schema version 2, SDK 3.0). A pin the profile does
|
|
609
621
|
not set is never driven, and a call that needs it says which one to pass: `bp.flash()` without
|
|
610
622
|
`swclk`/`swdio` in the profile raises `ValueError: swd_swclk was not given and the wiring profile has
|
|
611
|
-
no swd_swclk`. The
|
|
612
|
-
on LA11/LA12, 3.3 V, internal 5 V),
|
|
613
|
-
`Wiring.preset("embeddedci-
|
|
614
|
-
|
|
623
|
+
no swd_swclk`. The default pins, what profiles used to default to (UART RX on LA5 and TX on LA4, I2C
|
|
624
|
+
SDA on LA1 and SCL on LA2, SWD on LA11/LA12, 3.3 V, internal 5 V), are a preset:
|
|
625
|
+
`Wiring.preset("embeddedci-default")` (the old name `"embeddedci-reference"` still works). They are
|
|
626
|
+
not the wiring of any particular bench: load your board's own profile by name
|
|
627
|
+
(`BenchPod(conn, wiring_profile="process-node-stm32")`, `bp.load_wiring("process-node-stm32")`), as
|
|
628
|
+
the [process-node example](https://github.com/embeddedci-com/examples/tree/main/process-node-stm32)
|
|
629
|
+
does with its `wiring/process-node-stm32.json`. A version 1 file or dict (or one without a `version`
|
|
630
|
+
key) still means what it did: what it leaves out takes the default pins' values, and the profile you
|
|
615
631
|
get back is version 2 with them written out. Re-save such a file as version 2 with
|
|
616
632
|
`benchpod wiring upgrade wiring.json`.
|
|
617
633
|
|
|
@@ -666,7 +682,9 @@ cloud device's single profile on embeddedci.com, and raises over the LAN or USB.
|
|
|
666
682
|
**Power-on applies the profile.** `bp.power_on()` (or `bp.power_on(wiring_profile="k66")`) sets the
|
|
667
683
|
profile's I/O voltage when the pod has none or another one, sets its pull resistors, then switches
|
|
668
684
|
the profile's rail on and records on the pod which profile powered the board (`target_status`).
|
|
669
|
-
`Wiring.pulls`
|
|
685
|
+
`Wiring.pulls` says which pull resistors are on, as a map of channel to direction
|
|
686
|
+
(`{"pulls": {"1": "up", "2": "up", "8": "down"}}` in the JSON) or as a list of channels that pull
|
|
687
|
+
their own direction (`{"pulls": [1, 2]}`); `Wiring.pull_directions()` gives either as the map.
|
|
670
688
|
`power_on` switches exactly those on and the others off. They work at 3.3 V only, so at 1.8 V nothing
|
|
671
689
|
is sent, and a profile without `pulls` (`None`) leaves them as they are. It never changes the I/O
|
|
672
690
|
voltage under a board that is already powered: that raises, and `bp.set_la_voltage()` does it if you
|
|
@@ -682,6 +700,19 @@ A file holds the same JSON object the pod stores:
|
|
|
682
700
|
`bp.signal(name)` returns a GPIO handle for a signal (see [GPIO on the LA pins](#gpio-on-the-la-pins));
|
|
683
701
|
channel arguments accept a role or signal name too (`bp.open_uart(rx="uart_rx", tx=4)`).
|
|
684
702
|
|
|
703
|
+
**The profile on the pod's header.** `bp.board_header()` says which I/O header the pod has:
|
|
704
|
+
`"j1"` (the 2x11 pin headers of the one-piece boards up to v3-r2) or `"front"` (the 2x13 connector
|
|
705
|
+
on the front of digital v3r3 and later), None when the pod cannot tell. `header_map(wiring, header)`
|
|
706
|
+
writes the profile on that header as text: every pin in its physical place, then what to connect
|
|
707
|
+
to each pin on your board (header None writes both headers). The web and desktop apps draw the same
|
|
708
|
+
thing from the Pins pane's Visualize button.
|
|
709
|
+
|
|
710
|
+
```python
|
|
711
|
+
from embeddedci.benchpod import header_map
|
|
712
|
+
|
|
713
|
+
print(header_map(bp.wiring, bp.board_header()))
|
|
714
|
+
```
|
|
715
|
+
|
|
685
716
|
## Power, reset and power monitoring
|
|
686
717
|
|
|
687
718
|
```python
|
|
@@ -1005,36 +1036,92 @@ 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.
|
|
|
1005
1036
|
level shifter, and Modbus RTU on RS-485 an external RS-485 transceiver powered at 3.3 V (or a 5 V
|
|
1006
1037
|
transceiver behind a level shifter), between the pod and the device.
|
|
1007
1038
|
|
|
1039
|
+
**One wire (half duplex).** Some parts talk UART on a single pin, for example a boot ROM's
|
|
1040
|
+
programming pin. `half_duplex=True` runs the session on `rx` alone (`tx` defaults to the same
|
|
1041
|
+
channel): the pod only pulls the line low and lets the pull-up hold it high, so the device answers
|
|
1042
|
+
on the same wire, and the pod does not read back its own bytes. Use LA1 to LA6, whose pull-up the
|
|
1043
|
+
pod turns on for the session, or a pull-up on the board.
|
|
1044
|
+
|
|
1045
|
+
**Boot-mode entry.** A boot ROM that picks its mode from the UART pin at reset needs the pin held
|
|
1046
|
+
low while the chip leaves reset, then a byte soon after. `entry=UartEntry(...)` has the pod run that
|
|
1047
|
+
sequence before the session starts, timed on the pod so no network delay sits in between: TX
|
|
1048
|
+
low (`tx_low`), reset for `reset_ms`, release, wait `hold_ms`, release TX, wait `idle_ms`, then send
|
|
1049
|
+
`data` (at most 32 bytes). Times are whole milliseconds, 0 to 1000:
|
|
1050
|
+
|
|
1051
|
+
```python
|
|
1052
|
+
from embeddedci.benchpod import UartEntry
|
|
1053
|
+
|
|
1054
|
+
entry = UartEntry(reset_ms=5, hold_ms=3, idle_ms=2, data=b"\x00")
|
|
1055
|
+
with bp.open_uart(rx=PIN3, half_duplex=True, entry=entry, encoding="latin-1") as uart:
|
|
1056
|
+
reply = uart.read(timeout=0.5)
|
|
1057
|
+
```
|
|
1058
|
+
|
|
1059
|
+
Both need gateware v57 (`bp.supports("uart_hd")`), and `entry` also the pod's reset pin
|
|
1060
|
+
(`bp.supports("nrst_pin")`); older pods raise `UnsupportedFeatureError` before anything is sent.
|
|
1061
|
+
The USB console has neither.
|
|
1062
|
+
|
|
1008
1063
|
**Binary protocols.** A session decodes what it receives as UTF-8, which suits a console. For bytes
|
|
1009
1064
|
that are not text (a binary protocol's frames), open it with `encoding="latin-1"`: every byte is one
|
|
1010
1065
|
character, so `uart.read().encode("latin-1")` gives the bytes back unchanged, and a `bytes` write is
|
|
1011
1066
|
sent as is. For the adapter wiring and a Modbus RTU test through a transceiver, see
|
|
1012
1067
|
[5 V logic and RS-485](https://www.embeddedci.com/docs/benchpod-targets/5v-rs485).
|
|
1013
1068
|
|
|
1014
|
-
|
|
1069
|
+
**RS-485 direction (DE).** A half-duplex RS-485 transceiver sends while its DE (tied to /RE) is
|
|
1070
|
+
high and listens while it is low. `de=` names the LA channel wired to DE, and the pod switches it
|
|
1071
|
+
itself: high from before the first start bit of what it sends to the end of the last stop bit, low
|
|
1072
|
+
otherwise. Nothing on the host times it, so a device that answers within a millisecond is still
|
|
1073
|
+
heard (switching DE with `gpio` calls from the host takes tens of milliseconds over the network,
|
|
1074
|
+
and the reply of a fast device is lost meanwhile). `de_active_low=True` inverts it:
|
|
1075
|
+
|
|
1076
|
+
```python
|
|
1077
|
+
with bp.open_uart(rx=PIN5, tx=PIN4, de=PIN9, baud=19200, parity="even",
|
|
1078
|
+
encoding="latin-1") as uart:
|
|
1079
|
+
uart.write(request) # DE goes high and low with the bytes
|
|
1080
|
+
reply = uart.read(timeout=0.2)
|
|
1081
|
+
```
|
|
1015
1082
|
|
|
1016
|
-
|
|
1017
|
-
|
|
1083
|
+
`de` needs gateware v58 (`bp.supports("uart_de")`); older pods raise `UnsupportedFeatureError`
|
|
1084
|
+
before anything is sent. The USB console has no DE.
|
|
1018
1085
|
|
|
1019
|
-
|
|
1086
|
+
## LA pull resistors
|
|
1087
|
+
|
|
1088
|
+
You name the direction, `"up"`, `"down"` or `"off"`; the pod picks the resistor and reports its
|
|
1089
|
+
value. Which channels have one and which way each can pull depends on the board, and
|
|
1090
|
+
`PullState.supported` says it per channel. On today's boards each resistor pulls one way only:
|
|
1091
|
+
|
|
1092
|
+
| Channels | Pulls | Value |
|
|
1020
1093
|
|---|---|---|
|
|
1021
|
-
| LA1, LA2 |
|
|
1022
|
-
| LA3, LA4 |
|
|
1023
|
-
| LA5, LA6 |
|
|
1024
|
-
| LA7, LA8 |
|
|
1094
|
+
| LA1, LA2 | up | 4.7k |
|
|
1095
|
+
| LA3, LA4 | up | 2.2k |
|
|
1096
|
+
| LA5, LA6 | up | 10k |
|
|
1097
|
+
| LA7, LA8 | **down** | 10k |
|
|
1025
1098
|
| LA9–LA14 | none | — |
|
|
1026
1099
|
|
|
1100
|
+
The resistors are referenced to 3V3, so the pod won't engage one while the LA bank is at 1.8 V
|
|
1101
|
+
(`PullState.available` is false).
|
|
1102
|
+
|
|
1027
1103
|
```python
|
|
1028
1104
|
from embeddedci.benchpod import PIN1, PIN2, PIN7
|
|
1029
1105
|
|
|
1030
|
-
bp.
|
|
1031
|
-
bp.
|
|
1032
|
-
|
|
1033
|
-
print(bp.
|
|
1034
|
-
bp.
|
|
1035
|
-
bp.
|
|
1106
|
+
bp.set_pull(PIN1, "up") # PullState(la=1, enabled=True, direction='up', ohms='4.7k', supported=('up',), ...)
|
|
1107
|
+
bp.set_pull(PIN7, "down")
|
|
1108
|
+
bp.set_pull(PIN7, "off") # None is off too; "off" works on every channel
|
|
1109
|
+
print(bp.pull_state(PIN1).state) # 'up' ('up', 'down' or 'off')
|
|
1110
|
+
print(bp.enabled_pulls()) # [1]
|
|
1111
|
+
bp.enable_pullup(PIN1, PIN2) # shortcuts: set_pull(la, "up") ...
|
|
1112
|
+
bp.enable_pulldown(PIN7) # ... and set_pull(la, "down")
|
|
1113
|
+
bp.disable_pullup(PIN1, PIN2) # off, on a channel that pulls up
|
|
1036
1114
|
```
|
|
1037
1115
|
|
|
1116
|
+
A direction the channel can't pull raises `PullDirectionError` (a `FirmwareError` and a
|
|
1117
|
+
`ValueError`) with code `BP0024`, "LA7 supports pull-down only on this board", and `"up"` or `"down"`
|
|
1118
|
+
on a channel without a resistor raises it with `BP0023`. `.la`, `.want` and `.have` name the channel
|
|
1119
|
+
and the directions. `set_pull(la, True)` / `set_pull(la, False)` (or `enabled=`) still work but are
|
|
1120
|
+
deprecated: True pulls the channel's own direction.
|
|
1121
|
+
|
|
1122
|
+
Firmware before the `la_pull_dir` feature (`bp.supports("la_pull_dir")`) only takes on/off; the SDK
|
|
1123
|
+
then sends that and checks the direction itself, so the calls above work on every pod.
|
|
1124
|
+
|
|
1038
1125
|
An open-drain bus such as I2C must sit on LA1–LA6.
|
|
1039
1126
|
|
|
1040
1127
|
## GPIO on the LA pins
|
|
@@ -1081,7 +1168,7 @@ The other owners point to `bp.sensors.stop("<instance>")`, closing the session f
|
|
|
1081
1168
|
`bp.open_uart()` or `bp.open_spi()`, or waiting for a flash or step train to finish. The pod's own
|
|
1082
1169
|
text, with its raw protocol command, stays in `exc.firmware_message`.
|
|
1083
1170
|
|
|
1084
|
-
`bp.la_pins()` lists every channel's `LaPinState` (`function`, `gpio` mode, `level`, `pull`, `pull_on`),
|
|
1171
|
+
`bp.la_pins()` lists every channel's `LaPinState` (`function`, `gpio` mode, `level`, `pull`, `pull_on`, `pull_dirs`),
|
|
1085
1172
|
and `bp.configure_gpio(channels, mode)` is the same group claim as `gpio_pins()` returning those states.
|
|
1086
1173
|
Captures observe every channel whatever its function. GPIO channels stay GPIO — also across
|
|
1087
1174
|
disconnects — until released (the pytest `benchpod` fixture releases them at session start and end),
|
|
@@ -2218,6 +2305,7 @@ Invalid arguments raise `ValueError` before anything is sent. Everything else ra
|
|
|
2218
2305
|
| `DirectionConflictError` | a push-pull driver on a pin `la_dir` marks as a DUT output (a `FirmwareError`) | `la` |
|
|
2219
2306
|
| `I2CNackError` | an I2C device did not acknowledge (`I2CMaster.write`, `read`, `write_read`, `read_reg`, `write_reg`) | `addr`, `nack_at` |
|
|
2220
2307
|
| `PullConflictError` | an engaged bias resistor can't work with the channel's function (a `FirmwareError`) | `la` |
|
|
2308
|
+
| `PullDirectionError` | the channel can't pull that way (BP0024) or has no pull resistor (BP0023); also a `ValueError` | `la`, `want`, `have` |
|
|
2221
2309
|
| `TriggerTimeout` | a triggered capture's condition never happened (a `FirmwareError`) | `la`, `edge` |
|
|
2222
2310
|
| `CanTimeout` | `CanBus.expect` timed out | `frames` |
|
|
2223
2311
|
|
|
@@ -2284,7 +2372,7 @@ few built from other shapes); `to_dict()` goes the other way where a type is sen
|
|
|
2284
2372
|
| `LanTls` | `lan_tls`, `set_lan_tls_https_only`, `regenerate_lan_tls`, `set_lan_tls_cert` | `port`, `https_only`, `sessions`, `origin` (`generated`/`user`), `key`, `subject`, `san`, `not_after`, `sha256` (what clients pin), `error` (no certificate) |
|
|
2285
2373
|
| `UsbCcStatus` | `usb_cc` | `orientation`, `advertised`, `advertised_current` (A), `cc1_voltage`, `cc2_voltage` (V) |
|
|
2286
2374
|
| `PullState` | `pull_state`, `set_pull` | `la`, `enabled`, `direction`, `ohms`, `available` |
|
|
2287
|
-
| `LaPinState` | `la_pins`, `configure_gpio`, `la_dir` | `la`, `function`, `gpio`, `level`, `pull`, `pull_ohms`, `pull_on`, `dir`, `warn`, `warnings`, `in_use` |
|
|
2375
|
+
| `LaPinState` | `la_pins`, `configure_gpio`, `la_dir` | `la`, `function`, `gpio`, `level`, `pull`, `pull_ohms`, `pull_on`, `pull_dirs`, `dir`, `warn`, `warnings`, `in_use` |
|
|
2288
2376
|
| `GpioPin` (class) | `gpio`, `gpio_pins`, `signal` | `name`, `configure()`, `set(level)`, `high()`, `low()`, `activate()`, `deactivate()`, `is_active()`, `read()`, `wait_for(level, *, timeout)`, `pulse(width, *, count=1)`, `state()`, `release()` |
|
|
2289
2377
|
| `ExtPin` (class) | `gpio`, `gpio_pins`, `signal` on an EXT pin | a `GpioPin` with `ext`, `pin`; `la` is `None`; `pulse()` raises `ExpansionError` |
|
|
2290
2378
|
| `FlashResult` | `flash` | `ok`, `returncode`, `stdout`, `stderr`, `target_unreachable`, `stalled`, `artifact` (the uploaded build, for `flash(build=...)`) |
|
|
@@ -2297,6 +2385,7 @@ few built from other shapes); `to_dict()` goes the other way where a type is sen
|
|
|
2297
2385
|
| `SpiFlashResult` | `spi_flash`, `SpiSession.flash_program` | `jedec_id`, `addr`, `length`, `erased`, `verified`, `seconds` |
|
|
2298
2386
|
| `SpiStreamResult` | `SpiSession.stream` | `sent`, `seconds` |
|
|
2299
2387
|
| `UartCapture` | `capture_uart`, `power_cycle_and_capture` | `text`, `lines`, `matched`, `match(pattern)`, `contains(needle)` (also `needle in capture`) |
|
|
2388
|
+
| `UartEntry` (frozen dataclass) | passed to `open_uart` / `capture_uart` as `entry` | `reset_ms`, `tx_low`, `hold_ms`, `idle_ms`, `data`, `to_request()` |
|
|
2300
2389
|
| `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()` |
|
|
2301
2390
|
| `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()` |
|
|
2302
2391
|
| `SensorEmulation` (class) | `BenchPod.sensors` | see [Emulated sensors](#emulated-sensors) |
|
|
@@ -2359,7 +2448,7 @@ reported keeps its default (`False`, `0` or `""`), so a feature check is just
|
|
|
2359
2448
|
| Identity | `board`, `firmware_version`, `board_rev` (`"v2"`, `"v3"`, `"unknown"`, or `""`), `la_vccio_mv` (the LA bank voltage the pod reports) |
|
|
2360
2449
|
| 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)` |
|
|
2361
2450
|
| 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) |
|
|
2362
|
-
| 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) |
|
|
2451
|
+
| 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) |
|
|
2363
2452
|
| 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) |
|
|
2364
2453
|
| Boot health | `safe_mode`, `safe_reason`, `last_crash`, `reset_cause`, `boot_warning()` (a one-line warning after safe mode or a crash, else `None`) |
|
|
2365
2454
|
| Source | `raw` (the map it was parsed from) |
|
|
@@ -34,7 +34,7 @@ No pin numbers: the SWD channels, the UART pair, the baud and the power rail com
|
|
|
34
34
|
**Contents:** [Install](#install) · [Quick start](#quick-start) ·
|
|
35
35
|
[API conventions](#api-conventions-and-stability) · [pytest plugin](#pytest-plugin) ·
|
|
36
36
|
[Power and reset](#power-reset-and-power-monitoring) · [Flashing](#flashing) · [UART](#uart) ·
|
|
37
|
-
[
|
|
37
|
+
[Pull resistors](#la-pull-resistors) · [Emulated sensors](#emulated-sensors) ·
|
|
38
38
|
[Analog paths](#analog-paths-dc-output-and-single-readings) · [Captures](#captures) ·
|
|
39
39
|
[DAC](#dac-generator-replay-and-faults) · [Control loop](#in-fabric-dac-control-loop) ·
|
|
40
40
|
[CAN](#can) · [AI Vision](#ai-vision-board) · [Cloud](#cloud-embeddedcidevice-name) · [Build reporting](#build-reporting) ·
|
|
@@ -374,7 +374,18 @@ properties `can_gpio`, `can_trigger`, `can_spi`, `can_profile_power`, `can_calib
|
|
|
374
374
|
`can_current_out`, `can_reset_target` and `can_analog` name the common ones (`can_config` …
|
|
375
375
|
`can_disable` stay the CAN bus commands). A call the pod cannot serve raises
|
|
376
376
|
`UnsupportedFeatureError` (see [Errors](#errors)), before anything is sent when the capabilities
|
|
377
|
-
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
|
+
|
|
378
389
|
|
|
379
390
|
```python
|
|
380
391
|
import pytest
|
|
@@ -558,6 +569,7 @@ print(wiring.describe()) # a pin table: bias resistor and
|
|
|
558
569
|
| `la_mv` | not set | LA I/O-bank voltage in mV (1800 or 3300); `wiring.la_voltage` in volts |
|
|
559
570
|
| `efuse` | not set (pass `efuse=`) | target-power rail: 1 internal 5 V, 2 external |
|
|
560
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+ |
|
|
561
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) |
|
|
562
574
|
| `swd_swclk`, `swd_swdio`, `swd_nreset`, `swd_target` | not wired, not wired, `False`, `""` (auto-detect) | flashing |
|
|
563
575
|
| `spi_sclk`, `spi_mosi`, `spi_miso`, `spi_cs` | not wired | decoder channels |
|
|
@@ -567,10 +579,14 @@ print(wiring.describe()) # a pin table: bias resistor and
|
|
|
567
579
|
**Nothing is wired unless the profile says so** (schema version 2, SDK 3.0). A pin the profile does
|
|
568
580
|
not set is never driven, and a call that needs it says which one to pass: `bp.flash()` without
|
|
569
581
|
`swclk`/`swdio` in the profile raises `ValueError: swd_swclk was not given and the wiring profile has
|
|
570
|
-
no swd_swclk`. The
|
|
571
|
-
on LA11/LA12, 3.3 V, internal 5 V),
|
|
572
|
-
`Wiring.preset("embeddedci-
|
|
573
|
-
|
|
582
|
+
no swd_swclk`. The default pins, what profiles used to default to (UART RX on LA5 and TX on LA4, I2C
|
|
583
|
+
SDA on LA1 and SCL on LA2, SWD on LA11/LA12, 3.3 V, internal 5 V), are a preset:
|
|
584
|
+
`Wiring.preset("embeddedci-default")` (the old name `"embeddedci-reference"` still works). They are
|
|
585
|
+
not the wiring of any particular bench: load your board's own profile by name
|
|
586
|
+
(`BenchPod(conn, wiring_profile="process-node-stm32")`, `bp.load_wiring("process-node-stm32")`), as
|
|
587
|
+
the [process-node example](https://github.com/embeddedci-com/examples/tree/main/process-node-stm32)
|
|
588
|
+
does with its `wiring/process-node-stm32.json`. A version 1 file or dict (or one without a `version`
|
|
589
|
+
key) still means what it did: what it leaves out takes the default pins' values, and the profile you
|
|
574
590
|
get back is version 2 with them written out. Re-save such a file as version 2 with
|
|
575
591
|
`benchpod wiring upgrade wiring.json`.
|
|
576
592
|
|
|
@@ -625,7 +641,9 @@ cloud device's single profile on embeddedci.com, and raises over the LAN or USB.
|
|
|
625
641
|
**Power-on applies the profile.** `bp.power_on()` (or `bp.power_on(wiring_profile="k66")`) sets the
|
|
626
642
|
profile's I/O voltage when the pod has none or another one, sets its pull resistors, then switches
|
|
627
643
|
the profile's rail on and records on the pod which profile powered the board (`target_status`).
|
|
628
|
-
`Wiring.pulls`
|
|
644
|
+
`Wiring.pulls` says which pull resistors are on, as a map of channel to direction
|
|
645
|
+
(`{"pulls": {"1": "up", "2": "up", "8": "down"}}` in the JSON) or as a list of channels that pull
|
|
646
|
+
their own direction (`{"pulls": [1, 2]}`); `Wiring.pull_directions()` gives either as the map.
|
|
629
647
|
`power_on` switches exactly those on and the others off. They work at 3.3 V only, so at 1.8 V nothing
|
|
630
648
|
is sent, and a profile without `pulls` (`None`) leaves them as they are. It never changes the I/O
|
|
631
649
|
voltage under a board that is already powered: that raises, and `bp.set_la_voltage()` does it if you
|
|
@@ -641,6 +659,19 @@ A file holds the same JSON object the pod stores:
|
|
|
641
659
|
`bp.signal(name)` returns a GPIO handle for a signal (see [GPIO on the LA pins](#gpio-on-the-la-pins));
|
|
642
660
|
channel arguments accept a role or signal name too (`bp.open_uart(rx="uart_rx", tx=4)`).
|
|
643
661
|
|
|
662
|
+
**The profile on the pod's header.** `bp.board_header()` says which I/O header the pod has:
|
|
663
|
+
`"j1"` (the 2x11 pin headers of the one-piece boards up to v3-r2) or `"front"` (the 2x13 connector
|
|
664
|
+
on the front of digital v3r3 and later), None when the pod cannot tell. `header_map(wiring, header)`
|
|
665
|
+
writes the profile on that header as text: every pin in its physical place, then what to connect
|
|
666
|
+
to each pin on your board (header None writes both headers). The web and desktop apps draw the same
|
|
667
|
+
thing from the Pins pane's Visualize button.
|
|
668
|
+
|
|
669
|
+
```python
|
|
670
|
+
from embeddedci.benchpod import header_map
|
|
671
|
+
|
|
672
|
+
print(header_map(bp.wiring, bp.board_header()))
|
|
673
|
+
```
|
|
674
|
+
|
|
644
675
|
## Power, reset and power monitoring
|
|
645
676
|
|
|
646
677
|
```python
|
|
@@ -964,36 +995,92 @@ 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.
|
|
|
964
995
|
level shifter, and Modbus RTU on RS-485 an external RS-485 transceiver powered at 3.3 V (or a 5 V
|
|
965
996
|
transceiver behind a level shifter), between the pod and the device.
|
|
966
997
|
|
|
998
|
+
**One wire (half duplex).** Some parts talk UART on a single pin, for example a boot ROM's
|
|
999
|
+
programming pin. `half_duplex=True` runs the session on `rx` alone (`tx` defaults to the same
|
|
1000
|
+
channel): the pod only pulls the line low and lets the pull-up hold it high, so the device answers
|
|
1001
|
+
on the same wire, and the pod does not read back its own bytes. Use LA1 to LA6, whose pull-up the
|
|
1002
|
+
pod turns on for the session, or a pull-up on the board.
|
|
1003
|
+
|
|
1004
|
+
**Boot-mode entry.** A boot ROM that picks its mode from the UART pin at reset needs the pin held
|
|
1005
|
+
low while the chip leaves reset, then a byte soon after. `entry=UartEntry(...)` has the pod run that
|
|
1006
|
+
sequence before the session starts, timed on the pod so no network delay sits in between: TX
|
|
1007
|
+
low (`tx_low`), reset for `reset_ms`, release, wait `hold_ms`, release TX, wait `idle_ms`, then send
|
|
1008
|
+
`data` (at most 32 bytes). Times are whole milliseconds, 0 to 1000:
|
|
1009
|
+
|
|
1010
|
+
```python
|
|
1011
|
+
from embeddedci.benchpod import UartEntry
|
|
1012
|
+
|
|
1013
|
+
entry = UartEntry(reset_ms=5, hold_ms=3, idle_ms=2, data=b"\x00")
|
|
1014
|
+
with bp.open_uart(rx=PIN3, half_duplex=True, entry=entry, encoding="latin-1") as uart:
|
|
1015
|
+
reply = uart.read(timeout=0.5)
|
|
1016
|
+
```
|
|
1017
|
+
|
|
1018
|
+
Both need gateware v57 (`bp.supports("uart_hd")`), and `entry` also the pod's reset pin
|
|
1019
|
+
(`bp.supports("nrst_pin")`); older pods raise `UnsupportedFeatureError` before anything is sent.
|
|
1020
|
+
The USB console has neither.
|
|
1021
|
+
|
|
967
1022
|
**Binary protocols.** A session decodes what it receives as UTF-8, which suits a console. For bytes
|
|
968
1023
|
that are not text (a binary protocol's frames), open it with `encoding="latin-1"`: every byte is one
|
|
969
1024
|
character, so `uart.read().encode("latin-1")` gives the bytes back unchanged, and a `bytes` write is
|
|
970
1025
|
sent as is. For the adapter wiring and a Modbus RTU test through a transceiver, see
|
|
971
1026
|
[5 V logic and RS-485](https://www.embeddedci.com/docs/benchpod-targets/5v-rs485).
|
|
972
1027
|
|
|
973
|
-
|
|
1028
|
+
**RS-485 direction (DE).** A half-duplex RS-485 transceiver sends while its DE (tied to /RE) is
|
|
1029
|
+
high and listens while it is low. `de=` names the LA channel wired to DE, and the pod switches it
|
|
1030
|
+
itself: high from before the first start bit of what it sends to the end of the last stop bit, low
|
|
1031
|
+
otherwise. Nothing on the host times it, so a device that answers within a millisecond is still
|
|
1032
|
+
heard (switching DE with `gpio` calls from the host takes tens of milliseconds over the network,
|
|
1033
|
+
and the reply of a fast device is lost meanwhile). `de_active_low=True` inverts it:
|
|
1034
|
+
|
|
1035
|
+
```python
|
|
1036
|
+
with bp.open_uart(rx=PIN5, tx=PIN4, de=PIN9, baud=19200, parity="even",
|
|
1037
|
+
encoding="latin-1") as uart:
|
|
1038
|
+
uart.write(request) # DE goes high and low with the bytes
|
|
1039
|
+
reply = uart.read(timeout=0.2)
|
|
1040
|
+
```
|
|
974
1041
|
|
|
975
|
-
|
|
976
|
-
|
|
1042
|
+
`de` needs gateware v58 (`bp.supports("uart_de")`); older pods raise `UnsupportedFeatureError`
|
|
1043
|
+
before anything is sent. The USB console has no DE.
|
|
977
1044
|
|
|
978
|
-
|
|
1045
|
+
## LA pull resistors
|
|
1046
|
+
|
|
1047
|
+
You name the direction, `"up"`, `"down"` or `"off"`; the pod picks the resistor and reports its
|
|
1048
|
+
value. Which channels have one and which way each can pull depends on the board, and
|
|
1049
|
+
`PullState.supported` says it per channel. On today's boards each resistor pulls one way only:
|
|
1050
|
+
|
|
1051
|
+
| Channels | Pulls | Value |
|
|
979
1052
|
|---|---|---|
|
|
980
|
-
| LA1, LA2 |
|
|
981
|
-
| LA3, LA4 |
|
|
982
|
-
| LA5, LA6 |
|
|
983
|
-
| LA7, LA8 |
|
|
1053
|
+
| LA1, LA2 | up | 4.7k |
|
|
1054
|
+
| LA3, LA4 | up | 2.2k |
|
|
1055
|
+
| LA5, LA6 | up | 10k |
|
|
1056
|
+
| LA7, LA8 | **down** | 10k |
|
|
984
1057
|
| LA9–LA14 | none | — |
|
|
985
1058
|
|
|
1059
|
+
The resistors are referenced to 3V3, so the pod won't engage one while the LA bank is at 1.8 V
|
|
1060
|
+
(`PullState.available` is false).
|
|
1061
|
+
|
|
986
1062
|
```python
|
|
987
1063
|
from embeddedci.benchpod import PIN1, PIN2, PIN7
|
|
988
1064
|
|
|
989
|
-
bp.
|
|
990
|
-
bp.
|
|
991
|
-
|
|
992
|
-
print(bp.
|
|
993
|
-
bp.
|
|
994
|
-
bp.
|
|
1065
|
+
bp.set_pull(PIN1, "up") # PullState(la=1, enabled=True, direction='up', ohms='4.7k', supported=('up',), ...)
|
|
1066
|
+
bp.set_pull(PIN7, "down")
|
|
1067
|
+
bp.set_pull(PIN7, "off") # None is off too; "off" works on every channel
|
|
1068
|
+
print(bp.pull_state(PIN1).state) # 'up' ('up', 'down' or 'off')
|
|
1069
|
+
print(bp.enabled_pulls()) # [1]
|
|
1070
|
+
bp.enable_pullup(PIN1, PIN2) # shortcuts: set_pull(la, "up") ...
|
|
1071
|
+
bp.enable_pulldown(PIN7) # ... and set_pull(la, "down")
|
|
1072
|
+
bp.disable_pullup(PIN1, PIN2) # off, on a channel that pulls up
|
|
995
1073
|
```
|
|
996
1074
|
|
|
1075
|
+
A direction the channel can't pull raises `PullDirectionError` (a `FirmwareError` and a
|
|
1076
|
+
`ValueError`) with code `BP0024`, "LA7 supports pull-down only on this board", and `"up"` or `"down"`
|
|
1077
|
+
on a channel without a resistor raises it with `BP0023`. `.la`, `.want` and `.have` name the channel
|
|
1078
|
+
and the directions. `set_pull(la, True)` / `set_pull(la, False)` (or `enabled=`) still work but are
|
|
1079
|
+
deprecated: True pulls the channel's own direction.
|
|
1080
|
+
|
|
1081
|
+
Firmware before the `la_pull_dir` feature (`bp.supports("la_pull_dir")`) only takes on/off; the SDK
|
|
1082
|
+
then sends that and checks the direction itself, so the calls above work on every pod.
|
|
1083
|
+
|
|
997
1084
|
An open-drain bus such as I2C must sit on LA1–LA6.
|
|
998
1085
|
|
|
999
1086
|
## GPIO on the LA pins
|
|
@@ -1040,7 +1127,7 @@ The other owners point to `bp.sensors.stop("<instance>")`, closing the session f
|
|
|
1040
1127
|
`bp.open_uart()` or `bp.open_spi()`, or waiting for a flash or step train to finish. The pod's own
|
|
1041
1128
|
text, with its raw protocol command, stays in `exc.firmware_message`.
|
|
1042
1129
|
|
|
1043
|
-
`bp.la_pins()` lists every channel's `LaPinState` (`function`, `gpio` mode, `level`, `pull`, `pull_on`),
|
|
1130
|
+
`bp.la_pins()` lists every channel's `LaPinState` (`function`, `gpio` mode, `level`, `pull`, `pull_on`, `pull_dirs`),
|
|
1044
1131
|
and `bp.configure_gpio(channels, mode)` is the same group claim as `gpio_pins()` returning those states.
|
|
1045
1132
|
Captures observe every channel whatever its function. GPIO channels stay GPIO — also across
|
|
1046
1133
|
disconnects — until released (the pytest `benchpod` fixture releases them at session start and end),
|
|
@@ -2177,6 +2264,7 @@ Invalid arguments raise `ValueError` before anything is sent. Everything else ra
|
|
|
2177
2264
|
| `DirectionConflictError` | a push-pull driver on a pin `la_dir` marks as a DUT output (a `FirmwareError`) | `la` |
|
|
2178
2265
|
| `I2CNackError` | an I2C device did not acknowledge (`I2CMaster.write`, `read`, `write_read`, `read_reg`, `write_reg`) | `addr`, `nack_at` |
|
|
2179
2266
|
| `PullConflictError` | an engaged bias resistor can't work with the channel's function (a `FirmwareError`) | `la` |
|
|
2267
|
+
| `PullDirectionError` | the channel can't pull that way (BP0024) or has no pull resistor (BP0023); also a `ValueError` | `la`, `want`, `have` |
|
|
2180
2268
|
| `TriggerTimeout` | a triggered capture's condition never happened (a `FirmwareError`) | `la`, `edge` |
|
|
2181
2269
|
| `CanTimeout` | `CanBus.expect` timed out | `frames` |
|
|
2182
2270
|
|
|
@@ -2243,7 +2331,7 @@ few built from other shapes); `to_dict()` goes the other way where a type is sen
|
|
|
2243
2331
|
| `LanTls` | `lan_tls`, `set_lan_tls_https_only`, `regenerate_lan_tls`, `set_lan_tls_cert` | `port`, `https_only`, `sessions`, `origin` (`generated`/`user`), `key`, `subject`, `san`, `not_after`, `sha256` (what clients pin), `error` (no certificate) |
|
|
2244
2332
|
| `UsbCcStatus` | `usb_cc` | `orientation`, `advertised`, `advertised_current` (A), `cc1_voltage`, `cc2_voltage` (V) |
|
|
2245
2333
|
| `PullState` | `pull_state`, `set_pull` | `la`, `enabled`, `direction`, `ohms`, `available` |
|
|
2246
|
-
| `LaPinState` | `la_pins`, `configure_gpio`, `la_dir` | `la`, `function`, `gpio`, `level`, `pull`, `pull_ohms`, `pull_on`, `dir`, `warn`, `warnings`, `in_use` |
|
|
2334
|
+
| `LaPinState` | `la_pins`, `configure_gpio`, `la_dir` | `la`, `function`, `gpio`, `level`, `pull`, `pull_ohms`, `pull_on`, `pull_dirs`, `dir`, `warn`, `warnings`, `in_use` |
|
|
2247
2335
|
| `GpioPin` (class) | `gpio`, `gpio_pins`, `signal` | `name`, `configure()`, `set(level)`, `high()`, `low()`, `activate()`, `deactivate()`, `is_active()`, `read()`, `wait_for(level, *, timeout)`, `pulse(width, *, count=1)`, `state()`, `release()` |
|
|
2248
2336
|
| `ExtPin` (class) | `gpio`, `gpio_pins`, `signal` on an EXT pin | a `GpioPin` with `ext`, `pin`; `la` is `None`; `pulse()` raises `ExpansionError` |
|
|
2249
2337
|
| `FlashResult` | `flash` | `ok`, `returncode`, `stdout`, `stderr`, `target_unreachable`, `stalled`, `artifact` (the uploaded build, for `flash(build=...)`) |
|
|
@@ -2256,6 +2344,7 @@ few built from other shapes); `to_dict()` goes the other way where a type is sen
|
|
|
2256
2344
|
| `SpiFlashResult` | `spi_flash`, `SpiSession.flash_program` | `jedec_id`, `addr`, `length`, `erased`, `verified`, `seconds` |
|
|
2257
2345
|
| `SpiStreamResult` | `SpiSession.stream` | `sent`, `seconds` |
|
|
2258
2346
|
| `UartCapture` | `capture_uart`, `power_cycle_and_capture` | `text`, `lines`, `matched`, `match(pattern)`, `contains(needle)` (also `needle in capture`) |
|
|
2347
|
+
| `UartEntry` (frozen dataclass) | passed to `open_uart` / `capture_uart` as `entry` | `reset_ms`, `tx_low`, `hold_ms`, `idle_ms`, `data`, `to_request()` |
|
|
2259
2348
|
| `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()` |
|
|
2260
2349
|
| `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()` |
|
|
2261
2350
|
| `SensorEmulation` (class) | `BenchPod.sensors` | see [Emulated sensors](#emulated-sensors) |
|
|
@@ -2318,7 +2407,7 @@ reported keeps its default (`False`, `0` or `""`), so a feature check is just
|
|
|
2318
2407
|
| Identity | `board`, `firmware_version`, `board_rev` (`"v2"`, `"v3"`, `"unknown"`, or `""`), `la_vccio_mv` (the LA bank voltage the pod reports) |
|
|
2319
2408
|
| 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)` |
|
|
2320
2409
|
| 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) |
|
|
2321
|
-
| 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) |
|
|
2410
|
+
| 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) |
|
|
2322
2411
|
| 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) |
|
|
2323
2412
|
| Boot health | `safe_mode`, `safe_reason`, `last_crash`, `reset_cause`, `boot_warning()` (a one-line warning after safe mode or a crash, else `None`) |
|
|
2324
2413
|
| Source | `raw` (the map it was parsed from) |
|
|
@@ -110,6 +110,7 @@ from .errors import (
|
|
|
110
110
|
PodLeasedError,
|
|
111
111
|
PodLockedError,
|
|
112
112
|
PullConflictError,
|
|
113
|
+
PullDirectionError,
|
|
113
114
|
TargetUnreachableError,
|
|
114
115
|
TlsPinMismatchError,
|
|
115
116
|
TransportError,
|
|
@@ -161,17 +162,19 @@ from .state import (
|
|
|
161
162
|
TargetStatus,
|
|
162
163
|
UsbCcStatus,
|
|
163
164
|
)
|
|
164
|
-
from .uart import UartCapture, UartSession
|
|
165
|
+
from .uart import UartCapture, UartEntry, UartSession
|
|
165
166
|
from .spi import SpiFlashInfo, SpiFlashResult, SpiSession, SpiStreamResult
|
|
166
167
|
from . import motor_emulator
|
|
167
168
|
from .motor_emulator import BatteryModel, EmulatorCalibration, MotorEmulator
|
|
168
169
|
from .waveforms import Waveform, WaveformLibrary
|
|
169
170
|
from .wiring import Signal, Wiring
|
|
171
|
+
from .header import header_map
|
|
170
172
|
|
|
171
173
|
__all__ = [
|
|
172
174
|
"BenchPod",
|
|
173
175
|
# wiring profile
|
|
174
176
|
"Wiring",
|
|
177
|
+
"header_map",
|
|
175
178
|
"Signal",
|
|
176
179
|
# LA pin modes + GPIO
|
|
177
180
|
"GpioPin",
|
|
@@ -212,6 +215,7 @@ __all__ = [
|
|
|
212
215
|
# flash + UART
|
|
213
216
|
"FlashResult",
|
|
214
217
|
"UartCapture",
|
|
218
|
+
"UartEntry",
|
|
215
219
|
"UartSession",
|
|
216
220
|
"SpiSession",
|
|
217
221
|
"SpiFlashInfo",
|
|
@@ -353,6 +357,7 @@ __all__ = [
|
|
|
353
357
|
"CanTimeout",
|
|
354
358
|
"PinConflictError",
|
|
355
359
|
"PullConflictError",
|
|
360
|
+
"PullDirectionError",
|
|
356
361
|
"DirectionConflictError",
|
|
357
362
|
"TriggerTimeout",
|
|
358
363
|
"UnsupportedFeatureError",
|