Re: [OpenOCD-user] How do I support STM32F030F4P6 on openocd?

[Paul F. <fer...@gm...>]

Hi,

On Thu, Nov 06, 2014 at 02:39:06PM +0900, Kiwamu Okabe wrote:
> Then, I tried following commands, however, can't get success....
...
> $ arm-none-eabi-gdb build/hacker-emblem.elf
> (gdb) tar ext :3333
> Remote debugging using :3333
> reset () at sys.c:699
> 699       asm volatile ("cpsid  i\n\t"          /* Mask all interrupts. */

That means you've successfully connected and control the target equipment.

> (gdb) c
> Continuing.
> jtag status contains invalid mode value - communication failure
> Polling target stm32f0x.cpu failed, GDB will be halted. Polling again in 100ms

This means you let the firmware run and shortly after that the
firmware is either remapping the SWD pins or switching to some
extremely low frequency or entering some power saving mode, so the
debugger can no longer access the target at all.

So far everything seems normal, and you should also be able to do
"load" to reflash new firmware etc.

HTH
-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...