Ewildenberg (talk | contribs) m (Update todo) |
Ewildenberg (talk | contribs) m |
||
| Line 22: | Line 22: | ||
* Page on rough code style and commenting guidelines - do we enforce doxygen style comments? | * Page on rough code style and commenting guidelines - do we enforce doxygen style comments? | ||
* Page on navigating gitlab, merge requests, issues, etc. | * Page on navigating gitlab, merge requests, issues, etc. | ||
| − | --[[User:Ewildenberg|Ewildenberg]] ([[User talk:Ewildenberg|talk]]) | + | --[[User:Ewildenberg|Ewildenberg]] ([[User talk:Ewildenberg|talk]]) 22:27, 15 July 2021 (CDT) |
Revision as of 23:27, 15 July 2021
Firmware documentation TODO
Here is my rough list of things that should be done still:
- Finish setup guide, with descriptions on how to install rest of tools. A setup video or video series should also be made.
Git guide- VSCode
- CANoe/CANape
- ECU programming (motohawk/mototune)
- Matlab
- Uniflash
- C2Prog (inverter bootloader)
- Serial console (UART/putty)
- SVN setup page (not firmware specific, should be generic somewhere and just linked to from setup guide + brief summary
- Google drive setup page (also not firmware specific, same as above)
- Acronyms page (also not firmware specific, etc)
- Tutorial on doing blinky light on a TM4C, possibly also with video
- CCS page, tour of the basic features, with a troubleshooting section for common issues
- C2000 Bootloader page, including how to use
- TM4C Bootloader page, including how to use
- Tutorial or page on printing UART to console from TM4C
- CAN page, detail what it is, how it works, how the team uses it.
- pages on CANoe and CANape, possibly also tutorials on using them
- Page on rough code style and commenting guidelines - do we enforce doxygen style comments?
- Page on navigating gitlab, merge requests, issues, etc.
--Evan Wildenberg (talk) 22:27, 15 July 2021 (CDT)
