CSCE UVM Hands-on Session-1 Pre-Work

Transcription

1 CSCE UVM Hands-on Session-1 Pre-Work Please complete the following steps before the lecture on Feb-16. These steps will help set-up the environment and tools necessary for the hands-on session. You are expected to bring your own machine (preferably a laptop) to the session. This serves as a sanity check of your system, connection and the HERA server. Post any issues you face with the below instructions on Piazza. Please realize that some issues might be specific to your system. It is your responsibility to ensure that this pre-work is completed before the session. Connect to the HERA Server: On Windows: Use Putty along with Xming or Mobaxterm. The detailed instructions are provided in tool_demo_manual.pdf. On Linux: From within the terminal $ ssh -X <username>@hera.ece.tamu.edu Enter your credentials (netid and password) To copy files between the server and your machine: Windows: winscp, Mobaxterm (check piazza for instructions) Linux: $ scp examplefile yourusername@yourserver:/home/yourusername/ ( Essentially, ensure that you can connect to the server and transfer files between your machine and the server. All the instructions below, assume that you use bash as your shell. To check this: $ echo $SHELL or $ echo $0 Expected output is: /bin/bash If you are using a different shell, switch your default shell to Bash or adapt the instructions to your shell. Clone Lab01 GitHub Repository: Create a GitHub user profile, if you do not have one already. Simply, login to the following site with your netid and howdy password: Create a clone of the lab repository in a directory of your choice: $ cd ~ $ git clone This step creates a copy of the lab files in your directory. A version control system, like GitHub, is slightly confusing initially. But it is immensely helpful in tracking changes, especially when working in a group. We will go through the basics of GitHub in the first session. In case you are impatient, check out this tutorial. It is strongly recommended that you complete your labs and project on GitHub (private view).

2 Verify that you have a clone of the repository. You must find a directory named lab01. $ ls $ cd ~/lab01 Enter the lab01 directory and verify its contents. You should see the following. Please peruse through the README and browse through the design files (top.sv). setup.sh A bash script to setup environment variables git_commands Some basic git commands README.md README first for file structure project A directory containing the relevant design files Clean Compile: Source the setup script: $ source setup.bash Success Check the setup: $ irun -version TOOL: irun s013 is your expected output. If you do not see this, setup was not successful. Go to the simulation folder: $ cd./project/sim/ Compile and elaborate the files: $ irun -f cmd_line_comp_elab.f You should see a directory INCA_libs. This directory stores the work library on compilation. The name INCA_libs is specific to the Cadence toolset. You should also see the log file irun.log. This has a detailed description of the compilation. It is useful to browse through this file. Open irun.log with a text editor of your choice (vim) and look for errors and warnings. $ vim irun.log The keywords for warnings and errors are *W and *E respectively. Search for errors in vim: :/*E You should see E486: Pattern not found: *E. At the end of the file, you should see Writing initial simulation snapshot: worklib.top:sv. Now we can conclude that compilation is clean and free of errors. It is helpful to understand the warnings in the log file. You could also peruse through the following files: file_list.f, and cmd_line_comp_elab.f. Clear up the simulation files: $./ALL_CLEAR Create your own GitHub Repository: The directory lab01 is your own local workspace. In order to have a backup of the changes, you need to create an online repository on GitHub and link the two. You cannot commit any changes to the original lab01 repository. Therefore, you need to create your own github repository.

3 Please ensure that you clear the simulation files (ALL_CLEAR) before this step. Disconnect from original repository: $ cd ~/lab01 $ git remote rm origin Login to Click on new repository on the top right:

4 Give your repository a name, and a description. Make it private. No need for a README or gitignore. Click on create repository. Connect your local workspace to this remote repository. Use the directions described under or push an existing repository from the command line

5 $ git remote add origin $ git push -u origin master Check the status of the local workspace: $ git status # On branch master nothing to commit, working directory clean is the expected result. Refresh your GitHub page. You will see all the files on your webpage. That s all folks! You are set for the first hands-on session.