Re: [OpenOCD-user] stm32f4 discovery

[Tim S. <ti...@kr...>]

Hi Spencer

Sorry for the late reply, i was t
> > Even for the risk of spamming this mailing list. I have two stm32f4
> > discovery boards lying around. One has an updated firmware from a testrun
> > with atollic studio (if i remember correctly). I started both with
> > 
> >   openocd -f interface/stlink-v2.cfg -f board/stm32f4discovery.cfg -d3
> 
> Be careful as the board cfg in this case already includes the interface,
> this would be safer as a test.
> 
> openocd -f interface/stlink-v2.cfg -f target/stm32f4x_stlink.cfg -d3
> 
> or
> 
> openocd -f board/stm32f4discovery.cfg -d3
Both commands work with  0.8.0-dev-00195-g4e79b48 (2013-09-30-09:04)
and the v16 stlink v2 framework. Tested with two devices one oneboard stlink 
and one standalone device. Works also with openOCD 0.7.0 windows.

> > The output is attached. The first difference i noticed that in line 164
> > the
> > version is different v14 vs. v15. In the next line the mode is different.
The v15 version is not working at all not with the 0.8.0 mentioned above nor
with the 0.7.0 release.

> The mode is nothing to be concerned about, 0x02 means it is setup for
> debugging. It appears your issues are caused because all reads are
> returning 0, as to why I am unsure.
> 
> The version of OpenOCD you are using includes some changes I have made
> recently to the stlink driver, can you try an older version or if
> possible a git bisect?
As for the v15 stm32f4discovery board here: After i managed to update the 
firmware on this board it still does not work. I tried v14 (which worked with 
the other stm32discovery board i happen to have) and v17 from your archive.

Both show strange listings of nr of breakpoints. As i have three other boards
with different firmwares which work, i tend to say that this board might have an 
hw error?

Best regards
Tim