Hardware Access

Remote FPGA development systems for PowerCommons contributors.

Available Systems

PowerCommons provides remote access to FPGA hardware for developers without boards.

University of Oregon FPGA Lab

• Location: Eugene, Oregon, USA
• Access: SSH + VPN
• Boards: VCU-118, Arty A7
• Status: Active
• Cost: Free for contributors

See UO FPGA Systems for details.

Access Requirements

Eligibility

• Active PowerCommons contributor (commits, documentation, testing)
• Students and researchers in open hardware
• Request approved by advisory board

Request Process

1. Create account: codeberg.org (if not already)
2. Submit request: Email [email protected]
3. Provide:
   • Name and affiliation
   • Codeberg username
   • Project description
   • Estimated usage (hours/week)
4. Wait for approval: Typically 2-3 business days
5. Receive credentials: VPN config and SSH key

Usage Guidelines

Fair Use Policy

• Time limits: Max 4 hours continuous use
• Scheduling: Use provided calendar system
• Priority: Active development > testing > learning
• Sharing: Do not share credentials

Responsibilities

• Clean up files after sessions
• Report hardware issues immediately
• Acknowledge PowerCommons in publications
• Contribute improvements back to project

What You Can Do

With Remote Access

✓ Program FPGAs remotely ✓ Access serial console ✓ Run synthesis and builds ✓ Test bitstreams ✓ Debug hardware issues

Not Available

✗ Physical board access ✗ Logic analyzer/oscilloscope ✗ Board modifications ✗ Long-running jobs (>4 hours)

Alternative Options

No Remote Access Yet?

1. Use prebuilt bitstreams: Downloads
2. Simulation: GHDL/Verilator for functional testing
3. Buy affordable board: Arty A7 (~$250)
4. Apply for grant: Funding opportunities

Supported Boards

See Supported Boards for compatibility and board recommendations.

Support

Questions about hardware access?

• Email: [email protected]
• Matrix: #powercommons:matrix.org