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)
-
The FP Adder is a single-precision, IEEE-754 compliant, signed adder/substractor. It includes both single-cycle and 6-stage pipelined design...
-
When ModelSim is automatically lunched within the ISE environment it just displays the top entity level signals in the Wave View window. Ho...
-
There are some differences between UDIMMs and RDIMMs that are important in choosing the best options for memory performance. First, let’s ta...
-
The semiconductor industry's transition to making chips on 450-millimeter wafers is better described as a "transformation," J...
-
String data type is used for storing strings, the size is dynamic and string data types come with build in methods. If you have ever tried...
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.