manifest: sdk-zephyr: [nrf noup] soc:nordic:nrf54l Fix for arch_busy_wait on 54l with tfm

[NordicBuilder]

Automatically created by action-manifest-pr GH action from PR: nrfconnect/sdk-zephyr#2256

[NordicBuilder]

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

Name	Old Revision	New Revision	Diff
zephyr	nrfconnect/sdk-zephyr@a70d6bd	nrfconnect/sdk-zephyr#2256	nrfconnect/sdk-zephyr#2256/files

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

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 18

Inputs:

Sources:

sdk-nrf: PR head: 1ed9c911e643c2cd8bef1b870970692a5a0a3267
zephyr: PR head: 4f712e70891e3c5903b612cbfd9d0da7477aa519

more details

sdk-nrf:

PR head: 1ed9c911e643c2cd8bef1b870970692a5a0a3267
merge base: 71f6d485f2c1c392e627119c10eee28730e4a576
target head (main): 811c806f2715c0c2707618184a821c73f045536d
Diff

zephyr:

PR head: 4f712e70891e3c5903b612cbfd9d0da7477aa519
merge base: a70d6bd9660a3450f264d1d7017828196a964b3f
target head (main): dab9c11bdcc80f1e0670ef686e6066ee3304ac47
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 (15)

west.yml
zephyr
│  ├── .github
│  │  │ test-spec.yml
│  ├── arch
│  │  ├── arm
│  │  │  ├── core
│  │  │  │  ├── cortex_m
│  │  │  │  │  │ pm_s2ram.S
│  ├── drivers
│  │  ├── dp
│  │  │  │ swdp_bitbang.c
│  │  ├── pwm
│  │  │  │ pwm_nrfx.c
│  │  ├── spi
│  │  │  ├── spi_dw.c
│  │  │  │ spi_nrfx_spim.c
│  ├── modules
│  │  │ Kconfig.mcuboot
│  ├── samples
│  │  ├── subsys
│  │  │  ├── mgmt
│  │  │  │  ├── mcumgr
│  │  │  │  │  ├── smp_svr
│  │  │  │  │  │  │ prj.conf
│  ├── soc
│  │  ├── nordic
│  │  │  ├── nrf54h
│  │  │  │  ├── pm_s2ram.c
│  │  │  │  │ power.c
│  │  │  ├── nrf54l
│  │  │  │  │ soc.c
│  ├── subsys
│  │  ├── mgmt
│  │  │  ├── mcumgr
│  │  │  │  ├── grp
│  │  │  │  │  ├── img_mgmt
│  │  │  │  │  │  ├── include
│  │  │  │  │  │  │  ├── mgmt
│  │  │  │  │  │  │  │  ├── mcumgr
│  │  │  │  │  │  │  │  │  ├── grp
│  │  │  │  │  │  │  │  │  │  ├── img_mgmt
│  │  │  │  │  │  │  │  │  │  │  │ img_mgmt_priv.h
│  │  │  │  │  │  ├── src
│  │  │  │  │  │  │  ├── img_mgmt.c
│  │  │  │  │  │  │  │ img_mgmt_state.c

Outputs:

Toolchain

Version: b81a7cd864
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:b81a7cd864_912848a074

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

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
  • sdk-nrf test count: 1274
  • sdk-zephyr test count: 8940
• ✅ Integration tests
  • ✅ test-sdk-audio
  • ✅ test-fw-nrfconnect-boot
  • ✅ test-fw-nrfconnect-chip
  • ✅ test-fw-nrfconnect-nfc
  • ✅ test-fw-nrfconnect-nrf-iot_cloud
  • ✅ test-fw-nrfconnect-rs
  • ✅ test-fw-nrfconnect-fem
  • ✅ test-fw-nrfconnect-thread
  • ✅ test-fw-nrfconnect-zigbee
  • ✅ test-sdk-find-my
  • ✅ test-sdk-sidewalk
  • ✅ test-low-level
  • ✅ test-sdk-mcuboot
  • ✅ test-sdk-dfu

Disabled integration tests

• • desktop52_verification
  • doc-internal
  • test_ble_nrf_config
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • 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-tfm
  • test-sdk-pmic-samples
  • test-sdk-wifi

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

[NordicBuilder]

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.