Re: [OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-25 Thread Andreas Fritiofson
On Wed, May 25, 2016 at 2:32 PM, Paul Fertser wrote: > > On Wed, May 25, 2016 at 02:19:02PM +0200, Daniel Kowalski wrote: > > Debugging works correctly when I remove last script line (program). > > I don't know why debugger is stuck in half-working state after flashing > > chip. > > I'm still con

Re: [OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-25 Thread Paul Fertser
Hello, I'm glad you found it out finally! Please see few commits inline. On Wed, May 25, 2016 at 02:19:02PM +0200, Daniel Kowalski wrote: > Debugging works correctly when I remove last script line (program). > I don't know why debugger is stuck in half-working state after flashing > chip. "prog

Re: [OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-25 Thread Daniel Kowalski
On Wed, 25 May 2016 03:44:52 +0200 Daniel Kowalski wrote: > I downgraded openocd to v0.8.0 (compiled from sources) and it works > correctly (catches breakpoint). I had to change probe to jlink and > transport to jtag (I was using Jtag Lock-pick tiny 2 with SWD - FTDI > based), but it makes no dif

Re: [OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-24 Thread Daniel Kowalski
I downgraded openocd to v0.8.0 (compiled from sources) and it works correctly (catches breakpoint). I had to change probe to jlink and transport to jtag (I was using Jtag Lock-pick tiny 2 with SWD - FTDI based), but it makes no difference to openocd 0.9.0. I will try bisecting this tomorrow. Dani

Re: [OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-24 Thread Daniel Kowalski
On Tue, 24 May 2016 19:11:28 +0300 Paul Fertser wrote: > Hello, > > On Tue, May 24, 2016 at 04:29:01PM +0200, Daniel Kowalski wrote: > > I tried debugging this with gdb (arm-none-eabi version). GDB > > attaches to openocd correctly, I can setup breakpoints, and program > > halts in correct spo

Re: [OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-24 Thread Paul Fertser
Hello, On Tue, May 24, 2016 at 04:29:01PM +0200, Daniel Kowalski wrote: > I tried debugging this with gdb (arm-none-eabi version). GDB attaches > to openocd correctly, I can setup breakpoints, and program halts in > correct spot, but I cannot get any stack trace - it just prints > (gdb) bt > #0 0

[OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-24 Thread Daniel Kowalski
Hello, I am trying to debug strange behavior of malloc/free on STM32L151VCT6A (ARM,Cortex-M3,32k ram, 256k flash) with openocd and gdb. Gdb attaches to openocd fine, target can be halted, but I cannot get any backtrace, semms like information about mcu staus is not passed back to gdb. TL;DR; skip