With this release, you can now do a lot more with your configuration file.
Do you need to tightly control the version of DSim for your development and testing? Want to test out a new DSim version? Now you can configure the version of DSim you want to use.
To get all of these new features, you'll need to download and install the latest version of the DSim Cloud CLI and re-initialize your workspace.
To learn about all configuration options, as well as how to get an updated default config file, see the DSim Cloud Configuration article.
Previously, DSim Cloud loaded a number of packages to make source and precompiled libraries available to you. You can now configure which packages you want enabled as well as which version to use.
Using these packages will save you from duplicating vendor source files in your local workspace. Just enable the package you want and use the provided environment variables to reference the sources you need.
The following packages are now available and configurable. See DSim Cloud Packages for details.
Some packages include precompiled libraries, further speeding up your workflow. Use these to skip the compilation of vendor standard libraries and save even more time.
See DSim Cloud Packages for how to make use of the various packages and precompiled libraries.
Note: Only the IEEE package is enabled by default. If your design relies on any of the other packages, just enable them in your config file.
Below is the complete list of features and bugs contained within the release.
The DSim Cloud 0.9.0 release contains the following highlights:
- 5 Features Included
- 2 Bugs fixed
- 2 MEDIUM Severity
|S797||Configuration: Select which DSim version to use||Initialize, CLI Update|
||Initialize, CLI Update|
|S821||Configuration: Select which packages to load.||Initialize, CLI Update|
|S838||New dvlencrypt command for encrypting source files||CLI Update|
|S842||Default DSIM version is now 20220822.13.0||Initialize|
Bug Fixes Included:
|B543||mdc argument parser fails when arguments include equal sign||MEDIUM||
|B546||File sync failure when file created locally conflict with remote files in a subdirectory||MEDIUM||Initialize|
* To obtain a new feature/fix, one or more user actions may be required. See the below table for a legend providing details on the various Availability values.
|Availability||User Action(s) Needed|
|Immediate||Nothing is needed from the user. Feature/fix will be seen immediately|
|CLI Update||Users must install the latest version of the CLI|
|Resume||Users must pause existing workspaces and then resume|
|Initialize||Users must destroy existing workspaces and initialize|