← Latest papers
🤖 AI

EstRTL: Functional Estimation Guided RTL Code Generation

This paper introduces EstRTL, a three-stage LLM-powered collaborative agent framework that enhances the functional correctness of generated RTL code through static functional score estimation, achieving a 3.2%–9.0% improvement over generic models.

Original authors: Qi Xiong, Renzhi Chen, Bowei Wang, Yuqing Xiong, Libo Huang, Lei Wang

Published 2026-06-10
📖 4 min read☕ Coffee break read

Original authors: Qi Xiong, Renzhi Chen, Bowei Wang, Yuqing Xiong, Libo Huang, Lei Wang

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are trying to build a complex machine, like a high-performance car engine, but instead of using wrenches and blueprints, you are asking a very smart, well-read robot to write the instructions for you. In the world of computer chips, these instructions are called RTL code (Register Transfer Level).

The problem is that while these robots (called Large Language Models or LLMs) are great at writing sentences, they often make silly mistakes when writing these technical instructions. They might mix up a "stop" sign with a "go" sign, or put a gear in the wrong place. Usually, checking if the engine actually works requires building a massive, expensive test track (called a "testbench") to run the car, which takes a lot of time and money.

Enter EstRTL: The "Quality Control" Team

The paper introduces EstRTL, a new system that acts like a three-person quality control team working together to fix the robot's mistakes before the engine is ever built. Instead of just asking the robot to "do it again," this system uses a clever loop of Generation, Estimation, and Correction.

Here is how the team works, using a simple analogy:

1. The Generator (The Architect)

First, the Code Generation Agent is the architect. It listens to your request (e.g., "Build a counter that counts to 255") and draws up the initial blueprints (the RTL code).

  • The Check: Before anyone looks at the design, a grammar checker ensures the blueprints aren't nonsense (like missing brackets or typos). If the blueprints are grammatically wrong, the architect redraws them immediately.

2. The Estimator (The Intuitive Inspector)

This is the paper's biggest innovation. Usually, to know if a blueprint works, you have to build the whole engine and test it. That's slow.

  • The Trick: The Functional Estimation Agent is like a super-intuitive inspector who looks at the blueprint and says, "I haven't built this yet, but based on the design, it looks 85% likely to work."
  • How it works: It doesn't build the engine. Instead, it reads the blueprint and tries to write a description of what the machine should do. Then, it compares that description to your original request.
    • Analogy: If you asked for a "red sports car," and the blueprint describes a "blue truck," the inspector knows immediately that something is wrong, even without seeing the car.
  • The Decision:
    • If the score is low (the design looks terrible), the inspector sends it back to the Architect to start over completely.
    • If the score is medium (the design is okay but has some flaws), it sends it to the Fixer.

3. The Corrector (The Mechanic)

The Code Correction Agent is the mechanic. It doesn't just guess; it uses a "Chain of Thought" process.

  • The Process: It first asks, "Where exactly is the problem? Why is it happening?" (e.g., "The gear is on the wrong axle because the robot confused 'left' with 'right'").
  • The Fix: Once it understands the why, it rewrites the specific part of the blueprint to fix the error. It then sends the fixed blueprint back to the Inspector to double-check.

Why is this a big deal?

The paper claims that by adding this "Inspector" and "Mechanic" team to the process, the system significantly improves the success rate of the robots.

  • The Results: When they tested this on a standard set of 156 hardware design tasks, the system improved the accuracy of the robots by 3.2% to 9%.
  • The Efficiency: The "Inspector" was able to tell the difference between a working design and a broken one with about 78% accuracy without needing to build the expensive test track.
  • The Fixer: The mechanic successfully fixed over 12% of the errors that the robots made on their own.

The Bottom Line

Think of EstRTL as a safety net. Instead of trusting a robot to get it perfect on the first try (which it rarely does), this system creates a loop where the robot writes, an AI inspector grades it, and an AI mechanic fixes the bad parts. This ensures that the final code is not just grammatically correct, but actually does what you asked it to do, saving engineers from having to manually debug thousands of lines of code.

The authors have made this "team" open-source, meaning anyone can use this three-stage process to help their own robots write better hardware code.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →