• 1x BeagleBone Green
• 1x Zen cape: custom built I/O cape; may be Green (V1) or Red (V1.1)
• 1x 1/2 sized breadboard
• ~3x LEDs: such as blue, yellow, red, red (big), green (big), blue (big)
• 1x tri-colour
• ~3x Buttons, or these buttons.
• Resistors: 1,000 Ohm (1k), or 10,000 Ohms (10k),
  and 470 Ohms (0.47k)
• 1x Photocell light sensor or this photoresistor
• Jumper wires: female-to-male, and male-to-male (may be of slightly different lengths)
• 1x 8-LED NeoPixel stick
• 1x Stacking header to make it easier to connect wires to P8 and P9 headers
• 1x micro USB cable (plus one short one included with the BBG)
• 1x Mounting plate (or similar)
• 1x Anti-static bag, large enough to put in assembled BBG + Zen + mounting plate. Zen cape is likely already in this bag.
• Plastic box to put everything in.
• Some kits may also include:
  • TMP36 analog temperature sensor (not needed)

• If assignment was done as a pair, it's best to have both people there (but not required).
• Each student get 1 free no-show to a marking appointment; after that a 5% penalty for each subsequent unexcused no-show.
  Email the TAs and instructor if you are unable to make a sign-up appointment.

Process

• A few days after each assignment is due, the instructor will share a link for how to sign-up for demo slots.
  • Most demos will be in Surrey, but some in Burnaby may be possible.
  • If you will need to compile your project on the TA's laptop (don't have one yourself), you will need to indicate that when signing up: At most one student per time-slot (per TA) can need the TA's laptop.
• When you arrive for your demo, check in with the TA who may have a sign-in sheet to ensure students are marked in the correct order.
  • TAs will mark students in the order of their time-slots, not first-come-first-serve.
  • If a student misses their time slot (and the TA was ready for them), then they will have to wait until the TA has a free moment (after students who have marking appointments).
• If you have your own laptop (or are borrowing a friend's), then have your VM and web-browser up and running, and your BeagleBone booted.
  • If you do not have your own laptop capable of running the software, then the TA will have a computer that can be used. Their computer will be setup in the way described in the guides. On their computer, they may want you to do the work of extracting/building/..., or they may do it themselves with you there.
  • Either way, should expect to bring your BeagleBone and Zen cape to the marking.
• During the demo you will likely need to do the following while the TA is watching:
  1. Download your code from CourSys
  2. Compile without any errors (warnings OK, but you should really resolve those!)
  3. Run your code on your BBG
  4. You and the TA will exercise your program, showing how it handles both simple and edge use cases (trying to find bugs!). Likely using tools as required by the assignment such as valgrind, a web browser, or netcat. The TA will likely play around with your solution, possibly getting your help to do things as needed.
  5. Show the TA your code inside of your IDE (or, perhaps they will load it on their computer). They may ask you to explain or discuss some aspect of your code to ensure that you wrote it with at most a reasonable amount of help from others/online/AI.
• The TA will likely take notes as they go, and give you feedback as well. They may comment on the functionality of your solution, or on things they notice in your code (good and bad).
  • The TA will likely look at any other files submitted for the assignment (output captures, etc) while you are building your assignment.
  • If there are any misunderstandings about requirements, or how to get things running, you and the TA can discuss the issue.
  • There may be a mark penalty if any changes to the code are needed in order to get it working. The TA will assign any deductions based on what they feel is reasonable. If there are any disagreements, you and the TA should work on finishing marking and capturing your solution's behaviour; then you can talk to the instructor to work out any issues.
• During the demo, expect to get feedback on your work and how to improve. Treat this feedback as constructive criticism. It will be given to you respecting you and your abilities, and shared as an educator providing feedback on your work.
  • Marking is not expected to be a debate: students are welcome to comment on how to demonstrate the full functionality of their solution; however, it is the TA's decision about what is and is not worth marks, or what triggers a deduction. If a discussion between the student and TA cannot easily be resolved, the student is encouraged to discuss it with the instructor.