manifest: Bring Zephyr with disabled Cracen RAMs

[Vge0rge]

Updated soc file in Zephyr to disable Cracen RAMs
on system off.

[NordicBuilder]

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

Name	Old Revision	New Revision	Diff
zephyr	nrfconnect/sdk-zephyr@b063a96	nrfconnect/sdk-zephyr#1983	nrfconnect/sdk-zephyr#1983/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: 19

Inputs:

Sources:

sdk-nrf: PR head: c11b05fdbe2342f8d89ad4d5df3843915bac7822
zephyr: PR head: 8b49f242ff4cc89589787f813e4f59ae437f3a32

more details

sdk-nrf:

PR head: c11b05fdbe2342f8d89ad4d5df3843915bac7822
merge base: 4aab4b21b8bba9773eba6ba1521f75497a84dd8a
target head (main): c673d2b5c544d59260a08a8b4531017c11dcd0a2
Diff

zephyr:

PR head: 8b49f242ff4cc89589787f813e4f59ae437f3a32
merge base: b063a96d60f4b881114fb99157c7b394daaa4448
target head (main): dded8c29fbd2e3930e865bb6986d472ccf266e3c
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 (12)

west.yml
zephyr
│  ├── boards
│  │  ├── nordic
│  │  │  ├── nrf54h20dk
│  │  │  │  ├── nrf54h20dk_nrf54h20_cpuapp.dts
│  │  │  │  ├── nrf54h20dk_nrf54h20_cpuppr.dts
│  │  │  │  │ nrf54h20dk_nrf54h20_cpurad.dts
│  │  │  ├── nrf54l15dk
│  │  │  │  ├── nrf54l15_cpuapp_common.dtsi
│  │  │  │  │ nrf54l15dk_nrf54l15_cpuflpr.dts
│  │  │  ├── nrf54l15pdk
│  │  │  │  ├── nrf54l15_cpuapp_common.dtsi
│  │  │  │  │ nrf54l15pdk_nrf54l15_cpuflpr.dts
│  │  │  ├── nrf9280pdk
│  │  │  │  ├── nrf9280pdk_nrf9280_cpuapp.dts
│  │  │  │  ├── nrf9280pdk_nrf9280_cpuppr.dts
│  │  │  │  │ nrf9280pdk_nrf9280_cpurad.dts
│  ├── soc
│  │  ├── nordic
│  │  │  ├── nrf54l
│  │  │  │  │ soc.c

Outputs:

Toolchain

Version: 3dd8985b56
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:3dd8985b56_912848a074

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

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
  • sdk-nrf test count: 1037
  • sdk-zephyr test count: 6255
• ❌ Integration tests
  • ✅ test-sdk-audio
  • ❌ 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-sdk-find-my
  • ✅ test-sdk-sidewalk
  • ✅ 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-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-proprietary_esb
  • test-fw-nrfconnect-ps
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-zigbee
  • test-sdk-dfu
  • test-sdk-mcuboot
  • test-sdk-pmic-samples
  • test-sdk-wifi
  • test-secdom-samples-public

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.

[tomi-font]

The commit title is incorrect?

[Vge0rge]

The commit title is incorrect?

You are right, I updated it now.

[github-actions]

This pull request has been marked as stale because it has been open (more than) 30 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 7 days. Note, that you can always re-open a closed pull request at any time.