1 ramp infrastructure status daniel burke 19 aug 08
TRANSCRIPT
2
““Transitioning to OpenRAMP…”Transitioning to OpenRAMP…”
OverviewOverview
Formal board support package for BEE3/RAMP2Formal board support package for BEE3/RAMP2 Provided now by BEEcube as part of purchase costProvided now by BEEcube as part of purchase cost Research support through Berkeley (sole point of contact)Research support through Berkeley (sole point of contact)
Current StatusCurrent Status BEE Repository upgrade status and evolutionBEE Repository upgrade status and evolution
Proposed BEE3/RAMP2 InfrastructureProposed BEE3/RAMP2 Infrastructure Online hardware stackOnline hardware stack Enhanced web resources to foster collaboration/disseminationEnhanced web resources to foster collaboration/dissemination
Infrastructure layers/responsibilitiesInfrastructure layers/responsibilities Documentation concernsDocumentation concerns
3
Where we are in the project?
Year 1Year 1 Year 2Year 2 Year 3Year 3
3/063/06 3/073/07 3/03/088
3/093/09
REDREDBLUEBLUE
GOLDGOLDWHITEWHITE
Areas for Improvement:Areas for Improvement:
Not adequate sharing between effortsNot adequate sharing between efforts Difficult for external groups to acquire and operate designs (Difficult for external groups to acquire and operate designs (manymany BEE2s in the field) BEE2s in the field) User support still not sufficientUser support still not sufficient Documentation insufficientDocumentation insufficient Basic reference designs would be beneficialBasic reference designs would be beneficial
Although lagging (optimistic) projected schedule, we should be disseminating results.Although lagging (optimistic) projected schedule, we should be disseminating results.
4
Current InfrastructureTwo Principal ElementsTwo Principal Elements
Hardware support: Hardware support: BEE2 board with accessories and cable set (UCB responsibility)BEE2 board with accessories and cable set (UCB responsibility) Establish/maintain online stack accessible by remote users (8 BEE2s)Establish/maintain online stack accessible by remote users (8 BEE2s)
Web/Gateware supportWeb/Gateware support Website for information and HW information (schematics/docs): Website for information and HW information (schematics/docs): ramp.eecs.berkeley.eduramp.eecs.berkeley.edu Library of archived designs and components: Library of archived designs and components: repository.eecs.berkeley.edurepository.eecs.berkeley.edu Means for submitting issues and obtaining help (listserv): Means for submitting issues and obtaining help (listserv): lists.berkeley.edulists.berkeley.edu
Users report difficult to use!Users report difficult to use!
5
Proposed InfrastructurePrimary ComponentsPrimary Components
Hardware support: Hardware support: BEE3 board with accessories (delegate to BEEcube)BEE3 board with accessories (delegate to BEEcube) Upgrade online stack accessible by remote users (6 BEE3s)Upgrade online stack accessible by remote users (6 BEE3s)
Web/gateware support with four discrete areas:Web/gateware support with four discrete areas:
1.1. Website for information and HW information (schematics/docs): Website for information and HW information (schematics/docs): openRAMP.orgopenRAMP.org New look: incorporate existing information, but expand to reflect broader communityNew look: incorporate existing information, but expand to reflect broader community
2.2. Repository of archived designs and components: Repository of archived designs and components: openRAMP.orgopenRAMP.org//librarylibrary RAMP-specific focus; move basic ref. designs/components to BEEcube.comRAMP-specific focus; move basic ref. designs/components to BEEcube.com
3.3. Forum for submitting RAMP issues and obtaining help: Forum for submitting RAMP issues and obtaining help: openRAMP.orgopenRAMP.org//forumforumNew interactive collaborative community for discussion and disseminationNew interactive collaborative community for discussion and dissemination
4.4. Mechanism for submitting RAMP bugs and monitoring fixes: Mechanism for submitting RAMP bugs and monitoring fixes:
openRAMP.orgopenRAMP.org//bugtrackingbugtrackingOperate in coordination with forum—faster response to issues.Operate in coordination with forum—faster response to issues.
6
Online Cluster of Hardware ComponentsOnline Cluster of Hardware Components
Hardware:Hardware: Scheduling softwareScheduling software
Power management Power management
Shared programming means: VMs and beekeeperShared programming means: VMs and beekeeper
Sun X4150 rackmount server to host VMsSun 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 drives4x146GB SAS drives
accessaccessRAMPRAMP
BEEKeeper
JTAG Chain
Backend System
Xilinx Tools
JTAG Chain
Group
JTAG Chain
JTAG Chain
Group
Group
Ethernet
BEEKeeper
Backend System, many FPGAs
BEEKeeper BEEKeeper
Group of JTAG
Chains #1
Group of JTAG
Chains #2
Group of JTAG
Chains #3
User 1
Xilinx Tools
User 2
Xilinx Tools
User 3
Xilinx Tools
LocalNetwork
BEEKeeper
Backend System
BEEKeeper
Group of JTAG
Chains
User
Xilinx Tools
UART UART
Front Panel Display
BEEKeeper Driver
Custom Tools
I2C
7
System Map
Power
XUPv5
BEE3BEE2
WinXP Fedora 9WinXP
OpenRAMP
RAMP Server
Test
Build
Internet
Virtual Virtual MachineMachiness
8
Web ComponentsWeb Components Facelift of main page and rebrand to Facelift of main page and rebrand to OpenRAMPOpenRAMP Repository Repository ForumForum BugtrackerBugtracker
OpenRAMP.orgOpenRAMP.orgOpenRAMP.orgOpenRAMP.org
9
ApplicationsSystems(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
Example: Gold Onion
Applications
System(Target/Back End)
Models(Implementation/Back End)
Abstraction Platform(Implementation/Back End)
Raw Platform(Host/Back End)
BEEcube*
11
Documentation
New emphasis on thorough docsNew emphasis on thorough docs
All components and projects submitted require documentationAll components and projects submitted require documentation Generate user guides and tutorials for ease of adoptionGenerate user guides and tutorials for ease of adoption For external consumption, offer Quickstart projects For external consumption, offer Quickstart projects User guides and manuals, as well as testbench generation require disciplined approach, but are User guides and manuals, as well as testbench generation require disciplined approach, but are
necessary for widespread success: the onus is on the PIs.necessary for widespread success: the onus is on the PIs.
12
Status
Delivery of 4 BEE3s FridayDelivery of 3 more following weekServer ordered and arrival pendingNetwork power switch undergoing configurationNetwork switch ordered and arrival pending
Use symmetry in Use symmetry in multi-FPGA system : multi-FPGA system : Program in parallelProgram in parallel
Bond multiple JTAG Bond multiple JTAG chains : Xilinx tools chains : Xilinx tools see one long chainsee one long chain
Program multi-FPGA systems efficiently
BEEKeeper
JTAG Chain
Backend System
Xilinx Tools
JTAG Chain
Group
JTAG Chain
JTAG Chain
Group
Group
Ethernet
See all FPGAs at once See all FPGAs at once connect to many connect to many BEEKeepersBEEKeepers
Share BEEKeepers Share BEEKeepers between users between users programmer accepts many programmer accepts many connectionsconnections
Use BEEKeeper in a large system
BEEKeeper
Backend System, many FPGAs
BEEKeeper BEEKeeper
Group of JTAG
Chains #1
Group of JTAG
Chains #2
Group of JTAG
Chains #3
User 1
Xilinx Tools
User 2
Xilinx Tools
User 3
Xilinx Tools
LocalNetwork
Remotely access debug Remotely access debug ports ports BEEKeeper tunnels IBEEKeeper tunnels I22C, C, UART, othersUART, others
Debug across entire Debug across entire system system Access signals from Access signals from multiple FPGAs simultaneouslymultiple FPGAs simultaneously
Remotely Manage and Debug System
BEEKeeper
Backend System
BEEKeeper
Group of JTAG
Chains
User
Xilinx Tools
UART UART
Front Panel Display
BEEKeeper Driver
Custom Tools
I2C