-
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: nRF9280 SUIT support #18496
base: main
Are you sure you want to change the base?
suit: nRF9280 SUIT support #18496
Conversation
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: f3dd4ad3912c1a7d93e49f49f567774d2bed41ff more detailssdk-nrf:
suit-generator:
Github labels
List of changed files detected by CI (35)
Outputs:ToolchainVersion: b77d8c1312 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
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.
2 comments are optional, rest are required
@@ -20,6 +20,11 @@ config SUIT_MCI_IMPL_NRF54H20_SDFW | |||
bool "nRF54H20: Secure domain" | |||
depends on SUIT_PLATFORM_VARIANT_SDFW |
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.
needs nrf54h20 guard
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'd not agree here. We have cases, where we use the 54 implementation on POSIX to run tests.
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.
depends on <nrf54h20> || <posix>
?
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.
And actually tests should not need this because they should force config e.g. https://github.com/nrfconnect/sdk-nrf/blob/main/tests/lib/modem_info/CMakeLists.txt there is a similar thing for network tests
# WARNING: | ||
# All addresses and sizes in this file must be sunchronized with the SUIT storage address | ||
# defined in the Device Tree. | ||
# Any modification of those values require alignment in the SDFW. | ||
# Contents of the MPI (vendor name, class name, policies) may be modified by the | ||
# product vendor. |
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.
get the values from devicetree then? Why are there kconfigs duplicating what already exists
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.
The storage address is read from devicetree, so you may cross-out the addresses
from the warning message (it used to be hard-coded here).
There is a minor duplication, but this is solely due to the fact that SDFW-specific device-tree files are not accessible from NCS applications (you cannot even build for cpusec).
The current state is:
- the SUIT storage address is encoded as reserved area in sdk-nrf
- the reserved area is compared with SDFW definitions though static asserts
- the storage partitioning/layout is documented and only at the domain-level visible in SDFW dts files (so other SDFW components can implement per-domain firewalls).
- all offsets visible in this file are necessary to generate the output artifacts. They are also hard-coded in other places (storage implementation, suit generator), but since changing those break the compatibility, they should be constant for a given board for a lifetime (see engb/engc migration to realize how hard that is). There is no point to make it configurable at user level. There is also no point to make all offset values depending on the Kconfigs, because: SDFW does not even generate MPI, suit-generator may be used in other contexts than sdk-nrf app build.
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 following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
ce5733a
to
5625d67
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 Publish GitHub Action. |
Memory footprint analysis revealed the following potential issuessample.matter.template.debug[nrf52840dk/nrf52840]: ROM size increased by 6824[B] in comparison to the main[a07b87c] branch. - link (cc: @kkasperczyk-no @ArekBalysNordic @markaj-nordic) Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-18496/12) |
0e91c41
to
fc9875d
Compare
Add SUIT support for nRF9280 EngB product. Signed-off-by: Tuomas Parttimaa <[email protected]>
57e182a
to
13bb933
Compare
Remove debug logging lines. Signed-off-by: Tuomas Parttimaa <[email protected]>
Fix sizeof calculation for cellular FW manifest. Signed-off-by: Tuomas Parttimaa <[email protected]>
Update suit-generator version in order to add support for nRF9280 EngB HSoC1 device. Signed-off-by: Tuomas Parttimaa <[email protected]>
SUIT support for nRF9280