Skip to content

Conversation

@ahasztag
Copy link
Contributor

…text

This commit adds the possibility to add additional custom context for flash operations for usage by non-standard flash drivers.

Upstream PR #: 87745

masz-nordic and others added 30 commits March 5, 2025 12:49
…_QUAD_1_4_4

Extend driver to support single lane and 1-4-4 IO modes.

Upstream PR #: 85520

Signed-off-by: Marcin Szymczyk <[email protected]>
Added clocks to GRTC node to allow GRTC output and
access to frequency property.

Upstream PR #: 86701

Signed-off-by: Michał Stasiak <[email protected]>
…and MODE_QUAD_1_4_4"

This reverts commit b44731a.

Signed-off-by: Marcin Szymczyk <[email protected]>
…_QUAD_1_4_4

Extend driver to support single lane and 1-4-4 IO modes.

Upstream PR #: 85520

Signed-off-by: Marcin Szymczyk <[email protected]>
…uflpr

Enabled west flash and west erase for nRF54L20 PDK FLPR core.
Added missing reset qualifier for nRF54L20 and nRF54L09.

Upstream PR #: 79355

Signed-off-by: Michał Stasiak <[email protected]>
…F54L20pdk"

This reverts commit 9b95c91.

Signed-off-by: Michał Stasiak <[email protected]>
Added support for FLPR core in nRF54L20pdk board.

Upstream PR #: 79355

Signed-off-by: Michał Stasiak <[email protected]>
JLink now recognises the proper device names.

Signed-off-by: Jordan Yates <[email protected]>
(cherry picked from commit e7ccf82)
…uide docs for 4.2

This introduces the release notes and migration guide for Zephyr 4.2.0
earlier so that people have a placeholder to start adding content as
they line up pull requests for the 4.2 release.

Signed-off-by: Benjamin Cabé <[email protected]>
(cherry picked from commit 3ef9540)
Nordic has a new tool, nRF Util (`nrfutil`) which is replacing the
previous set of command-line tools (particularly `nrfjprog`) that Zephyr
had been using by default in many of the boards to flash the firmware
onto the device.

Since nRF Util is already mature and is going to be replacing the existing
tools, including `nrfjprog`, it is now a good time to change the default
flash tool to reflect this fact.

Note that `nrfjprog` support is not being removed at all, but this may
be a breaking change for users that do not have nRF Util installed. For
this reason we also add a note in the migration guide.

More info:
https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-util-unified-command-line-utility

Installation:
https://www.nordicsemi.com/Products/Development-tools/nrf-util

Documentation:
https://docs.nordicsemi.com/bundle/nrfutil/page/README.html

Upstream PR #: 86729

Signed-off-by: Carles Cufi <[email protected]>
nrf-squash! [nrf noup] tests: drivers: mspi: api: Add nRF54L15 overlay file

Custom overlay is now in `nrf/tests/zephyr/...`

Signed-off-by: Marcin Szymczyk <[email protected]>
Add USB variant config files for esp32c3 boards.

Signed-off-by: Raffael Rostagno <[email protected]>

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit 8048a6a)
Enable flash samples for s32z board

Signed-off-by: Cong Nguyen Huu <[email protected]>

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

The tests for settings will not work properly with just provided config
file for mimxrt1020:
west build -p always -b mimxrt1020_evk samples/subsys/settings

as there the settings_save_one() would return -2 (-ENOENT) as by default
the CONFIG_SETTINGS_NONE is defined for mimxrt1020 configuration.

For proper operation (i.e. to have a memory medium to store settings
values) the NVS backend needs to be enabled.

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

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit 8719aba)
S2 has 12-bit ADC.

Signed-off-by: Marek Matej <[email protected]>

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit 37f2f7e)
Remove ADC2 support (identified as adc1 entry)
for additional ESP32-C3 based board targets.
Other boards have those instances already deleted.

Signed-off-by: Sylvio Alves <[email protected]>

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit 40b474c)
Added build configuration for nRF54L09.

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

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit 5064401)
Move overlays and conf from boards to socs in following samples :
- samples/drivers/adc/adc_dt
- samples/drivers/counter/alarm
- samples/drivers/dac
- samples/subsys/settings

Signed-off-by: Marek Matej <[email protected]>

add more samples

Signed-off-by: Marek Matej <[email protected]>

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit b58c424)
Almost all overlays only enable NVS and SETTINGS_NVS, something that
should be enabled in sample directly. Remove all overlays and make the
sample more genenric.

Use filter on storage partition to enable testing the sample on more
plaforms.

Signed-off-by: Anas Nashif <[email protected]>

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

Fix mistake in host implementation of Advertising Coding Selection.

The host should only try set the BT_LE_FEAT_BIT_ADV_CODING_SEL_HOST
when the observer role is enabled. If a broadcaster enables the
CONFIG_BT_EXT_ADV_CODING_SELECTION Kconfig option bluetooth will
fail to initialise.

Upstream PR #: 86731

Signed-off-by: Thomas Deppe <[email protected]>
String location information should only be sent for core which
do not append strings to the log message (PPR, FLPR). Without
this, cpurad was also sending that information and that was
redundant.

Upstream PR #: 86242

Signed-off-by: Krzysztof Chruściński <[email protected]>
Update the HW models module to:
b84bd7314a239f818e78f6927f5673247816df53

Including the following:
b84bd73 UART PTY backend: Correct a few comments
f945d62 RADIO 54: Fix reset value of TIMING register
9fd4133 MDK nrfx_erratas.h: Ensure backwards compatibility with old
        nrfx versions
85061b1 MDK: Provide empty replacement for nrf_erratas.h

Signed-off-by: Alberto Escolar Piedras <[email protected]>
(cherry picked from commit b932e14)
…ipherals

Add dmic to the list of supported peripherals on nRF54L20pdk.

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

Add test configuration on DMIC nodes that are compatible
with 'nordic_nrf_pdm'.
Add missing DTS definitions in a board overlay.

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit 22d9f0c)
…20pdk

Enable execution of DMIC sample on nRF54L20pdk.

Signed-off-by: Sebastian Głąb <[email protected]>
(cherry picked from commit 773cf96)
…and MODE_QUAD_1_4_4"

This reverts commit ee6cc76.

Signed-off-by: Marcin Szymczyk <[email protected]>
…tion for nRF54H20 DK"

This reverts commit 664042f.

Signed-off-by: Marcin Szymczyk <[email protected]>
…to memory map"

This reverts commit bd74349.

Signed-off-by: Marcin Szymczyk <[email protected]>
… "jedec,mspi-nor" devices"

This reverts commit 87a4e34.

Signed-off-by: Marcin Szymczyk <[email protected]>
…MIF node"

This reverts commit 3b45cae.

Signed-off-by: Marcin Szymczyk <[email protected]>
tmon-nordic and others added 19 commits March 28, 2025 10:25
For many devices iSerialNumber is not required. The only device class
currently supported in Zephyr that requires iSerialNumber is MSC. If the
serial number is not available then iSerialNumber must be 0. Failure to
read the string descriptor for non-zero iSerialNumber fails USB Command
Verifier Chapter 9 tests.

When USBD_DESC_SERIAL_NUMBER_DEFINE() was used without CONFIG_HWINFO
then it did lead to runtime failure when requesting the string (thus
failing certification).

Fail USBD_DESC_SERIAL_NUMBER_DEFINE() at build-time if CONFIG_HWINFO is
not set to prevent the surprise at runtime. Only define serial number
descriptors if CONFIG_HWINFO is enabled.

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

It should be possible to select maximum supported MQTT version, so that
for example MQTT 5.0 features can be compiled-out in case they're not
needed.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit f31a45f)
…QTT 5.0 enabled

Add test variant which enables MQTT 5.0 support. MQTT 3.1.1 should still
work just fine in such case, so it needs to be verified that's the case.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 08f8e2f)
…ngth

The macro did not take into account the 2-byte binary data length
encoded before the actual binary data.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 1eb9a5c)
Add support for CONNECT message specified in MQTT 5.0, along with
property encoders required to encode MQTT properties which is a new
concept in MQTT 5.0. Connect and will properties can be specified by the
application in the mqtt_client structure before connecting.

Introduce a helper function which allows to verify whether MQTT 5.0 is
used or not, so that it's still possible to use MQTT 3.1 even if MQTT
5.0 support is enabled in Kconfig.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 8fe2965)
Add support for CONNACK message specified in MQTT 5.0, along with
property decoders required to decode MQTT properties. Decoded properties
are provided to the application within mqtt_connack_param structure,
accompanying the CONNACK event.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 6038676)
Add support for PUBLISH message specified in MQTT 5.0. The message
encoder and decoder were updated to support MQTT properties.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 15ad90a)
Add support for PUBACK, PUBREC, PUBREL and PUBCOMP specified in MQTT
5.0. As all of these acknowledgment packets have similar format,
introduced a common encoder/decoder to handle ACK packets.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit c21e642)
Add support for SUBSCRIBE/UNSUBSCRIBE messages specified in MQTT 5.0.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit efd795b)
Add support for SUBACK/UNSUBACK messaged specified in MQTT 5.0.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 2459ffa)
Add support for DICONNECT message specified in MQTT 5.0.
As with MQTT 5.0, the disconnect can now also be initiated by the
broker, it was needed to add decoder support for the message.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 55e1c10)
Add support for a new AUTH message introduced in MQTT 5.0.
This is a new mechanism specified by MQTT 5.0, which allows clients and
brokers for enhanced authentication in between CONNECT and CONNACK
exchange. An additional MQTT event (MQTT_EVT_AUTH) was specified which
is triggered when the AUTH packet arrives from the broker.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 1d743fa)
Add support for handling topic aliases received from the broker.
The MQTT client implementation will store received topic for further use
in case consecutive PUBLISH received from the broker contains no topic
but alias only.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit e9da3b3)
…QTT 5.0

As MQTT 5.0 allows to specify the disconnect reason in the Disconnect
packet, use this new feature to improve error notification to the
broker, according to the error guidelines in the MQTT 5.0 spec.
For most cases, a generic arbitrary mapping between errno values and
reason codes is used, however the parser can specify the disconnect
reason code manually to better handle certain corner cases (like invalid
topic alias used).

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 8935579)
…tests

Add new test suite covering MQTT 5.0 packet format.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit 347653e)
…ntation

Make sure conditionally compiled parts of the public header related to
MQTT 5.0 support are rendered by doxygen.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit f9b4e27)
MQTT 5.0 is now supported so reflect this in the library documentation.

Signed-off-by: Robert Lubos <[email protected]>
(cherry picked from commit e380473)
…ompile errors

Upstream PR #: 87741

Add some extra ifdefs around MQTT 5.0 specific structures to prevent
compiler errors due to undefined symbols in certain configurations.

Signed-off-by: Robert Lubos <[email protected]>
This commit provides an extension to the i2c_nrfx_twim driver.
It introduces possibility to acquire/release exclusive access to the
i2c bus. While the exclusive access to the i2c bus is acquired
you can access the underlying nrfx_twim driver directly.

Signed-off-by: Andrzej Kuros <[email protected]>
(cherry picked from commit d15c9fe)
PavelVPV and others added 2 commits March 31, 2025 15:40
This is needed for privacy tests. Specifically, this fixes
GAP/PRIV/CONN/BV-10-C and GAP/CONN/UCON/BV-06-C on nRF54H20.

Signed-off-by: Pavel Vasilyev <[email protected]>
…text

This commit adds the possibility to add additional custom
context for flash operations for usage by non-standard
flash drivers.

Signed-off-by: Artur Hadasz <[email protected]>
(cherry picked from commit 38b959e)
@ahasztag ahasztag force-pushed the feat/soc_flash_nrf_custom_context branch from 3caf008 to 39e6a6c Compare April 1, 2025 05:54
@sonarqubecloud
Copy link

sonarqubecloud bot commented Apr 1, 2025

@ahasztag ahasztag changed the title [nrf fromlist] drivers: flash: nrf: Add possibility to add custom con… [nrf fromtree] drivers: flash: nrf: Add possibility to add custom con… Apr 1, 2025
@ahasztag
Copy link
Contributor Author

No longer needed, changes have arrived from upstream

@ahasztag ahasztag closed this May 27, 2025
@ahasztag ahasztag deleted the feat/soc_flash_nrf_custom_context branch September 18, 2025 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet