Dear Nordic Support Team,
I am currently working on a project involving Over-the-Air (OTA) firmware updates using the Memfault platform with a Nordic sample application. While I can download new firmware using the shell, I'm encountering difficulties with the installation process post-download.
Memfault representatives have advised enabling mcuboot and dfu support in the sample app, either by using a specific sample app or by updating the prj.conf in the Memfault+Nordic sample app. Additionally, Memfault's documentation was referenced for configuring and invoking an OTA update in the Nordic nRF Connect SDK.
However, my specific concern is with implementing this configuration on the nRF7002DK board, particularly over WiFi. The available documentation and guidance seem primarily focused on LTE and Bluetooth configurations. I am seeking clarification on whether the standard Memfault configurations for OTA (as applied to nRF9160) are applicable to nRF7002DK, and any specific considerations or challenges I should be aware of, especially regarding the use of internal vs. external flash memory for secondary image slots.
I would appreciate a complete walk-through of the configuration I need to make it work from your memfault sample.
Your expert advice on this matter would be greatly appreciated to ensure successful implementation and address any potential issues specific to the nRF7002DK board.
Thank you for your assistance.
Best regards,
Actif
Vincent Morin (Actif) Hello, folks; I have another question. One of my clients tasked my team to investigate OTA capabilities with memfault from the Nordic sample. I wonder if the sample provides OTA out of the box. I am able to download the new firmware with the shell, but I don't see any installation process triggered after. Any guidance that could help me answer my client's request faster would be welcome. Regards, Vincent 8 replies (Memfault) Hi @Vincent Morin (Actif) -- for OTA to work end to end, mcuboot + dfu support needs to be enabled in the sample app. One option would be to try this sample app which does enable Mcuboot. Alternatively, you could enable mcuboot in the memfault+Nordic sample app by updating the prj.conf. These should be the approximate flags you need. Vincent Morin (Actif) Thank you, name_hidden! I appreciate your support. I will definitely give it a try. (Memfault) Depending on the specific chip, there's a few more bits of information here: https://docs.memfault.com/docs/mcu/nordic-nrf-connect-sdk-guide/#configuring-and-invoking-an-ota-update docs.memfault.comdocs.memfault.com Nordic nRF Connect SDK Integration Guide | Memfault Docs Integrate Memfault using the Nordic Semiconductor's nRF Connect SDK. Vincent Morin (Actif) Thank you for providing the information. I am attempting to configure it, but I am facing some issues. Although I plan to investigate the issue further, could you clarify whether this configuration has been tested with a 7002DK over WiFi? I tried looking for a mention of the 7002DK in the documentation, and the steps appear to have been written for LTE and Bluetooth. Is the configuration could be different for the 7002DK? (Memfault) The nRF7002 will use the same Memfault configs as the nRF9160 for OTA. Note that as far as I know, Nordic doesn't have a functional OTA example for that board; the base image size is about 700kB, which prevents using a secondary image slot using internal (nRF53) flash, and requires placing the secondary slot in the external qspi nor flash chip, which is tricky. If you're getting stuck I definitely recommend posting to Nordic devzone, they're pretty responsive usually. Vincent Morin (Actif) Thank you for following up with me. I will reach out to Nordic for assistance regarding this matter. (Memfault) No problem! Let us know if you get it working, it's been on our to-do list to get OTA tested on that board