Repository navigation
STM32 bench-pod firmware v3.10.8
BenchPod firmware 3.10.8: wiring profiles stored on the pod, stable error codes, UART parity and stop bits, and the pod's MAC addresses in status. Gateware v56.
New
-
Wiring profiles live on the pod. The pod keeps up to 16 named wiring profiles (which board signal is on which pin, the I/O voltage, the power rail), one of them the default, so every connection sees the same ones: Ethernet, USB and the cloud, from any computer. New commands
wiring_list,wiring_get,wiring_put,wiring_deleteandwiring_default. Saving a profile someone else changed since you loaded it is refused, so two people cannot overwrite each other. Use them with SDK/MCP 3.0.0 (bp.save_wiring,bp.load_wiring,save_wiringin the MCP), CLI 0.9.0 (benchpod wiring list|show|save|default|delete) or the web app's Wiring tab. -
Power on with a profile.
target_powertakesprofile: the pod records which wiring profile the board was powered on with, andtarget_statusreports it for every rail, so every tool shows which wiring the board runs with, whoever turned it on. The SDK, MCP and web app set the profile's I/O voltage first. -
Stable error codes. Refusals now carry a code (
BP0001and up) and the values that go with it, next to the message. Codes never change meaning and are never reused; each one is explained, with the fix, on https://www.embeddedci.com/docs/errors. Tools should match on the code, not on the text. SDK 3.0.0 (FirmwareError.code), CLI 0.9.0 (benchpod explain BP0009) and the MCP show the fix. -
UART parity and stop bits (gateware v56). The UART proxy takes
parity(none, even, odd) andstop_bits(1, 2), for devices that are not 8N1: 8E1, 8O1, 8N2, 8E2. A wrong parity bit is flagged (uart_rx_parity_errorinstatus). The pod's pins stay 1.8/3.3 V: a 5 V serial device needs a level shifter, and Modbus RTU on RS-485 needs an external 3.3 V RS-485 transceiver between the pod and the bus. SDK/MCP 3.0.0 and the web terminal support it. -
MAC addresses in
status.eth_macand, on pods with Wi-Fi,wifi_mac, for networks that register a device's MAC before giving it an address. A Wi-Fi scan now also learns the Wi-Fi MAC on a pod that never joined a network.benchpod statusandbenchpod discovershow them.
Fixed
- The UART status read cleared its error flags too early, so overflow, framing error and parity error always read 0. They now report.
Release assets
- The release also publishes
benchpod-wifi-bridge-plain.zip, the Wi-Fi bridge's factory set without secure boot or flash encryption, for flashing new bridges.
Tested
- The release candidate (main 8adc25d, gateware v56) on a BenchPod analog v3r2 (benchpod-30a9f1), over Ethernet:
- Wiring profiles: save, load on a new connection, the stale-save refusal (BP0009), deleting the default refused (BP0013), power on with a profile (sets 3.3 V and records it), power off clears it; the same through CLI 0.9.0 and MCP 3.0.0: 18 checks passed.
- SDK end-to-end 158 passed (68 skipped: features this bench has no wiring for), MCP 9, OpenHTF 2.
- UART parity before the merge, on the same pod with a NUCLEO-F446RE: 8E1, 8O1, 8N2 and 8E2 echo loopback 256/256 bytes on all three gateware images, a parity mismatch flagged on both sides.
- MAC addresses on the same pod over Ethernet and USB, the Wi-Fi MAC after a scan.
- The published build on two pods, a BenchPod analog v3r2 and a BenchPod v3 with the analog module, installed with
benchpod flash-self(signed firmware and gateware blobs): wiring profiles 18 checks passed on each, SDK end-to-end 158 passed on each, MCP 9, OpenHTF 2.