diff options
| author | Christopher Arndt | 2016-03-08 11:29:22 +0100 |
|---|---|---|
| committer | Damien George | 2016-03-09 23:00:17 +0000 |
| commit | 9b5e05a7c793ae0f3817af3ecba63f7b02713dea (patch) | |
| tree | 5fff38df95c7d4a4808bcc385d620840d72d7bee /stmhal/README.md | |
| parent | ad725a6661b2672cff5cdb7332dd01128505d3d9 (diff) | |
stmhal: Add makefile target and configuration to deploy via OpenOCD.
Diffstat (limited to 'stmhal/README.md')
| -rw-r--r-- | stmhal/README.md | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/stmhal/README.md b/stmhal/README.md index 457aaf996..6ebee3525 100644 --- a/stmhal/README.md +++ b/stmhal/README.md @@ -82,6 +82,21 @@ and set the `STLINK_DEVICE` environment variable accordingly, using the format $ make BOARD=STM32F4DISC deploy-stlink +### Flashing the Firmware with OpenOCD + +Another option to deploy the firmware on ST Discovery or Nucleo boards with a +ST-LINK interface uses [OpenOCD](http://openocd.org/). Connect the board with +a mini USB cable to its ST-LINK USB port and then use the make target +`deploy-openocd`. For example, if you have the STM32F4DISCOVERY board: + + $ make BOARD=STM32F4DISC deploy-openocd + +The `openocd` program, which writes the firmware to the target board's flash, +is configured via the file `stmhal/boards/openocd_stm32f4.cfg`. This +configuration should work for all boards based on a STM32F4xx MCU with a +ST-LINKv2 interface. You can override the path to this configuration by setting +`OPENOCD_CONFIG` in your Makefile or on the command line. + Accessing the board ------------------- |