Partition Manager (PM) is a component of the nRF Connect SDK (NCS)
which uses yaml files to resolve flash partition placement with a
holistic view of the entire device, including each firmware image
present on the flash device, and various subsystems, such as settings
and NFFS.

When this NCS extension is used, various source files which would use
partition information from devicetree in "vanilla" zephyr instead use
defines generated by PM instead.

This commit removes support for HEX_FILES_TO_MERGE, as it conflicts
with PM.

The settings subsystem pm.yml defines a partition 'settings_storage'.
The nffs subsystem pm.yml defines 'nffs_storage'.

Leverage label translation to avoid patching partition names.

Refer to the NCS documentation page for this feature for more details.

This is a long-running out of tree patch which has been worked on by
several people. The following sign-offs are in alphabetical order by
first name.

Signed-off-by: Andrzej Głąbek <[email protected]>
Signed-off-by: Andrzej Puzdrowski <[email protected]>
Signed-off-by: Håkon Øye Amundsen <[email protected]>
Signed-off-by: Ioannis Glaropoulos <[email protected]>
Signed-off-by: Joakim Andersson <[email protected]>
Signed-off-by: Johann Fischer <[email protected]>
Signed-off-by: Martí Bolívar <[email protected]>
Signed-off-by: Ole Sæther <[email protected]>
Signed-off-by: Robert Lubos <[email protected]>
Signed-off-by: Sebastian Bøe <[email protected]>
Signed-off-by: Sigvart Hovland <[email protected]>
Signed-off-by: Thomas Stenersen <[email protected]>
Signed-off-by: Torsten Rasmussen <[email protected]>
Signed-off-by: Øyvind Rønningstad <[email protected]>
Signed-off-by: Trond Einar Snekvik <[email protected]>
Signed-off-by: Gerard Marull-Paretas <[email protected]>
Signed-off-by: Tomasz Moń <[email protected]>
Signed-off-by: Dominik Ermel <[email protected]>
(cherry picked from commit fbfb4df)

This commit adds the nRF54l15//nrf54l15/cpuapp/ns board variant to
sdk-zephyr. It allows to build nRF54l15pdk with TF-M in nRF Connect SDK.

This is done as a nrf noup patch as the out-of-tree board extension
feature is not available. When zephyrproject-rtos/zephyr#69548 is
completed, then this commit can be reverted and the variant be placed in
sdk-nrf repository.

Signed-off-by: Torsten Rasmussen <[email protected]>
(cherry picked from commit 8217fd3)

Zephyr's boot banner should not be used if NCS boot banner is enabled.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 67b7cca)

Complete rewrite of the 54l_ns DT board definition.

Now the secure board and non-secure board re-use a lot more code,
giving us a more maintainable solution.

Signed-off-by: Sebastian Bøe <[email protected]>
(cherry picked from commit 5e11b5f)

…eferences"

This reverts commit b876bd2.

That needs mbed TLS 3.6.0 to work, as pk_ecc.c was added in that
version.

To be reverted, when mbed TLS is updated to 3.6.0 in NCS.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 590a64a)

Removes explicit support for the legacy advertiser due
to incompatibility with SDC.

The legacy advertiser can be used (experimentally) with the
Zephyr Link Layer enabled, but is not recommended.

Signed-off-by: Håvard Reierstad <[email protected]>
(cherry picked from commit 60fce5e)

Disable processing of extended ADV packets by mesh scanner.
This is done to prevent loss of scan time due to reception
of pointer packets while scanning for mesh packets.

Signed-off-by: Ingar Kulbrandstad <[email protected]>
(cherry picked from commit 18285a0)

Changes the default MCUboot mode to update only for the thingy53,
to align with previous bootloader builds

Signed-off-by: Jamie McCrae <[email protected]>
(cherry picked from commit 48cb4e7)

Align to changes in DTS:
  renamed: rram0 -> cpuapp_rram
  sized up cpauapp_rram region szie as part of it was reserved for
  cpuflpr_rram (which is not used by this config).

Signed-off-by: Andrzej Puzdrowski <[email protected]>
(cherry picked from commit c3898cc)

This will be replaced by a different solution upstream (NCSDK-27673).

Migrate the existing BICR bindings from NCS 2.4.99-cs3 to NCS 2.7.0.
They are updated to remove obsoleted values. Enable generating bicr.hex
for Application core by default.

Signed-off-by: Grzegorz Swiderski <[email protected]>
(cherry picked from commit eb8e8ef)

Adjustment LFXO CLOAD value. New value is a resualt of DK's characterization.

Signed-off-by: Karol Lisak <[email protected]>
(cherry picked from commit fa10fde)

PM support is still required for nRF53 in the context of NCS.

Signed-off-by: Gerard Marull-Paretas <[email protected]>
(cherry picked from commit b42e02d)

Introduce NVS_LOOKUP_CACHE_FOR_SETTINGS Kconfig option that
enables a dedicated hash function for the NVS lookup cache
that takes advantage of the NVS ID allocation scheme used
by the NVS settings backend. As such, this option should
only be used if an application uses NVS via the settings
layer.

Signed-off-by: Damian Krolik <[email protected]>
(cherry picked from commit 3198700)

This adds temporary entropy driver simulation for
nRF54h20 device since final entropy source is not
available yet.

TODO: Remove this commit when proper solution will
be available.

Jira: NCSDK-25947

Signed-off-by: Kamil Gawor <[email protected]>
Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit c80ee99)

Allow for an additional buffer reference if callback is provided. This
can be used to extend lifetime of the net buffer until the data
transmission is confirmed by ACK of the remote.

Jira: NCSDK-27422

Signed-off-by: Marek Pieta <[email protected]>
(cherry picked from commit c735ea2)

By default, the BLE stack calls sent callback for ATT data when the data
is passed to BLE controller for transmission. Enabling this Kconfig
option delays calling the sent callback until data transmission is
finished by BLE controller (the callback is delayed until receiving the
num complete packets event).

Jira: NCSDK-27422

Signed-off-by: Marek Pieta <[email protected]>
(cherry picked from commit 3611f46)

Turn off suspending MRAM for NRF54H20 DK
This change is required so sections of code
depending on critical timings will not have unacceptable latency.

Turn on NRFS globally so turning off
suspending MRAM for NRF54H20 DK will work.

Signed-off-by: Jan Zyczkowski <[email protected]>
(cherry picked from commit 58284ff)
(cherry picked from commit 9b6cae8)
(cherry picked from commit 2c2f60d)

Since the introduction of zephyr_file() then the minimum required CMake
version has become 3.20.
Update zephyr_file() to use cmake_path insteasd of set().
This allows us to normalize the path and thereby also remove duplicates
in the list as paths are normalized.

Signed-off-by: Torsten Rasmussen <[email protected]>
(cherry picked from commit 8b3d4c6)

Fixes: #73066

Introduce sysbuild_root CMake module similar to the Zephyr root CMake
module. The sysbuild_root CMake module works similar to existing root
module, but with the difference that root paths are adjusted relative to
APP_DIR which is the main image, instead of relative to sysbuild.

Signed-off-by: Torsten Rasmussen <[email protected]>
(cherry picked from commit 24acc7d)

Add functions for local domain suspend to RAM. Add matching resume
procedure. Add pm_s2ram function for determining source of reset.
Add preserving NVIC and MPU state in retained RAM when CPU is powered off
during S2RAM procedure.

Upstream PR: zephyrproject-rtos/zephyr#73095

Signed-off-by: Adam Kondraciuk <[email protected]>

… cores

Currently function `z_nrf_grtc_wakeup_prepare()` should be available
only for the GRTC manager (`CONFIG_NRF_GRTC_START_SYSCOUNTER` is active).

Upstream PR: zephyrproject-rtos/zephyr#73095

Signed-off-by: Adam Kondraciuk <[email protected]>

Fix typo in `PM_S2RAM_CUSTOM_MARKING` description.

Upstream PR: zephyrproject-rtos/zephyr#73095

Signed-off-by: Adam Kondraciuk <[email protected]>

…vice

Expands driver to cover nRF54L15 features like AIN as GPIO configuration,
new reference voltage, different set of supported gain options.

Signed-off-by: Karol Lasończyk <[email protected]>
(cherry picked from commit 5f1fdc4)

…vice

Expands driver to cover nRF54H20 features like 8bit sample width.

Signed-off-by: Karol Lasończyk <[email protected]>
(cherry picked from commit 13196ec)

Adds full description of the adc node and support for memory regions.

Signed-off-by: Karol Lasończyk <[email protected]>
(cherry picked from commit 15fa37d)

Adds configuration to play with nRF54H20 PDK board.

Signed-off-by: Karol Lasończyk <[email protected]>
(cherry picked from commit 3c4ea76)

Adds configuration for making tests work.

Signed-off-by: Karol Lasończyk <[email protected]>
(cherry picked from commit ba30517)

Enables adc node to make it usable in tests/examples.

Signed-off-by: Karol Lasończyk <[email protected]>
(cherry picked from commit a04b2ad)

Add support for gains: 1/2, 1/3, 2/5, 1/4.

Upstream PR: zephyrproject-rtos/zephyr#74929

Signed-off-by: Karol Lasończyk <[email protected]>

…rted peripherals

ADC driver was aligned to nrf54h20 target.
Enable ADC Twister tests on that platform.

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit a3e1e39)

…m_allow

Enable test execution on nrf54h20dk.
Overlay file already exists.

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit cc9bd6d)

…tion on nrf54h20

Add overlay file for nrf54h20 cpuapp target.
Add nrf54h20 target to platform_allow.

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit 48fc687)

This change removes the BT_LE_PER_ADV_OPT_USE_TX_POWER option for
extended advertisement in BLE Audio PTS tests.

The Broadcaster setup options was hardcoded to include the
BT_LE_PER_ADV_OPT_USE_TX_POWER option. This causes incompabilities
for any controller not support it, and since the option is not
required for the audio tests it should not be used here.

Upstream PR: zephyrproject-rtos/zephyr#73361

signed-off-by: Frode van der Meeren <[email protected]>

…on Subrating

Add Kconfigs to enable experimental subrating HCI commands.

Signed-off-by: Timothy Keys <[email protected]>
(cherry picked from commit 570c86d)

Signed-off-by: Timothy Keys <[email protected]>

Expand testing for QDEC at nrf platforms.
It uses general sensor API,
however there are also nrf driver specific assumptions.

Upstream PR: zephyrproject-rtos/zephyr#74677

Signed-off-by: Piotr Kosycarz <[email protected]>

Extend nrf pwm driver test coverage by testing invalid port number

Upstream PR: zephyrproject-rtos/zephyr#75583

Signed-off-by: Piotr Krzyzanowski <[email protected]>

…Connection Subrating"

This reverts commit f6325a5.

Signed-off-by: Rubin Gerritsen <[email protected]>

This patch removes all uses of the adv auto-resume feature in the host
bsim tests, except for the test of that feature itself, and instead
makes all adv starts explicit.

The auto-resume feature is planned for deprecation. And, explicit
starting of adv makes what happens in the test more explicit as well.

Signed-off-by: Aleksander Wasaznik <[email protected]>
(cherry picked from commit 765b244)

…_disable()

Expectation: After calling `bt_disable()` it is possible to
use the Bluetooth APIs as if `bt_enable()` was never called.

This was not the case for `bt_id_create()`, it was not possible
to set the default identity. This prevented an application
developer to restart the stack as a different identity.

Keys also need to be cleared to avoid the following pattern:
1. Pair two devices
2. Central calls `bt_disable()` and `bt_enable()`.
   The central will now generate a new identity address.
3. Connect the two devices.
4. Re-establish encryption. Now the central will try to use
   the previously used keys. The procedure will fail
   because the peripheral does not have any keys associated
   with the new central address.

The API documentation is updated accordingly.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 3ce106c)

… timeout

Before this commit, the following bugs were present:
- When `CONFIG_BT_FILTER_ACCEPT_LIST` was set, connection establishment
  was cancelled upon RPA timeout. This required the application
  to restart the initiator every RPA timeout.
- When `CONFIG_BT_FILTER_ACCEPT_LIST` was not set, the RPA was not updated
  while the initiator was running.

This commit unifies the RPA timeout handling for both these cases.
Upon RPA timeout the initiator is cancelled and restarted when
the controller raises the LE Connection Complete event.
The workqueue state is checked when restarting the initiator to prevent
it being restarted when the timeout is hit.

Corresponding test cases have been added to ensure that this
feature works.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit ff80c0b)

When using the post_init_f to initialize the `bst_result`,
it is not possible to mark the test as
passed immediately as the `bst_result` will be
initialized after the test completes.

This change should overcome this limitation.

Bluetooth mesh tests are kept as is as we are not
sure if this will change the behavior.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 1aa33fe)

When reading the error message:
"ASSERTION_FAIL: command opcode 0x0c03 timeout with err -11" it may not be
obvious what is wrong with their setup unless you are very familiar
with HCI.

This commit adds some more documentation to make this more obvious.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 3609d97)

These macros allows us to compare strings in a simpler way.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit a35d5e7)

…meout

It seemed like there was lacking test coverage for this
functionality.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit b30d2d1)

… RPA timeout

zephyrproject-rtos/zephyr#72674 fixed
a bug where this configuration did not work.

Now that this configuration is tested, we should mark it
as supported.

The timeout check that was present in the code before
was useless and was not working because the check was
run before a default timeout of 0 was converted to a timeout.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 9cf6839)

…llbacks

A naive implementation would look like

```c
void bt_init()
{
  bt_le_conn_cb_register();
  bt_enable();
}
```

When the app later adds the possibility to enable and disable
Bluetooth, it may happen that the application developer calls
`bt_init()` instead of `bt_enable()`. This results in invalid
behavior. This kind of bug is currently a bit harder to debug
as the callback register APIs do not reject registering a
callback twice.

Improving the API documentation is the first step towards making
this a bit more user friendly.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 2712b32)

This commit adds host support for the Path Loss Monitoring
feature see Bluetooth Core specification, Version 5.4,
Vol 6, Part B, Section 4.6.32.

Limited logic is required, just adding a wrapper around the
HCI command and callback for HCI event.

Add new zone - BT_CONN_LE_PATH_LOSS_ZONE_UNAVAILABLE, to
convert 0xFF path loss to a useful zone.

Add new Kconfigs and functionality to the bt shell.

Signed-off-by: Sean Madigan <[email protected]>
(cherry picked from commit 0b327db)

This allows us to use functionality provided by slist.
First use case: Avoid adding an element twice.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 6e6bb26)

Callbacks can only be registered once. Otherwise the slist
will become circular.

In this commit we have choosen to ignore the second registration
call if the callback has already been registed. The alternative
is to trigger an assertion. That doesn't work if the assertions
are turned off.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 2ec3cd3)

This improves consistency with other callback lists like
scan_cbs and pa_sync_cbs.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 3eb975d)

…urn status

Returning a status code will allow the application developer
to detect logic issues.

We consider this as not breaking the API.
If `-Werror -Wunused-result` is enabled, the application developer needs
to validate the return code.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 5098bf3)

…nning

The HCI command LE Read Supported States command returns
if the controller supports running the scanner and initiator
roles in parallel.

This commit utilizes this information in the host:
- It does not prevent initiating a connection when the scanner is
  running
- It does not prevent the host from restarting the background
  scanner when there the host wants to auto-initiate a connection.
- It does not stop the scanner when the host wants to auto-initiate
  a connection.

To support this feature, the scanner and initiator
always have to use the same address.
This because the HCI command LE Set Random Address
cannot be issued after the initiator or scanner has started.
1. When privacy is disabled, the scanner has to use its identity
   address to ensure it uses the same address as the initiator.
2. Only one identity is supported.

To simplify the implementation, it is a requirement to use
extended advertising commands to avoid interfering with
the random address used by the advertiser(s).

Also, it is a requirement to never use time-limited scanning,
as RPA this feature does not work when privacy is being used.
See zephyrproject-rtos/zephyr#73634.

The changes in this commit will be tested out of tree as the
Zephyr Bluetooth Controller does not support this functionality.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 9984adf)

…cros

When brackets are used in macros, there may sometimes be a space in
front of them. The checkpatch script should allow this.
The change includes the example that triggered the need for this
change.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit f78c51d)

This API converts a HCI error code to a string.
This can be useful if application developers want to print them
in the applications.

Later we can also use them in the host to improve debuggability.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit bfba19d)

We want to able to use cocinelle on ztest functions as
well when transforming APIs.

Provide a simple macro so that test functions are recognized.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit fc37736)

…ssertions

ztest now provides functionality to compare strings.
These are simpler to use than the strcmp ways.

The semantic patch transforms many of the commonly used patterns.
It does not handle variable length macros.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 470a0fc)

… timeout

This makes it more clear what is happening when the host cancels
connection creation where the controller raises
the connection complete event with status set to
"UNKNOWN CONNECTION IDENTIFIER (0x02)".

This is especially useful for developers not familiar with this
detail in the spec.

See also: Core_v5.4, Vol 4, Part E, Section 7.8.13,
LE Create Connection Cancel command.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 1b33616)

This can be useful if application developers
want to print them in the applications.

Later we can also use them in
the host to improve debuggability.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 94d712e)

The function reuses the ATT implementation.
To make the function simpler to use, the function handles both positive
and negative values.

Unfortunately the APIs do not document if the API returns an
errno val or a GATT return value.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 4e30803)

The `type` parameter of `struct bt_le_scan_param` is documented as
taking a `BT_LE_SCAN_TYPE_*` value, not a `BT_HCI_LE_SCAN_*` value.

In practice this makes no difference as the values are defined as the
same integer, but does result in `<zephyr/bluetooth/hci.h>` not needing
to be included.

Signed-off-by: Jordan Yates <[email protected]>
(cherry picked from commit cf870e8)

…IVACY=y

See comment in code.

Fixes #73634

Signed-off-by: Jonathan Rico <[email protected]>
(cherry picked from commit be61ae4)

…on Subrating

Add Kconfigs to enable experimental subrating HCI commands.

Signed-off-by: Timothy Keys <[email protected]>
(cherry picked from commit 570c86d)

fixup! [nrf noup] soc: arm: nRF91: Add SPU Flash/RAM alignment

The nRF54L15 doesn't use the SPU for setting the security attributes
for flash/RAM regions. In order to avoid having multiple Kconfigs
with similar meaning I renamed the alignment Kconfig option to something
more generic in order to use the same symbol for all the TrustZone enabled
devices.

Ref: NCSDK-25023

Signed-off-by: Georgios Vasilakis <[email protected]>

fixup! [nrf noup] boards: add nrf54l15/nrf54l15/cpuapp/ns as board variant

The nRF54L15 is using the SAU and the MPC to configure the security
attributes for TrustZone. The SPU is only used for the configuration
of the peripherals. This sets the Kconfig configurations for TrustZone
which use the correct region size(based on the MPC) for nRF54L15.

Ref: NCSDK-25023

Signed-off-by: Georgios Vasilakis <[email protected]>

squash! [nrf noup] board: nordic: thingy53: Default to update only MCUboot type

Changes the thingy53 default configuration for sysbuild to enable
using all RAM in the MCUboot image

Signed-off-by: Jamie McCrae <[email protected]>

Should be executed only when bluetooth is changing.

Signed-off-by: Piotr Kosycarz <[email protected]>

Folder renamed at HWMv2:
soc/arm/nordic_nrf->soc/nordic

Signed-off-by: Piotr Kosycarz <[email protected]>

Renamed:
samples/bluetooth/hci_rpc->samples/bluetooth/hci_ipc

Signed-off-by: Piotr Kosycarz <[email protected]>

Update dependent sources.

Signed-off-by: Piotr Kosycarz <[email protected]>

No longer used.

Signed-off-by: Piotr Kosycarz <[email protected]>

Update dependent sources.

Signed-off-by: Piotr Kosycarz <[email protected]>

…test suite

Test NACK handling, bus recovery and FAST speed read.

Upstream PR: zephyrproject-rtos/zephyr#74844

Signed-off-by: Bartosz Miller <[email protected]>

In function nrfs_backend_send_work tx_data buffer was
used in function ipc_service_send instead of
data_to_send. This is fixed and also tx_data and rx_data
are moved to coresponding functions preventing such
issues in future.

Upstream PR: zephyrproject-rtos/zephyr#75803

Signed-off-by: Lukasz Stepnicki <[email protected]>

Add negative test cases for the MBOX driver.
Confirm that driver implementation is aligned with
the MBOX API documentation available at
https://docs.zephyrproject.org/latest/hardware/peripherals/mbox.html

Enable test execution on nRF54H20 Application and PPR cores.

Upstream PR: zephyrproject-rtos/zephyr#75114

Signed-off-by: Sebastian Głąb <[email protected]>

… nRF54l15

Add overlay that enables execution of mbox_error_cases on
nrf54l15pdk/nrf54l15/cpuapp.

Upstream PR: zephyrproject-rtos/zephyr#75114

Signed-off-by: Sebastian Głąb <[email protected]>

Print on what board/core sample is executing.

Print how many bytes of data can be sent
in the mbox message (show use of mbox_mtu_get_dt()).

Print how many channels are available for incoming and/or
outgoing messages (show use of mbox_max_channels_get_dt()).

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit c6ef694)

Add sample configuration 'nrf54h20_app_ppr' where:
- cpuapp sends messages to cpuppr vevif channel 15,
- cpuppr sends messages to cpuapp bellboard channel 18.

Add sample configuration 'nrf54h20_rad_app' where:
- cpuapp sends messages to cpurad bellboard channel 12,
- cpurad sends messages to cpuapp bellboard channel 18.

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit 92b0d6d)

…rf54h20

Nrf54h20dk has UART Flow Control enabled by default on all cores.
It's a source of problem when mbox sample is run in Twister.
Twister opens serial port only on host core,
thus nobody confirms reception of logs from remote core.
As a result, remote core stucks on printing boot banner.

Twister fails sample due to the timeout while waiting for messages
from remote to host.

Disable Flow Control on remote core when mbox sample is executed
on nrf54h20.

Upstream PR: zephyrproject-rtos/zephyr#75309

Signed-off-by: Sebastian Głąb <[email protected]>

Still trigger on all code changes but excluded non-code folders.

Signed-off-by: Piotr Kosycarz <[email protected]>

Base on compilation dependencies.

Signed-off-by: Piotr Kosycarz <[email protected]>

Do not permit configuring clocks from non-secure as NRF_OSCILLATORS is
a not supported as a non-secure peripheral

Signed-off-by: Sebastian Bøe <[email protected]>

In this patch we do several things to be able to configure power and
clocks when NRF_OSCILLATORS and NRF_REGULATORS is secure.

We port soc.c to TF-M so that the TF-M image can do the same
configuration that would normally be done by the Zephyr image.

This is done by explicitly including autoconf.h for instance.

We also ifdef-out the configuration when nordicsemi_nrf54l_init is
invoked from a non-secure image, because the peripherals are secure.

Signed-off-by: Sebastian Bøe <[email protected]>

This action will automatically manage a PR to sdk-nrf
once a PR to sdk-zephyr is created.

This includes:
 - Creating an initial PR
 - Updating and (optionally) rebase it once the PR
   to sdk-nrf is merged.

The action can be disabled by adding the string
"manifest-pr-skip" to the title or body of the PR.

This will simplify cherry-picking changes from upstream
zephyr.

Signed-off-by: Rubin Gerritsen <[email protected]>

To make the scanner module more understandable and more streamlined, I
reworked the update mechanism of the scanner. The scanner tracks now the
parameters that were used to enable it and the reason why it is running.
This facilitates state logic and allows other modules to "start the
scanner", altough it is already running.
This is mostly a refactoring and not a functional change.

Added a test to verify the behavior.

Upstream PR: zephyrproject-rtos/zephyr#73923

Signed-off-by: Jan Müller <[email protected]>

Handling of board changes was broken and did not support v2 boards, fix
this to optimize CI execution on localized changes of board files.

Signed-off-by: Anas Nashif <[email protected]>
(cherry picked from commit 94b9790)

…when !XIP

Many boards/SoCs in-tree do this:
    if !XIP
    config FLASH_SIZE
        default 0
    config FLASH_BASE_ADDRESS
        default 0
    endif

And many other boards are missing this configuration (e.g. stm32 series).
Making this the default helps get non-XIP just working

Signed-off-by: Grant Ramsay <[email protected]>
(cherry picked from commit c5642a7)

Move the GitHub runners currently on macos-11 to macos-14 as the former is
no longer supported by GitHub.

Signed-off-by: Henrik Brix Andersen <[email protected]>
(cherry picked from commit fa4537d)

…ch in modules

Fixes #71761

The `west boards` command parses extra BOARD_ROOTs from Zephyr modules,
so that the boards defined in those modules are automatically listed.

In HWMv2, OOT boards can be described in terms of OOT SoCs, which means
that extra SOC_ROOTs must also be provided. Otherwise, an error message
will be displayed when attempting to list all boards. Therefore, every
Zephyr module SOC_ROOT should be included as well.

In HWMv1 (deprecated), OOT boards can be defined in terms of OOT archs,
but module ARCH_ROOTs had never been included automatically. The fix for
this is long overdue, but it's included for symmetry.

Signed-off-by: Grzegorz Swiderski <[email protected]>
(cherry picked from commit 7a10c7d)

…runner configs

When validating the flash runner configurations in `soc.yml`, the only
SoCs that were considered had to be defined under this structure:

   family:
     - series:
         - socs:
             - name: ...

However, the `family` and `series` keys are optional, so the `soc.yml`
files can also be arranged like this:

   family:
     - socs:
         - name: ...
   series:
     - socs:
         - name: ...
   socs:
     - name: ...

The solution is to move the validation code further down, so that it can
reuse the SoC data that was already correctly parsed while initializing
a `Systems` instance.

Signed-off-by: Grzegorz Swiderski <[email protected]>
(cherry picked from commit 9b68230)

Upstream PR: zephyrproject-rtos/zephyr#72857

Cleanup the Kconfig generating code in hwm_v2.cmake by moving common
logic inside the kconfig_gen() helper function.

This prepares the code for board extension feature.

Signed-off-by: Torsten Rasmussen <[email protected]>
(cherry picked from commit d39cc46b56294b6eb297a67478334c23db8c8ca3)

This automated patch is inserted before a cherry-pick of:

ad16407 cmake: scripts: support board extension

This allows the above commit to be applied cleanly, even though it
appears to conflict with the following commit(s):

ec3b301 [nrf fromlist] scripts: support soc/boards in Zephyr modules

The conflicts are left to be fixed in a follow-up patch, instead of
doing so in the cherry-pick itself.

Signed-off-by: Grzegorz Swiderski <[email protected]>

Upstream PR: zephyrproject-rtos/zephyr#72857

Fixes: #69548

Support extending an existing board with new board variants.

This commit introduces the following changes to allow a board to be
extended out-of-tree.

The board yaml schema is extended to support an extend field which
will be used to identify the board to be extended.

A board 'plank' can be extended like this:
> board:
>   extend: plank
>   variants:
>     - name: ext
>       qualifier: soc1

For the rest of the build system this means that there is no longer a
single board directory.
The existing CMake variable BOARD_DIR is kept and reference the
directory which defines the board.
A new CMake variable BOARD_DIRECTORIES provides a list of all
directories which defines board targets for the board.
This means the directory which defines the board as well as all
directories that extends the board.

Signed-off-by: Torsten Rasmussen <[email protected]>
(cherry picked from commit ad16407aca8ccde1aaa57d4d1dcb15bb4d0bfc25)

This patch finalizes the 3-way merge between:

ad16407 cmake: scripts: support board extension

and:

ec3b301 [nrf fromlist] scripts: support soc/boards in Zephyr modules

Signed-off-by: Grzegorz Swiderski <[email protected]>