manifest: update collab-nrfx-4.0 to have PDM prescaler calculation

[mstasiaknordic]

test-sdk-nrf: collab-nrfx-4.0

[NordicBuilder]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
nrfx	https://github.com/nrfconnect/nrfx/commit/f958395d86d9e499b12e6c0470ba384c1a25b070	https://github.com/nrfconnect/nrfx/commit/7ed74ac12ab94f561af820da8fb7089a0323e6de (4.0-dev)	nrfconnect/[email protected]
zephyr	nrfconnect/sdk-zephyr@5c04023	nrfconnect/sdk-zephyr@079d803 (collab-nrfx-4.0)	nrfconnect/[email protected]

✅ All manifest checks OK

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: 17

Inputs:

Sources:

sdk-nrf: PR head: d25c7e1a8db38b1dea6756a0828245045e6bf3b8
zephyr: PR head: 079d80388a6240f572442ce7021f1aab31a56139

more details

sdk-nrf:

PR head: d25c7e1a8db38b1dea6756a0828245045e6bf3b8
merge base: 82cdd9420c64211c58681c562a1413a980843bc7
target head (collab-nrfx-4.0): 82cdd9420c64211c58681c562a1413a980843bc7
Diff

zephyr:

PR head: 079d80388a6240f572442ce7021f1aab31a56139
merge base: 5c0402339a005c1abe995018bcea1bacc56648c8
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 (2)

west.yml
zephyr
│  ├── drivers
│  │  ├── audio
│  │  │  │ dmic_nrfx_pdm.c

Outputs:

Toolchain

Version: 2b2cd9579a
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:2b2cd9579a_bba2ea5f2e

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

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
• ❌ Integration tests
  • ❌ desktop52_verification
  • ✅ test-fw-nrfconnect-apps
  • ✅ test-fw-nrfconnect-ble_samples
  • ❌ test-fw-nrfconnect-chip
  • ✅ test-fw-nrfconnect-nfc
  • ✅ test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • ✅ test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • ✅ test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • ✅ test-fw-nrfconnect-nrf-iot_samples
  • ✅ test-fw-nrfconnect-nrf-iot_lwm2m
  • ❌ test-fw-nrfconnect-nrf-iot_thingy91
  • ❌ test-fw-nrfconnect-proprietary_esb
  • ✅ test-fw-nrfconnect-rpc
  • ✅ test-fw-nrfconnect-tfm
  • ✅ test-fw-nrfconnect-thread-main
  • ❌ test-fw-nrfconnect-nrf_lrcs_mosh
  • ❌ test-fw-nrfconnect-nrf_lrcs_positioning
  • ✅ test-sdk-wifi
  • ❌ test-low-level
  • ❌ test-sdk-pmic-samples
  • ✅ test-fw-nrfconnect-ps-main

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

[NordicBuilder]

Memory footprint analysis revealed the following potential issues

applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 12744[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 9492[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 9102[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 5858[B] - link (cc: @nrfconnect/ncs-ll-ursus)

Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-24744/17)

[mstasiaknordic]

test-fw-nrfconnect-chip seems to report unrelated failures, will rerun to possibly make it green