EECS 373 Labs

News Piazza Project Lecture Homework Gradescope Labs References Description Times Schedule Staff

Lab Postings and Due Dates

Each lab assignment is indicated as a link to Lab #. Important support documents such as tutorials and examples are also listed with each lab. Each assignment is due during the week indicated within the first hour of the home lab unless an exception is noted. See below for details regarding submissions, late policies and assignment types.

Lab 1: Hardware Tools: Week of 8 January

Lab 2: Software Tools: Week of 15 January

Lab 3: Memory Mapped IO: Week of 22 January

Lab 4: Interrupts: Week of 29 January

Lab 5: Timers: Weeks of 5 and 12 February

Lab 6: Serial interfaces: Week of 19 February, 5 March

Lab 7: ADCs and DACs: Week of 12 March

Assignments

Each lab may have one more of the following parts.

Pre-Lab (Pre-Lab Ans)

The pre-lab typically consists of a set of questions designed to provide you with essential lab background. This assignment must be completed and submitted individually. Presently only lab 3 has a pre-lab assignment.

In-Lab Questions (In Lab Ans)

Many of the labs have a few questions posed during an in-lab exercise. Answers to these questions or screen shots from logic analyzers or scopes can be completed by the lab team and submitted by the lab team. Be sure to include everyones name on the submission.

Lab Demonstration (Lab Demo)

All labs will have one or more demonstrations that you will perform for the lab instructor. A demonstration must be filled out with all group members names, signed, dated and collected by one of the lab staff.

Post Lab Questions (Post Lab Ans)

Many of the labs have a few questions posed during an in-lab exercise. Answers to these questions or screen shots from logic analyzers or scopes can be completed by the lab team and submitted by the lab team. Be sure to include everyones name on the submission.

Assignment Submission Policy

Common Debugging Problems

See this link to see common debugging problems with Libero, SoftConsole and lab specific issues. The document is periodically updated by the staff so check for updates.

Lab Document Organization

For the most part, the labs start with an example design or walk through style exercise. The intention is that you will develop enough experience with the topic and tools to do a follow up assignment. The follow up assignment is generally a hardware, software or combination of both design problem. For example, in Lab 1 you will do a tutorial showing you how to implement hardware in the FPGA. The post lab assignment asks you to implement a simple hardware application. You will generally be asked to verify your design to the lab staff. There may even be some follow up questions.

Lab Partners

The 373 labs are difficult requiring the efforts of 2 or more people. You should find that it is easier especially with debugging to have someone to bounce ideas off of while you are working. There are also a limited number of stations in 373 limiting solo lab work.

You may choose your lab partner. If you don't know anyone in your section you want to work with, introduce yourself to someone and get started. If you discover you cannot work with your partner, consult the lab coordinator and resolve the issue as soon as possible.

Lab Safety Policy

You will be given 24 hours access to the lab on the first day of lab. Most of the lab time is unsupervised so it is very important that we you follow our safety policies during those times. On the first day you will be asked to read and sign a safety policy document acknowledging your understanding of the policy.

Lab Access

You will be given access to the lab via door keypad entry. You may use the lab anytime there is not a conflict (check lab schedule). It is imperative you follow the posted lab safety and use policy.

Attendance Policy

Home Lab Sections: You may attend any 373 home lab pending availability and the discretion of the lab instructor. Home lab students always have priority for stations.

Open Lab Sections: You may attend any staffed 373 open lab section and obtain priority help.

Alternate Resources

Libero and SoftConsole Software in CAEN Labs: Currently these tools are not available in the CAEN labs.

Free Libero SoC Web Pack Software: You can download Libero SoC software from the Microsemi website at no cost for your personal use. The software is designed to run on Windows OS. Having the software available for the project phase of the course can be very useful. It takes roughly 60 minutes to install. The lab currently uses Libero SoC version 11.7 with service pack 1. It can be found here. You will need to select the SmartFusion device during the install (not SmartFusion2). Do not install SoftConsole 3.4 with Libero install. It has some issues so we use the older version SoftConsole 3.3 at this link. You will also need to register and obtain a free license (disk ID locked). The instructions for obtaining the free license are here.

Although Microsemi does not officially support Libero or Softconsole on Windows 10 we have verified that it works and we are currently running it in the lab. We have verified that it works in Windows 7 and it should work in Windows 8, but we haven't tried it.

SmartFusion Kits: Each group will be provided a kit. If you want an extra kit they are available for loan. Kits need to be returned at the end of the term.

Lab Accounts

Logon to the W10 loads using your Kerbos PWD.

Page maintained by Robert Dick, Colin Szechy, and Matthew Smith.