An end-to-end workflow does not necessarily require a single tool. It needs consistent project data and a clear contract between the steps. The editor, static analysis and simulation should examine the same design intent while answering different questions.
1. Define a shared view of the project
Define files, logical libraries, language versions and dependencies. Keep the authoritative project description under version control. Avoid maintaining separate manual file lists for the editor and build over the long term. Start with a small project target and check the build from a clean directory.
2. Edit HDL in the editor
Sigasi Visual HDL works with the project model inside VS Code. Use immediate diagnostics for editing and navigation. When diagnostics conflict, first check library assignments and language versions; analysing a different set of files is not a useful comparison.
3. Add the external compiler deliberately
The current Sigasi manual documents external compiler tasks for Modular Projects. Riviera-PRO is listed with the task type sigasiRivieraCompile . Settings include the installation path, precompiled libraries and compiler-specific arguments. The precise configuration is explained in the application note on the Sigasi–Aldec workflow .
4. Run simulation as a separate step
Choose the top level, parameters and libraries for elaboration. Then start a self-checking test in the intended simulator environment. A result needs an unambiguous success indication, a failure status and a limit for tests that do not terminate. Preserve the configuration needed to repeat the run.
5. Add checks for static risks
Where the project has relevant risks, ALINT-PRO complements dynamic simulation with static analysis. Check constraints and justified waivers with the same care as testbench expectations. A cross-tool marketing description is not technical evidence of integration.
6. Transfer the workflow to the team
| Handover | What must be preserved | Acceptance check |
|---|---|---|
| Editor → compiler | Files, order, libraries, language versions | Fresh compilation run |
| Compiler → simulation | Top level, parameters, testbench, run options | A deliberately failing test is detected |
| Workstation → regression | Versions, licences, seeds, timeouts, reports | Same source revision in a clean environment |
This process description is an editorial compilation of documented capabilities. It has not been executed as an overall integration in a licensed Aldec/Sigasi environment. A bounded pilot in your own project is required before production adoption.
The topics code quality, simulation and automation explore the individual decisions in more detail.