What you’ll do
1
Connect an agent
Connect an agent once. A client that can add a remote HTTP MCP server signs in through the browser. Setup for each client is on Connect an agent.
2
Build the ELF
Build the ELF. You can compile it on your side, and Chiplab runs that binary as-is. A Chiplab build job is coming soon: your agent starts it from the tools it discovers when it connects, then downloads the artifacts.
3
Run it on the target board model
Your agent uploads the ELF and runs it on the target board model, with the UARTs to capture. Only the UARTs you list are captured. The STM32F4 Discovery model is
stm32f4_discovery, and its examples write usart2.4
Read the UART output
The run returns a
run_id immediately. Your agent waits for the job, then downloads stdout, the captured UART output. The run lasts up to 5 seconds of virtual time by default and ends early if the firmware finishes or panics.Ask your agent
What you get back
You get a status (running, succeeded, or failed) and stdout for the UARTs you captured. On the STM32F4 Discovery examples, usart2 prints Hello world!.
Next
build
Compile firmware as a job on the project.
run
Execute an ELF on a virtual board and read the UART.