Amiq is pleased to announce the release of the FC4SC 2.1.1!
You can read more about the FC4SC library and first release in this blog post.
Download
You can download the FC4SC library from GitHub.
For getting up to speed you can read our previous post, download FC4SC’s User Guide or browse the API’s HTML documentation.
The FC4SC code is provided as an opensource library under Apache License 2.0.
Change Log
This release contains fixes and improvements required by FC4SC users and Accellera SystemC Verification Working Group.
- Added enforced (compile time) restrictions on bins and coverpoints definition
- Re-worked the coverpoint definition mechanism
- Added support for algorithmic bins creation
- Fixed the bin_array mechanism for bin interval splitting
See the full change log here.
Roadmap
The following improvements were requested by FC4SC users and Accellera SystemC Verification Working Group members:
- Merging of multiple UCIS DB instances
- Better UCIS support
- SystemC event-based sampling
- Support for sampling on custom classes
We welcome your feedback!
3 Responses
Hello, I wanted to know if there is any way to combine functional coverage reports from separate executions together.
Thanks!
Hi Shobhit,
Yes, it is possible to merge multiple runs into a single coverage database. For that, you need to use the merge.py script found under https://github.com/amiq-consulting/fc4sc/tree/master/tools/coverage_merge
The script takes 2 arguments:
Example:
Best Regards,
Dragos
Hi Dragos,
Based on my understanding, FC4SC should be UCIS compliant. If so, can we use VCS URG to generate reports? If it’s possible, do you know how it can be done?
Thanks,
Raymond