New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serial recovery & encryption & swap fails to build #1377
Comments
Encyption in serial recovery mode is limited to single slot mode. Ref. #1255 |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
@nvlsianpu @d3zd3z @de-nordic Are there any plans to support serial recovery of encrypted images using dual slot mode any time soon ? |
@jimmyzumthurm You can log an issue/enhancement for that. It may get picked up if somebody finds time to do it. You can also propose your own implementation if you are up to the task. |
There are any news about serial recovery of encrypted images using dual slot mode ? |
We encountered this issue on Nordic's fork (https://github.com/nrfconnect/sdk-mcuboot) but I believe upstream is affected as well.
We are using the following Kconfig settings:
I.e. swap between primary and secondary slot, encryption and serial recovery enabled.
The problem is that
boot_serial.c::bs_upload()
wants to callsingle_loader.c::boot_handle_enc_fw()
, but the latter module is only built whenCONFIG_SINGLE_APPLICATION_SLOT=y
.The text was updated successfully, but these errors were encountered: