Error codes

When the pod refuses a request, the SDK, the CLI, the MCP server and the apps show a stable code such as BP0001, what went wrong and how to fix it. A code never changes meaning and is never reused, so you can match on it in tests and scripts instead of on the message text.

In Python the code is on the exception: FirmwareError.code (and .values for the values that go with it, a dict). The CLI prints it with every refusal, and benchpod explain BP0001 shows this page's entry offline. Pods with older firmware send no code: see Updating the firmware.

CodeMessage
BP0001The I/O voltage is not set
BP0002The pod does not know the command {cmd}
BP0003An I2C session is already open
BP0004An SPI session is already open
BP0005The engine that runs SWD, SPI and I2C is in use, so {want} cannot start
BP0006The request is missing {arg}
BP0007The pod has no wiring profile named {name}
BP0008{name} is not a valid wiring profile name
BP0009The wiring profile {name} changed since it was loaded (it is now at revision {rev})
BP0010The pod cannot hold another wiring profile (at most {max}, and 16 KB in all)
BP0011The wiring profile is {bytes} bytes; the pod takes at most {max}
BP0012The wiring profile is not one JSON object
BP0013{name} is the pod's default wiring profile and cannot be deleted
BP0014The wiring profile upload skipped ahead (the pod expected offset {expected})
BP0015The pod could not read or write its wiring profiles
BP0016The pod cannot save now: the DAC or a capture is using the bus the storage shares
BP0017{feature} needs gateware v{min} or later
BP0018UART rx and tx are both LA{la}; a one-wire UART needs half_duplex
BP0019half_duplex runs on one pin, but rx is LA{rx} and tx is LA{tx}
BP0020The UART entry sequence needs the pod's reset pin, which this board does not have
BP0021The UART entry option {arg} is out of range (0 to {max})
BP0022The UART's DE pin LA{la} is also its rx or tx
BP0023LA{la} has no pull resistor on this board
BP0024LA{la} supports pull-{have} only on this board
BP0025{holder} holds this pod ({purpose}, {left_s} s left)
BP0026The pod's lease was stopped by {by}
BP0027The pod holds no lease with id {id}

I/O voltage and pins

BP0001

la_voltage_not_set
next firmware

The I/O voltage is not set

The pod starts with its I/O voltage unset and never picks one on its own, so it cannot drive a board at a voltage the board does not take. Anything that uses the LA pins (UART, flashing, captures, GPIO, I2C, SPI, sensor emulation) needs it first.

set the board's I/O voltage first: BenchPod(conn, la_voltage=3.3) (1.8 for a 1.8 V board), the benchpod_la_voltage fixture in conftest.py, or bp.set_la_voltage(3.3)

BP0023

la_no_pull
next firmware

LA{la} has no pull resistor on this board

Only some LA channels have a pull resistor the pod can switch, and which ones depends on the board. la_pins lists each channel's pull and the directions it supports.

Values sent with it: la (number)

pick a channel with a pull resistor (bp.la_pins() shows them), or add one on the board

BP0024

la_pull_direction
next firmware

LA{la} supports pull-{have} only on this board

The pull resistor on LA{la} is wired one way on this board, so it cannot pull {want}. Which way each channel pulls depends on the board; la_pins lists it.

Values sent with it: la (number), want (text), have (text)

use bp.set_pull({la}, "{have}"), or pick a channel that pulls {want} (bp.la_pins() shows them)

Commands and firmware

BP0002

unknown_command
next firmware

The pod does not know the command {cmd}

The firmware on the pod is older than the tool that sent the command, or the command name is wrong. Newer SDK, CLI and MCP versions check the pod's capabilities first and say which firmware a feature needs.

Values sent with it: cmd (text)

update the pod's firmware (benchpod flash-self, or the firmware update in the web app)

BP0006

missing_argument
next firmware

The request is missing {arg}

A required value was not sent. The SDK, CLI and MCP always send it, so this usually means a hand-written protocol request or a tool older than the firmware.

Values sent with it: arg (text)

pass {arg}; if you did, update the SDK (pip install -U embeddedci)

I2C

BP0003

i2c_session_open
next firmware

An I2C session is already open

The pod runs one I2C master session at a time.

close the open session first (its close(), or leave its with block)

SPI, SWD and the shared engine

BP0004

spi_session_open
next firmware

An SPI session is already open

The pod runs one SPI master session at a time.

close the open session first (its close(), or leave its with block)

BP0005

bus_engine_busy
next firmware

The engine that runs SWD, SPI and I2C is in use, so {want} cannot start

Flashing (SWD), the SPI master and the I2C master share one engine on the pod. While one of them runs, the other two wait.

Values sent with it: want (text)

wait for the running flash, SPI or I2C session to finish (close it), then try again

Wiring profiles

BP0007

wiring_profile_not_found
next firmware

The pod has no wiring profile named {name}

Wiring profiles live on the pod. This one was never saved there, was deleted, or was saved on another pod.

Values sent with it: name (text)

list the pod's profiles with bp.wiring_profiles(), or save this one first with bp.save_wiring(profile, name="{name}")

BP0008

wiring_bad_name
next firmware

{name} is not a valid wiring profile name

Profile names are 1 to 40 characters: lowercase letters, digits and dashes, not starting with a dash.

Values sent with it: name (text)

use a name like "nrf52840-dk" or "k66"

BP0009

wiring_revision_conflict
next firmware

The wiring profile {name} changed since it was loaded (it is now at revision {rev})

Someone saved {name} from another connection (the web app, another script or agent) after this one loaded it. Saving now would overwrite their change, so the pod refuses.

Values sent with it: name (text), rev (number)

load it again (bp.load_wiring("{name}")), redo your change and save, or save under another name

BP0010

wiring_store_full
next firmware

The pod cannot hold another wiring profile (at most {max}, and 16 KB in all)

Wiring profiles live on the pod, in a fixed amount of storage.

Values sent with it: max (number)

delete a profile you no longer use (bp.delete_wiring("name")) or replace an existing one

BP0011

wiring_profile_too_large
next firmware

The wiring profile is {bytes} bytes; the pod takes at most {max}

One wiring profile fits in {max} bytes of JSON. Long signal descriptions or many signals add up.

Values sent with it: bytes (number), max (number)

shorten the signal descriptions, or split the board into two profiles

BP0012

wiring_not_json_object
next firmware

The wiring profile is not one JSON object

The pod stores a profile as the JSON object the tools send. This one is cut off or not an object, which points at a damaged upload or a hand-written request.

save it again; if it keeps failing, check the profile is valid (Wiring.from_dict)

BP0013

wiring_delete_default
next firmware

{name} is the pod's default wiring profile and cannot be deleted

A connection that names no profile uses the default, so the pod always keeps one.

Values sent with it: name (text)

make another profile the default first (bp.set_default_wiring("other")), then delete {name}

BP0014

wiring_upload_out_of_order
next firmware

The wiring profile upload skipped ahead (the pod expected offset {expected})

Profiles are sent to the pod in pieces, in order, starting at offset 0. A piece went missing or another upload started in between.

Values sent with it: expected (number)

save again

BP0015

wiring_storage_failed
next firmware

The pod could not read or write its wiring profiles

The flash chip that holds the profiles did not answer or a write did not verify. Profiles saved before are kept: a write never replaces them until it has been read back.

try again; if it keeps failing, power-cycle the pod and report it

BP0016

storage_busy
next firmware

The pod cannot save now: the DAC or a capture is using the bus the storage shares

The flash chip that holds the wiring profiles shares a bus with the DAC replay and the captures. Saving would stop a running waveform, so the pod refuses instead. Reading profiles always works.

stop the DAC (bp.dac_stop()) or wait for the capture to finish, then save again

firmware

BP0017

gateware_too_old
next firmware

{feature} needs gateware v{min} or later

The pod's FPGA image is older than the feature. Firmware updates bring the matching gateware with them.

Values sent with it: feature (text), min (number)

update the pod's firmware (benchpod flash-self, or the firmware update in the web app)

uart

BP0018

uart_same_pin
next firmware

UART rx and tx are both LA{la}; a one-wire UART needs half_duplex

A normal UART drives its TX pin all the time, so it cannot share the pin with RX. In half duplex the pod only pulls the line low and lets the pull-up hold it high, so both sides can talk on one wire.

Values sent with it: la (number)

pass half_duplex=True for a one-wire UART, or put rx and tx on two LA channels

BP0019

uart_half_duplex_two_pins
next firmware

half_duplex runs on one pin, but rx is LA{rx} and tx is LA{tx}

In half duplex the pod sends and receives on the same wire, so rx and tx name the same LA channel.

Values sent with it: rx (number), tx (number)

give the same LA channel for rx and tx, or leave half_duplex off

BP0020

uart_entry_no_reset_pin
next firmware

The UART entry sequence needs the pod's reset pin, which this board does not have

The entry sequence holds the target in reset with the pod's own reset pin while it holds TX low. Pods before v3 have no reset pin.

use a v3 pod, or open the UART without entry and reset the target yourself

BP0021

uart_entry_invalid
next firmware

The UART entry option {arg} is out of range (0 to {max})

The entry sequence times are milliseconds, each up to a limit, and the first bytes are at most a few dozen hex bytes.

Values sent with it: arg (text), max (number)

pass {arg} between 0 and {max}

BP0022

uart_de_pin
next firmware

The UART's DE pin LA{la} is also its rx or tx

DE switches an RS-485 transceiver between sending and listening, so it is a wire of its own, from an LA channel to the transceiver's DE and /RE pins.

Values sent with it: la (number)

give de the LA channel wired to the transceiver's DE and /RE, not rx or tx

lease

BP0025

lease_busy
next firmware

{holder} holds this pod ({purpose}, {left_s} s left)

Someone took the pod's lease (a CI run, an SDK or CLI session, or a cloud job). While it is held, only its owners may drive the pod; everyone else may still read status and other light reads. The lease ends when its owner releases it, when it is not renewed in time, or when the pod restarts.

Values sent with it: holder (text), purpose (text), left_s (number)

wait until {holder} is done (about {left_s} s); a process of the same run joins its lease with lease_acquire and the same id

BP0026

lease_lost
next firmware

The pod's lease was stopped by {by}

This connection or this lease id owned the pod's lease, and {by} stopped it from the web app or the cloud. The command was not run. A connection that owned it hears this once. A command, lease_acquire or lease_renew that carries the stopped lease's id keeps getting it for 30 minutes, so a run that was stopped does not take the pod back; a new id gets a new lease.

Values sent with it: by (text)

the run was stopped on purpose: end it, or take a new lease (lease_acquire) if it should go on

BP0027

lease_not_held
next firmware

The pod holds no lease with id {id}

lease_renew found no lease: it ran out (it was not renewed before its deadline), it was released, or the pod restarted, which clears it. A lease that was stopped answers BP0026 instead.

Values sent with it: id (text)

take the lease again with lease_acquire; renew it well before its ttl_s runs out