-
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
manifest: support sdsc binary bundle 0.6.8 (SDFW 8.0.1 SCFW 3.0.0) #18078
Conversation
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. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:more detailsGithub labels
List of changed files detected by CI (0)
Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
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. |
1914c84
to
116e2ef
Compare
d51d8c5
to
e6fab58
Compare
d178252
to
f3940c4
Compare
9c0e5a6
to
947f20b
Compare
0d346f4
to
43fa95c
Compare
1ee8087
to
c3b295f
Compare
why is it approved if twister tests are not passing? |
We had two failures that were going to be quarantined. The failing tests will be addressed, so I guess the approvals is assuming that tests are good. |
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.
lgtm.
small nit on line length.
I feel some other lines might also be >100, so would be nice if you check those in addition.
samples/peripheral/802154_phy_test/modules/app_rpc/zephyr/Kconfig
Outdated
Show resolved
Hide resolved
c3b295f
to
192bed3
Compare
Failing twister tests for 192bed3 related to TF-M are known to be red on main, so twister tests are all good. |
77b3771
to
ff713e4
Compare
This reverts commit f65009c. Signed-off-by: Håkon Amunsden <[email protected]>
Ref: NCSDK-NONE Signed-off-by: Håkon Amundsen <[email protected]>
Certain Kconfigs were only enabled for or in relation to nRF54H20 EngC, which is the default chip revision. Ensure that the same settings are available on EngB. Signed-off-by: Grzegorz Swiderski <[email protected]>
ff713e4
to
b4d5e96
Compare
Memory footprint analysis revealed the following potential issuessample.matter.template.release[nrf7002dk/nrf5340/cpuapp]: High ROM usage: 812426[B] - link (cc: @kkasperczyk-no @ArekBalysNordic @markaj-nordic) Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-18078/35) |
@hakonfam Please update SHA and fix the compliance issue (commit author). This PR will need to be backported manually to the release branch |
Pull in updates to several repositories to support the SDSC bundle for NCS 2.8.0 and fix build issues with [email protected]. Signed-off-by: Håkon Amundsen <[email protected]> Signed-off-by: Jonathan Nilsen <[email protected]>
This is needed for new UICR layout. Signed-off-by: Håkon Amundsen <[email protected]>
Don't configure access to cpuapp/cpurad shared memory from the cpuapp side, as the shared access is configured by the cpurad side. Signed-off-by: Jonathan Nilsen <[email protected]>
b4d5e96
to
90a437b
Compare
Ref: NCSDK-NONE
test-sdk-nrf: sdk-nrf-pr-18078