UC Berkeley CS150

Lab Guide

Lab Checkoff Procedure

Lab checkoffs will be done at the end of the first or beginning of the second lab after they are released. Each lab checkoff consists of two parts:

  1. The checkoff sheet is a handwritten(or typed) set of answers to questions listed at the bottom of their relevant sections in the lab document. Be prepared to explain any of your written answers orally.

  2. The hardware demo is exactly what it sounds like, show us, on board, what your design does. This means you need to save your .bit files for checkoff! The best place to do this is in your home directory.

125 Cory, CentOS 5.5 Machines

Software

Text Editor

Version Control

Shell

Noteworthy Directories

Working Remotely

There are 33 machines in the lab, p380-[11-45].eecs.berkeley.edu, all of which can be accessed through a variety of means. You can do anything working remotely that you can do locally, except test hardware implementations. Since you will have access to that hardware, even when working remotely, do not run any programs that affect the hardware, or block resources required when working locally(impact, chipscope, serial terminals, tftp daemons, etc.).

SSH

Fast, text based, good if you do not need any sort of graphical display.

SSH X Forwarding

If you need a graphical display, X window forwarding works, but is very slow.

NX Client

For graphical displays we suggest using NX Client. The download is free, and the configuration is simple. You merely need to get a copy of ~cs150/nx@inst.pub and tell NX Client to use it as your key, then login with your CS150 account. Unfortunately we have a limit of 2 heads per server, please be sure to terminate your sessions when you are done.