The process of ble ota is a bit long

[666]

HI ALL,

      I am using v2.8.0, NRF54L15,and peripheral_uart demo has not made any modifications except for adding the following content. The test shows that the OTA upgrade (from start to device restart) takes about 80 seconds. Through Wirshark packet capture, it was found that the air transmission only takes about 6 seconds. Is this around 80 seconds normal?

[Vidar Berg]

Hi,

It seems like MCUBoot builds do not enable the RRAM write buffer by default. As a result, the routine that copies the updated image from the secondary slot to the primary slot becomes very slow.

Please try to add this line to your mcuboot configuration:  

# Increase log level in bootloader
CONFIG_LOG_DEFAULT_LEVEL=4
CONFIG_MCUBOOT_LOG_LEVEL_DBG=y
# Enable write buffer for faster writes to RRAM
CONFIG_NRF_RRAM_WRITE_BUFFER_SIZE=32

<PROJ_DIR>/sysbuild
└── mcuboot.conf

Best regards,

Vidar

[666]

1.It seems to have no effect. I created a 'mcuboot.conf' file based on my previous work and included the following content.

However, the device runs very slowly and takes over 70 seconds to operate.

Then I changed "CONFIG_MAIN_STACK_SIZE=1152" to "CONFIG_MAIN_STACK_SIZE=4096" and it will run normally, but the effect was the same as before and had no effect

2.How long is normal for ble ota in NRF54L15?

Looking forwad to your reply!

[Vidar Berg]

Please check if the CONFIG_NRF_RRAM_WRITE_BUFFER_SIZE symbol got set to '32' in your build by checking the configuration file generated for the mcuboot build:

Note that you must perform a pristine build after adding new Kconfig or DT overlays for it to be applied to the build. 

666 said:

2.How long is normal for ble ota in NRF54L15?

I tested this change, and the copy process was reduced from around 80 seconds as in your case, to just 6 seconds.

[666]

I first created file mcuboot.conf, then clicked  pristine build,I didn't add new Kconfig or DT overlays .I don't know why it didn't set up successfully. Do you have any suggestions

[Vidar Berg]

The mcuboot.conf file (Kconfig fragment) must be placed in a folder named 'sysbuild' for it to be detected by the build system. 

Edit: Here is the project I used for test:

7776.peripheral_lbs_dfu.zip

[666]

I succeeded, thank you very much