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

Nrfx 6832 enable lpuart tests on nrf54l20pdk #19804

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

nordic-segl
Copy link
Contributor

No description provided.

@github-actions github-actions bot added the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Jan 8, 2025
@nordic-piks
Copy link
Contributor

Please extend https://github.com/nrfconnect/sdk-nrf/blob/main/samples/peripheral/lpuart/README.rst - table with products and required loopbacks.

@NordicBuilder
Copy link
Contributor

NordicBuilder commented Jan 8, 2025

CI Information

To view the history of this post, clich the 'edited' button above
Build number: 4

Inputs:

Sources:

sdk-nrf: PR head: 067777195cd47af67f3a40eb20aa5b4cdeafed35

more details

sdk-nrf:

PR head: 067777195cd47af67f3a40eb20aa5b4cdeafed35
merge base: 658662845a8e4d4cb677800c8d36acfac9176c90
target head (main): 658662845a8e4d4cb677800c8d36acfac9176c90
Diff

Github labels

Enabled Name Description
ci-disabled Disable the ci execution
ci-all-test Run all of ci, no test spec filtering will be done
ci-force-downstream Force execution of downstream even if twister fails
ci-run-twister Force run twister
ci-run-zephyr-twister Force run zephyr twister
List of changed files detected by CI (7)
samples
│  ├── peripheral
│  │  ├── lpuart
│  │  │  ├── README.rst
│  │  │  ├── boards
│  │  │  │  ├── nrf54l20pdk_nrf54l20_cpuapp.conf
│  │  │  │  │ nrf54l20pdk_nrf54l20_cpuapp.overlay
│  │  │  │ sample.yaml
tests
│  ├── drivers
│  │  ├── lpuart
│  │  │  ├── boards
│  │  │  │  ├── nrf54l20pdk_nrf54l20_cpuapp.conf
│  │  │  │  │ nrf54l20pdk_nrf54l20_cpuapp.overlay
│  │  │  │ testcase.yaml

Outputs:

Toolchain

Version: b77d8c1312
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:b77d8c1312_912848a074

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

  • ◻️ Toolchain - Skipped: existing toolchain is used
  • ✅ Build twister
    • sdk-nrf test count: 85
  • ✅ Integration tests
    • ✅ test-low-level
Disabled integration tests
    • desktop52_verification
    • doc-internal
    • test_ble_nrf_config
    • test-fw-nrfconnect-apps
    • test-fw-nrfconnect-ble_mesh
    • test-fw-nrfconnect-ble_samples
    • test-fw-nrfconnect-boot
    • test-fw-nrfconnect-chip
    • test-fw-nrfconnect-fem
    • test-fw-nrfconnect-nfc
    • test-fw-nrfconnect-nrf-iot_libmodem-nrf
    • test-fw-nrfconnect-nrf-iot_lwm2m
    • test-fw-nrfconnect-nrf-iot_mosh
    • test-fw-nrfconnect-nrf-iot_nrf_provisioning
    • test-fw-nrfconnect-nrf-iot_positioning
    • test-fw-nrfconnect-nrf-iot_samples
    • test-fw-nrfconnect-nrf-iot_serial_lte_modem
    • test-fw-nrfconnect-nrf-iot_thingy91
    • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
    • test-fw-nrfconnect-nrf_crypto
    • test-fw-nrfconnect-ps
    • test-fw-nrfconnect-rpc
    • test-fw-nrfconnect-rs
    • test-fw-nrfconnect-tfm
    • test-fw-nrfconnect-thread
    • test-fw-nrfconnect-zigbee
    • test-sdk-audio
    • test-sdk-dfu
    • test-sdk-find-my
    • test-sdk-mcuboot
    • test-sdk-pmic-samples
    • test-sdk-sidewalk
    • test-sdk-wifi
    • test-secdom-samples-public

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

@nordic-segl nordic-segl force-pushed the NRFX-6832_Enable-uart-tests-on-nrf54l20pdk branch from 0053c0a to bc0e4b6 Compare January 8, 2025 13:55
@nordic-segl
Copy link
Contributor Author

Not sure if this PR has sense. It's to early to run current consumption tests on 54L20.
When I run Twister I got three tests passing and another three failing.
Pass:

  1. nrf54l20pdk/nrf54l20/cpuapp:sample.peripheral.lpuart.debug
  2. nrf54l20pdk/nrf54l20/cpuapp:sample.peripheral.lpuart_int_driven.debug
  3. nrf54l20pdk/nrf54l20/cpuapp:lpuart.loopback.nrf54l

Failure:

  1. nrf54l20pdk/nrf54l20/cpuapp:sample.peripheral.lpuart - Pytest error - return code 4
  2. nrf54l20pdk/nrf54l20/cpuapp:sample.peripheral.lpuart_int_driven - Pytest error - return code 4
  3. nrf54l20pdk/nrf54l20/cpuapp:lpuart.loopback.nrf54l.busy_sim - Assertion failed at ../../../../../ncs/nrf/tests/drivers/lpuart/src/main.c:242: test_lpuart_stress_test_stress: test_err is true

@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 Publish GitHub Action.

@nordic-segl nordic-segl force-pushed the NRFX-6832_Enable-uart-tests-on-nrf54l20pdk branch from bc0e4b6 to ef0b35a Compare January 9, 2025 09:51
Add overlyas needed to run the test on nrf54l20pdk.

Signed-off-by: Sebastian Głąb <[email protected]>
Add overlays needed to execute lpuart tests on nrf54l20pdk.

Signed-off-by: Sebastian Głąb <[email protected]>
@nordic-segl nordic-segl force-pushed the NRFX-6832_Enable-uart-tests-on-nrf54l20pdk branch from ef0b35a to 0677771 Compare January 13, 2025 08:00
@nordic-segl nordic-segl requested a review from a team as a code owner January 13, 2025 08:00
@github-actions github-actions bot added the doc-required PR must not be merged without tech writer approval. label Jan 13, 2025
@umapraseeda
Copy link
Contributor

Any changelog entry required?

@nordic-segl
Copy link
Contributor Author

Any changelog entry required?

I don't think so. This change is for internal testing. nRF54L20 is not available for sampling yet.

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. doc-required PR must not be merged without tech writer approval.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants