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)
-
Today India is home to some of the finest semiconductor companies in the world. The semiconductor companies in India are reputed across t...
-
Below written VHDL code is for 4x1 multiplexer using when-else statement. LIBRARY IEEE; USE IEEE.std_logic_1164.ALL; ENTITY mux IS PORT (...
-
The semiconductor industry's transition to making chips on 450-millimeter wafers is better described as a "transformation," J...
-
The procedure is a form of subprograms. It contains local declarations and a sequence of statements. Procedure can be called in any place of...
-
Static timing analysis verifies circuit timing by “ adding up propagation delays along paths between clocked elements ” in a circuit. It c...
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.