Skip to main content
steve23
Associate II
October 22, 2008
Question

STM32 - Flash programming timeout

  • October 22, 2008
  • 4 replies
  • 1354 views
Posted on October 22, 2008 at 09:04

STM32 - Flash programming timeout

    This topic has been closed for replies.

    4 replies

    steve23
    steve23Author
    Associate II
    May 17, 2011
    Posted on May 17, 2011 at 12:48

    Apparently, the controller seems to have changed its mind and today it's programmable again

    Problem solved. Thanks anyway.

    steve23
    steve23Author
    Associate II
    May 17, 2011
    Posted on May 17, 2011 at 12:48

    I just checked the eva-board again and recognized, that the controller on the board is not an STM32F103ZD, but an STM32F103ZE. Hence, the controller I tried to configure got completely wrong flash informations.

    Is there any way to completely reset the chip to the factory settings?

    steve23
    steve23Author
    Associate II
    May 17, 2011
    Posted on May 17, 2011 at 12:48

    Hi,

    I'm currently trying to program an STM32F103ZD with 284k Flash. In the beginning programming worked just fine but debugging was quiet slow. Thus, I checked the configurations and found out, that the controller has 284kB of flash memory but in the 'utilities' register the chip was set to 512kB and so I changed the settings of the memory address range to start at 0x08000000 with a size of 0x00047000.

    I tried to program, it seemed to work in the first place.

    Now, every time I try to program the device via JTAG interface it gives the error message ''flash timeout...'' or ''flash programming failed''. The full chip erase seems to work but nothing else.

    I tried the flash loader demonstrator but doesn't even get a connection.

    Is there any way I can revive the chip?

    Your help is much appreciated.

    Thanks.

    Steve

    [ This message was edited by: steve.haettasch on 22-10-2008 08:25 ]

    pt1
    Associate III
    May 17, 2011
    Posted on May 17, 2011 at 12:48

    Hi Steve,

    that's what I found so times. One day a feature works and the other it don't. The whole environment I'm working with (RIDE7/GNU) seems to be not very stable up to this time.

    Best regards Edi