stm32f103 - memory protection

[domanski0karol]

Posted on March 31, 2014 at 23:46

Hi, I have problem with my stm32f103, I use a st-link utility and I cant send program. When I try erase sectors I get error ''

Verify the memory protection.

''.

23:37:18 : ST-LINK Firmware version : V2J19S0

23:37:18 : Connected via SWD.23:37:18 : Connetion mode : Normal.23:37:18 : Debug in sleep and stop mode enabled.23:37:18 : Device ID:0x410 23:37:18 : Device flash Size : 128KBytes23:37:18 : Device family :STM32F10x Medium-density23:37:23 : Flash memory erased.23:37:34 : Flash page 0 erased.23:37:34 : Flash page 1 erased.23:37:34 : Flash page 2 erased.23:37:34 : Flash page 3 erased.23:37:34 : Flash page 4 erased.23:37:34 : Flash page 5 erased.23:37:34 : Flash page @0x08001800 is not erased. Verify the memory protection.23:37:34 : Flash page 7 erased.23:37:35 : Flash page 8 erased.23:37:35 : Flash page 9 erased.23:37:35 : Flash page @0x08002800 is not erased. Verify the memory protection.23:37:35 : Flash page 11 erased.23:37:35 : Flash page 12 erased.23:37:35 : Flash page 13 erased.23:37:35 : Flash page @0x08003800 is not erased. Verify the memory protection.23:37:35 : Flash page 15 erased.23:37:35 : Flash page 16 erased.23:37:35 : Flash page 17 erased.23:37:35 : Flash page @0x08004800 is not erased. Verify the memory protection.23:37:36 : Flash page 19 erased.23:37:36 : Flash page 20 erased.23:37:36 : Flash page 21 erased.23:37:36 : Flash page @0x08005800 is not erased. Verify the memory protection.23:37:36 : Flash page 23 erased.23:37:36 : Flash page 24 erased.23:37:36 : Flash page 25 erased.23:37:36 : Flash page @0x08006800 is not erased. Verify the memory protection.23:37:36 : Flash page 27 erased.23:37:36 : Flash page 28 erased.23:37:37 : Flash page 29 erased.23:37:37 : Flash page @0x08007800 is not erased. Verify the memory protection.23:37:37 : Flash page 31 erased.23:37:37 : Flash page 32 erased.23:37:37 : Flash page 33 erased.23:37:37 : Flash page @0x08008800 is not erased. Verify the memory protection.23:37:37 : Flash page 35 erased.23:37:37 : Flash page 36 erased.23:37:37 : Flash page 37 erased.23:37:37 : Flash page @0x08009800 is not erased. Verify the memory protection.23:37:38 : Flash page 39 erased.23:37:38 : Flash page 40 erased.23:37:38 : Flash page 41 erased.23:37:38 : Flash page @0x0800A800 is not erased. Verify the memory protection.23:37:38 : Flash page 43 erased.23:37:38 : Flash page 44 erased.23:37:38 : Flash page 45 erased.23:37:38 : Flash page @0x0800B800 is not erased. Verify the memory protection.23:37:38 : Flash page 47 erased.23:37:38 : Flash page 48 erased.23:37:38 : Flash page 49 erased.23:37:39 : Flash page @0x0800C800 is not erased. Verify the memory protection.23:37:39 : Flash page 51 erased.23:37:39 : Flash page 52 erased.23:37:39 : Flash page 53 erased.23:37:39 : Flash page @0x0800D800 is not erased. Verify the memory protection.23:37:39 : Flash page 55 erased.23:37:39 : Flash page 56 erased.23:37:39 : Flash page 57 erased.23:37:39 : Flash page @0x0800E800 is not erased. Verify the memory protection.23:37:39 : Flash page 59 erased.23:37:40 : Flash page 60 erased.23:37:40 : Flash page 61 erased.23:37:40 : Flash page @0x0800F800 is not erased. Verify the memory protection.23:37:40 : Flash page 63 erased.23:37:40 : Flash page 64 erased.23:37:40 : Flash page 65 erased.23:37:40 : Flash page @0x08010800 is not erased. Verify the memory protection.23:37:40 : Flash page 67 erased.23:37:40 : Flash page 68 erased.23:37:40 : Flash page 69 erased.23:37:40 : Flash page @0x08011800 is not erased. Verify the memory protection.23:37:41 : Flash page 71 erased.23:37:41 : Flash page 72 erased.23:37:41 : Flash page 73 erased.23:37:41 : Flash page @0x08012800 is not erased. Verify the memory protection.23:37:41 : Flash page 75 erased.23:37:41 : Flash page 76 erased.23:37:41 : Flash page 77 erased.23:37:41 : Flash page @0x08013800 is not erased. Verify the memory protection.23:37:41 : Flash page 79 erased.23:37:41 : Flash page 80 erased.23:37:42 : Flash page 81 erased.23:37:42 : Flash page @0x08014800 is not erased. Verify the memory protection.23:37:42 : Flash page 83 erased.23:37:42 : Flash page 84 erased.23:37:42 : Flash page 85 erased.23:37:42 : Flash page @0x08015800 is not erased. Verify the memory protection.23:37:42 : Flash page 87 erased.23:37:42 : Flash page 88 erased.23:37:42 : Flash page 89 erased.23:37:42 : Flash page @0x08016800 is not erased. Verify the memory protection.23:37:42 : Flash page 91 erased.23:37:43 : Flash page 92 erased.23:37:43 : Flash page 93 erased.23:37:43 : Flash page @0x08017800 is not erased. Verify the memory protection.23:37:43 : Flash page 95 erased.23:37:43 : Flash page 96 erased.23:37:43 : Flash page 97 erased.23:37:43 : Flash page @0x08018800 is not erased. Verify the memory protection.23:37:43 : Flash page 99 erased.23:37:43 : Flash page 100 erased.23:37:43 : Flash page 101 erased.23:37:43 : Flash page @0x08019800 is not erased. Verify the memory protection.23:37:44 : Flash page 103 erased.23:37:44 : Flash page 104 erased.23:37:44 : Flash page 105 erased.23:37:44 : Flash page @0x0801A800 is not erased. Verify the memory protection.23:37:44 : Flash page 107 erased.23:37:44 : Flash page 108 erased.23:37:44 : Flash page 109 erased.23:37:44 : Flash page @0x0801B800 is not erased. Verify the memory protection.23:37:44 : Flash page 111 erased.23:37:44 : Flash page 112 erased.23:37:45 : Flash page 113 erased.23:37:45 : Flash page @0x0801C800 is not erased. Verify the memory protection.23:37:45 : Flash page 115 erased.23:37:45 : Flash page 116 erased.23:37:45 : Flash page 117 erased.23:37:45 : Flash page @0x0801D800 is not erased. Verify the memory protection.23:37:45 : Flash page 119 erased.23:37:45 : Flash page 120 erased.23:37:45 : Flash page 121 erased.23:37:45 : Flash page @0x0801E800 is not erased. Verify the memory protection.23:37:45 : Flash page 123 erased.23:37:46 : Flash page 124 erased.23:37:46 : Flash page 125 erased.23:37:46 : Flash page @0x0801F800 is not erased. Verify the memory protection.23:37:46 : Flash page 127 erased.23:37:53 : [fibon.bin] opened successfully.23:38:14 : Memory-Loader error23:38:14 : Error occured during erase operation!23:38:15 : Programming error @ 0x200008F4!Another error from true studio. #prot #memory #flash #stm32f103

[chen]

Posted on April 02, 2014 at 11:58

Hi

''I can put program into processor in other low power modes'' This does not sound right. ALL the low power mode stop the ARM core from running! It should NOT be possible to download binaries into the STM32 when it is in a low power mode! There is a contradiction in what you are reporting : You say you are using the ST Link Utility - this should stop any program running and put processor into debug mode. You also show a screen capture from Atollic. Now you say that you are programming in a low power mode. It is not possible to debug/program in any low power mode. Disable the low power mode when programming.

[domanski0karol]

Posted on April 02, 2014 at 13:39

I try different Connection mode from Settings, but always I get the same error: some of pages have memory protection. 

[chen]

Posted on April 02, 2014 at 13:49

Hi

One thought comes to mind : How old is your stm32f103? How many erase/program cycles has the stm32f103 been through? Is this an Eval board or a board that has been designed and built? How reliable is the power? How reliable is the ST-Link connection to the STM32 processor?

[Tesla DeLorean]

Posted on April 02, 2014 at 16:06

I can only send to stm32f103 stm32f10xLoader.bin from st-link folders, when I try to send the other .bin or .hex files I get error.

Trying to wrap my head around why that's an appropriate file to burn to the device? Wouldn't you want to burn a board appropriate file that blinks LEDs or output via the USART?

[domanski0karol]

Posted on April 02, 2014 at 16:13

The stm32f103 is new, I send program to processor about 100-200 times. Stm32f103 is using in my project which I have designed, few days ago all was OK. The power and connection is ok. 

Perhaps the firmware on st-link processor isnt good, but why I can send program into stm32f3? I try different types of them.

[Tesla DeLorean]

Posted on April 02, 2014 at 16:26

Perhaps the firmware on st-link processor isnt good, but why I can send program into stm32f3?

Perhaps, but it sounds like a diagnosis of convenience. More probable is a design and/or manufacturing issue with your board. What other validation have you done? Can you use the System Loader via USART or USB?

[domanski0karol]

Posted on April 02, 2014 at 19:35

When I try connect via uart also get error.

Why I may send stm32f10xLoader.bin to processor while when I send different files I get error?

[Tesla DeLorean]

Posted on April 02, 2014 at 19:59

BOOT0 = High?

Why I may send stm32f10xLoader.bin to processor while when I send different files I get error? I don't know, it's very small and designed to run in RAM? It's clearly not an appropriate file to flash into the device. If your board used to work, and now doesn't, go back in your mind and consider what you might have changed, or what might have happened too the board. Go back to the software that worked, does that work now?

[domanski0karol]

Posted on April 02, 2014 at 23:07

Yes, boot0 = 1.

I remember that I try send to stm32f3 demo example, next I download st-link utility and perhaps I updated st-link firmware. Is it possible to block the flash memory? Its very odd that just some of them. Where I find the original firmware to st-link stm32f3discovery?

[Tesla DeLorean]

Posted on April 03, 2014 at 00:35

Yes, it is rather odd.

The thread I cited earlier links to several firmware versions, the various ST-LINK Utilities also have some too, I might have some older ones lying around.

Google had these when I went fishing

yesterday

..

https://drive.google.com/folderview?id=0Bzv7UpKpOQhnbXJVVEg4VUo2M1k