Runs your tools
It executes your simulator and reads the real output.
Verilog Atlas is an autonomous agent that runs your simulation, reads the logs, edits files, and proposes diffs you review. Prompts go to the chosen model endpoint, whether local or cloud, and it helps you fix vhdl code.
It executes your simulator and reads the real output.
It edits files and shows you a diff to accept in Ask first.
API keys and chats stay on the PC; prompt text goes only to the model endpoint you choose; local model keeps all on the PC.
It runs your tools, reads the output, and suggests changes you review.
*.svfound 3tb_counter.svloadedError1 matchtb_counter.svsavedcompile and runexit 0Verilog Atlas runs your local simulator to fix blocking vs non-blocking assignments in verilog designs that exhibit race conditions, so you can resolve timing issues without leaving your PC. It works locally. The agent uses glob to locate your source files in the working folder. It reads the design and searches the log for errors and warnings. It proposes an edit_file change to convert the blocking logic correctly. You review the diff in Ask first mode and accept it. It runs your simulator again to verify the fix successfully. The rerun shows whether the tested cases pass, not that the fix is proven, like an online verilog simulator or a vhdl compiler.
The agent writes a plan in Plan only mode and you switch to Auto-run to execute the commands using Shell. Verify the result. Verilog Atlas runs your own simulator through Shell commands on your local machine. Read the log output to check for errors and warnings. A passing simulation shows only that the tested cases behaved as expected. You can learn systemverilog fpga design in 6 months. Use grep to find FAIL or x values in the log file. Review the generated code and accept the changes to your project.
It is the reader's responsibility to use it only on their own designs, coursework and openly licensed code.