CC2340R5: MCUBoot verification has delay to start application

Hello Vignesh,

I hope you are well. In order to reduce the time, you could try to disable debugging mode.

There are a few other threads recently related to your issue.

CC2340R5: MCUBoot speed optimization - Bluetooth forum - Bluetooth®︎ - TI E2E support forums

CC2340R5: The CC2340 OAD project takes approximately 10 seconds for the first reset to run after flashing - Bluetooth forum - Bluetooth®︎ - TI E2E support forums

If you need some more information there is some good documentation in our SDK, links provided below:

MCUBoot for On-Chip OAD (Stack Library)

MCUBoot Over-the-Air Download (OAD)

Thanks,
Alex F

Hi ,
                 I was trying  to disable debugging mode so I have tried to import the new MCUBoot project found in {SDK_INSTALL_DIR}\examples\nortos\LP_EM_CC2340R5\mcuboot. But while importing an project am getting the this error.

so I have imported mcuboot_LP_EM_CC2340R5_nortos_ticlang project and compiled. I have loaded compiled MCUBoot bin file, example persistent app bin file from SDK and Application code. Now persistent app only starting. When i have checked the memory address In flash_map_backend/flash_map_backend.h has an some example address.

so I have tried to change configuration to default address as

#elif defined DeviceFamily_CC23X0R5
 #define BOOTLOADER_BASE_ADDRESS 0x00000000
 #define BOOT_BOOTLOADER_SIZE 0x00006000

 #define BOOT_PRIMARY_1_BASE_ADDRESS 0x00006000
 #define BOOT_PRIMARY_1_SIZE 0x0002c000

 #define BOOT_SECONDARY_1_BASE_ADDRESS 0x00032000
 #define BOOT_SECONDARY_1_SIZE 0x0004a000

even persistent app only starting. But with example MCUBoot hex file  after 10 seconds application working  fine.

Need to know how to disable the debugging mode.

Thank you.

Hello Vignesh,

One way to disable GPIO debug is to physically remove the pin covers/connectors on the SW0, TDI, TD0, TCK, and TMS.

Here is another post which discusses the effect of disabling debugging mode on MCUBoot CC2340R5: CC2340R5 - OAD bootloader check - Bluetooth forum - Bluetooth®︎ - TI E2E support forums. 

Your configuration looks very similar to the one provided in the readme of mcuboot_lp_em_cc2340r5... with some slight differences in addresses, did you try running with the same exact configuration as in the readme? 

Have you tried another GCC project in the past? You may need to download the compiler tool for GCC support. To download GCC support in code composer studio click Help -> Install GCC Arm Compiler tools -> select and install GCC tools (like 9.2.1.2019-q4-major). 

Thanks,
Alex F 

Hi Alex,

      By disabling the GPIO debug I could reduce that MCUBoot checking period from 10 secs to 2secs to start the application. But my application needs less than 500ms. 

CC2340R5: MCUBoot speed optimization - Bluetooth forum - Bluetooth®︎ - TI E2E support forums

I have tried in MCUBoot ticlang  still getting 2 sec to start the application. Is there a further way to optimize the MCUBoot code to speed up the process?

Thank you.

Hello Vignesh, 

It is good to hear that the GPIO debug reduced the timing from 10 seconds to 2 seconds. Since the CC2340R5 device does not have ECC hardware accelerator, and that MCUBoot needs to do a full image verification each boot, the time you measured is somewhat expected. To further optimize the time, we could disable the image checks at boot time (which will introduce risks into the system), otherwise 2 seconds might be the best time. 

Thanks, 
Alex F