Hi
We have an application where STM32G071RB are used and can only be programmed via ST's Serial Bootloader. That works fine but after 1st programming, we realised that the Boot options bits in the Userbytes of the Flash memory need to be configured correctly to allow for subsequent Serial Bootloader access (these are all set by default):
To achieve that, within our applicaiton firmware, we wrote a code that programs those bits:
nBOOT_SEL to 0
nBOOT1 to 1
nBOOT0 to 0 (Although this will be ignored for the use case)
To boot in Serial boot mode, we set the PA14-nBoot0 pin to logic 1 and this all works perfect - so that's great.
The issue is that after few power cycles (random 5-10), the MCUs do not boot at all - neither in Normal mode to run application firmware, Nor can these be put in Serial bootloader mode. Also, these cannot be access using SWD interface.
For simplicity and to avoid any uncertainties in the custom hardware, we did this exercise on the Nucelo-G071RB and the same issue happens. We now have 2 Nucleo boards whose on board MCUs cannot be accessed via Serial Bootloader or SWD interface, and also these do not boot to run the Application firmware.
Here is the code snippet that we use to write the Boot related option bytes:
// Write required Option bits for Serial Bootloader, otherwise, MCU can only be revived using SWD interface
{
FLASH_OBProgramInitTypeDef OBStruct = {0};
HAL_FLASHEx_OBGetConfig(&OBStruct);
OBStruct.USERConfig = OBStruct.USERConfig & (~FLASH_OPTR_nBOOT_SEL);
OBStruct.USERConfig = OBStruct.USERConfig | FLASH_OPTR_nBOOT1;
OBStruct.USERConfig = OBStruct.USERConfig | FLASH_OPTR_nBOOT0;
OBStruct.OptionType = OPTIONBYTE_USER;
HAL_FLASH_Unlock();
HAL_FLASH_OB_Unlock();
HAL_FLASHEx_OBProgram(&OBStruct);
HAL_FLASH_OB_Lock();
HAL_FLASH_Lock();
HAL_FLASH_OB_Launch();
}
/* USER CODE END 2 */
Please could you advise on this what could be wrong with these MCUs and more importantly to recover these from this state?
Thanks
