Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
user:kluong:improvement_-_bare_boards_for_every_generation [2021/03/30 15:21] kluong created |
user:kluong:improvement_-_bare_boards_for_every_generation [2021/09/19 21:59] (current) |
||
|---|---|---|---|
| Line 33: | Line 33: | ||
| Once these boards are created, they could be left permanently attached to the lab server, or another machine. This way, they can be easily shared among team members for testing, simply by just using the lab server as a development machine. You just need to SSH into the machine, compile and upload. This can be done remotely as well by anyone who needs to do testing. | Once these boards are created, they could be left permanently attached to the lab server, or another machine. This way, they can be easily shared among team members for testing, simply by just using the lab server as a development machine. You just need to SSH into the machine, compile and upload. This can be done remotely as well by anyone who needs to do testing. | ||
| + | |||
| + | |||
| + | **Who would be responsible for this** | ||
| + | |||
| + | I think this is something the hardware teams should deliver, especially since there is often some time waiting for boards to come back from fabrication. I would talk with the leadership team to make this a priority for every team | ||
| + | so that it can be properly scheduled in as a deliverable for every semester. | ||
| + | |||
| + | There should definitely be some help from the firmware team during the process to verify that the bare boards are working. | ||
| + | |||