cancel
Showing results for 
Search instead for 
Did you mean: 

STM32WB FUOTA issue with custom Application FW

Hello Geeks...

Hope all are doing well

Recently, I'm working on STM32WB FUOTA

I know the FUOTA terminology of the STM32WB through the application document AN5247

Moreover, I have gone through the YouTube Tutorial series of the FUOTA for WB series

I'm trying to update my application over FUOTA but, some how it's verification always fails and it's rollover to BLE OTA loader app!

here are the steps which I'm following

  1. Updated the linker script as per the "BLE_HeartRate_ota" example
  2. commented SCB->VTOR from system_stm32wbxx.c file
  3. BLE_CFG_OTA_REBOOT_CHAR set to 1 in ble_conf.h
  4. Added the OTA reboot characteristic (which is working well, and MCU able to reboot during the OTA request)
  5. Flashed "BLE_Ota" Firmware starting from 0x08000000 flash memory location
  6. Flashed the main application Firmware with OTA enable char. starting from 0x08007000 flash memory location
  7. Verified the MagicKeywordAddress address 0x08007140

Problem statements & Test procedure

1. Application firmware seems working well and I can pair the BLE device with STBLE app

2. I can send the OTA reboot request from the STBLE app, and MCU also reboot from the application code

3. However the main issue is, "STM_OTA" ble unable to advertise!

4. After power reboot, it's advertising as a "STM_OTA"

5.when I'm trying to send the application bin from 0x7000 then it's downloading from the app seamless

6.However the main issue is, it's always rollback to OTA loader and advertise as "STM_OTA"!!

For the reference, here I have attached the linker script, Memory region & memory details screenshot

I'm using the Wireless FW version: 1.13.2 and FUS version: 1.2.0

/**
*****************************************************************************
**
**  File        : stm32wb55xx_flash_cm4.ld
**
**  Abstract    : STM32CubeIDE Minimal System calls file
**
** 		          For more information about which c-functions
**                need which of these lowlevel functions
**                please consult the Newlib libc-manual
**
**  Environment : STM32CubeIDE for MCU
**
**  Distribution: The file is distributed as is, without any warranty
**                of any kind.
**
*****************************************************************************
**
** <h2><center>&copy; COPYRIGHT(c) 2019 STMicroelectronics</center></h2>
**
** Redistribution and use in source and binary forms, with or without modification,
** are permitted provided that the following conditions are met:
**   1. Redistributions of source code must retain the above copyright notice,
**      this list of conditions and the following disclaimer.
**   2. Redistributions in binary form must reproduce the above copyright notice,
**      this list of conditions and the following disclaimer in the documentation
**      and/or other materials provided with the distribution.
**   3. Neither the name of STMicroelectronics nor the names of its contributors
**      may be used to endorse or promote products derived from this software
**      without specific prior written permission.
**
** THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
** AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
** IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
** DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
** FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
** DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
** SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
** CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
** OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
** OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
**
*****************************************************************************
*/
 
/* Entry Point */
ENTRY(Reset_Handler)
 
/* Highest address of the user mode stack */
_estack = 0x20030000;           /* end of RAM */
/* Generate a link error if heap and stack don't fit into RAM */
_Min_Heap_Size  = 0x7500 ;      /* required amount of heap  */
_Min_Stack_Size = 0x9500 ;      /* required amount of stack */
 
/* Specify the memory areas */
MEMORY
{
FLASH (rx)                 : ORIGIN = 0x08007000, LENGTH = 484k
RAM1 (xrw)                 : ORIGIN = 0x20000004, LENGTH = 191k
RAM_SHARED (xrw)           : ORIGIN = 0x20030000, LENGTH = 10K
}
 
/* Define output sections */
SECTIONS
{
  /* The startup code goes first into FLASH */
  .isr_vector :
  {
    . = ALIGN(4);
    KEEP(*(.isr_vector)) /* Startup code */
    . = ALIGN(4);
  } >FLASH
 
 .ota_region 0x08007140:
  {
	KEEP(*(TAG_OTA_START))
	. = ALIGN(4);
  } >FLASH
  /* The program code and other data goes into FLASH */
  .text :
  {
    . = ALIGN(4);
    *(.text)           /* .text sections (code) */
    *(.text*)          /* .text* sections (code) */
    *(.glue_7)         /* glue arm to thumb code */
    *(.glue_7t)        /* glue thumb to arm code */
    *(.eh_frame)
 
    KEEP (*(.init))
    KEEP (*(.fini))
 
    . = ALIGN(4);
    _etext = .;        /* define a global symbols at end of code */
  } >FLASH
 
  /* Constant data goes into FLASH */
  .rodata :
  {
    . = ALIGN(4);
    *(.rodata)         /* .rodata sections (constants, strings, etc.) */
    *(.rodata*)        /* .rodata* sections (constants, strings, etc.) */
    . = ALIGN(4);
  } >FLASH
 
  .ARM.extab   : { *(.ARM.extab* .gnu.linkonce.armextab.*) } >FLASH
  .ARM : {
    __exidx_start = .;
    *(.ARM.exidx*)
    __exidx_end = .;
  } >FLASH
 
  .preinit_array     :
  {
    PROVIDE_HIDDEN (__preinit_array_start = .);
    KEEP (*(.preinit_array*))
    PROVIDE_HIDDEN (__preinit_array_end = .);
  } >FLASH
  .init_array :
  {
    PROVIDE_HIDDEN (__init_array_start = .);
    KEEP (*(SORT(.init_array.*)))
    KEEP (*(.init_array*))
    PROVIDE_HIDDEN (__init_array_end = .);
  } >FLASH
  .fini_array :
  {
    PROVIDE_HIDDEN (__fini_array_start = .);
    KEEP (*(SORT(.fini_array.*)))
    KEEP (*(.fini_array*))
    PROVIDE_HIDDEN (__fini_array_end = .);
  } >FLASH
 
 .ota_region_end :
  {
	. = ALIGN(4);
	KEEP(*(TAG_OTA_END))
	. = ALIGN(4);
  } >FLASH
  /* used by the startup to initialize data */
  _sidata = LOADADDR(.data);
 
  /* Initialized data sections goes into RAM, load LMA copy after code */
  .data : 
  {
    . = ALIGN(4);
    _sdata = .;        /* create a global symbol at data start */
    *(.data)           /* .data sections */
    *(.data*)          /* .data* sections */
 
    . = ALIGN(4);
    _edata = .;        /* define a global symbol at data end */
  } >RAM1 AT> FLASH
 
  
  /* Uninitialized data section */
  . = ALIGN(4);
  .bss :
  {
    /* This is used by the startup in order to initialize the .bss secion */
    _sbss = .;         /* define a global symbol at bss start */
    __bss_start__ = _sbss;
    *(.bss)
    *(.bss*)
    *(COMMON)
 
    . = ALIGN(4);
    _ebss = .;         /* define a global symbol at bss end */
    __bss_end__ = _ebss;
  } >RAM1
 
  /* User_heap_stack section, used to check that there is enough RAM left */
  ._user_heap_stack :
  {
    . = ALIGN(8);
    PROVIDE ( end = . );
    PROVIDE ( _end = . );
    . = . + _Min_Heap_Size;
    . = . + _Min_Stack_Size;
    . = ALIGN(8);
  } >RAM1
 
  
 
  /* Remove information from the standard libraries */
  /DISCARD/ :
  {
    libc.a ( * )
    libm.a ( * )
    libgcc.a ( * )
  }
 
  .ARM.attributes 0       : { *(.ARM.attributes) }
   MAPPING_TABLE (NOLOAD) : { *(MAPPING_TABLE) } >RAM_SHARED
   MB_MEM1 (NOLOAD)       : { *(MB_MEM1) } >RAM_SHARED
   MB_MEM2 (NOLOAD)       : { _sMB_MEM2 = . ; *(MB_MEM2) ; _eMB_MEM2 = . ; } >RAM_SHARED
   TAG_OTA_END(NOLOAD)    : { KEEP (*(TAG_OTA_END)) } >FLASH
}
 
 
 

0693W00000LzLkBQAV.png0693W00000LzLjwQAF.pngCan anyone help me here?

All comments and suggestions welcome

Thanks

Mahendra

19 REPLIES 19

Hi... @Greg_​ 

As I told the earlier, I have custom firmware which is just adopted from the P2P server app

I haven't modified anything with the BLE loader app

Here is the file that i have attached here

Thanks

you may find the file from here

I guess, app_ble.c also helps

here it is

Greg_
Associate II

I can not open or download the file. Was it BLE_p2pServer or BLE_p2pServer_ota example?

Greg_
Associate II

The file is unavailable. Please chceck if your basis was BLE_p2pServer or BLE_p2pServer_ota and check if in the file p2p_server_app.c you have anything related to OTA.

here it is @Greg_​ 

it's a custom one

Remy ISSALYS
ST Employee

Hello,

I looked your screenshot and I observed that the value 0x4c05b510 is the value at 0x08007150. I didn't understand why BLE_Ota is reading at this address instead of 0x08007140. You have to investigate this point.

Best Regards

Jtron.11
Senior

@Remy ISSALYS​ I am facing the issue that my custom application couldn't come back to OTA loader application. I sent 0x01 0x07 0x02 to the BM characteristic as the instruction hoping to start OTA loader app, and erase 2 sectors starting from 0x08007000.

But my application just reset and come back to my custom application right away.

Can you please help to give me some pointer why my OTA loader (exactly the code from BLE_OTA code) couldn't start, or if it is start but couldn't erase the custom's app?

Thank you so much for your helps

AKhan.18
Associate

The issue is that the "STM_OTA" BLE advertisement is not working, and the device always rolls back to the OTA loader app and advertises as "STM_OTA" after power reboot. The application firmware seems to be working well, and the OTA reboot request can be sent from the STBLE app, causing the MCU to reboot from the application code. However, when attempting to send the application binary from 0x7000, it always rolls back to the OTA loader and advertises as "STM_OTA."

Without additional information, it is difficult to determine the exact cause of the issue. However, some possible solutions could be to check if the BLE stack is correctly initialized, check if the BLE advertisement parameters are correctly set, and check if there are any errors in the code related to FUOTA. The user could also try to debug the code using a debugger or logging messages to identify the root cause of the issue. SWA

Jtron.11
Senior

Thank you AKhan,

My problem is from Custom App can't get back to STM_OTA.

Found the issue when I copied and pasted my source code I didn't assign the Handler correctly so the command is sent in still route to notification Handler. Problem solved thank you.

&(CustomContext.RebootReqCharHdle));