stm32F103R8 chip programming problem

[TOPGUN]

Hi

It's just that something strange happened to me

If I use RKit-ARM 1.68.18.0108 I get the following CheckSum "D9D0460"

But if I upgrade RKit-ARM to 1.72.19.0253, there will be a version error problem

But 1.72.19.0253 is to fix the problem of CheckSum display, so I have this dilemma now

[TDK]

Can STM32CubeProgrammer connect and work correctly? If so, likely a bug in the software you're using.

[TOPGUN]

STM32CubeProgrammer cannot read Cheaksum,so our engineer donot like use,but if we use RLink Programming tool to test be ok

So Sad,What can i do? 

[Peter BENSCH · Accepted solution]

The checksum used there with only 32 bits is probably just a simple summation of the contents of the Flash area. Such checksums were still used in earlier EPROMs of the last century because their storage capacity was small enough to detect possible bit errors.

Because of this procedure, the significantly larger flash area of the STM32 and the small data width of the checksum, the sense is rather questionable, especially since the STM32CubeProgrammer also offers a bit-by-bit comparison of the programmed area after programming.

As @TDK​  has already indicated, the use of the STM32CubeProgrammer would be strongly recommended.

Regards

/Peter

[TOPGUN]

ok, thanks for your suggestion

I will discuss with my supervisor

[TDK]

You also do not need to use STM32CubeProgrammer permanently , but checking it would help to narrow down the problem to a connection issue or a software issue.