Skip to content
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

nRF54L15: TF-M regression Tests #15508

Closed
wants to merge 3 commits into from

Conversation

mswarowsky
Copy link
Contributor

@mswarowsky mswarowsky commented May 27, 2024

test_tfm: PR-161

@github-actions github-actions bot added manifest changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. labels May 27, 2024
@NordicBuilder
Copy link
Contributor

NordicBuilder commented May 27, 2024

The following west manifest projects have been modified in this Pull Request:

Name Old Revision New Revision Diff
trusted-firmware-m nrfconnect/[email protected] nrfconnect/sdk-trusted-firmware-m#153 nrfconnect/sdk-trusted-firmware-m#153/files

Note: This message is automatically posted and updated by the Manifest GitHub Action.

@NordicBuilder
Copy link
Contributor

NordicBuilder commented May 27, 2024

Test specification

CI/Jenkins/NRF

  • Integration Platforms

CI/Jenkins/integration

Test Module File based changes Manually selected West overwrite
test-fw-nrfconnect-boot X
test-fw-nrfconnect-nrf_crypto X
test-fw-nrfconnect-tfm X
test-sdk-find-my X
test-sdk-mcuboot X

test-fw-nrfconnect-tfm: added because there was no .github/test-spec.yml in 'trusted-firmware-m'

Detailed information of selected test modules

Note: This message is automatically posted and updated by the CI

integration_platforms:
- nrf5340dk/nrf5340/cpuapp/ns
- nrf9160dk/nrf9160/ns
- nrf54l15pdk/nrf54l15/cpuapp/ns
harness: console
harness_config:
type: multi_line
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's strange.

We didn't need to filter out

tfm.regression_ipc_lvl2.cc3xx:

?

How does this work?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because I haven't done yet the validation of what is run on CI and what not...

@NordicBuilder
Copy link
Contributor

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.

@mswarowsky mswarowsky force-pushed the tfm_regression branch 7 times, most recently from 223ac0f to 369828b Compare May 31, 2024 08:46
The old app.overlay doesn't work for nRF54L15 as the uart peripherals
got renamed, so moving it to the boards folder with having a separate
overlay file per board.

Ref: NCSDK-27431

Signed-off-by: Markus Swarowsky <[email protected]>
The timer peripheral got rename to TIMER00 from TIMER0 in the the 54L
platform so selecting that when building the regression tests

Ref: NCSDK-27431
Signed-off-by: Markus Swarowsky <[email protected]>
Get peripheral UARTE config to make the TF-M regression tests run
and enable them in thest config.

Ref: NCSDK-27431

Signed-off-by: Markus Swarowsky <[email protected]>
Copy link

This pull request 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 pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions bot added the Stale label Oct 13, 2024
@github-actions github-actions bot closed this Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. DNM manifest manifest-trusted-firmware-m Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants