DVT IDE is perfect to me. I feel great with DVT, its editor and intelligent sense function help me develop easier. I like to use it in my jobs.
Our company has been using DVT IDE for 9 years and it's an indispensable part of our workflow. The productivity we gain from the tool's testbench analysis capabilities enables us to focus on the larger picture rather than getting lost in the details while fixing endless minor bugs in our code. During those 9 years, I've asked multiple times for enhancements that I thought were difficult or impossible for the AMIQ team to achieve and they've come through, to my amazement. Thank you AMIQ for a wonderful product!
Just a short note of thanks to give the AMIQ team kudos as they are in my experience the most proactive EDA vendor I've come across for support on any query no matter how big or small. Thanks!
I've enjoyed now for many years already DVT Eclipse IDE.
I used to be (and still am) a big Emacs editor aficionado and usually I was able to do a lot with the editor alone... after all, it has regular expression search and replace, ...block editing....even a psychiatrist online written in common Lisp...what else could you need when you code Specman e Language or SystemVerilog ? ?
WELL, when I started using DVT Eclipse IDE, I've found that ALL THE EDITING capabilities were in it of course as well (apart the psychiatrist but perhaps the AMIQ engineers will implement it in a next release), so if you are after "search and replace with regular expressions" ... emacs compatibility mode... do not fear!! All of that is anyway there!!
BUT THEN THE REAL differentiation starts: do you always remember in your mind all WHEN subtypes of a when inheritance hierarchy of your project ?
Do you remember all "is first" "is also" "is only" AND IN WHICH ORDER ARE THEY SEEN by your specman parser when the simulator loads the .e files ? ?
In DVT, here they are: use a mouse button and a menu and you can immediately see how they are wrapped and in which order ...
Do you want to refactor your code but you fear to break something ?
Well, the chances you break something are VASTLY reduced using DVT Eclipse IDE because you do not have "just an editor" that stores your ascii files. You have a tool that has PARSED and CONSTRUCTED AST (abstract syntax trees) of your files, and KNOWS where something is used and from where it came from.
So I can really only suggest to use DVT Eclipse IDE if you are coding Specman e Language (or SystemVerilog and UVM, if for that) verification environments.
I use DVT Eclipse IDE in a System Verilog UVM based project. I could instantly see the value of the tool, as I was able to see complied errors without running tests with meaningful messages of what the issue was. This also saves usage of the simulation tool licenses. I was also able to switch to the definition of the function and classes very fast. The AMIQ support is amazing - they quickly respond and fix any issues or questions.
After working with many HDL editors in my career, open source or paid tools, DVT Eclipse IDE is by far the best tool for RTL design. So much time is saved when you have the ability to catch errors and see connectivity of large projects in a fast and intuitive way. I don't think I can work without it anymore. If it was up to me, I would have bought all the four tools you provide just by the trust you gave me with DVT and the support you provide.
I am a signal processing engineer defining the DSP specs for the RTL designers. Through the process of design verification I interact with digital verification team and RTL designers. I am not fluent in System Verilog and UVM framework, but in case the test bench does not match the specification I often need to look into the test bench and the RTL implementation and run and tweak the tests and design myself. DVT Eclipse IDE provides exceptional help for me to quickly navigate the design, reference C++ models and understand the hierarchy of the design and the UVM test bench. Highly recommended productivity tool.
A few years ago, I took a break from RTL design and did some software work. When I came back to RTL design, I was not happy with the old editors. I was spoiled with the IDE's available for software work. I searched around and tried a few IDE's available for SystemVerilog. DVT Eclipse IDE was by far the best and is just as good as the software IDE I used. I've ran into few bugs since I started using DVT. AMIQ was very responsive and fixed the bugs in no time.
I’ve been working with DVT Eclipse IDE both in ‘e’ language, and with SystemVerilog for the past few years, and I can truly say that the effect it has on the development time and the code styling is huge.
Getting around the project’s environment using ‘go-to’ usage/implementations/writers/readers of members/functions and easy code development features like refactoring, code templates, auto-indent, auto-complete, while being notified on compilation/lint issues, all these allow us to have more time for planning and analyzing results and eventually improve the entire verification process and probably the chip itself!
I was very satisfied with the support I got from AMIQ’s team over the years, and with the online tutorial that helped me get started and find answers along the way.
Here is my top 3 reasons for using DVT Eclipse IDE: (1) autocomplete, (2) on the fly build and syntax checking and (3) code 'hopping' (jumping to member/function/method/class/etc. declaration/extensions). This piece of software makes the ramp-up period so much more immersive and easily to handle and then it helps in shortening the implementation and debug loops. It is in the top 3 list of tools that helps me deliver high quality & on time. Thanks you and keep it up!