Set up STEPico for the biosignal monitor.

STEPico setup · six steps

For a new board, follow all six steps. A board already running compatible MicroPython with st7789 can continue at step 5. These instructions adapt the manufacturer’s STEPico setup guide to the biosignal monitor’s display driver and source files.

1. 1

   Prepare Thonny and USB

   Install Thonny from thonny.org. Connect STEPico with a USB-C data cable.

2. 2

   Choose the firmware

   Use an RP2040 / Raspberry Pi Pico build that provides the st7789 display driver. The builder’s working board reports MicroPython 1.20.0; the exact original firmware image is unavailable. The driver project provides precompiled RP2 firmware as an upstream reference.

3. 3

   Enter BOOT mode

   Hold BOOT, press and release RUN, then release BOOT. Alternatively, hold BOOT while plugging in USB. A drive named RPI-RP2 should appear.

4. 4

   Transfer the UF2 image

   Drag the compatible .uf2 file onto RPI-RP2. STEPico restarts and the drive disappears. This installs the runtime; Python files are transferred through Thonny afterwards.

5. 5

   Connect the interpreter

   In Thonny, select the MicroPython Raspberry Pi Pico / RP2040 interpreter and the board’s serial port. Open the Shell. For a new installation, import st7789 to confirm that the display driver is available.

6. 6

   Copy and start the project

   Extract application-source.zip. In Thonny’s Files view, copy the four root Python files and the max30102 folder to the device root, preserving both files inside that folder. Open main.py and choose Run current script (F5).

A .uf2 file installs the board’s runtime. main.py and its libraries are copied into that runtime’s filesystem through Thonny. The st7789 project’s precompiled RP2 firmware is an upstream driver-inclusive reference; it has not been confirmed as the builder’s original image.

Directory structure

The two MAX30102 files belong inside the max30102 directory. The other four Python files belong in the device root. The supplied filenames containing upload suffixes have already been normalised in the source ZIP.

Supplied firmware references

UF2 block structure and internal version strings were inspected. These three uploaded files are references; they do not identify the current board’s reported 1.20.0 image. Their display-driver compatibility has not been established, and they are not bundled as project firmware.