Re: [OpenOCD-devel] Trouble with flashing STM32F4 Discovery

[Jens B. <jen...@gp...>]

Hi John.

Thanks for the input and assuring me that the board can be recovered.
The board showed no signs of damage, though (I just couldn't get out from the 'demo' stage until Paul sent me the unlock information), so I'm not really worried that it's the case (yet). :)
Fortunately, it would take a lot of effort to brick a device permanently; I've managed to disable a LPC812 by setting the clock speed too high once, but I know that the device can be recovered even from that (I shelved that 812, though, so I can deal with it later).


Love
Jens

On Sun, 21 Dec 2014 20:35:47 +0000, John wrote:
> On Sun, Dec 21, 2014 at 04:13:37AM +0100, Jens Bauer wrote:
>> Hi all.
>> 
>> The most important thing first: Merry Christmas to all of you!
>> -And may there be a lot of Cortex-A15 boards under your trees this 
>> year.. ;)
> 
> Likewise!
> 
>> Have anyone tried flashing a STM32F4 Discovery board lately ?
>> 
>> I'm asking, because I'm having some strange problems, and I believe 
>> that those problems are 'unique to me' (like always) :)
>> I posted the question on my.st.com's forum, as I thought it was very 
>> likely that there are many discovery-board users there, and a few of 
>> them might have had the problem too.
> 
> I had trouble with that board, yes (with a 407VGT6 cpu).
> 
> It's a while ago and I'm not sure what happened - sorry! - but it turned
> out that OOcd had erased or reprogrammed wrongly the option bytes.
> 
> The board was then described as having 0KB of flash.
> 
> Back then I didn't even know there were such bytes describing the board
> so had no idea what was wrong but some reading and messing and I ended
> up getting the board back to working via ST's own tool on Windows,
> sadly.
> 
> I suspect if I'd known more I could have rescued it using OOcd and I do
> wish I'd made proper notes as to how I broke it in the first place, as I
> commonly do.  I'd got used to various ST / ARM boards just working
> through Ocd and by the time I realised something was very wrong it was a
> bit late to start taking notes.
> 
> Anyway, the good news is that it's not terminally damaged and can be
> rescued.
> 
> John
>