Accepted Solutions
So I found this info,
When my device is up, it has the option "OTA Reboot Request" when I use ST Ble Toolbox,
I write Hex "000702" but nothing is happening
My code has
case CUSTOM_STM_BOOT_REQUEST_EVT:
*(uint32_t*)(SRAM1_BASE) = *(uint32_t*)pNotification->DataTransfered.pPayload;
NVIC_SystemReset();
break;
Do I understand the logic is OTA loader will use the information from SRAM1_BASE (which is define at 0x20000000UL, to erase my 2 sector starting at 0x08007000?
#define SRAM_BASE (0x20000000UL)/*!< SRAM(up to 256 KB) base address */
#define SRAM1_BASE SRAM_BASE /*!< SRAM1(up to 192 KB) base address */
If I used the programmer, and manually erased 2 sectors starting from 0x08007000, after the power cycle, my device always comes up with STM_OTA which is the OTA loader application was loaded at 0x08000000.
Please suggest where should I need to double check or my errors.
Hello @Jtron.1​ ,
Please not that I am not an expert of BLE or OTA, but from my own experience I could give you some advises.
First of all, may I have for information about your configuration?
What MCU are you using, running on an EVAL board ? What binary OTA application do you flash ? It is the last release ?
For the following I am assuming that your are running an custom BLE application.
Here is the general idea of procedure for OTA application:
- {Ensure your BLE stack is update and running}
- Flash OTA application at @0x08000000
- Add OTA reboot characteristic to one of your BLE service
- Managed the OTA reboot characteristic
In custom_app.c:
...
case CUSTOM_STM_OTA_REBOOT_REQUEST_WRITE_EVT:
/* USER CODE BEGIN CUSTOM_STM_OTA_REBOOT_REQUEST_WRITE_EVT */
APP_DBG_MSG("\r\n\r** OTA Reboot event!\n");
/* Write reboot reason at 0x20000000 (SRAM1):
* Boot Mode: 0x00-> User Application (0x08007000), 0x01-> OTA application (0x08000000)
* Sector index: 0x07 (7 sectors is the first to be program)
* Number of sector to be erase (4K granulation): Filesize/4K + 1
* Total: 3bytes (octets).
* */
*(uint32_t *)SRAM1_BASE = *(uint32_t*)pNotification->DataTransfered.pPayload;
NVIC_SystemReset();
while(1);
/* USER CODE END CUSTOM_STM_OTA_REBOOT_REQUEST_WRITE_EVT */
break;
...- Managed the vector table relocation (or not?)
In /Core/Src/system_stm32wbxx.c
...
#define USER_VECT_TAB_ADDRESS
#if defined(USER_VECT_TAB_ADDRESS)
/*!< Uncomment this line for user vector table remap in Sram else user remap
will be done in Flash. */
/* #define VECT_TAB_SRAM */
#if defined(VECT_TAB_SRAM)
#define VECT_TAB_BASE_ADDRESS SRAM1_BASE /*!< Vector Table base address field.
This value must be a multiple of 0x200. */
#define VECT_TAB_OFFSET 0x00000000U /*!< Vector Table base offset field.
This value must be a multiple of 0x200. */
#else
#define VECT_TAB_BASE_ADDRESS FLASH_BASE /*!< Vector Table base address field.
This value must be a multiple of 0x200. */
#define VECT_TAB_OFFSET 0x00007000U /*!< Vector Table base offset field.
This value must be a multiple of 0x200. */
#endif /* VECT_TAB_SRAM */
#endif /* USER_VECT_TAB_ADDRESS */- Modify linkerscript (STM32WB5xx_FLASH.ld file) to add the magic keyword section
...
.ota_region 0x08007140:
{
KEEP(*(TAG_OTA_START))
. = ALIGN(4);
} >FLASH
...
.ota_region_end :
{
. = ALIGN(4);
KEEP(*(TAG_OTA_END))
. = ALIGN(4);
} >FLASH
...- In app_ble.c
/**
* These are the two tags used to manage a power failure during OTA
* The MagicKeywordAdress shall be mapped @0x140 from start of the binary image
* The MagicKeywordvalue is checked in the ble_ota application
*/
PLACE_IN_SECTION("TAG_OTA_END") const uint32_t MagicKeywordValue = 0x94448A29 ;
PLACE_IN_SECTION("TAG_OTA_START") const uint32_t MagicKeywordAddress = (uint32_t)&MagicKeywordValue;- Ensure your MagicKeyword is correctly written (using STM32CubeProgrammer for exemple)
You may see the OTA procedure describe in this figure
AN5247 may be usefull for you.
BeST Regards,
Axel L.
