Meetings will be on Sundays at 3pm via Zoom.
Using avrdude/Atmel Studio to flash code
You should have sufficient comments such that someone who has general assembly experience but zero AVR experience can understand your code.
Every block of code should have a description of what it does.
Different parts of the program should be visually separated.
When you're using a general purpose register, say what it's being used for.
Use // for comments instead of ;
There will be code reviews and you will be sad if you didn't follow these guidelines.
If you send code over Slack or put it in the GrabCAD / Google Drive, you are required to buy Rohan a snack from the vending machine.
The only thing that should be in the esc-firmware repo is the code/files for the actual firmware. Everything else should be in esc-testing repo.
Use branches to prevent exciting merge conflicts.
Atmel AVR Manual - Also see the purple binder in the lab
GreatScott ESC Video <-- Required viewing (parts 1 and 2)
Source code for firmware on BlueRobotics ESCs
Slides about useful assemble features (Macros, preprocessor, etc.)