Chat to Chip Firmware Flashing
Chat to Chip is the path from a conversation with a coding/chat agent to firmware programmed onto your DUT. The agent writes a YAML test plan using the Blue Clover Devices Agent Kit, the PLT runs it, and a Test Agent with an attached Flashr programs the target through a Tag-Connect cable.
Hardware chain
Stage |
Part |
Role |
|---|---|---|
Production Line Tool |
Orchestrates the test. Runs the YAML test plan and drives the Test Agent over USB. |
|
Test Agent |
Linux SBC running agentOS. |
|
Flashr |
USB programming device running flashOS. Communicates with the MCU in real time over I2C, JTAG, SPI, or SWD. |
|
DUT |
The target being programmed. The Bento Board (RP2350B) is the example programming target; see its Flashr test plan. |
Connections
Connect the Test Agent’s Type-C USB port to one of the PLT’s peripheral Type-A USB ports, and power the Test Agent externally. See Blue Clover Test Agent PER-101.
Connect the Flashr to a USB port on the Test Agent. Attach only one Flashr to each Test Agent.
Connect the Flashr to the DUT’s programming port.
From chat to chip
Chat: Install the Blue Clover Devices Agent Kit in your agent. Its skills carry the PLT command reference, so the agent can write and debug test plans for this hardware.
Plan: The agent produces a YAML test plan that sends the firmware image to the Test Agent with agentCfg - Configure Agent and programs it with agentExec - Execute command on Agent.
Deploy: Release the test plan and firmware to the PLT through PLTcloud Reference.
Flash: The PLT runs the plan. The Test Agent executes flashr-flash - Program a target through Flashr, and the Flashr writes, verifies, and resets the target.
Example test plan
title: "Program DUT with Flashr"
suite:
- title: "Setup Test Agent"
steps:
- command: agentCfg AGENT
with:
- firmware.hex
- title: "Program DUT"
steps:
- command: agentExec AGENT "flashr-flash nrf52 /run/pltagent/mnt/firmware.hex"
timeout: 2m