Files
ODrive/docs/configuring-eclipse.md
T
Samuel Sadok 7f1873dfc4 Documentation reorganization
Move all documentation to docs/ and add a couple of layout/styling
files to customize the appearance when the documentation is
published on GitHub pages
2018-04-13 16:19:31 -07:00

35 lines
1.7 KiB
Markdown

# Setting up Eclipse development environment
## Install
* Install [Eclipse IDE for C/C++ Developers](http://www.eclipse.org/downloads/packages/eclipse-ide-cc-developers/neon3)
* Install the [OpenOCD Eclipse plugin](http://gnuarmeclipse.github.io/plugins/install/)
## Import project
* File -> Import -> C/C++ -> Existing Code as Makefile Project
* Browse for existing code location, find the OdriveFirmware root.
* In the Toolchain options, select `Cross GCC`
* Hit Finish
* Build the project (press ctrl-B)
![Toolchain options](screenshots/CodeAsMakefile.png "Toolchain options")
## Load the launch configuration
* File -> Import -> Run/Debug -> Launch Configurations -> Next
* Highlight (don't tick) the OdriveFirmare folder in the left column
* Tick OdriveFirmware.launch in the right column
* Hit Finish
![Launch Configurations](screenshots/ImportLaunch.png "Launch Configurations")
## Launch!
* Make sure the programmer is connected to the board as per [Flashing the firmware](#flashing-the-firmware).
* Press the down-arrow of the debug symbol in the toolbar, and hit Debug Configurations
* You can also hit Run -> Debug Configurations
* Highlight the debug configuration you imported, called OdriveFirmware. If you do not see the imported launch configuration rename your project to `ODriveFirmware` or edit the launch configuration to match your project name by unfiltering unavailable projects:
![Launch Configuration Filters](screenshots/LaunchConfigFilter.png "Launch Configuration Filters")
* Hit Debug
* Eclipse should flash the board for you and the program should start halted on the first instruction in `Main`
* Set beakpoints, step, hit Resume, etc.
* Make some cool features! ;D