Error: failed to erase memory

[pozeetive]

Hello,

So, i have created a small project in which the diagnostic information was saved in the internal flash of STM32F429ZET6 at the time of a crash. So, to test this project i have triggered usage-fault exception in an infinite loop by dividing a number via 0.
In the exception handler, i'm capturing and storing the diagnostic information in sector 0 of internal flash (I have modified the linker script to reserve this area, and configured sector 0 as non-executable area via MPU). The below is the logic i am using to store the diagnostic info.

FLASH_OBProgramInitTypeDef OBInit;

HAL_FLASH_OB_Unlock();

OBInit.OptionType = OPTIONBYTE_WRP;
OBInit.WRPSector  = OB_WRP_SECTOR_0;  
OBInit.WRPState   = OB_WRPSTATE_DISABLE;    

HAL_FLASHEx_OBProgram(&OBInit);
    
HAL_FLASH_OB_Launch();
HAL_FLASH_OB_Lock();


HAL_FLASH_Unlock();

HAL_FLASH_Program(FLASH_TYPEPROGRAM_WORD, list_ad, p_gnl[i]);

HAL_FLASH_Program(FLASH_TYPEPROGRAM_WORD, diag_ad, p_gnl[i])

HAL_FLASH_Lock();

HAL_FLASH_OB_Unlock();

OBInit.OptionType = OPTIONBYTE_WRP;
OBInit.WRPState   = OB_WRPSTATE_ENABLE;
OBInit.WRPSector  = OB_WRP_SECTOR_0;

HAL_FLASHEx_OBProgram(&OBInit);
HAL_FLASH_OB_Launch();
HAL_FLASH_OB_Lock();

And now, after i flash this code, i could not flash other code, this is the error i'm getting :

Error: failed to erase memory

Error: failed to erase memory

Encountered Error when opening C:\ST\STM32CubeIDE_1.17.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.0.202409170845\tools\bin\STM32_Programmer_CLI.exe

Error in STM32CubeProgrammer

Shutting down...

Exit.

Please help me fix this issue.

Thanks in advance.

[TDK]

Dont do stuff with flash in the first 1s of a program running or the debugger will have a hard time maintaining a connection.

Hold BOOT0 high during reset to boot in the bootloader and erase the chip to recover.

[pozeetive]

Hello @TDK,

I have followed your suggestion, i have provided 3.3v to BOOT0 pin and in STM CUBE Programmer and in ST-LINK Configuration i have kept the mode 'under reset', and i have tried to connect via resetting the MCU, but the connection failed and it says "the target was held under reset", but when i try to connect without resetting it is connected but i'm unable to perform chip erase/flash operations. 

[TDK]

> but i'm unable to perform chip erase/flash operations. 

Why not? What happens when you try?

[pozeetive]

I'm getting an error like unable to perform sector erase as the sector is protected something like this, i have also tried to disable the nWRP for all sectors but it is also failing and i'm getting error like this operation is initiated after OB_LAUNCH.

[TDK]

If you want help, please provide the full error message.

You enable WRP in the code, so you will need to disable it in CubeProgrammer. Show what you're doing. First disable WRP, then erase the chip. Screenshots help, vague "something like this" error messages not as much.

[pozeetive]

Hello @TDK ,

I apologize, When i try to disable the WRP I am getting this error.

And also when i try to erase the chip, this error is generated.

When i try to connect the device by changing the mode to 'under-reset' and holding the reset button this is the generated error.

[TDK]

Not real sure.

You have this board, correct?

https://www.st.com/en/evaluation-tools/32f429idiscovery.html

The flash size it's reading out is incorrect. I have an older version of this board and it works fine there.

Do you need the external loader? I don't think this board has additional on-board flash memory.

Are you on v2.19.0 of STM32CubeProgrammer?

[pozeetive]

Yes i do have this board(STM32F429ZIT6-DISC1), but i am using this board as ST-Link, my main target board has STM32F429ZET6 and this has 512KB of internal Flash.

I am on v2.18.0 of STM32 CUBE Programmer.

[TDK]

Okay, so custom board.

Has it ever worked?

Is part orientation correct?

Is the board powered?

Is VCAP voltage correct?

Can you share schematic?

Is NRST being held low as the error message suggests?

Is the onboard ST-Link disconnected from the onboard chip? Probably the CN4 jumpers.