Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>Soft Forge HDL StudioNew to Visual Studio Code? Get it now.
Soft Forge HDL Studio

Soft Forge HDL Studio

Soft Forge

|
70 installs
| (3) | Free
| Sponsor
VHDL development on GHDL and Vivado: highlighting, a debugger that steps through processes and through simulation time in both directions, a signal viewer for live simulations and GHW/VCD files, a Vivado flow and a block design editor.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Soft Forge HDL Studio

VHDL on GHDL and Vivado, inside VS Code: a debugger that steps through processes and through simulation time in both directions, a signal viewer for live simulations and GHW/VCD files, the Vivado flow from synthesis to a programmed board, and a block design editor.

Website · Documentation · Quick start · Examples · Pricing

F5 on a testbench: the session pauses at 0 fs, the signal viewer opens beside the editor, and run 100 ns in the Debug Console fills it with waveforms

Press F5 on a testbench. That is the setup: no launch configuration to write, the folder is analysed, the open entity is elaborated, and the simulation pauses at 0 fs with the signal viewer beside the editor. Every view is a VS Code view, with the workbench's rows, tabs, status bar and theme.

What it does

Debugger Breakpoints in processes and subprograms, Step Over / Into / Out, Step Time to the next activity, Run For… a duration, data breakpoints on a signal change, break on failing assertions, hover and watch any signal, deposit values.
Time travel Step Back, Reverse Continue and Run Back To… rewind a recorded session in under a second on the examples.
Signal viewer (Pro) Every signal of the elaborated design, streamed live as the simulation runs; cursor, edges, zoom, radixes, analog traces, VCD export. The same viewer opens .ghw and .vcd files and follows them when they change.
Workspace file One <name>.hdl-workspace per folder (sources, testbenches, top, part, board, constraints, toolchains), edited as a settings-like dashboard; a plain text file that merges cleanly when several people change it.
Vivado flow Synthesis, implementation, bitstream and xsim as VS Code tasks, a Flow view with WNS, utilisation and DRC, and a Hardware view that programs the board through hw_server.
Block designs Entities, Xilinx IP and primitives on a canvas with automatic layout; .vbd files that merge cleanly; HDL wrapper and export to Vivado.
hdl command line On the PATH of every VS Code terminal: analyse, run, signals, flow, program, and drive the open debug session. Machine-readable output for scripts and AI agents, a skill for Claude Code, language model tools.

Free: everything that edits, simulates, debugs and builds. Pro: the signal viewer. A 60-minute trial of Pro starts when you ask for it, once per installation, with no account. Your plan shows in the status bar; click it to sign in with your Soft Forge account, start the trial, see plans or enter a license key. Plans and keys →

Requirements

Tool Needed for
GHDL (any backend, with VPI) and gcc simulation, the debugger, the viewer
GHDL GCC or LLVM backend + GDB source breakpoints, stepping, call stacks
AMD Vivado synthesis, implementation, bitstream, xsim, programming

Supported systems and installation →

The debugger

A breakpoint in the counter process is hit; Step Over walks the statements, a hover shows a signal's value, Step Time advances to the next activity

Action What it does
Breakpoint in a process or subprogram stops there; conditions and hit counts
Step Over / Into / Out sequential statements; leaving a process moves to the next time step
Step Time (Ctrl+F10) the next time with activity, or the step set with HDL Studio: Set Step Time…
Run For… (Ctrl+Shift+F11) advances by a duration such as 100 ns
Variables → Signals the design hierarchy with current values; edit a value to deposit it
Right-click a signal → Break on Value Change a data breakpoint, optionally on a value such as x"5"
Breakpoints → Assertion Failures stops where an assert fails

Debug Console: run <time>, step, force <signal> <value>, gdb <command>, help. The debugger →

Time travel

After run 150 ns, Step Back moves the marker back through the recorded waveforms three times, then Run Back To returns to 40 ns

Ctrl+Shift+F10 steps back, Reverse Continue runs back to the previous breakpoint, and HDL Studio: Run Back To… returns to any earlier time. How it works →

The signal viewer

The live signal viewer: fit, a cursor on the ruler, jumps between edges, zoom, a scope expanded, an analog trace

  • The left pane is the design hierarchy; expanding a scope adds its signals.
  • Click places the cursor; ←/→ jump between edges; F fits; +/- and Ctrl+wheel zoom; L follows the simulation.
  • A turns the selected signal into an analog trace; the radix menu reads vectors as hex, bin, unsigned or signed.
  • Future time is shaded until the simulation reaches it; the debugger's time is a marker.

The signal viewer →

Waveform files

dds_tb.ghw opened from the Explorer: a state machine by name, hex buses, and the sine output as an analog trace

Open a .ghw or .vcd from the Explorer, or with HDL Studio: Open Waveform File. GHW keeps the VHDL types (enumerations by name, records as groups, reals as analog); VCD comes from any simulator. Waveform files →

The workspace dashboard

The workspace dashboard: overview, top design, testbenches, sources and toolchains, and the Run testbench button

HDL Studio: Create Workspace File writes <name>.hdl-workspace; opening it shows the dashboard. F5, the Flow view and hdl read it. The workspace file →

The Vivado flow

The Flow view on the Arty A7 example running synthesis, implementation and bitstream generation, then the reports

The Flow view runs Synthesise, Implement and Generate bitstream as tasks (checkpoints are reused while newer than the sources), shows WNS, utilisation and DRC, and generates constraints for Basys 3, Arty A7, Nexys A7, Zybo Z7 and Cmod S7. The Hardware view starts or connects to hw_server, lists targets and devices with their XADC readings, and programs a bitstream. Vivado flow → · Programming →

Block designs

design_1.vbd in the block design editor: auto-layout, fit, validate, then Generate HDL wrapper opens the generated VHDL

HDL Studio: New Block Design creates a .vbd; the editor has an IP catalogue, your entities as user modules, validation and automatic layout. Generate HDL Wrapper writes VHDL for GHDL and Export to Vivado writes a script that rebuilds the design in Vivado's IP integrator. Block designs →

The hdl command line

A VS Code terminal: hdl --help, hdl run counter_tb, hdl signals at 90 ns from the recording, and hdl skill --install

hdl run counter_tb                             # simulate without the editor, record a .ghw
hdl signals --at 90ns --file .hdl-studio/counter_tb.ghw
hdl flow bitstream                             # Vivado in batch mode, in the work folder
hdl step / continue / run-for 100ns / watch    # drive the open debug session
hdl skill --install                            # teach Claude Code to use hdl

The hdl command → · AI agents →

Examples

examples/counter (the quick start), examples/cmake (a DDS built by CMake, with GHW and VCD recordings), examples/basys3 and examples/arty-a7 (blinkers with constraints) and examples/blockdesign. Each one is also downloadable as a zip.

Limits

  • Live signals are bits, std_logic, booleans and vectors of them. Integers, reals, enumerations and records do not appear live (GHW files have them).
  • Process variables are shown raw, as GDB sees them.
  • Supported systems, limits and troubleshooting →
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft