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.
| Code | Message |
|---|---|
| BP0001 | The I/O voltage is not set |
| BP0002 | The pod does not know the command {cmd} |
| BP0003 | An I2C session is already open |
| BP0004 | An SPI session is already open |
| BP0005 | The engine that runs SWD, SPI and I2C is in use, so {want} cannot start |
| BP0006 | The request is missing {arg} |
| BP0007 | The pod has no wiring profile named {name} |
| BP0008 | {name} is not a valid wiring profile name |
| BP0009 | The wiring profile {name} changed since it was loaded (it is now at revision {rev}) |
| BP0010 | The pod cannot hold another wiring profile (at most {max}, and 16 KB in all) |
| BP0011 | The wiring profile is {bytes} bytes; the pod takes at most {max} |
| BP0012 | The wiring profile is not one JSON object |
| BP0013 | {name} is the pod's default wiring profile and cannot be deleted |
| BP0014 | The wiring profile upload skipped ahead (the pod expected offset {expected}) |
| BP0015 | The pod could not read or write its wiring profiles |
| BP0016 | The pod cannot save now: the DAC or a capture is using the bus the storage shares |
I/O voltage and pins
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)
Commands and 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)
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
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
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)
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
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}")
{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"
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
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
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
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)
{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}
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
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
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