bcd7d57c11
Instead of OOCD_SERIAL triggering an attempt to use a specific ftdi based adapter, introduce common target/interface pairs, OOCD_INTERFACE and OOCD_TARGET, and an override via OOCD_FILE allowing full control. Further, attempt to connect to a running openocd instance to flash if possible. This _will not_ work well if you have multiple openocd instances open at once, but that's a rare use case. Examples: OOCD_INTERFACE=stlink-v2 OOCD_TARGET=stm32f0x --> openocd ... -f interface/stlink-v2.cfg -f target/stm32f0x.cfg) OOCD_FILE=board/ek-lm4f120xl.cfg --> openocd ... -f $(OOCD_FILE) (ie, the variable is passed untouched) As part of implementing this, correct variables that were always wrong, and update the openocd flashing commands to use current commands.
README
This example demonstrates the following:
- Configuriong GPIO pins
- Toggling GPIO pins
- Setting up and using GPIO interrupts
- Unlocking protected GPIO pins
- Controlling the system clock
- Changing the system clock on the fly
Flashes the Red, Green and Blue diodes on the board, in order. The system clock starts at 80MHz. Pressing SW2 toggles the system clock between 80MHz, 57MHz, 40MHz ,20MHz, and 16MHz by changing the PLL divisor. Pressing SW1 bypasses the PLL completely, and runs off the raw 16MHz clock provided by the external crystal oscillator. The LEDs will toggle at different speeds, depending on the system clock. The system clock changes are handled within the interrupt service routine.