manifest: Add mcuboot #120
Conversation
Add mcuboot fork to manifest. Signed-off-by: Aksel Skauge Mellbye <[email protected]>
Sysbuild defaults to RSA signing. Use ECDSA on Series 2 to be compatible with root of trust. Signed-off-by: Aksel Skauge Mellbye <[email protected]>
While MCUboot uses imgtool for signing applications, the bootloader binary itself must be signed by Simplicity Commander to be securely booted by the SE on Series 2 devices. Integrate a custom signing script to sign the bootloader image. This ensures that `west build`/`west flash` work out of the box on devices that enforce secure boot. The script assumes that `commander` is available on the path. Signed-off-by: Aksel Skauge Mellbye <[email protected]>
Build `with_mcuboot` sample app for representative devices. Signed-off-by: Aksel Skauge Mellbye <[email protected]>
Use find_program() to locate Simplicity Commander, either from SLT or a system install location. Signed-off-by: Aksel Skauge Mellbye <[email protected]>
asmellby
force-pushed
the
feature/mcuboot
branch
from
77a3956 to
12100b9
Compare
Add Simplicity Commander to SLT package file. Signed-off-by: Aksel Skauge Mellbye <[email protected]>
asmellby
force-pushed
the
feature/mcuboot
branch
from
12100b9 to
01d5950
Compare
| - name: Install packages | ||
| shell: bash | ||
| run: | | ||
| slt install -f ${{ inputs.package-file }} --no-lock |
There was a problem hiding this comment.
What is the benefit of downloading slt rather than directly downloading commander?
There was a problem hiding this comment.
slt enables version management of the installed tools, and has other tools available. If the user uses the Network Analyzer or Energy Profiler tools installed via slt, it would be inconvenient if the SDK uses a different way of getting Commander.
|
|
|
I'm not sure if
When it comes to supporting Commander both standalone and discovered through SLT, IMO the answer is "yes". The SLT variant is the most integrated, but being able to directly point at a specific binary to use makes sense to me as an option for situations where SLT isn't available or there is a strong desire to not use it. |
3 participants
Add mcuboot fork to manifest.
Sysbuild defaults to RSA signing. Use ECDSA on Series 2 to be compatible with root of trust.
While MCUboot uses imgtool for signing applications, the bootloader binary itself must be signed by Simplicity Commander to be securely booted by the SE on Series 2 devices. Integrate a custom signing script to sign the bootloader image.
This ensures that
west build/west flashwork out of the box on devices that enforce secure boot.