Tue Mar 28 11:19:21 EDT 2017

openocd stlink

really... fucking dev tools.  can't figure out how to halt the
processor.  it comes up fine but won't go into halt.

Open On-Chip Debugger 0.9.0 (2015-05-28-17:08)
Licensed under GNU GPL v2
For bug reports, read
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.177706
Info : stm32f103c8t6.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection on tcp/3333
Info : device id = 0x20036410
Warn : STM32 flash size failed, probe inaccurate - assuming 128k flash
Info : flash size = 128kbytes
undefined debug reason 7 - target needs reset

Tried on HY-MiniSTM32V, separately powered.  Now "mon halt" worked:

1. power up board.
2. power up programmer
3. target remote
4. monitor halt

5. reset board
6. monitor halt

target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x61000000 pc: 0x08000288 msp: 0x20001ff0

Now trying fresh small strip board, stlink-powered.  That worked.

Looks like my board is bad.  Taking it out of the breadboard.