DOCSLIB.ORG

A Large Distributed Control System Using Ada in Fusion Research John P

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Large Distributed Control System Using Ada in Fusion Research John P A Large Distributed Control System Using Ada in Fusion Research John P. Woodruff Paul J. Van Arsdall Lawrence Livermore National Laboratory Lawrence Livermore National Laboratory PO Box 808 MS L-493 PO Box 808 MS L-493 Livermore, CA 94551-0808 Livermore, CA 94551-0808 925.422.4661 925.422.4489 [email protected] [email protected] 1. ABSTRACT This laser is the latest in a series of experimental machines Construction of the National Ignition Facility used to study inertial confinement fusion: nuclear fusion laser at Lawrence Livermore National reactions produced in a plasma of deuterium and tritium Laboratory features a distributed control that is compressed by a burst of laser energy[4][15]. The system that uses object-oriented software NIF laser, which will be the worldÕs largest high power engineering techniques. Control of 60,000 laser, will deliver 1.8 MegaJoule pulses of optical energy onto a BB-sized fusion fuel capsule in a pulse 25 devices is effected using a network of some 500 nanoseconds long. In an experiment, the target will be computers. The software is being written in heated to more than 100,000,000 degrees Celsius and Ada and communicates through CORBA. compressed to a density more than 20 times that of lead. Software controls are implemented in two The scientific data that NIF produces in support of the layers: individual device controllers and a inertial confinement fusion program will support three supervisory layer. The software architecture diverse objectives. As a key component of the US Department of EnergyÕs Stockpile Stewardship and provides services in the form of frameworks Management Program, the NIF will enable the US to that address issues common to event-driven maintain its nuclear device stockpile without resorting to control systems. Those services are allocated underground testing[11]. It will also collect preliminary to levels that strictly prescribe their data about fusion as an environmentally attractive energy interdependency so the levels are separately source[7]. The ability to re-create conditions existing inside the sun and stars will significantly impact the science of reusable. The project has completed its final astrophysics and high energy density physics[5]. design review. The delivery of the first NIFÕs Integrated Computer Control System (ICCS) must increment takes place in October 1998. integrate more than 60,000 control points to manage 192 Keywords laser beamlines. Each shot of the NIF, which generates Distributed control system, object-oriented development, about 400 Mb of data, will require aligning all components CORBA, application frameworks, levels of abstraction of the laser so that all 192 beams propagate down 600-foot paths through their amplifiers and into the target chamber 2. THE NATIONAL IGNITION FACILITY within 50 microns of their assigned spot on the The $1.2 billion National Ignition Facility (NIF) centimeter-scale target ¾ and so that all beams arrive at the laser[8][10] is under construction at Lawrence Livermore center simultaneously within 30 picoseconds. The National Laboratory in California. When completed in alignment process will involve approximately 9500 stepper 2003, it will be housed in a building the size of a football motors, every one contributing to the position of a beam. stadium-704 feet long by 403 feet wide [FigureÊ1]. This alignment activity is carried out by an automated system that analyzes some 3000 distinct images to command motion of the stepper motors. Only when a control loop fails to stabilize is it necessary for an operator to intervene. Optics assembly building Cavity mirror mount assembly Pockels cell assembly Amplifier Spatial filters Control room Master oscillator room Power conditioning Switchyard transmission support structure lines Amplifier power conditioning modules Periscope polarizer mount assembly Beam control & laser diagnostic systems Pre-amplifier modules Diagnostics Transport turning building mirrors Target chamber Final optics system Figure 1: The National Ignition Facility The ICCS provides the necessary controls for a dozen 3. CONTROL SYSTEM REQUIREMENTS · Facilities such as the NIF represent major capital operators and technicians to carry out coordinated investments that will be operated, maintained, and activities on a machine composed of about 60,000 upgraded for decades. The facility is, in a sense, a factory distinct control points; in which physics experiments are manufactured. · Automatic alignment of the entire laser, controlling Accordingly the computer and control subsystems must be actuators in 4000 control loops driven by image relatively easy to extend as innovative experiments are analysis, takes place in one hour; planned. To assure a 30-year service life, the system must · Data are collected to support operational and mainte- permit periodic replacement with newer technology. The nance planning; system is being built using Ada on a modern object-oriented software framework that will be extensible · Selected images from a population of 600 cameras can and maintainable throughout the facilityÕs life cycle. be displayed to an operator at ten frames per second; The NIF controls must be highly automated and robust. The · The operatorÕs broad view of the entire machineÕs system will operate continuously around the clock with an status is updated with a latency less than ten seconds; allowed downtime of 7.5 days per year for unscheduled · The system architecture must be flexible enough to maintenance. A brief summary of requirements follows. absorb significant changes in requirements late in project construction; · The facility executes a physics shot once per 8 hours; The system must be delivered on time and on budget. · The control system coordinates several experimental · cycles concurrently to allow different sections of the laser to be used independently; FEP layers and provides plug-in software extensibility for 4. LAYERED ARCHITECTURE The ICCS layered architecture [Figure 2] was devised to attaching control points and other software services address the general problem of providing distributed [FigureÊ3]. control for large scientific facilities that do not require real-time capability within the supervisory software. The Online Configuration resultant architecture consists of front-end processors (FEP) Database Name Server coordinated by a supervisory system, and includes Operator Console commercially available components where possible. Client Supervisory Controls Upper-level Software computers Objects File Servers Supervisory Control Operator Consoles Layer ORBexpress distribution Database Sun Solaris UltraSparc Workstations Server Real-time Front End Software Control Processors Layer Objects Front End Processors Industrial Controls Switched Network Field bus Control Points: Sensors & Actuators Intel-based Timing System WindowsNT Figure 3: The Supervisor and the Front-end layer communicate using CORBA PowerPC-based VME/VXI crates Programmable Logic Controllers Data Safety Actuators Utilities Acquisition Interlocks 4.2 Front-end layer Front-end processors implement the distributed control functions of the ICCS by interfacing to the NIF control Figure 2: Control System Architecture points. There are eighteen different types of FEP computers Ð some 450 computers in all Ð that differ by the devices that 4.1 Supervisor layer Supervisory controls, which are hosted on UNIX they control. These FEP units are constructed from workstations housed in control consoles, provide VME/VXI-bus or PCI-bus crates of embedded controllers centralized operator controls and status, data archiving, and and interfaces that attach to control points. integration services. Two high-performance servers sharing The control points are sensors and actuators attached to redundant disk storage provide enhanced performance for interface boards plugged into an FEP backplane. In many database operations, with the added benefit of greater cases, control points are handled by intelligent components availability in the event one server fails. Several databases that incorporate embedded controllers operated by small are incorporated to manage both experimental data and data fixed programs. This firmware that runs in the embedded used during operations and maintenance. controller does much of the low-level work that would The supervisory software system is estimated to comprise otherwise be allocated to an FEP. Example components 400 KSLOC. This layer provides a human interface in the implemented in this manner are stepping motor controllers, form of operator displays, data retrieval, and processing photodiode detectors, and power supply controls. Laser that is used to coordinate control functions across laser and diagnostic sensors attach to FEP units by utilizing low-cost target area equipment. The ICCS supervisor is partitioned field bus microcontrollers. into eight cohesive subsystems, each of which controls a The FEP software performs sequencing, instrumentation primary NIF subsystem such as beam control or power control, data acquisition and data reduction on control conditioning. The supervisory software is responsible for points that are collocated. The software required for all the duties ranging from configuration and control sequencing FEPÕs is estimated to comprise 100 KSLOC. The to data processing and archival. architecture being described in this paper provides a Interoperability among computers and operating systems is standard way for FEP units to be integrated with the addressed by leveraging the international
Load more

Recommended publications
  • Steve Bernier, M.Sc
    Presented by: Steve Bernier, M.Sc., Research Manager Advanced Radio Systems Communications Research Centre Canada How Different Messaging Semantics Can Affect Applications Performances SCA applications are made of several software components typically connected in a pipeline configuration Using the SCA, software components can be implemented by different organizations Interactions between components requires a middleware The middleware for SCA is CORBA 2 How Different Messaging Semantics Can Affect Applications Performances This paper provides metrics comparing two types of CORBA interactions: One-way and Two-way Using CORBA, every interaction is transformed into a message sent from a source component to a destination component Two-way interactions Source is blocked until a response is received from the destination Synchronized with the target One-way interactions Source is not blocked until a response is received from the destination 3 levels of synchronization: with the middleware, with the transport, or with the server 3 How Different Messaging Semantics Can Affect Applications Performances Two-way messaging can lead to the empty pipeline problem 4 How Different Messaging Semantics Can Affect Applications Performances One-way messaging can lead to the packet reordering problem 3, 2, 1 2, 3, 1 3, 1, 2 5 How Different Messaging Semantics Can Affect Applications Performances This paper provides metrics for 4 tests. All tests work as follows: Pipeline configuration of 4 components The first component produces 1000 packets
    [Show full text]
  • Partner Directory Wind River Partner Program
    PARTNER DIRECTORY WIND RIVER PARTNER PROGRAM The Internet of Things (IoT), cloud computing, and Network Functions Virtualization are but some of the market forces at play today. These forces impact Wind River® customers in markets ranging from aerospace and defense to consumer, networking to automotive, and industrial to medical. The Wind River® edge-to-cloud portfolio of products is ideally suited to address the emerging needs of IoT, from the secure and managed intelligent devices at the edge to the gateway, into the critical network infrastructure, and up into the cloud. Wind River offers cross-architecture support. We are proud to partner with leading companies across various industries to help our mutual customers ease integration challenges; shorten development times; and provide greater functionality to their devices, systems, and networks for building IoT. With more than 200 members and still growing, Wind River has one of the embedded software industry’s largest ecosystems to complement its comprehensive portfolio. Please use this guide as a resource to identify companies that can help with your development across markets. For updates, browse our online Partner Directory. 2 | Partner Program Guide MARKET FOCUS For an alphabetical listing of all members of the *Clavister ..................................................37 Wind River Partner Program, please see the Cloudera ...................................................37 Partner Index on page 139. *Dell ..........................................................45 *EnterpriseWeb
    [Show full text]
  • Success Oriented Ground and Space Software Defined Architectures
    Success Oriented Ground and Space Software Defined Architectures 30 March 2004 Jerry Brand, Vince Kovarik and James Faist Melbourne, Florida Presented at the GSAW 2004 Manhattan Beach, CA GSAW 2004 (Slide 1/17) assuredcommunications™ 16-Apr-04 Introduction • Software Defined Radio (SDR) Architectures Background • JTRS/SCA Terminology • SCA Software Structure • Example Ground SDR • Example Flight SDR • Successful Architecture Attributes • Conclusions GSAW 2004 (Slide 2/17) assuredcommunications™ 16-Apr-04 JTRS/SCA Terminology • Joint Tactical Radio System (JTRS): A radio system within the 2MHz to 2Ghz (tactical) frequency 2Mhz-2GHz range and has the SCA infrastructure (see below). JTRS Radio • Software Communication Architecture (SCA): The Core Framework underlying infrastructure specification that must be implemented. Defines >2GHz • Core Framework (CF): The SCA 2.2 realization of the SCA specification that provides the SATCOM Radio radio infrastructure services specified in the SCA. Core Framework • SCA-Compliant: A radio that has a Core Framework that adheres to the SCA is SCA-Compliant. Both radios are SCA-Compliant GSAW 2004 (Slide 3/17) assuredcommunications™ 16-Apr-04 SDR Abstraction • Dynamic (re)configurability Waveform Implementation Paths – Components – Waveforms Waveform Specification – Processing paths VHDL • Plug-n-Play components C/C++ • Reuse of common Framework/Infrastructure implementations • The Framework or Operating System Infrastructure provides the Abstraction FPGA ASIC intelligent abstraction GPP DSP away from the
    [Show full text]
  • High Performance Java Software
    High Performance Java™ Software Comparing a Common Design in Three Languages Kevin Buesing Field Applications Engineer Objective Interface Systems http://www.ois.com 1 Presentation Objectives Compare the performance of a single middleware design implemented in Java, C++, and Ada 95. Compare performance of using C sockets vs. Java sockets vs. JNI C sockets. Compare multiple middleware designs implemented in various languages. 2 High Performance Java Software Foundation Knowledge Comparing Sockets Comparing One Design Implemented in Multiple Languages Comparing Different ORBs Lessons Learned Summary 3 High Performance Java Software Foundation Knowledge Comparing Sockets Comparing One Design Implemented in Multiple Languages Comparing Different ORBs Lessons Learned Summary 4 Objective Interface Perspective • Vendor of communications software for: ─ Real-time and embedded systems ─ High-performance enterprise systems • Common themes ─ Invest in long-term technologies ─ An extreme fixation on performance ─ High reliability requirements ─ Wide platform support (over 500 binary platforms) ─ Committed to standards (OMG, Open Group, JCP) 5 Technology Used for Comparison • ORBexpress™: High Performance CORBA • One design ─ Predictable and oriented for performance ─ Replaceable transports ─ Desktop, server, real-time and embedded systems • Three ORBs implemented in their native languages ─ Ada ORB written in Ada ─ C++ ORB written in C++ ─ Java ORB written in Java ─ Not language bindings ─ Common design and architecture 6 Transport Comparison C++ Sockets vs. Java Sockets vs. JNI to C++ • With ORBexpress the transport itself is typically the bottleneck ─ Is using the JNI to access C sockets faster than the Java Socket class? ─ Pluggable transport API in ORBexpress makes this easy to test ─ JNI can require copies ─Depends on JVM ─JVM’s that force extra copies in either the socket class or JNI interface preclude high bandwidth utilization • Objective Interface tests run on ─ 1.7 ghz Pentium 4 ─ Microsoft Windows XP 7 Common Architecture ORB Comparison ORBexpress: Java vs.
    [Show full text]
  • EULA for Probasec 1.4 June 8, 2018 Page 1 of 41
    Diebold Nixdorf EULA for ProBaseC 1.4 June 8, 2018 Page 1 of 41 EULA for ProBaseC 1.4 Diebold Nixdorf Software End User License Agreement Software programs which you received either installed on the device provided by Diebold Nixdorf, Incorporated or one of its affiliates (“Diebold or DN”), downloaded from a Diebold website or provided on a CD by Diebold are copyrighted by the respective authors and use of each program is governed by the respective author's terms included herein or in the software. Diebold Nixdorf, Incorporated. (“DN Software”) claims copyright in the compilation only. THIS SOFTWARE IS PROVIDED AS IS AND WITHOUT WARRANTY OF ANY KIND. Installation or use of this software or the terminal constitutes your agreement to be legally bound by these terms. If you do not agree with these terms, do not use or install this software and contact Diebold Nixdorf at www.dnlegalterms.com to arrange for return of the software and a refund of the value of the media. NEITHER DIEBOLD NIXDORF SOFTWARE NOR ITS AGENTS, DISTRIBUTORS, AFFILIATES, SUPPLIERS OR CONTENT PROVIDERS, SHALL BE LIABLE FOR ANY VIOLATION OF INTELLECTUAL PROPERTY RIGHTS OR FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING FROM OR RELATING TO THE SOFTWARE DESCRIBED HEREIN. THE LIABILITY OF ANY SUCH ENTITIES IS LIMITED SOLELY AND EXCLUSIVELY TO REFUNDING THE VALUE OF THE MEDIA (BLANK CD) ON WHICH THE SOFTWARE IS PROVIDED, IF ANY. The following are the list of licenses and software components under them: License Component Name Version Copyright Notice AES Brian Gladman AES by Brian Glandman Not Applicable Copyright 1999-2010, License Brian Gladman, Worcester, UK.
    [Show full text]
  • High-Assurance, Real-Time MILS Architecture
    High-Assurance, Real-time MILS Architecture W. Mark Vanfleet Bill Beckwith Senior NSA/IAD Objective Interface Systems Security Analyst CEO/CTO [email protected] [email protected] This presentation represents joint research between the Air Force, Army, Navy, NSA, Boeing, Lockheed Martin, Objective Interface, Green Hills, LynuxWorks, Wind River, GD, Rockwell Collins, MITRE, U of Idaho Why Security in Embedded Systems? 6/28/2004 High-Assurance, Real-Time MILS Architecture Vanfleet, Beckwith - 2 1 Why Security in Embedded Systems? • A Year in the Life of a Utility System – 100 - 150 hits/day on control network – 17 intrusions – 2 Denial of Service (DoS) events – 3 Loss of Control Events • Switchgear controller • Boiler Deaerator controls 6/28/2004 High-Assurance, Real-Time MILS Architecture Vanfleet, Beckwith - 3 Why Security in Embedded Systems? (cont.) • To reduce the risk of – Damage to internal systems • Expense to repair • Operational blockage – Damage to customer systems • Loss of goodwill • Market recognition: irreparable damage to quality image • Liability for customer losses – Peace of mind • Spend attention on forward initiatives • Less monitoring required • Sleep better • To reduce costs – Potentially lower insurance – Less monitoring costs 6/28/2004 High-Assurance, Real-Time MILS Architecture Vanfleet, Beckwith - 4 2 Why Security in Embedded Systems? (cont.) • Australian Water Utility – Vitek Boden, 48, April 23rd, 2000, Queensland, Australia • disgruntled ex-employee of equipment supplier • Vehicle became command
    [Show full text]
  • Preliminary Design of MUSES Control System Based on RT-CORBA and Java Toshiya Tanabe*, Toshikatsu Masuoka, Jun-Ichi Ohnishi
    Preliminary Design of MUSES Control System Based on RT-CORBA and Java Toshiya Tanabe*, Toshikatsu Masuoka, Jun-ichi Ohnishi, Motonobu Takano and Takeshi Katayama RIKEN, Beam Technology Division / Beam Physics and Engineering Lab. 2-1 Hirosawa, Wako, Saitama 351-0198, JAPAN *e-mail: [email protected] Icalepcs2001, 27-30 November, 2001 RIkagakuRIKENKENkyusho (Bio Resource Center) (SP8) (Genome Science) RIKEN Aerial Photo Accelerator Complex Occupied by Local School USA Owned by the Ministry of Finance RI Beam Factory (RIBF) Facilities Overview Existing Facility [RIKEN Accelerator Research Facility (RARF)] – ECR Ion Source – RFQ – RIKEN Linear Accelerator (RILAC) – Charge State Multiplier (CSM) – Riken Ring Cyclotron (RRC) [K=540] – RIKEN Projectile fragment Separator (RIPS) 1st Phase – Intermediate Ring Cyclotron (IRC) [K=950], – Superconducting Ring Cyclotron (SRC) [K=2500], – Big-RIPS 2nd Phase [Multi-USe Experimental Storage rings (MUSES)] – Accumulator Cooler Ring (ACR) [Emax=400MeV/u for light ions] – e-RI Collider http://www.rarf.riken.go.jp/rarf/index.html -> e-RI Collider (2001) URL:http://ribfweb1.riken.go.jp/ RIBF Controls General Policies Vendor/Platform Independence & Portability of Applications – Long-term maintenance and future upgrade – Industry Standard (CORBA, Java, etc.) • Avoid MS-lead standards (DCOM, Active-X, etc.) Minimization of Own Software Development – Lack of man power (~5FTE) – Use of COTS products as much as possible – Software sharing with other labs (JSI, KEK, etc) Reliability over Cost on Hardware
    [Show full text]
  • Software Engineering On
    Title page - CLEO Baltimore, May 9, 2007 Software Engineering Processes Used to Develop the NIF Integrated Computer Control System* A. Peter Ludwigsen 2007 International Conference on Accelerators and Large Experimental Physics Control Systems, Knoxville, TN, October 14, 2007 Lawrence Livermore National Laboratory, USA 1 * This work performed under the auspices of the U.S. Department of Energy by Lawrence Livermore National Laboratory under Contract DE-AC52-07NA27344. NIF is a stadium-sized facility that will contain • 192-beam, 1.8-Megajoule, 500-Terawatt, ultraviolet laser system • 10-meter diameter target chamber with room for nearly 100 diagnostics 2 National Ignition Facility “Quads” (4 beams) and “Bundles” (8 beams) are the basic building blocks of the NIF 3 NIF’s 192 energetic laser beams will compress small deuterium-tritium fusion targets to conditions where they will ignite and burn, and achieve energy gain 4 The Integrated Computer Control System (ICCS) robustly operates a complex physics facility •• ControlControl 60,00060,000 pointspoints ¾¾ 1,500 processes 1,500 processes AutomaticAutomatic controlcontrol ofof 192-beam192-beam shotsshots ¾¾ 850 computers 850 computers areare overseenoverseen byby 1414 operatoroperator stationsstations ¾¾ 140,000140,000 distributeddistributed objectsobjects •• AlignAlign andand firefire 192192 laserslasers ¾¾ << 5050 micronsmicrons onon targettarget ¾¾ << 3030 psecpsec timing timing •• AutomaticAutomatic shotshot controlscontrols ¾¾ << 4-hours4-hours shot-to-shotshot-to-shot ¾¾ Hands-offHands-off
    [Show full text]
  • The SCA: Myths Vs Reality Is the SCA What You Think It Is?
    The SCA: Myths vs Reality Is the SCA what you think it is? Steve Bernier Researcher, Project Leader Advanced Radio Systems 1 OutlineOutline 1. Overview of the Software Communications Architecture (SCA) 2. Is the SCA too slow ? 3. Is the SCA too fat ? 4. Summary 2 1. SCAOutline Overview • The SCA was developed to assist in the development of SDR for the Joint Tactical Radio System (JTRS). As such, the SCA has been structured to: – Provide for portability of applications between different SCA platforms – Leverage commercials standards to reduce development costs – Reduce software development time with the ability to reuse design modules – Build on evolving commercial frameworks and architectures • The SCA is not a system specification but an implementation-independent set of rules that constrain the design of systems to achieve the above objectives 3 1. SCAOutline Overview • Myth #1: The SCA is only for military Radios – While its true the SCA specification was developed for the US DoD JTRS program, the reality is the core framework specification contains no military features at all ! • Myth #2: The SCA is for building Software Defined Radios – None of the core framework APIs are radio specific ! – An SCA platform can host any kind of application • radar, medical imagery, test equipment, etc. 4 1. SCAOutline Overview • The SCA Core Framework specification (version 2.2.2) is made of five documents: – Main document (130 pages) – Appendix B – Application Environment Profile (21 pages) – Appendix C – IDL (41 pages) – Appendix D – Domain Profile (64 pages) – Appendix D – Attachment 2 – Common Properties (4 pages) • Previous releases of the SCA specification had two extra documents named Security Supplement and API Supplement – These documents were last published in 2001 – The security supplement adds RED/BLACK centric APIs – The API supplement adds communications/radio centric APIs 5 1.
    [Show full text]
  • Towards a Common Hardware/Software Specification
    Towards a common hardware/software specification and implementation approach for distributed, rel time and embedded systems, based on middlewares and object-oriented components Gregory Gailliard To cite this version: Gregory Gailliard. Towards a common hardware/software specification and implementation approach for distributed, rel time and embedded systems, based on middlewares and object-oriented components. Engineering Sciences [physics]. Université de Cergy Pontoise, 2010. English. tel-00524737 HAL Id: tel-00524737 https://tel.archives-ouvertes.fr/tel-00524737 Submitted on 8 Oct 2010 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. ECOLE DOCTORALE SCIENCES ET INGENIERIE de l’université de Cergy-Pontoise THESE Présentée pour obtenir le grade de docteur d’université Discipline : Sciences et Technologies de l’Information et de la Communication Spécialité : Informatique Vers une approche commune pour le logiciel et le matériel de spécification et d’implémentation des systèmes embarqués temps-réels distribués, basée sur les intergiciels et les composants
    [Show full text]
  • Integrated Computer Control System CORBA-Based Simulator
    UCRL-ID-133243 Integrated Computer Control System CORBA-based Simulator P. J. Van Arsdall R. M. Bryant F. W. Holloway January 15, 1999 Lawrence Livermore National Laboratory This is an informal report intended primarily for internal or limited external distribution. The opinions and conclusions stated are those of the author and may or may not be those of the Laboratory. Work performed under the auspices of the U.S. Department of Energy by the Lawrence Livermore National Laboratory under Contract W-7405-ENG-48. DISCLAIMER This document was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or the University of California. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product endorsement purposes. This report has been reproduced directly from the best available copy. Available to DOE and DOE contractors from the Office of Scientific and Technical Information P.O. Box 62, Oak Ridge, TN 37831 Prices available from (423) 576-8401 Available to the public from the National Technical Information Service U.S.
    [Show full text]
  • Embedded Computing Design Resource Guide
    RSC# @ www.embedded-computing.com/rsc RSC# @ www.embedded-computing.com/rsc www.embedded-computing.com VOLUME 4 • NUMBER 6 A U G U S T 2 0 0 6 COLUMNS RESOURCE GUIDE 7 Editor’s Foreword Federation of Associations 27 Middleware: The last roadblock to distributed By Jerry Gipper systems development By Dr. Stan Schneider, RTI 8 Embedded Perspective Ab fabless deals 29 BIOS, firmware, middleware By Don Dingee 33 FPGAs, reconfigurable computing 10 Embedded Technology in Europe Embedded devices for those with disabilities By Hermann Strass 52 High-performance computing 14 Eclipse Perspective and News ALF and 10 questions every QA team should ask 61 Why automate testing? By Tracy Ragan By Kingston Duffie, Fanfare 63 Integrated development environment FEATURES 67 Intellectual Property cores SPECIAL: Custom solutions and short design cycles 17 Customization for the masses 70 Mezzanine cards By Jerry Gipper PCI Express: Software/Firmware 84 Microprocessors, microcontrollers 23 Advanced functional verification and debug of PCI Express-based designs By Chris Browy, Avery Design Systems 89 Improving code migration and reuse By Robert Day, LynuxWorks DEPARTMENTS 94 Operating systems – embedded 30, 138 Editor’s Choice Products 102 Packaging By Jerry Gipper 105 Techniques to shrink embedded system E-CASTS design cycles RapidIO System Architecture: What Designers Need to Know By Rodger H. Hosking, Pentek August 24, 2 p.m. EST 108 Single board computers and blades www.opensystems-publishing.com/ecast OpenSystems 137 Storage solutions E-LETTER Publishing™ August: www.embedded-computing.com/eletter 143 It’s all just plumbing, isn’t it? Mobile phone security – in your face OpenSystems By Victor Menasce, AMCC By Seiji Inoue, Oki Electric Publishing™ 148 Switch network fabrics 153 System-on-Chip (SoC) Published by: OpenSystems OpenSystems 157 Using assertions to track functional coverage Publishing™Publishing™ By Kelly D.
    [Show full text]