User Tools

Site Tools


lab_2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

lab_2 [2018/05/18 11:06]
hutch [Submitting Source Code]
lab_2 [2018/05/18 11:07] (current)
hutch [Grading]
Line 263: Line 263:
   - 30% Code quality and adherence to the coding standard. You are allowed 10 freebies for this lab.   - 30% Code quality and adherence to the coding standard. You are allowed 10 freebies for this lab.
   - 70% Pass off. If your code works well and shows no bugs, you should get the full 70%.   - 70% Pass off. If your code works well and shows no bugs, you should get the full 70%.
 +
 +==== Submitting Source Code ====
 +Follow [[http://​ecen330wiki.groups.et.byu.net/​wiki/​doku.php?​id=submitting_source_code|this procedure]] to submit your source code to learning-suite.
 +
  
 ==== Notes ===== ==== Notes =====
  
   - The buttons_init() and switches_init() functions return an int that represents the status of the init(), i.e., was it successful or did it fail. For GPIO, there is no way to determine if the init() was successful or not. However, other init() functions that you may write may potentially fail. In these cases, returning a status value is helpful. For the sake of uniformity, all init() functions will return status even if there is no way for them to fail (as is the case with the GPIO).   - The buttons_init() and switches_init() functions return an int that represents the status of the init(), i.e., was it successful or did it fail. For GPIO, there is no way to determine if the init() was successful or not. However, other init() functions that you may write may potentially fail. In these cases, returning a status value is helpful. For the sake of uniformity, all init() functions will return status even if there is no way for them to fail (as is the case with the GPIO).
lab_2.txt ยท Last modified: 2018/05/18 11:07 by hutch