boards: nordic: Fix issues with nRF54LV10A/ns

[degjorva]

Update to align with other 54L devices.

[NordicBuilder]

CI Information

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

Inputs:

Sources:

sdk-nrf: PR head: 4edb77320ea7a277d1539fcc163d39d772bd6489

more details

sdk-nrf:

PR head: 4edb77320ea7a277d1539fcc163d39d772bd6489
merge base: 52c59d9572291fb09e0b9db13732e0c9bb7bdf8c
target head (main): 20839e643c7632798bb9d8549c4c806eb4e24d86
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)

boards
│  ├── nordic
│  │  ├── nrf54lv10dk
│  │  │  ├── Kconfig.defconfig
│  │  │  │ nrf54lv10dk_nrf54lv10a_cpuapp_ns.dts

Outputs:

Toolchain

Version: f911d4f4e7
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:f911d4f4e7_5ea73affbf

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

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
  • sdk-nrf test count: 295
• ✅ Integration tests
  • ✅ test-low-level

Disabled integration tests

• • test-fw-nrfconnect-nrf_lrcs_mosh
  • desktop52_verification
  • test_ble_nrf_config
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-chip
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_cloud
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-ps-main
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-thread-main
  • test-sdk-audio
  • test-sdk-dfu
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-wifi
  • test-secdom-samples-public

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

[Copilot]

Pull request overview

This PR fixes the nRF54LV10A non-secure (ns) board configuration to properly support ARM TrustZone-M by aligning it with conventions used in other Nordic 54L series devices. The changes ensure correct memory partition references for non-secure firmware execution with TF-M as the Secure Processing Environment.

Key changes:

• Updated device tree to reference non-secure memory partitions (slot0_ns_partition and sram0_ns)
• Added USE_DT_CODE_PARTITION configuration selection for the non-secure board variant

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
boards/nordic/nrf54lv10dk/nrf54lv10dk_nrf54lv10a_cpuapp_ns.dts	Updated chosen nodes to reference non-secure flash partition (slot0_ns_partition) and SRAM region (sram0_ns) appropriate for TrustZone-M configuration
boards/nordic/nrf54lv10dk/Kconfig.defconfig	Added USE_DT_CODE_PARTITION selection for the non-secure board variant to properly utilize device tree code partition information

The changes are technically correct and consistent with TrustZone-M patterns used across other Nordic boards. No issues were identified during the review.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[degjorva]

@kl-cruz Please take a look

[degjorva]

@kl-cruz Ping