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

Hi Andreas. Thank you for the information. It then seems that my problem is specific to the STM32F4 Discovery board which contains the STM32F407 only. It's great to hear that the 429 works with OpenOCD out-of-the-box. This means that OpenOCD probably need to handle the 407 board in a slight dif

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

Hi, Am 21.12.2014 um 04:13 schrieb Jens Bauer: > The most important thing first: Merry Christmas to all of you! Happy New Year. > Have anyone tried flashing a STM32F4 Discovery board lately ? Yes, I demo'ed our OpenOCD 0.8.0 package with the STM32F429I-DISCO at the openSUSE booth at ARM Tech Sy

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

Hi Peter, Paul and Spencer. Once again, John Frenz gave me valuable information on the OPTCR register. The following sequence allows me to write the new option values permanently to the OPTCR register: > reset halt; mww 0x40023C08 0x08192A3B; mww 0x40023C08 0x4C5D6E7F; mdw > 0x40023c14 > mww 0x4

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

Jens Bauer wrote: > ... I think it would make sense if OpenOCD reads the OPTCR register > and checks that it contains the right value. Certainly, and anyone trying to say otherwise is not helping. I'm sadly unsurprised that the check is missing in OpenOCD. > If not, it could either... > 1: Tell t

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

Hi Spencer and Paul. With the help from John Frenz on this post: I finally managed to write to the flash memory. The value that is supposed to be in OPTCR, according to John, is 0x0FFFAAED; he read this value from a board that was writable (and I believe it's unlocke

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

Hi Spencer and Paul. I didn't get any errors when I tried to flash-program the device, but the data did not show up in the Flash-memory. -So I decided to have a look at the status register right after issuing a flash image_write command: > reset halt target state: halted target halted due to de

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

Hi Spencer and Paul. On Mon, 22 Dec 2014 08:44:53 +, Spencer Oliver wrote: > Looking at the log you attached the cmds all look ok to me. > May be the watchdog that is causing problems - see > http://openocd.zylin.com/988 I tried doing this right after my first halt ... > mww 0xE0042008 4096

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

On 22 December 2014 at 06:58, Jens Bauer wrote: > Hi Paul. > > The reason I made a mdw 0, is that I understood that 0x0800 is mapped to > 0x by default. > Anyway, before I unlocked the board, All I got from OpenOCD was... > > in procedure 'mdw' > > ...for both 'mdw 0' and 'mdw 0x08000

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

Hi Paul. The reason I made a mdw 0, is that I understood that 0x0800 is mapped to 0x by default. Anyway, before I unlocked the board, All I got from OpenOCD was... in procedure 'mdw' ...for both 'mdw 0' and 'mdw 0x0800' (I know by now that "in procedure 'mdw'" means 'read error

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

Hey Jens, On Mon, Dec 22, 2014 at 04:58:02AM +0100, Jens Bauer wrote: > > halt > > stm32f4x unlock 0 > stm32f4x errata detected - fixing incorrect MCU_IDCODE > device id = 0x10006413 > flash size = 1024kbytes > stm32f2x unlocked. > INFO: a reset or power cycle is required for

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

Hi Paul. I just tried this ... > halt > stm32f4x unlock 0 stm32f4x errata detected - fixing incorrect MCU_IDCODE device id = 0x10006413 flash size = 1024kbytes stm32f2x unlocked. INFO: a reset or power cycle is required for the new settings to take effect. > mdw 0 1000 0x

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

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

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

Hi Paul. Thank you for the hints. :) I've gotten a small step further now, because 'stm32f4x unlock 0' stops the initial demo-firmware from running (even after a power-cycle). But I still get an error when trying to mass_erase ... > halt > stm32f4x unlock 0 stm32f2x unlocked. INFO: a reset or p

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

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

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

Hey, On Sun, Dec 21, 2014 at 04:13:37AM +0100, Jens Bauer wrote: > 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 disco

[OpenOCD-devel] Trouble with flashing STM32F4 Discovery

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.. ;) Have anyone tried flashing a STM32F4 Discovery board lately ? I'm asking, because I'm having some strange problems, and I believe that those probl