As is sometimes the case, I have been asked to provide an unsecured MCUBoot build and a Secure MCUBoot build.
By unsecured, I mean using the default key whereas the secured version used their generated key. Mine is not to reason why so I won’t get into that 🙂
I have no issues with accomplishing what they’ve asked for, however, I know there will be questions like, “How do I know it worked?”.
In my testing, I assumed that MCUBoot wouldn’t even try to load it. That assumption appears to be incorrect and it actually does the process and falls back to the original secured image upon reboot. I can tell because the two builds are using different BLE names. So the unsecured build is definitely not loaded.
This method of testing was only for my own peace of mind and their builds will not do that so how can I assure them this is the case? Any ideas, since NRF Connect for iOS does not seem to care about the keys?
Any ideas much appreciated.