Commit fc916900 authored by Davide Cieri's avatar Davide Cieri
Browse files

Update docs/02-User-Manual/01-Hog-local/02b-Simulation.md

parent feb4cbc6
Loading
Loading
Loading
Loading
+3
Changes for docs/02-User-Manual/01-Hog-local/02b-Simulation.md: 3 added lines, 0 removed lines.
Original line number Diff line number Diff line
@@ -56,6 +56,7 @@ A typical `sim.conf` file would look like then:
XSIM.ELABORATE.RANGECHECK = False

[my_sim]
ACTIVE=1
MODELSIM.COMPILE.VHDL_SYNTAX=2008
MODELSIM.CUSTOM_UDO=file1.do
MODELSIM.SIMULATE.CUSTOM_UDO=file1.do
@@ -70,6 +71,8 @@ Hog also offers the possibility to generate the `sim.conf` automatically, by cli

Remember that individual simset properties have always the priority with respect to the global. So you can set a global property for all your simsets, and change it just for one of them, for example.

To set a particular simset as the active one, you need to set the `ACTIVE` property to `1` in your `sim.conf`, under the relative simset section. If no active simset is specified, Hog will set as active the last created simulation set.

```{note}
In Hog versions older than `Hog2022.2`, only a limited set of simulation properties could be specified. These properties were directly set inside the `.sim` files and were: