Design decisions

Every testbed requires a unique name. This here is called testbed_showcase.

Note

Other testbed could be:

  • testbed_modbus: Modbus RTU is very time critical, specially timeouts/retires. This testbed could test these timing aspects, specially in error and race condition.

  • testbed_I2C_multicontroller: In multicontroller (multimaster) mode many special situations an race condition may occur. This testbed could provide the hardware to create error conditions like shortening the bus. It may be tested if and how the software recovers from these errors.

  • …

testbed_showcase is designed to demonstrates the various aspects of octoprobe. But also allows to write/run meaningful tests.

Block diagram

../../_images/block_diagram.drawio.png

Testing the pico firmware agains I2C and capture with DAQ

../../_images/block_diagram_pico.drawio.png

Testing the pyboard firmware agains I2C and capture with DAQ

../../_images/block_diagram_pyboard.drawio.png

Every testbed must specify:

Signals

See Signals

Tentacle Roles

See Tentacle roles

FUTs (FUT: Feature Under Test)

See Features under Test