-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
suit: recovery application build separately #15422
Conversation
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
b3eaa74
to
bbb8e68
Compare
cmake/sysbuild/suit.cmake
Outdated
list(APPEND CORE_ARGS | ||
--core ${target},${SUIT_ROOT_DIRECTORY}${target}.bin,${BINARY_DIR}/zephyr/edt.pickle,${BINARY_DIR}/zephyr/.config | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have one concern here. in flash_companion
I didn't set any value for CONFIG_SUIT_ENVELOPE_TARGET
, which means that it has application
by default. In that case both smp_transfer
and flash_companion
would have the same target name, which is a recipe for problems.
I am wondering how CONFIG_SUIT_ENVELOPE_TARGET
should be approached. On one hand, I think that using sysbuild
image name by default is convenient and would be easier to understand for the user.
On the second hand, we want the default manifest templates to be generic regardless of the application name.
Perhaps in the flash_companion
the CONFIG_SUIT_ENVELOPE_TARGET
should be set to "" (empty)
and in this loop there should be a check if there are multiple images with the same CONFIG_SUIT_ENVELOPE_TARGET
and a warning should be displayed in such case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps config SUIT_ENVELOPE_TARGET
should depend on SUIT_ENVELOPE
? In this case I think the CONFIG_SUIT_ENVELOPE_TARGET
symbol would be undefined for the flash_companion image, which we could detect. I don't think we should directly set CONFIG_SUIT_ENVELOPE_TARGET
in this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be a good approach.
samples/suit/smp_transfer/root_with_binary_nordic_top.yaml.jinja2
Outdated
Show resolved
Hide resolved
samples/suit/recovery/sysbuild.conf
Outdated
@@ -0,0 +1,13 @@ | |||
# # | |||
# # Copyright (c) 2024 Nordic Semiconductor ASA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Double comments?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
6a11c9c
to
f02ad8e
Compare
@@ -176,12 +176,20 @@ function(suit_create_package) | |||
foreach(image ${IMAGES}) | |||
sysbuild_get(BINARY_DIR IMAGE ${image} VAR APPLICATION_BINARY_DIR CACHE) | |||
sysbuild_get(BINARY_FILE IMAGE ${image} VAR CONFIG_KERNEL_BIN_NAME KCONFIG) | |||
sysbuild_get(target IMAGE ${image} VAR CONFIG_SUIT_ENVELOPE_TARGET KCONFIG) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is necessary to add unset(target)
, otherwise the parameters to suit-generator are wrong.
85fe451
to
baf532e
Compare
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
The recovery application can be built as a standalone application and flashed with nrfutil. Signed-off-by: Artur Hadasz <[email protected]>
This commit updates the suit-generator revision to bring in the newest changes needed for recovery application. Signed-off-by: Artur Hadasz <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some initial comments:
- If it is an Application, it needs to be moved to Application folder.
- It need to follow the Application/Sample templates that can be found https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/dev_model_and_contributions/documentation/templates.html.
- Since it is a new doc, it needs to be added in the Changelog.
The situation is currently not clear. It would better fit the core_fw category and the current recommendation is to put such applications in the sample directory. See NCSDK-10551 |
The documentation will be extended and Changelog will be added in a separate PR. When it comes to the "application" part - this will be finally placed in a completely different category - named something like "core firmware" together with some other applications. It is just temporarily kept in a sample - this was consulted with @wbober. |
Ok. Approving, assuming all the doc changes will be taken care of in another PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving. All the required doc changes will be done in another PR.
@@ -0,0 +1,50 @@ | |||
:orphan: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is orphaned, but still appearing in the docs because of the inclusion at the higher level:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/suit.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is/will be addressed in a different PR that is currently open, but thanks for catching!
This PR adds the SUIT BLE recovery application.
The application is build separately and than flashed after the main application is flashed.
test-sdk-nrf: sdk-nrf-pr-15422