The Temboo Agent now includes a dedicated mode for conducting in-depth runtime analysis on embedded systems.

Getting your embedded code to build feels like progress, but it doesn’t tell you much about how the system actually works. That tricky question can only be answered when you start running your firmware on real hardware.

Does it still work when physical sensors are connected? Are threads behaving as expected? Is memory usage acceptable? And lots more besides.

Earlier this year, we introduced runtime analysis in the Temboo Agent to give developers a way to work with the agent to understand runtime behavior. Now we’ve extended that work into a dedicated Runtime Analysis mode for the moments in your dev cycle when you need to examine your system in much greater depth.

A Deeper Look

Runtime Analysis mode is for when you’ve reached a meaningful checkpoint in your dev process and you want to know what your firmware is really doing. Maybe you’ve added a new feature, completed a significant refactor, connected real peripherals, or you’re working towards merging or releasing. This is when Runtime Analysis mode makes most sense.

When you request a report, the Temboo Agent inspects your system and determines which tests are appropriate. Depending on the nature of your application, the analysis will cover things like:

• Thread and task behaviour
• Memory usage and stability
• CPU performance
• Power consumption
• Timing behaviour
• General system health

The Temboo Agent runs the tests, analyzes the results, and generates a detailed report that explains what it observed, where potential issues can be found, and which optimizations should be considered.

The finished report can be copied or downloaded for use in tickets, code reviews, release documentation, internal discussions, or whatever best fits the way you and your team work.

Adding Embedded Experience to AI Workflow

General-purpose coding agents are becoming increasingly useful for embedded development. This is primarily thanks to semiconductor vendors making their documentation, SDKs, and tooling available through MCP.

While this is a great and welcome development, access to docs and tools is not the same as knowing how to use them to support an effective embedded development workflow.

A developer shouldn’t need to devise the perfect series of prompts every time they want to investigate thread behaviour, assess power consumption, or figure out if a requirement has been met. That’s why embedded-specific agents are better suited to the task.

In Runtime Analysis mode, you don’t have to specify every individual test in advance because the Temboo Agent knows what to do. It examines the system, determines which tests are appropriate, plans and carries them out, analyzes the results, and packages the findings into a detailed report.

This approach is at the heart of how we’re building the Temboo Agent. Our goal is not to be just another way to generate embedded code, but to create an AI-native product experience that helps developers move through the full embedded systems lifecycle, from requirements and architecture, to testing and iterative improvements.

The new Runtime Analysis mode is just one example of how embedded engineering specifics can be packaged into repeatable workflows that learn from past executions and improve over time, and there’s lots more to come under this umbrella.

Try Runtime Analysis Mode

Runtime Analysis mode is available now in the Temboo Agent.