On the face of it, this is true. VHDL was designed to be and is a technology independent design language. However, there is less of a compliance issue between different simulators than there is for synthesis tools. Generally speaking, moving VHDL code from one simulator to another involves one or two minor changes to the VHDL. Two different synthesis tools may have broad agreement of what constitutes synthesizable code, but may interpret that code in different ways.
Subscribe to:
Post Comments (Atom)
-
keysymbols : =, <=. Blocking (the = operator) With blocking assignments each statement in the same time frame is executed in sequential ...
-
This is in continuation of our previous post on Low Power Design Techniques , where we learned about different types of strategies used to... -
This is 8-bit microprocessor with 5 instructions. It is based on 8080 architecture. This architecture called SAP for Simple-As-Possible comp... -
This post will help you to understand the difference between real, realtime and shortreal data types of SystemVerilog and its usage. ...
-
Formal Definition Simulation control tasks allow you to stop or quit simulation. Simplified Syntax $ stop [(n)] ; $finish [(n)] ; Descri...
No comments:
Post a Comment
Please provide valuable comments and suggestions for our motivation. Feel free to write down any query if you have regarding this post.