Design Tools for Reconfigurable Hardware in Orbit (Rhino)

Design Tools for Reconfigurable Hardware in Orbit (Rhino)

Design Tools for Reconfigurable Hardware in Orbit (RHinO) Matthew French', Paul Graham', Michael Wirthlin', Gregory Larchev", Peter Bellows1, and Brian Schott' rnfiench6,isi.edu, Lrral-mx$i?lanl.eov, wirthlinGee.bvu.edu. n!archevi~m7il.arc.nasa.iro.., ube!lowsfiGsi.edu, bschottG2isi.edu 'University of Southern California, Information Sciences Institute, Arlington, VA 'Los Alamos National Laboratory, Los Alamos, NM 'Brigham Young University, Proto, UT 4NASA Ames Research Center, Moffett Field, CA Abstract- The Reconfigurable Hardware in Orbit (RHinO) their high proportion of memory structures; and (2) project is focused on creating a set of design tools that facilitate conventional FPGA designs are most often optimized for and automate design techniques for reconfigurable computing performance at the expense of disproportionately more in space, using SRAM-based field-programmable-gate-array power. (FPGA) technology. These tools leverage an established FPGA design environment and focus primarily on space effects Current foundry process technology for Xilinx FPGA mitigation and power optimization. The project is creating devices provides enough tolerance for a large number of ESE software to automatically test and evaluate the single-event- orbits for total dose and latching (no destructive latches have upsets (SEUs) sensitivities of an FPGA design and insert been reported), however the SEU presence is a major mitigation techniques. Extensions into the tool suite will also desigm'operational issue. The large amount of static memory allow evolvable algorithm techniques to reconfigure around single-event-latchup (SEL) events. In the power domain, tools within SRAM-based FPGAs, such as look-up tables, routing are being created for dynamic power visualiization and switch tables, etc., makes them sensitive to SEUs. Many optimization. Thus, this technology seeks to enable the use of techniques have been proposed and implemented for Reconfigurable Hardware in Orbit, via an integrated design improving the reliability of digital circuits in the presence of tool-suite aiming to reduce risk, cost, and design time of multi- SEUs. While traditional hardware redundancy techniques mission reconfigurable space processors using SRAM-based improve the reliability of FPGA designs (at the expense of FPGAs. increases in hardware, power, etc.), novel FPGA-specific techniques aie required to address the unique vulnerabilities 1. INTRODUCTION of SRAM-based FPGA architectures, while incurring less hardware overhead. Therefore, design automation tools SRAM-based FPGAs have become a tantalizing solution to processing on space-based payloads. They offer features evaluating and assessing the reliability of FPGA designs, inserting appropriate redundant hardware, and manipulating that anti-fuse FPGAs do not, such as reprogrammability, the low-level structures of the FPGA design are needed for embedded multipliers, and embedded processors, while also robust operation and SEU and latch-up immunity. offering 5-lox more logic gates than anti-fuse based FPGAs. These features allow SRAM-based FPGAs to address Available FPGA synthesis tools optimize for speed or resource multiplexing, fault tolerance, mission obsolescence area, but not for real-time power consumption. Limited and design flaws in on-orbit payloads that drectly impact power estimation tools are available, such as Xilinx's design cost and mission risk, while also providing better Xpower; however, these are difficult to use and have limited processkg performaxe. The reprogranmability of SUM- utility to the ackd FPGA desi= process. Accurate power based FPGAs enables the use of multiple mission estimates are only achievzble after completing the entire applications at different orbit stages, thus combining diverse iteration of the design cycle and provide no power mission attributes and payloads, reducing size, weight, and optimization guidance. To make effective use of FPGAs in power;~ln-cl.'5:i:~U-ltsin FPGAs can be corrected by updating space, tools prii~ t power estimation and real- the design to map out damaged resources. Computational and time optimization, operating on the FPGA's gate logic or on transmission resources can adapt dynamically to the individual configurable logic blocks (CLBs), are needed; environment based on established priorities. Furthermore, as specifically: i) to monitor power consumption early in the mission-specific algorithms invariably improve over time, design process at a useful granularity (e.g, at CLB); 2) to aid these improvements can be up-loaded. Design flaws in the in the design analysis that captures data-dependent transients system discovered after launch can be similarly corrected as well as overall power consumption; and 3) to perform with firmware updates real-time constraint-driven automated power optimization However, a significant bamer to developing space-ready similar to the way that aredtiming constraints are accounted SRAil-based FPGA applications is the difficulty in today. designing for the rigorous constraints mandated by the Both the radiation-induced and power consumption operational environment. Two main issues limit the use of effects are currently handled through manual intervention or, conventional FPGAs to such designs: (1) SR4.M-based at best, through ad-hoc in-house tools. There is a real need in FPGAs are sensitive to radiation effects, namely, total dose the community for validated design tool automation to raise (TD), latchup, and single-event-upsets (SEUs), because of the technology readiness level (TRL) of SUM-based FGPA user designs. The RHinO project is leveraging an work entirely in the JHDL design environment, using the established, open-source tool-suite that accepts output from RHinO power and SEU tools in concert with the normal commercially available synthesis tools to create tools that JHDL features for simulation, netlisting, and runtime control, allow the developer of a space-based FPGA application to all within a single user interface. automatically analyze and optimize a xihv Virtex 11 FPGA B, minoEnhancements circuit for space effects and power Utilization. In the first neprimary goal during the first year of this effort was to year of this effort, tools were developed primarily for ensure that the JHDL inhastructure could support the desired analyzing the circuits. The remaining years of this effort Will SEU mitigation and power tool functionality. To accomplish focus more heavily on GptLqization techniques and this goal, efforts were divided hio wo major xeas: JHI)L validation. This paper will outline the JI'EIL tool Suite and tool modifications and the development of a robust EDF extensions made to it for the RHinO tookt in section 11. netlist import infrastructure. SEU Radiation effects are discussed in Section 111, and The JHDL tool suite is currently operational and fully power utilities are discussed in Section IV. Synergy with supports the xlhvhex2 FPGA. Although the tool is evolvable algorithms for mitigating SEL effects are discussed operational, there were a number of limitations within JHDL in Section V. Section VI will summarize the progress to date that needed revisiting in order to fully integrate the custom and draw conclusions. tools envisioned for this project efficiently. A new GUI API 11. The JHDL Tool Suite was developed to simplify the process of adding custom user interfaces to JHDL.This GUI API includes a new GUI event A. Back,oroound mechanism for custom applications to generate and catch A criticsl techology to ~e tool suite is the open- JHDL related GUI events (i.e. mouse click, cell selection, sourced JKDL ~13FPGA desi@ environment. This set of etc.). This new API allows for example power visualization, design tools allows a designer to create complex, high-speed viewers, and waveform to share FPGA circuit modules progammatically from with java.A information and allow an FPGA developer unified time, variety of design aids are available for circuits constructed in Signal, and Power data across multiple viewpoints of their JHDL. The tool suite, shown in Figure 1, contains a digital desi@. circuit simulator, a circuit hierarchy browser, FPGA library The second major task during the first year was the primitives, and tools for exporting user designs into EDIF development of a new EDF netlist too1. mL znd WL. JHDL provides an open into he circuit provides support for EDIF parsing and netlisting, there were to facilitate the creation of app~~cation-specifica number of disadvantages to the original implementation design aids for viewbg, revising, or that limit its use in this project. First, the EDIF parser was interacting with a user design. The integrated design aids, not desi@ed for memory efficiency and required far too circuit MI, and flexibility ofmLmake it an ideal tool for much memOV.to Parse full-chip designs. Second, the EDIF aiding the development of radiation-hardened and power- parser did not import multiple EDIF files for designs that aware space-based FPGA designs. A variety of application- import 3rd party P.To address these issues, a new EDIF specific tools can be created to analyze and improve the netlist tool was developed. This tool, developed reliability of FPGA circuits. independently from JHDL, supports the parsing of large EDIF netlists and can successfully merge multiple EDIF files. In addition, a JHDL export feature was added to allow this EDIF tool to generate JHDL designs and exploit all of the JHDL GUI and simulation tools. The EDIF netlist infrastructure is operational

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    6 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us