Skip to content

STM32 bench-pod firmware v3.10.4

Choose a tag to compare

@github-actions github-actions released this 13 Nov 21:29
· 155 commits to main since this release
75380b4

BenchPod firmware 3.10.4 with gateware v55. The pod can now drive buses, not only listen to them.

New

  • I2C master on any two LA pins at 100 kHz, 400 kHz or 1 MHz: i2c_start, i2c_xfer (write, read, or write then read), i2c_scan, i2c_status, i2c_stop. Clock stretching is supported. With "pullups":"pod" the pins must be LA1 to LA6 with the pod's pull-up switched on, at 3.3 V; the pod never switches a pull-up by itself. On a real bus SCL runs a little slower than the rate asked, because the rise time adds to every clock period, and never faster.
  • SPI modes 1 and 2, next to modes 0 and 3.
  • Pin direction safety: la_dir marks each LA pin as a DUT input, a DUT output or bidirectional. The pod refuses a push-pull output (gpio output, UART TX, SPI clock and data, SWD, sensor outputs) on a pin wired to a DUT output, whichever is set first. Pin listings now show each pin's direction and a warning when a pull resistor sits under a push-pull output, or when a pin is driven high or pulled up while target power is off.
  • Send and capture: la_capture takes an optional send (an I2C transfer, an SPI frame or a gpio level) that runs right after the capture is armed. It is one command, so it also works over the cloud.
  • sensor_la waits for the bus's next START by default (trigger, timeout_ms).

Changed

  • The firmware checks the running gateware by image identity, not only by version.

Tested

On a BenchPod analog v3r2 with the process-node example: the whole process-node suite passed (137 passed, 4 skipped), including the new bus-master tests (I2C at all three speeds against the node as a target, send and capture with decode, SPI modes 0 to 3, gpio send, pin direction refusals), and the deep-replay image tests.

Use the new commands from the SDK and MCP 2.13.13 and CLI 0.8.9 or later.