Because large parts of the language make no sense in a hardware context, synthesizable VHDL is a relatively small subset of VHDL. You must stick to this subset, and understand exactly how the synthesis tool you use interprets that code. For FPGA in particular you must also develop a good understanding of the structure of your chip, and know how your code must reflect the most efficient use of that structure. Fundamentally, never forget that you are designing a circuit, not writing a program. Forgetting this simply but important fact will only lead to pain later.
Subscribe to:
Post Comments (Atom)
-
What is latch up in CMOS design and ways to prevent it? A Problem which is inherent in the p-well and n-well processes is due to relativel...
-
This is in continuation of our previous post on Low Power Design Techniques , where we learned about different types of strategies used to... -
Very often we come across questions from VLSI engineers that "Which scripting language should a VLSI engineer should learn?". Well... -
case, caseZ, caseX …..!!!! it use to be very confusing for me to differentiate between these three and i use to think that whats the need of...
-
In Verilog certain type of assignments or expression are scheduled for execution at the same time and order of their execution is not guara...
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.