E
Espen Tallaksen
Guest
How can we do FPGA VHDL Verification faster and with better quality â at no extra cost?
This is actually possible â and with an average efficiency improvement of 20 to 50% for medium to high complexity FPGAs. Less for data path oriented designs and more for control or protocol oriented designs. At no extra cost.
All that is required is that you do your testbench development the same way you do your design. Every single FPGA designer knows that a good top level design architecture is critical. Most FPGA designers also know that a good microarchitecture is at least as important for module design. It should thus be obvious that a good architecture is also equally important for your testbench, but for some strange reason most testbenches do not have the same good architecture as the design being verified.
Most designers agree that the following are critical for an efficient development of a high quality design module:
- Overview, Readability, Simplicity
- Modifiability, Maintainability, Extendibility
- Debuggability
- Reusability
So why should testbenches be any different, with on average the same time usage as the actual design?
It should be obvious that these aspects are equally critical for testbench development, but there has been no standard solution to build a good testbench architecture â until now â when UVVM has been introduced as a free and open source solution to this challenge.
See blog at EDACafĂŠ:
http://www10.edacafe.com/blogs/aldec/2016/11/14/fpga-vhdl-verification-can-we-do-this-faster-with-better-quality-at-no-extra-cost/
And please join the webinar tomorrow by registering at either of
https://www.aldec.com/en/events/770 for presentation at 3pm CET
https://www.aldec.com/en/events/771 for presentation at 11am PST
This is actually possible â and with an average efficiency improvement of 20 to 50% for medium to high complexity FPGAs. Less for data path oriented designs and more for control or protocol oriented designs. At no extra cost.
All that is required is that you do your testbench development the same way you do your design. Every single FPGA designer knows that a good top level design architecture is critical. Most FPGA designers also know that a good microarchitecture is at least as important for module design. It should thus be obvious that a good architecture is also equally important for your testbench, but for some strange reason most testbenches do not have the same good architecture as the design being verified.
Most designers agree that the following are critical for an efficient development of a high quality design module:
- Overview, Readability, Simplicity
- Modifiability, Maintainability, Extendibility
- Debuggability
- Reusability
So why should testbenches be any different, with on average the same time usage as the actual design?
It should be obvious that these aspects are equally critical for testbench development, but there has been no standard solution to build a good testbench architecture â until now â when UVVM has been introduced as a free and open source solution to this challenge.
See blog at EDACafĂŠ:
http://www10.edacafe.com/blogs/aldec/2016/11/14/fpga-vhdl-verification-can-we-do-this-faster-with-better-quality-at-no-extra-cost/
And please join the webinar tomorrow by registering at either of
https://www.aldec.com/en/events/770 for presentation at 3pm CET
https://www.aldec.com/en/events/771 for presentation at 11am PST