To build it, you'll need `gcc` or `clang`, as well as `make`, `libtool`, `pkg-config` version 0.23
or greater, and possibly others detailed [here](http://openocd.org/doc-release/README). Once you
have the prereqs, building is a standard process. Just note that you need to enable cmsis-dap, which is the protocol your computer will use to communicate with an ATMEL ICE debugger.
```
./bootstrap
./configure --enable-cmsis-dap
make
make install
```
## Basic Use
### Config files
When OpenOCD starts, it first processes some configuration commands. You can specify a specific
config file with `openocd -f path/to/your/config.cfg`, or by default it looks for `openocd.cfg`. At a minimum, OpenOCD needs to know how to communicate with the
programming/debug tool you're using (e.g. ATMEL ICE), and what microcontroller you're using. For
ATMEL ICE, we want `cmsis-dap`. (You can read more about what this means
To build it, you'll need `gcc` or `clang`, as well as `make`, `libtool`, `pkg-config` version 0.23
or greater, and possibly others detailed [here](http://openocd.org/doc-release/README). Once you
have the prereqs, building is a standard process. Just note that you need to enable cmsis-dap, which is the protocol your computer will use to communicate with an ATMEL ICE debugger.
```
./bootstrap
./configure --enable-cmsis-dap
make
make install
```
## Basic Use
### Config files
When OpenOCD starts, it first processes some configuration commands. You can specify a specific
config file with `openocd -f path/to/your/config.cfg`, or by default it looks for `openocd.cfg`. At a minimum, OpenOCD needs to know how to communicate with the
programming/debug tool you're using (e.g. ATMEL ICE), and what microcontroller you're using. For
ATMEL ICE, we want `cmsis-dap`. (You can read more about what this means