Add release notes for SDHC and Disk drivers, highlighting addition
of NVME support in the disk driver layer as well as CPOL/CPHA clock
modes within the SDHC SPI driver.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
Added RP2040 related changes to the v3.4.0 release notes,
including new boards, new drivers and HAL changes.
Signed-off-by: Yonatan Schachter <yonatan.schachter@gmail.com>
Add release notes on:
- change in west sign internal logic;
- additional LittleFS sample configuration for nrf52840dk_nrf52840
using SPI communication;
Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
Add points related to the POSIX arch and boards to the
3.4 release notes.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
In order to have clean, self-contained HCI headers that do not have any
dependencies towards the Host or any other part of the system (except
types), reorganize the headers in the following way:
- Split out the macros and structs from hci.h to a new hci_types.h
- Merge the existing hci_err.h into the new hci_types.h
Fixes#58214.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
This option is relevant enough to appear in the release notes, since it
is helpful to ease the debugging of a frequent issue.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
TF-M changes are documented in another section of the document, this is
likely a merge mistake.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Change order of buttons and switches on the nRF9160DK IO expander to
match the configuration without the IO expander.
Follow-up to commit d565aa2.
Signed-off-by: Eivind Jølsgard <eivind.jolsgard@nordicsemi.no>
Enable the external_flash_pins_routing switch in the board controller
overlay for nRF9160 DK revision 0.14.0 and newer. This is to match the
behaviour of the factory shipped borad controller on board revisions
that have external flash.
Signed-off-by: Gregers Gram Rygg <gregers.gram.rygg@nordicsemi.no>
Change the default revision of the nRF9160 DK to 0.14.0 to make it
easier to use external flash.
Signed-off-by: Gregers Gram Rygg <gregers.gram.rygg@nordicsemi.no>
Some 3P logic (Pigweed for example) is already heavily invested in
gTest as a testing framework. Adding the `gtest` harness enables
running the existing 3P tests on various Zephyr platforms and configs.
Signed-off-by: Yuval Peress <peress@google.com>
Update release notes 3.4 with description of
EXTRA_CONF_FILE, EXTRA_DTC_OVERLAY_FILE, and EXTRA_ZEPHYR_MODULES.
Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
If an operational amplifier is used on the DAC output it is
preferrable to disable the DAC output buffer.
Signed-off-by: Benedikt Schmidt <benedikt.schmidt@embedded-solutions.at>
After the MCUboot configuration options were moved out of the main
Kconfig.zephyr they were placed in a new Kconfig.mcuboot in the root of
the repo. This is not right, and the file belongs in the modules/
folder.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Adds a note that transports now need to set up the struct
themselves prior to calling the registration function.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Provide an extra struct net_if * iface parameter to
net_if_ipv*_maddr_join/leave functions, so that the corresponding
interface context, the mcast address belong to, can be locked for the
operation.
Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
Most available AT45 flash chips have their first two sectors shorter
than the consecutive ones. Usually, the first sector is marked as 0a
and has its size equal to eight pages (one block) and the second one
(usually 0b) is the complement to the size of a regular sector.
This commits modifies the driver so that erasing of these first two
sectors is performed correctly. This modified behavior is configurable
with a new DT property so that it is still possible to also use legacy
AT45 chips that do not feature such sector split. Such legacy chips
usually also do not support the chip erase and sector erase commands,
so two more DT properties are introduced to cover that.
Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
Add the ability for the flash simulator to store its contents in a
memory region.
This allows filesystems on the flash simulator to survive a reboot.
And allows subsystems (e.g. coredump) to store their info on ram while
using the (existing) flash partition backend.
Add a example (for nucleo_f411re) that shows how to configure the flash
simulator for hardware (cfg discussion #54166).
Signed-off-by: Laczen JMS <laczenjms@gmail.com>
Adds a note that *_ROOT variables are now supported properly on an
image basis when using sysbuild, and that sysbuild_cache_set has
been added, and that zephyr_get has had a MERGE option added.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Update 3.4 release notes to bring awareness to the
shifted values of voltage-ref and power-level
properties of the LPADC node
Signed-off-by: Declan Snyder <declan.snyder@nxp.com>
Inform about the cs field change in struct spi_config. Also mention what
drivers must use from now on.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Adds details on the newly introduced retention subsystem and boot
mode APIs to the release notes.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds a note that the old behaviour of setting the GPREGRET register
to the parameter of sys_reboot() is no longer the default as the
boot mode interface has replaced it.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
The test suite was limited to the native_posix board,
now it is built and run for any board supported by CI.
The native_posix yaml files for both 32 and 64 bit
boards have been expanded to support rtc, allowing CI
to build and test the rtc_api test suite against the
native_posix and native_posix_64 boards.
Signed-off-by: Bjarki Arge Andreasen <baa@trackunit.com>
Updates the release notes to document which absolute symbols
(generated via GEN_ABSOLUTE_SYM) have been removed.
Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>
Among other things, this update brings:
* C++ improvements
* float16 support
* Improved docs
* -Wall and -Wconversion compliance
Signed-off-by: Øyvind Rønningstad <oyvind.ronningstad@nordicsemi.no>
Normally, the driver deactivates the QSPI peripheral for periods when
no QSPI operation is performed. This is done to avoid increased current
consumption when the peripheral is idle. For the same reason, the base
clock on nRF53 Series SoCs (HFCLK192M) is configured for those periods
with the default /4 divider that cannot be used otherwise. However,
when XIP accesses are used, the driver must be prevented from doing
both these things as that would make XIP to fail. Hence, a function
is provided so that applications can inform the driver that XIP is
needed and the above idle actions should be suppressed.
This function (`nrf_qspi_nor_xip_enable()`) replaces the old one
(`nrf_qspi_nor_base_clock_div_force()`) that was intended for similar
purpose but after deactivation of the peripheral was introduced in
commit 95d867e8ed it became useless.
Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
Add a paragraph explaining the change from void main(void) to int
main(void) and the requirement for main functions to return zero.
Signed-off-by: Keith Packard <keithp@keithp.com>
Adds a note that the system timer stop function has now been
implemented for the nRF RTC timer driver.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Update the policy such that every completed sqe has a parallel cqe.
This has the primary purpose of making any reads in the sqe visible
to the consumer (since they might have different buffers).
Signed-off-by: Yuval Peress <peress@google.com>
Adds details on the update fs_mgmt features for faster
uploads/downloads and new Kconfig entries added.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Add note highlighting change to LPADC channel selection setup, so that
users will be aware they need to change their devicetree configuration
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
Some systems can support only legacy OOB pairing while others only
LE SC OOB pairing.
The existent API function "bt_set_oob_data_flag" was removed.
Two new API functions were added:
* "bt_le_oob_set_legacy_flag" to signal that legacy OOB pairing is used
* "bt_le_oob_set_sc_flag" to signal that LE SC OOB pairing is used
The code will now advertise the presence of OOB flag depending
on the type of pairing method(SC vs legacy)
Signed-off-by: Sebastian Panceac <sebastian.panceac@ext.grandcentrix.net>
In order to take granular input use micro seconds as input for TWT
intervals, this helps us in providing inputs such as 65.28ms without the
need of using floating points.
This also expands the TWT wake interval range to 262.144ms, earlier as
we want to use uint8, limited to 256ms.
Also, remove the units from the variable names, this is unnecessary and
also avoids doing breaking changes.
Update release notes as this is a breaking change, both type and
variable names are changed.
Signed-off-by: Krishna T <krishna.t@nordicsemi.no>
Updates the release notes to document a clarification to the sensor
driver API on sensor triggers.
Signed-off-by: Maureen Helm <maureen.helm@intel.com>
Adds a note that images are now bootable when built using sysbuild
with mcuboot in checksum only mode.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds a note on a fixed issue whereby the latest Zephyr SDK
toolchain was not used depending upon hash values in the cmake
registry.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds a note that FLASH_MAP and STREAM_FLASH now also need to be
selected to be able to enable the mcuboot image manager Kconfig
option, to avoid a cmake dependency loop, and Kconfigs required
for other mgmt subsystems.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Create and use a new `zephyr,i2c-target-eeprom` compatible
within I2C eeprom target driver that allows to use
that driver along with real atmel at24 EEPROM simultaneously.
Signed-off-by: Bartosz Bilas <b.bilas@grinn-global.com>
This commit removes the "Working Draft" status from the Zephyr 3.3.0
release notes.
Signed-off-by: Stephanos Ioannidis <stephanos.ioannidis@nordicsemi.no>
This content was mostly generated with a script, but there were some
manual changes and additions done to the output in some cases.
Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
Add release notes related to ADC and PWM drivers, Nordic HAL, and
boards featuring nRF SoCs. Nothing relevant to be added for I2S.
Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
Update for STM32 related changes during this release.
I focused on changes that could have impact for users.
Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
Added comments about new APIs, drivers, features, and bug fixes.
An impressive number of notes I have to say!
Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
Adds notes about bug fixes, features, and other noteworthy driver changes
made in the 3.3 release for i2c.
Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
Adds details on a bug for for the shell RX ring buffer receive
size being made larger when the shell MCUmgr transport is
selected, to fix an issue whereby commands were corrupt.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
More GigaDevice support added, include drivers, boards, etc.
Also, some known issue has been fixed.
Signed-off-by: HaiLong Yang <hailong.yang@brainco.cn>
Added comments about new drivers, bug fixes, and enhancements made to
sensor drivers since the last release.
Signed-off-by: Maureen Helm <maureen.helm@intel.com>
Adds a note that the nrf52840dongle_nrf52840 board has switched
from the default console being the unconnected UART to USB CDC.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Add disk driver release notes for 3.3. The following changes are
included:
- STM32 SDHC now uses device tree to configure clock settings.
- Flash disks are now configured via zephyr,flash-disk binding
- Flash disks support read only operation if flash partition is
read-only
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
Add release notes for SD host controller drivers for 3.3.
The following changes are highlighted:
- Added support for HS400 mode and HS200 mode in i.MX RT USDHC driver
- Added support for DMA operation on systems without NOCACHE memory
to i.MX RT USDHC driver
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
Update release notes for SD subsystem. The following changes are present:
- SD subsystem now supports eMMC
- SD cards that support only high speed mode now use 4 bit bus width
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
allow disabling reports (synchronise but don't generate sync reports)
and allows enabling sync reporting with filtering of duplicates.
the default option remains to establish sync, with sync reports,
but without duplicate filtering.
Signed-off-by: Raphael Treccani-Chinelli <raphael.treccani@nordicsemi.no>
Adds a note that python command line argument abbreviations have
been disabled, are no longer allowed in future and instructions of
how to update out-of-tree scripts that used abbreviated arguments.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds details for new logging added to MCUmgr and Kconfig options to
control the level of reporting.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Add option to disable CRC for fcb entries. This improves the write
throughput significantly at the cost of not detecting corrupted data
in flash. This is beneficial for aplications that needs the extra
write throughput, where error detection is done elsewhere.
Allow the FCB entries in flash to have a valid CRC when CRC is
disabled in the FCB. This allows existing solutions to disable
CRC checking, while keeping the CRC areas intact. Note that this
is a one-way option.
Fixes#53707
Signed-off-by: Eivind Jølsgard <eivind.jolsgard@nordicsemi.no>
Update usage of zephyr_code_relocate to new API, and add examples of
relocating a library target, as well as using multiple files in list or
CMake generator expressions.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
This commit adds the release notes related to the C++ subsystem-to-
library refactoring.
Signed-off-by: Stephanos Ioannidis <stephanos.ioannidis@nordicsemi.no>
Adds information on renaming of MCUmgr Kconfig options
and migration script that can be used to help with transition.
Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
This Kconfig is moved to the soc level since it determines
the flexspi clock initialization for XIP.
Signed-off-by: Emilio Benavente <emilio.benavente@nxp.com>
Adds a note on MCUmgr Bluetooth and UDP transports now being
automatically registered without needing an application to
manually register them.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds a note on MCUmgr handlers now being automatically called
without needing an application to manually register them.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds a note on rc responses to mcumgr commands where the status is
good that these responses will henceforth be emitted.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
There is already CONFIG_SETTINGS_FILE_PATH, which is set to full file path,
while CONFIG_SETTINGS_FILE_DIR is required to be set to its parent
directory. This is redundant, as parent directory path can be easily found
out either during runtime or optionally during buildtime by CMake.
CONFIG_SETTINGS_FILE_DIR was actually introduced recently after Zephyr 3.2
release as a replacement of deprecated CONFIG_SETTINGS_FS_DIR. This means,
that there is no need to deprecate it for 3.3 release and dropping it
should be fine. Adjust 3.3 release notes accordingly, so that
CONFIG_SETTINGS_FILE_PATH will be used directly.
This patch stops using deprecated CONFIG_SETTINGS_FS_DIR. There is actually
no value in respecting it, as setting anything other than parent directory
of CONFIG_SETTINGS_FS_FILE makes no sense.
There is actually one use of CONFIG_SETTINGS_FILE_DIR in file backend
tests, to derive directory for files containing tested settings.
CONFIG_SETTINGS_FILE_PATH is not used there, so it makes little sense to
derive directory name from it. Instead, just use hardcoded "/settings"
subdirectory, as this was the default value of CONFIG_SETTINGS_FILE_DIR.
Deriving parent directory can be done either in runtime or in
buildtime (e.g. using some helper CMake function). Doing it in runtime
however allows to create directory recursively (which this patch actually
implements), e.g. for some more nested FS tree structure. Additionally it
will simplify migration of settings configuration from Kconfig to
device-tree (yet to be developed feature).
Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>
There is little reason to panic on settings backend initialization error.
Such behavior was introduced with initial settings subsystem support, which
was adapted from MyNewt. This is not the usual way how Zephyr handles
errors, so it is time to change that.
There is already handling of some errors by simply returning / propagating
them to caller. Rework all the paths that resulted in k_panic() to also
return error codes.
Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>
The `bluetooth/common/log.h` and `bluetooth/common/log.c` files have been
removed. Files that were using them have been updated to use
`zephyr/logging/log.h` instead.
Those replacement have been done consequently:
- `/BT_DBG/LOG_DBG/`
- `/BT_ERR/LOG_ERR/`
- `/BT_WARN/LOG_WRN/`
- `/BT_INFO/LOG_INF/`
- `/BT_HEXDUMP_DBG/LOG_HEXDUMP_DBG/`
- `/BT_DBG_OBJ_ID/LOG_DBG_OBJ_ID/`
Also, some files were relying on the `common/log.h` include to include
`zephyr/bluetooth/hci.h`, in those cases the include of `hci.h` has
been added.
For files that were including `common/log.h` but not using any logs,
the include has been removed and not replaced.
Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
These functions are no longer needed with the centralized framework for
scanning for available PCIe devices and discovering their BDF value
through it.
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Currently there is inconsistency in repository file names, APIs, Kconfig
options and documentation around file / file-system backend for settings
storage, as both "file" and "FS (file system)" are used. As an example,
there is `CONFIG_SETTINGS_FS` Kconfig option, but the file that implements
this settings backend is called `settings_file.c`. Another example are
names of static functions that implement settings storage API:
`settings_file_load()`, `settings_file_save()` and
`settings_fs_storage_get()`.
This backend is actually storing all settings in a single file, so it makes
sense to use "File" as the name of backend, instead of a more general
"FS" (which would make sense if several files would be used to store
settings).
Fix inconsistency in used wording in the tree and unify it to "settings
file backend". This naming is more precise to how the implementation looks.
It will also make it easier to grep through the codebase and analyze
existing code.
Deprecate settings_mount_fs_backend() function and all Kconfig options
starting with `CONFIG_SETTINGS_FS`.
Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>
Add the local advertising address to bt_le_ext_adv_get_info.
This may help with debugging, but is also needed to
properly support something like the BAP Broadcast Assistant.
Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
Document the stable API change in the net_pkt API along with the
expected action from the existing applications.
Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
Add property mxicy,mx25r-power-mode to jedec,spi-nor binding for
controlling low power/high performance mode on Macronix MX25R* Ultra Low
Power flash devices.
- "low-power" configures the flash in ultra low power mode.
- "high-performance" configures the flash in high performance mode.
Signed-off-by: Gregers Gram Rygg <gregers.gram.rygg@nordicsemi.no>
Adds details of the stable API change to mcumgr's callback system,
including a link to the migration guide.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Update release notes 3.3 with the different modifications brought
to the STM32 RTC counter including new functionality, deprecated
and removed Kconfig
Signed-off-by: Guillaume Gautier <guillaume.gautier-ext@st.com>
Adds a note on changes needed to applications to update them for
changes introduced into MCUmgr.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds a note on a fixed mcumgr img_mgmt bug whereby image data could
persist when it should not.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Setting the extended advertiser as default advertiser
to improve both preformence and reliability.
Signed-off-by: Ingar Kulbrandstad <ingar.kulbrandstad@nordicsemi.no>
Mention removal of flashdisk Kconfig options in favor of new
zephyr,flash-disk devicetree binding.
Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no>
When deleting a PA sync with bt_le_per_adv_sync_delete
Zephyr should call the `term` callback for the PA sync
as per the documentation for the callback.
This was not done in the case that the PA sync was
terminated by local request.
Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
Adds a note about a possible stack overflow with the smp_svr sample
application using the Bluetooth transport being fixed.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Brings a few quality-of-life improvements for Zephyr, notably:
- No more collision with ARRAY_SIZE()
- C++ improvements
Add entry in release notes.
Signed-off-by: Øyvind Rønningstad <oyvind.ronningstad@nordicsemi.no>
The commit adds note on deprecation of zephyr_ prefix in SMP API
used by SMP transports, that allow MCUMgr receive and process
SMP frames.
Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
We have been encountering timeout issues when erasing large flash
sections (before receiving an image via mcuboot) from this semaphore
take:
5af0fbc2e3/drivers/flash/soc_flash_nrf_ticker.c (L225-L233)
I think this is because this constant is based on the time taken to erase
the chip but doesn't take account of the fact it is being done by a
ticker. If I understand correctly the ticker is a timeshare mechanism
so the actual max erase time is some factor based on how much time is
given to the task by the ticker.
This multiplies the max timeout by 1.5
Signed-off-by: Kyle Cooke <cookekyle97@gmail.com>
Adds a note about a workaround for an issue with mcumgr whereby a
file write command is sent to the same UART used for logging.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Add the list of open issues after the last triage:
wget https://builds.zephyrproject.io/zephyr/bug-snapshot/zephyr-bugs-2022-09-30.pickle.xz
unxz zephyr-bugs-2022-09-30.pickle.xz
./scripts/dump_bugs_pickle.py zephyr-bugs-2022-09-30.pickle
Manually fixed few doc generation warnings.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Adding the list of closed bugs since v3.1.0:
./scripts/release/list_issues.py -o zephyrproject-rtos -r zephyr -s
2022-06-05 -f issues.txt
And some manual fixup to make doxygen happy.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
