Hi,
We are exploring using the Firmware Loader to do the OTA for our firmware. As per what I understand from the documentation, the Firmware Loader application will be booted up mcuboot on the following cases
1. GPIO assertion
2. Retention memory setting
3. SMP manager initiated boot cmd
We don't have any GPIO left in our final product that can be used for this purpose so we are left with using 2 or 3.
My question is it looks like the application must be up and running in order for it to setup mcuboot to load up the firmware loader on reboot. If my application for whatsoever reason crashes or fails to bootup ( due to a bug for ex which causes a sigsegv ) , there is no way for the firmware loader to get booted up and provide an option to do DFU .
Is this understanding correct ? If yes, are there any other suggestion design patterns to mitigate this issue of application unavailability for DFU ?
Our primary concern is a bad application DFU bricking the board . Our current plan is to use test mode with mcuboot swap-move algorithm, and then confirm once app is good. That way at least we have a window to test. But I was interested in firmware loader + single slot because it could save us a good amount of flash space.
Thanks
Ramakrishnan.
