zephyr/doc/releases/release-notes-3.7.rst
Henrik Brix Andersen 8dd03c63d6 doc: releases: release-notes: 3.7: support minimum suported CAN bitrates
Add release notes related to the added support for minimum supported CAN
transceiver/controller bitrates.

Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2024-03-12 10:43:36 +01:00

215 lines
3.4 KiB
ReStructuredText

:orphan:
.. _zephyr_3.7:
Zephyr 3.7.0 (Working Draft)
############################
We are pleased to announce the release of Zephyr version 3.7.0.
Major enhancements with this release include:
* A new, completely overhauled hardware model has been introduced. This changes
the way both SoCs and boards are named, defined and constructed in Zephyr.
Additional information can be found in the :ref:`board_porting_guide`.
An overview of the changes required or recommended when migrating your application from Zephyr
v3.6.0 to Zephyr v3.7.0 can be found in the separate :ref:`migration guide<migration_3.7>`.
The following sections provide detailed lists of changes by component.
Security Vulnerability Related
******************************
The following CVEs are addressed by this release:
More detailed information can be found in:
https://docs.zephyrproject.org/latest/security/vulnerabilities.html
Architectures
*************
* ARC
* ARM
* Xtensa
Bluetooth
*********
Boards & SoC Support
********************
* Added support for these SoC series:
* Made these changes in other SoC series:
* Added support for these ARM boards:
* Added support for these Xtensa boards:
* Made these changes for ARM boards:
* Made these changes for RISC-V boards:
* Made these changes for native/POSIX boards:
* Added support for these following shields:
Build system and Infrastructure
*******************************
Drivers and Sensors
*******************
* ADC
* Auxiliary Display
* Audio
* Battery backed up RAM
* CAN
* Deprecated the :c:func:`can_calc_prescaler` API function, as it allows for bitrate
errors. Bitrate errors between nodes on the same network leads to them drifting apart after the
start-of-frame (SOF) synchronization has taken place, leading to bus errors.
* Extended support for automatic sample point location to also cover :c:func:`can_calc_timing` and
:c:func:`can_calc_timing_data`.
* Added optional ``min-bitrate`` devicetree property for CAN transceivers.
* Added devicetree macros :c:macro:`DT_CAN_TRANSCEIVER_MIN_BITRATE` and
:c:macro:`DT_INST_CAN_TRANSCEIVER_MIN_BITRATE` for getting the minimum supported bitrate of a CAN
transceiver.
* Added support for specifying the minimum bitrate supported by a CAN controller in the internal
``CAN_DT_DRIVER_CONFIG_GET`` and ``CAN_DT_DRIVER_CONFIG_INST_GET`` macros.
* Added a new CAN controller API function :c:func:`can_get_min_bitrate` for getting the minimum
supported bitrate of a CAN controller/transceiver combination.
* Updated the CAN timing functions to take the minimum supported bitrate into consideration when
validating the bitrate.
* Clock control
* Counter
* Crypto
* Display
* DMA
* Entropy
* Ethernet
* Flash
* GNSS
* GPIO
* I2C
* I2S
* I3C
* IEEE 802.15.4
* Input
* MDIO
* MFD
* PCIE
* MEMC
* MIPI-DBI
* Pin control
* PWM
* Regulators
* Retained memory
* RTC
* SMBUS:
* SDHC
* Sensor
* Serial
* SPI
* USB
* W1
* Wi-Fi
Networking
**********
* LwM2M:
* Added new API function:
* :c:func:`lwm2m_set_bulk`
USB
***
Devicetree
**********
Libraries / Subsystems
**********************
* Management
* Logging
* Modem modules
* Picolibc
* Power management
* Crypto
* Retention
* SD
* Storage
* POSIX API
* LoRa/LoRaWAN
* ZBus
HALs
****
* STM32
MCUboot
*******
zcbor
*****
LVGL
****
Tests and Samples
*****************