This reverts commit 7ad93e1.

Signed-off-by: Robert Lubos <[email protected]>

This reverts commit 0b1ebb5.

Signed-off-by: Robert Lubos <[email protected]>

…WIS slave"

This reverts commit 0301be3.

Signed-off-by: Robert Lubos <[email protected]>

This reverts commit ab8d66d.

Signed-off-by: Robert Lubos <[email protected]>

…54H20 target"

This reverts commit 1f655d6.

Signed-off-by: Robert Lubos <[email protected]>

This reverts commit 4aa01ec.

Signed-off-by: Robert Lubos <[email protected]>

…f54h20dk support"

This reverts commit 0bdee3c.

Signed-off-by: Robert Lubos <[email protected]>

…rty to SPI"

This reverts commit 1c5cc9d.

Signed-off-by: Robert Lubos <[email protected]>

…nd slave"

This reverts commit 51407a9.

Signed-off-by: Robert Lubos <[email protected]>

…handling"

This reverts commit 6498044.

Signed-off-by: Robert Lubos <[email protected]>

This reverts commit 16458ff.

Signed-off-by: Robert Lubos <[email protected]>

… nrf54h20dk"

This reverts commit f77e4e9.

Signed-off-by: Robert Lubos <[email protected]>

… nrf54l15"

This reverts commit 0fb3fdc.

Signed-off-by: Robert Lubos <[email protected]>

…_rx_reset function"

This reverts commit 7b3063a.

Signed-off-by: Robert Lubos <[email protected]>

…e on rx_enable"

This reverts commit 2ace1ea.

Signed-off-by: Robert Lubos <[email protected]>

This reverts commit 7b8fb26.

Signed-off-by: Robert Lubos <[email protected]>

…y mode"

This reverts commit d39eff8.

Signed-off-by: Robert Lubos <[email protected]>

This reverts commit 12f0521.

Signed-off-by: Robert Lubos <[email protected]>

…_STACK_SIZE use"

This reverts commit 77a7170.

Signed-off-by: Robert Lubos <[email protected]>

…unctions"

This reverts commit 85ed6f2.

Signed-off-by: Robert Lubos <[email protected]>

…er yaml for PDK 0.3.0"

This reverts commit 2c8aad6.

Signed-off-by: Robert Lubos <[email protected]>

…for BLE"

This reverts commit 12bfeea.

Signed-off-by: Robert Lubos <[email protected]>

… backend"

This reverts commit 443cae0.

Signed-off-by: Robert Lubos <[email protected]>

This reverts commit b3ec345.

Signed-off-by: Robert Lubos <[email protected]>

This reverts commit 4dd0af5.

Signed-off-by: Robert Lubos <[email protected]>

This reverts commit da1af7e.

Signed-off-by: Robert Lubos <[email protected]>

…ct` command"

This reverts commit 73bef57.

Signed-off-by: Robert Lubos <[email protected]>

… get opt parsing"

This reverts commit 08dee4b.

Signed-off-by: Robert Lubos <[email protected]>

… platform allow"

This reverts commit 51c8066.

Signed-off-by: Robert Lubos <[email protected]>

The tests do not depend on the usb_device or usbd feature.

Signed-off-by: Johann Fischer <[email protected]>
(cherry picked from commit 43c9176)

Use new feature "usbd" to distinguish the dependency.

Signed-off-by: Johann Fischer <[email protected]>
(cherry picked from commit 1e5a501)

…ol OUT

Make sure to feed control OUT endpoint with at least 8 bytes buffer to
make it possible to always receive SETUP data. This solves the assertion
failure in net_buf_add() called inside dwc2_handle_evt_setup() when a
host decides to start new control transfer immediately after it has
issued control transfer with Data Stage from host to device with wLength
less than 8.

Signed-off-by: Tomasz Moń <[email protected]>
(cherry picked from commit fa0a6e2)

Release buffer allocated in dwc2_ctrl_feed_dout() on endpoint deactivate
to prevent the buffer from leaking on USB stack disable.

Signed-off-by: Tomasz Moń <[email protected]>
(cherry picked from commit fb27c36)

Reduce RAM disk size from 192 sectors down to 1 sector to solve linking
issue due to qemu_cortex_m3 target having too little RAM. The RAM disk
size does not really matter in this test case and should be as small as
possible.

Enable test random generator to solve missing sys_rand_get() required by
networking subsystem.

Signed-off-by: Tomasz Moń <[email protected]>

Upstream PR: zephyrproject-rtos/zephyr#74220

…ction"

This reverts commit 98ba1b4.

Signed-off-by: Andrzej Głąbek <[email protected]>

Allow to protect the data part of each NVS item with a 32-bit CRC.
This uses 4 more bytes per NVS item.

Signed-off-by: Adrien Ricciardi <[email protected]>
(cherry picked from commit b76d630)
Signed-off-by: Andrzej Głąbek <[email protected]>

Adapt the test_nvs_gc_corrupt_close_ate test to forge the data CRC.

Signed-off-by: Adrien Ricciardi <[email protected]>
(cherry picked from commit e13840c)
Signed-off-by: Andrzej Głąbek <[email protected]>

The CONFIG_NVS_DATA_CRC configuration item allows to enable a CRC-32
on the data part of the NVS items.

Signed-off-by: Adrien Ricciardi <[email protected]>
(cherry picked from commit 61474ac)
Signed-off-by: Andrzej Głąbek <[email protected]>

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 59c0a7c)
(cherry picked from commit 98ba1b4)

…evice config

Pass the list of supported twister fixtures for a given platform to pytest
via DeviceConfig. This allows for the pytest suites to use knowledge of the
fixtures for test suite configuration.

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

…iguration

Allow twister fixtures to contain extra information, which can be used for
test suite configuration. The extra information can be appended to existing
fixtures separated by a colon (i.e. <fixture>:<configuration>).

This is especially useful for the pytest harness, where a fixture of a
given type may need to refer to an instance of a particular piece of host
hardware needed by the pytest suite (e.g. a network interface, a UART, or a
CAN interface connected to the device under test).

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

…ong with fixture

Allow specifying the python-can configuration context to use along with the
"can" fixture. This opens up for specifying board-specific contexts in the
twister hardware map file.

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

The list of reserved PPIs by MPSL should be kept if MPSL is enabled.
The 802154 radio driver is not the only user of MPSL.

Upstream PR: zephyrproject-rtos/zephyr#74139

Signed-off-by: Jonathan Rico <[email protected]>

…e output

Extend automated testing on HW by veryfing console output.

Signed-off-by: Piotr Kosycarz <[email protected]>
(cherry picked from commit c9c9c97)

Add more samples for verification.

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

Use of ARGV1 is undefined when number of arguments to function is less
than 2. Therefore switch to ARGN which holds arguments beyond required
arguments.
If there are no optional arguments, then ARGN is just an empty list,
thus making it safe to use.

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

…nt for samples

This commit refactors sysbuild entry code by creating a CMake sysbuild
module for image processing and place sysbuild entry code in a
<app>/sysbuild/CMakeLists.txt file.

A template/CMakeLists.txt file will be use as template for applications
which doesn't provide their own entry file.

An application may create a sysbuild/CMakeLists.txt file.
The sysbuild/CMakeLists.txt file is similar in nature to the
toplevel CMakeLists.txt file but intended to used by sysbuild.
This allows application developers to adjust how an application is
built with sysbuild.

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

…sbuild

APPLICATION_CONFIG_DIR is supported in Zephyr and allows to adjust the
location from which prj.conf and friends are picked up.

This also works for images when using sysbuild, however sysbuild itself
ignores the value of APPLICATION_CONFIG_DIR, meaning that sysbuild only
accepts sysbuild.conf located directly in the sample folder.

Extend sysbuild to support APPLICATION_CONFIG_DIR so sysbuild follows
regular Zephyr CMake behavior.

Introduce SB_APPLICATION_CONFIG_DIR to allow changing the location
for sysbuild only, without propagating the value to images.

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

… folder

If not defined by caller, then set APPLICATION_BINARY_DIR to
CMAKE_CURRENT_BINARY_DIR. This is normally be done by
`find_package(Zephyr)`, but due to the indirection introduced with
fc1884e to allow applications to
provide their own sysbuild entry point, then the APPLICATION_BINARY_DIR
is unexpectedly set to the bin dir of the entry point.

Restore the old behavior so that APPLICATION_BINARY_DIR per default
again points to top-level sysbuild binary dir.

Upstream PR: zephyrproject-rtos/zephyr#74210

Signed-off-by: Torsten Rasmussen <[email protected]>

The sysbuild part of sysbuild/application creates a sysbuild/application
folder under top-level build dir. However, having a sysbuild folder at
this level means that tab completion for sysbuild pre-fixed build
targets will stop after completing just `sysbuild` and then show several
subfolders, making it hard to see important build targets, such as:
`ninja sysbuild_menuconfig`.

As `sysbuild/application` is just a folder name, then move it to
`_sysbuild` instead to avoid impacting tab completion for  ninja and
make.

Also strip the `application` part in the process, as the extra folder
doesn't provide any extra benefit, but is just one more level to enter
when browsing the build folder structure.

Upstream PR: zephyrproject-rtos/zephyr#74210

Signed-off-by: Torsten Rasmussen <[email protected]>

…domain file

Fixes an issue whereby the domains file in sysbuild projects
would be loaded and used with outdated information if sysbuild
configuration was changed then west flash was ran directly after
it

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

This reverts commit 91eeadb.

Signed-off-by: Rafał Kuźnia <[email protected]>

Erase and reset must run only once during flashing.
This prevents a situation, where the next flashed image erases the
previous one.

Signed-off-by: Rafał Kuźnia <[email protected]>
(cherry picked from commit 6551492)

The nrfutil device v2.4.x now supports the recover operation. Configure
run once to ensure that domains are not unnecessarily erased.

Upstream PR: zephyrproject-rtos/zephyr#74298

Signed-off-by: Rafał Kuźnia <[email protected]>

It's just a stub until STM is working in upstream/NCS.

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