cancel
Showing results for 
Search instead for 
Did you mean: 

STLINK-V3MINI is not doing the full erasing the memory in the second programming cycle. In the test system, we have two steps of full erase the flash memory. In the first it works well, but in the second it isn't able to do the flash erase.

RBitt.1
Associate II

After this second trial, the only way that I'm able to program the MCU is using the JLINK, but I would really need the STLINK-V3MINI working as expect.

5 REPLIES 5
Bruno_ST
ST Employee

Hello @RBitt.1​ 

Are you able to test is with a STLINK V2 ? Can you give me the version of STMCubeProgrammer you are using ( STM32_Programmer_CLI.exe -version) ?

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

RBitt.1
Associate II

Hi Bruno,

tested with STLINKv2 -> same issue

Cube updated to 2.10.0, tested with 2.9 as well, same issue.

RBitt.1
Associate II

Hi Bruno,

Is there any news/suggestion to test?

Thank you!

Piranha
Chief II

As always - use "connect under reset" and "hardware reset" modes.

Ciao @RBitt.1​ 

Sorry about the delay, it took me some time to find a STMF board.

I confirm that the right way to program is to execute the following command :

STM32_Programmer_CLI.exe -c port=SWD mode=UR -d <file_to_program> -ob rdp=0xBB

That should download the file and lock the device in RDP level 1. If you want to verify the download just, add -v just before -ob.

To unlock the part, (mass erase will be performed automatically), execute

STM32_Programmer_CLI.exe -c port=SWD mode=UR -ob rdp=0xAA

Is it ok for you ?

BR,

Bruno

PS: Please select as best answer to improve best hit on query

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.