Hello,
We are working on NRF52832 + nRF Connect SDK 1.8.0 for our upcoming product. We need to do OTA of our Firmware.
Could you please help with pointing to the right direction (document/sample) for OTA of Firmware using BLE interface?
Thanks.
Hello,
We are working on NRF52832 + nRF Connect SDK 1.8.0 for our upcoming product. We need to do OTA of our Firmware.
Could you please help with pointing to the right direction (document/sample) for OTA of Firmware using BLE interface?
Thanks.
Check out the following: https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/ncs-dfu
Best regards,
Simon
Thanks, Simon. I am trying to use above guide with nRF52832. I've chip with 512KB of Flash and 64KB of SRAM.
I am using nRF Connect SDK 1.8.0.
When I enable DFU support on my application, using the same steps. I see there is a linking error in the build:
c:/ncs/v1.8.0/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: zephyr\zephyr_prebuilt.elf section `text' will not fit in region `FLASH' c:/ncs/v1.8.0/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: region `FLASH' overflowed by 36896 bytes
Memory region displayed in build is:
Memory region Used Size Region Size %age Used FLASH: 34448 B 48 KB 70.08% SRAM: 23744 B 64 KB 36.23% IDT_LIST: 0 GB 2 KB 0.00%
I don't understand why the Flash region size is showing as 48 KB here?
When I remove this DFU changes and build my application I see proper size in build:
Memory region Used Size Region Size %age Used FLASH: 252508 B 512 KB 48.16% SRAM: 32252 B 64 KB 49.21% IDT_LIST: 0 GB 2 KB 0.00%
Am I missing something here?
All I am trying to do here is running peripheral_lbs example with DFU on nRF52832. Do I need any changes in example plus above steps to do so?
Thanks.
Hi Simon,
Could you please check my response? What should be the max application size to support the DFU on nrf52832?
Is there a way we can utilize external flash (connected over SPI) for DFU?
Thanks!
Hello embeddedER. Sorry for the delay, I have been gone for the last two months. Have you figured this out?
Try to increase the size allocated for MCUboot (run ninja partition_manager_report to see the allocated mcuboot space), maybe the mcuboot image has overflowed this size. Try increasing CONFIG_PM_PARTITION_SIZE_MCUBOOT like done in step 12 in this guide: https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/device-firmware-update-dfu-with-mcuboot-bootloader
Best regards,
Simon
Hi Simon,
Thanks for getting back on this. We are yet to figure this out. We got off the course with few other stuff and we shall be resuming this soon.
We shall verify your suggestions very soon.
Thanks!