You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2018. It is now read-only.
Students document the process of flashing firmware onto their embedded board during Electronics Production, perhaps also in Electronics Design and Embedded Programming. Do they still need to document how they milled the pcb and flashed the firmware onto their embedded boards in subsequent assignments, e.g. Output Devices, Input Devices, Interface & Applications Programming and Final Project, including fabrication of the pcb?
Feedback from one of the global evaluators is that the student has to document his board fabrication process in more detail for his Input Devices week's assignment. The student's documentation here focused on the input devices, how they work and the programs that he wrote to interact with the input devices.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Students document the process of flashing firmware onto their embedded board during Electronics Production, perhaps also in Electronics Design and Embedded Programming. Do they still need to document how they milled the pcb and flashed the firmware onto their embedded boards in subsequent assignments, e.g. Output Devices, Input Devices, Interface & Applications Programming and Final Project, including fabrication of the pcb?
Feedback from one of the global evaluators is that the student has to document his board fabrication process in more detail for his Input Devices week's assignment. The student's documentation here focused on the input devices, how they work and the programs that he wrote to interact with the input devices.
The text was updated successfully, but these errors were encountered: