1. 1 RAMP Infrastructure Status Daniel Burke 19 Aug 08

2. 2 “Transitioning to OpenRAMP…” Overview  Formal board support package for BEE3/RAMP2  Provided now by BEEcube as part of purchase cost  Research support through Berkeley (sole point of contact)  Current Status  BEE Repository upgrade status and evolution  Proposed BEE3/RAMP2 Infrastructure  Online hardware stack  Enhanced web resources to foster collaboration/dissemination  Infrastructure layers/responsibilities  Documentation concerns

3. 3 Where we are in the project? Year 1 Year 2 Year 3 3/06 3/07 3/08 3/09 RED BLUE GOLD WHITE Areas for Improvement:  Not adequate sharing between efforts  Difficult for external groups to acquire and operate designs (many BEE2s in the field)  User support still not sufficient  Documentation insufficient  Basic reference designs would be beneficial Although lagging (optimistic) projected schedule, we should be disseminating results.

4. 4 Current Infrastructure Two Principal Elements Hardware support:  BEE2 board with accessories and cable set (UCB responsibility)  Establish/maintain online stack accessible by remote users (8 BEE2s) Web/Gateware support  Website for information and HW information (schematics/docs): ramp.eecs.berkeley.edu  Library of archived designs and components: repository.eecs.berkeley.edu  Means for submitting issues and obtaining help (listserv): lists.berkeley.edu Users report difficult to use!

5. 5 Proposed Infrastructure Primary Components Hardware support:  BEE3 board with accessories (delegate to BEEcube)  Upgrade online stack accessible by remote users (6 BEE3s) Web/gateware support with four discrete areas: 1. Website for information and HW information (schematics/docs): openRAMP.org New look: incorporate existing information, but expand to reflect broader community New look: incorporate existing information, but expand to reflect broader community 2. Repository of archived designs and components: openRAMP.org / library RAMP-specific focus; move basic ref. designs/components to BEEcube.com RAMP-specific focus; move basic ref. designs/components to BEEcube.com 3. Forum for submitting RAMP issues and obtaining help: openRAMP.org / forum New interactive collaborative community for discussion and dissemination 4. Mechanism for submitting RAMP bugs and monitoring fixes: openRAMP.org / bugtracking Operate in coordination with forum—faster response to issues.

6. 6 Online Cluster of Hardware Components Hardware:  Scheduling software  Power management  Shared programming means: VMs and beekeeper  Sun X4150 rackmount server to host VMs 2x Quad-core Intel Xeon 2.66 GHz 2x Quad-core Intel Xeon 2.66 GHz 8x2GB memory 8x2GB memory 4x146GB SAS drives 4x146GB SAS drives accessRAMP

7. 7 System Map Power XUPv5 BEE3 BEE2 WinXP Fedora 9 WinXP OpenRAMP RAMP Server Test Build Internet Virtual Machines

8. 8 Web Components  Facelift of main page and rebrand to OpenRAMP  Repository  Forum  Bugtracker OpenRAMP.org OpenRAMP.org

9. 9 Applications Systems (Target/Back End) Models (Implementation/Back End) Abstraction Features (Implementation/Back End) Abstractions Mechanisms Library Components (Host & Implementation/Back End) Languages Raw Platform (Host/Back End) Infrastructure Elements

10. 10 Example: Gold Onion Applications System (Target/Back End) Models (Implementation/Back End) Abstraction Platform (Implementation/Back End) Raw Platform (Host/Back End) BEEcube *

11. 11 Documentation New emphasis on thorough docs  All components and projects submitted require documentation  Generate user guides and tutorials for ease of adoption  For external consumption, offer Quickstart projects  User guides and manuals, as well as testbench generation require disciplined approach, but are necessary for widespread success: the onus is on the PIs.

12. 12 Status   Delivery of 4 BEE3s Friday   Delivery of 3 more following week   Server ordered and arrival pending   Network power switch undergoing configuration   Network switch ordered and arrival pending

13. 13 Backup Slides

14.  Use symmetry in multi- FPGA system : Program in parallel  Bond multiple JTAG chains : Xilinx tools see one long chain Program multi-FPGA systems efficiently

15.  See all FPGAs at once connect to many BEEKeepers  Share BEEKeepers between users programmer accepts many connections Use BEEKeeper in a large system

16.  Remotely access debug ports BEEKeeper tunnels I 2 C, UART, others  Debug across entire system Access signals from multiple FPGAs simultaneously Remotely Manage and Debug System