Find a copy online
Links to this item
Find a copy in the library
Finding libraries that hold this item...
|Additional Physical Format:||Print version:
System Engineers Handbook : Guide to Building VME and VXI Systems.
San Francisco : Elsevier Science, ©1992
|Material Type:||Document, Internet resource|
|Document Type:||Internet Resource, Computer File|
|All Authors / Contributors:||
|Description:||1 online resource (1113 pages).|
|Contents:||Front Cover; The System Engineer's Handbook: A Guide to Building VMEbus and VXIbus Systems; Dedication; Copyright Page; List of Contributors; Preface; Acknowledgements; Table of Contents; PART 1: Debugging The Hardware; CHAPTER 1. How To Use Special-Purpose Tools To Debug Your VMEbus Systems; Debugging a backplane-based system; Board-level debugging; System integration; Incorporation of application software; Using conventional instruments; Multimeters; Oscilloscopes; Logic analyzers; Emulators; Using VMEbus-specific tools; A summary of VMEbus-specific tools; VMEbus systems; Power supervisors. Extender boardsFirmware debug monitors; Signal breakout boards; VMEbus monitors; Anomaly triggers; VMEbus analyzers; VMEbus stimulators; Summary; CHAPTER 2. How To Use A VMEbus Analyzer To Integrate Your System; Using a bus analyzer; Adding the disk drive; Looking in the right place; Analyzing a sequence of events; Putting it all together; Tuning your system; What to look for in a VMEbus analyzer; Trace buffer size; Trace buffer expandability; Maximum sampling speed; Trigger/trace qualifiers; VMEbus stimulation and mastership; Temperature and voltage monitoring; The N9210 analyzer. A case historySummary; CHAPTER 3. How To Use Anomaly Triggers To Detect Subtle Bus Timing Violations; Common VMEbus timing violations; Detecting control signal interlock violations; Detection of a Rule 2.35 violation; Detection of Rule 2.17 violation; Detection of strobe-duration violations; Detection of a Rule 3.7 violation; Detecting glitches and bus signal degradation; Violations of stability requirements for address and data signals; Detection of instability on data Lines D00-D07; The Ultraview VBAT; Conclusion. CHAPTER 4. How To Use Soft Architectures To Build Versatile Diagnostic ToolsDriving VMEbus signal lines; Using a VMEbus analyzer; Data Collection; Active versus passive bus analyzers; Computer versus human interface; Signature analysis; Hard versus soft hardware architecture; The 5010 analyzer; Using a soft architecture to analyze 2 buses; Summary; CHAPTER 5. How To Use The Right Tools To Integrate Your VMEbus System; The 3 phases of debugging; VMEbus timing analyzers; Metastability effects; VMEbus state analyzers; Filtering; Software debugging; How fast should a VMEbus analyzer be? Providing bus analysis for VSBThe bus anomaly trigger; Performance and statistical analysis; The software method; The hardware method; The VBT-321; A typical scenario; CHAPTER 6. How To Use C To Debug Your VMEbus Hardware; Using assembly language to create diagnostic programs; Features of an idealized debugging language; High Level Languages; HLL compilers; HLL interpreters; Using High Level Languages to create diagnostic programs; The C programming language; Expressing your algorithm in a processor-independent fashion; Making subroutine calls, and passing parameters to those subroutines.|
|Series Title:||Morgan Kaufmann Series in Computer Architecture and Design.|