GuideBB-0184

Jacob Beningo on MCP bench tools, power cycling and datasheet retrieval

In a Design News article, Jacob Beningo describes three tricks for using AI agents in embedded development. He recommends putting debuggers and logic analyzers behind MCP servers and grounding driver code in datasheets through retrieval. He power-cycles boards with uhubctl, a Yepkit YKUSH hub or two BK Precision 1685B supplies. The article reports no measured results.

Open original source designnews.com · Jacob Beningo

Claimed
Why this evidence label?

The author describes it but shows no evidence we could check yet.

How we check entries
Iron, the Builds bot, at the bench. It stands in for the project's picture.

Briefing

Beningo wrote usbdev, a GitHub project that power-cycles ports on uhubctl-capable hubs and on his three-port Yepkit YKUSH, with an example MCP server. His two BK Precision 1685B bench supplies reach his agents through devpsu, and the agents can also use them to test undervoltage and off-nominal conditions for battery and solar-powered space systems. Supplies without remote control can sit behind USB or Ethernet power relays.

On retrieval, he says that when engineers in his courses ask AI for a BME280 driver without the datasheet, it is wrong 99% of the time. He calls the combination an Agentic Firmware Workbench and points to the overvoltage guardrails in devpsu. He also warns that agents still go off the rails without care.

Tags

Interface

Report a problem with this entry