too vast, too complex, too grand ... for deillegalscription. John Wesley Powell-1870 (discovering the Grand Canyon) VHDL is a big world. A beginner can be easily disappointed by the generality of this language. This generality is explained by the large number of domains covered - from specifications to logical simulation or synthesis. To the very beginner, VHDL appears as a "kit". He is quickly aware that his problem may be solved with VHDL, but does not know how. He does not even know how to start. In this state of mind, all the constraints that can be set to his modeling job, by using a subset of the language or a given design methodology, may be seen as a life preserver. The success of the introduction of VHDL in a company depends on solutions to many questions that should be answered months before the first line of code is written: - Why choose VHDL? - Which VHDL tools should be chosen? - Which modeling methodology should be adopted? - How should the VHDL environment be customized? - What are the tricks? Where are the traps? - What are the differences between VHDL and other competing HDLs? Answers to these questions are organized according to different concerns: buying the tools, organizing the environment, and designing. Decisions taken in each of these areas may have many consequences on the way to the acceptance and efficiently use of VHDL in a company.
1. Introduction. 2. VHDL Tools. 3. VHDL and Modeling Issues. 4. Structuring the Environment. 5. System Modeling. 6. Structuring Methodology. 7. Tricks and Traps. 8. M and VHDL. 9. VERILOG and VHDL. 10. UDL/I and VHDL. 11. Memo. 12. Index. List of Figures.
1. Introduction.- 1.1. VHDL Status.- 1.2. The VHDL Spectrum.- 1.3. Models, Modeling, and Modelware.- 1.4. The Other Languages and Formats.- 2. VHDL Tools.- 2.1. Introduction.- 2.2. Evaluating VHDL tools.- 2.3. Technology of Platforms.- 3. VHDL and Modeling Issues.- 3.1. Introduction.- 3.2. Core VHDL Concepts.- 3.3. Abstraction.- 3.4. Hierarchy.- 3.5. Modularity.- 3.6. Reusability.- 3.7. Portability.- 3.8. Efficiency.- 3.9. Documentation.- 3.10. Synthesis.- 3.11. Conclusion.- 4. Structuring the Environment.- 4.1. Choosing a Logic System.- 4.2. Utility Packages.- 5. System Modeling.- 5.1. Introduction.- 5.2. The FSM with a Single Thread of Control.- 5.3. Multiple Threads of Control.- 5.4. Hierarchy: State Charts and S-Nets.- 5.5. Conclusion.- 6. Structuring Methodology.- 6.1. Structuring.- 6.2. What are the Possibilities of VHDL?.- 6.3. To Summarize.- 7. Tricks and Traps.- 7.1. Modeling Traps.- 7.2. Modeling Tricks.- 7.3. Pitfalls.- 7.4. Designer.- 8. M and VHDL.- 8.1. Introduction.- 8.2. Design Unit.- 8.3. Sequential and Concurrent Domains.- 8.4. Objects.- 8.5. Predefined Operators.- 8.6. Statements.- 8.7. Deillegalscription Level.- 8.8. Translating from M to VHDL.- 8.9. Conclusion.- 9. Verilog and VHDL.- 9.1. Introduction.- 9.2. Design Unit.- 9.3. Sequential and Concurrent Domains.- 9.4. Objects.- 9.5. Predefined Operators.- 9.6. Statements.- 9.7. Deillegalscription Level.- 9.8. Translating from Verilog to VHDL.- 9.9. Conclusion.- 10. UDL/I and VHDL.- 10.1. Introduction.- 10.2. Design Unit.- 10.3. Sequential and Concurrent Domains.- 10.4. Objects.- 10.5. UDL/I Structural Deillegalscription.- 10.6. UDL/I Behavioral Deillegalscription.- 10.7. UDL/I Assertion Section.- 10.8. Deillegalscription Level.- 10.9. Translating from UDL/I to VHDL.- 10.10. Conclusion.- 11. Memo.- 12. Index.
Inhaltsverzeichnis
1. Introduction.- 1.1. VHDL Status.- 1.2. The VHDL Spectrum.- 1.3. Models, Modeling, and Modelware.- 1.4. The Other Languages and Formats.- 2. VHDL Tools.- 2.1. Introduction.- 2.2. Evaluating VHDL tools.- 2.3. Technology of Platforms.- 3. VHDL and Modeling Issues.- 3.1. Introduction.- 3.2. Core VHDL Concepts.- 3.3. Abstraction.- 3.4. Hierarchy.- 3.5. Modularity.- 3.6. Reusability.- 3.7. Portability.- 3.8. Efficiency.- 3.9. Documentation.- 3.10. Synthesis.- 3.11. Conclusion.- 4. Structuring the Environment.- 4.1. Choosing a Logic System.- 4.2. Utility Packages.- 5. System Modeling.- 5.1. Introduction.- 5.2. The FSM with a Single Thread of Control.- 5.3. Multiple Threads of Control.- 5.4. Hierarchy: State Charts and S-Nets.- 5.5. Conclusion.- 6. Structuring Methodology.- 6.1. Structuring.- 6.2. What are the Possibilities of VHDL?.- 6.3. To Summarize.- 7. Tricks and Traps.- 7.1. Modeling Traps.- 7.2. Modeling Tricks.- 7.3. Pitfalls.- 7.4. Designer.- 8. M and VHDL.- 8.1. Introduction.- 8.2. Design Unit.- 8.3. Sequential and Concurrent Domains.- 8.4. Objects.- 8.5. Predefined Operators.- 8.6. Statements.- 8.7. Deillegalscription Level.- 8.8. Translating from M to VHDL.- 8.9. Conclusion.- 9. Verilog and VHDL.- 9.1. Introduction.- 9.2. Design Unit.- 9.3. Sequential and Concurrent Domains.- 9.4. Objects.- 9.5. Predefined Operators.- 9.6. Statements.- 9.7. Deillegalscription Level.- 9.8. Translating from Verilog to VHDL.- 9.9. Conclusion.- 10. UDL/I and VHDL.- 10.1. Introduction.- 10.2. Design Unit.- 10.3. Sequential and Concurrent Domains.- 10.4. Objects.- 10.5. UDL/I Structural Deillegalscription.- 10.6. UDL/I Behavioral Deillegalscription.- 10.7. UDL/I Assertion Section.- 10.8. Deillegalscription Level.- 10.9. Translating from UDL/I to VHDL.- 10.10. Conclusion.- 11. Memo.- 12. Index.
Klappentext
too vast, too complex, too grand ... for deillegalscription. John Wesley Powell-1870 (discovering the Grand Canyon) VHDL is a big world. A beginner can be easily disappointed by the generality of this language. This generality is explained by the large number of domains covered - from specifications to logical simulation or synthesis. To the very beginner, VHDL appears as a "kit". He is quickly aware that his problem may be solved with VHDL, but does not know how. He does not even know how to start. In this state of mind, all the constraints that can be set to his modeling job, by using a subset of the language or a given design methodology, may be seen as a life preserver. The success of the introduction of VHDL in a company depends on solutions to many questions that should be answered months before the first line of code is written: . Why choose VHDL? . Which VHDL tools should be chosen? . Which modeling methodology should be adopted? . How should the VHDL environment be customized? . What are the tricks? Where are the traps? . What are the differences between VHDL and other competing HDLs? Answers to these questions are organized according to different concerns: buying the tools, organizing the environment, and designing. Decisions taken in each of these areas may have many consequences on the way to the acceptance and efficiently use of VHDL in a company.
Springer Book Archives
