2178 views|3 replies

37

Posts

0

Resources
The OP
 

TrueStudio flashes STM32 project and prompts Verify failed, and now I am helpless [Copy link]

TrueStudio flashes STM32 project and prompts Verify failed. Now I am helpless.

Compilation is OK, debug is burned to stm32103c8t6, it was normal before, burning other small projects is also normal,
but this time burning GRBL is overturned, basically confirmed that there is a problem with the code or project settings, but I don't know where the problem is.
Now I feel helpless...

Downloading 888 bytes @ address 0x0800FD90 - Verify failed
Downloading 8 bytes @ address 0x08010108 - Verify failed
Downloading 4 bytes @ address 0x08010110 - Verify failed
Downloading 4 bytes @ address 0x08010114 - Verify failed
Downloading 1000 bytes @ address 0x08010118 - Verify failed
Downloading 896 bytes @ address 0x08010500 - Verify failed

The chip is stm32103c8t6, I changed it to stm32103XB, because after modifying GRBL and
adding some functions, the size exceeded the limit. I heard that XB and C8 use the same wafer, I tried it before and it was successful, but it
failed this time...

This post is from stm32/stm8

Latest reply

Have you checked to see if the following blocks are locked manually?   Details Published on 2021-5-17 23:13
 

7422

Posts

2

Resources
2
 

If Verify OK appears at the beginning but Verify failed appears at the end, it means the Flash capacity has been exceeded.

This post is from stm32/stm8

Comments

Judging from the results, it may be really exceeded, but in fact, xB has twice as much as C8, whether it is ROM or RAM. I have re-selected stm32f103CB in TrueStudio, and the content I modified is only a little bit. It is impossible to use up all the 128K ROM. At most, it is a little more than 64K.  Details Published on 2021-5-17 21:26
 
Personal signature

默认摸鱼,再摸鱼。2022、9、28

 

37

Posts

0

Resources
3
 
freebsder posted on 2021-5-16 21:39 The first Verification OK, and the latter Verification failed, which means that the Flash capacity has been exceeded.

Judging from the results, it may really be exceeded.

But in fact, xB has twice as much ROM and RAM as C8.

I have reselected stm32f103CB in TrueStudio, and the content I modified is only a little bit.

The 128K ROM is all used up, and at most it is a little more than 64K. It should be within the 128K of the xB. I really don't understand why it exceeds

This post is from stm32/stm8

Comments

Have you checked to see if the following blocks are locked manually?  Details Published on 2021-5-17 23:13
 
 

7422

Posts

2

Resources
4
 
vincent.liu posted on 2021-5-17 21:26 Judging from the results, it may really be exceeded, but in fact, xB has twice as much as C8, both in ROM and RAM. I am in TrueStudio...

Have you checked to see if the following blocks are locked manually?

This post is from stm32/stm8
 
Personal signature

默认摸鱼,再摸鱼。2022、9、28

 
 

Guess Your Favourite
Just looking around
Find a datasheet?

EEWorld Datasheet Technical Support

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京B2-20211791 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号
快速回复 返回顶部 Return list