Split (1)

train · 2.03M rows

text stringlengths 9 39.2M	dir stringlengths 25 226	lang stringclasses 163 values	created_date timestamp[s]	updated_date timestamp[s]	repo_name stringclasses 751 values	repo_full_name stringclasses 752 values	star int64 1.01k 183k	len_tokens int64 1 18.5M
```restructuredtext :orphan: .. _zephyr_2.7: Zephyr 2.7.0 ############ We are pleased to announce the release of Zephyr RTOS version 2.7.0 (LTS2). Major enhancements since v2.6.0 include: * Bluetooth Audio, Direction Finding, and Mesh improvements * Support for Bluetooth Advertisement PDU Chaining * Added support for armclang / armlinker toolchain * Added support for MWDT C / C++ toolchain * Update to CMSIS v5.8.0 (Core v5.5.0, DSP v1.9.0) * Support for M-Profile Vector Extensions (MVE) on ARMv8.1-M * Improved thread safety for Newlib and C++ on SMP-capable systems * IEEE 802.15.4 Software Address Filtering * New Action-based Power Management API * USB Device Framework now includes all Chapter 9 defines and structures * Generic System Controller (``syscon``) driver and emulator * Linker Support for Tightly-Coupled Memory in RISC-V * Additional Blocking API calls for LoRa * Support for extended PCI / PCIe capabilities, improved MIS-X support * Added Support for Service Type Enumeration (STE) with mDNS / DNS Service Discovery * Added Zephyr Thread Awareness for OpenOCD to West * EEPROM now can be emulated in flash * Added both Ethernet MDIO and Ethernet generic PHY drivers Additional Major enhancements since v1.14.0 (LTS1) include: * The kernel now supports both 32- and 64-bit architectures * We added support for SOCKS5 proxy * Introduced support for 6LoCAN, a 6Lo adaption layer for Controller Area Networks * We added support for Point-to-Point Protocol (PPP) * We added support for UpdateHub, an end-to-end solution for over-the-air device updates * We added support for ARM Cortex-R Architecture * Normalized APIs across all architectures * Expanded support for ARMv6-M architecture * Added support for numerous new boards and shields * Added numerous new drivers and sensors * Added BLE support on Vega platform * Memory size improvements to Bluetooth host stack * We added initial support for 64-bit ARMv8-A architecture * CANopen protocol support through 3rd party CANopenNode stack * LoRa support was added along with the SX1276 LoRa modem driver * A new Zephyr CMake package has been introduced * A new Devicetree API which provides access to virtually all DT nodes and properties * The kernel timeout API has been overhauled * A new k_heap/sys_heap allocator, with improved performance * Zephyr now integrates with the TF-M (Trusted Firmware M) PSA-compliant framework * The Bluetooth Low Energy Host now supports LE Advertising Extensions * The CMSIS-DSP library is now included and integrated * Introduced initial support for virtual memory management * Added Bluetooth host support for periodic advertisement and isochronous channels. * Added a new TCP stack which improves network protocol testability * Introduced a new toolchain abstraction with initial support for GCC and LLVM/Clang * Moved to using C99 integer types and deprecate Zephyr integer types * Introduced support for the SPARC architecture and the LEON implementation * Added Thread Local Storage (TLS) support * Added support for per thread runtime statistics * Added support for building with LLVM on X86 * Added new synchronization mechanisms using Condition Variables * Add support for demand paging, initial support on X86 * Logging subsystem overhauled * Added support for 64-bit ARCv3 * Split ARM32 and ARM64, ARM64 is now a top-level architecture * Added initial support for Arm v8.1-m and Cortex-M55 * Removed legacy TCP stack support which was deprecated in 2.4 * Tracing subsystem overhaul / added support for Percepio Tracealyzer * Device runtime power management (PM) completely overhauled * Automatic SPDX SBOM generation has been added to West * Added an example standalone Zephyr application 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: path_to_url * CVE-2021-3510: `Zephyr project bug tracker GHSA-289f-7mw3-2qf4 <path_to_url`_. Known issues ********** You can check all currently known issues by listing them using the GitHub interface and listing all issues with the `bug label <path_to_url`_. API Changes ********* Deprecated in this release * :c:macro:`DT_ENUM_TOKEN` and :c:macro:`DT_ENUM_UPPER_TOKEN`, were deprecated in favor of utilizing :c:macro:`DT_STRING_TOKEN` and :c:macro:`DT_STRING_UPPER_TOKEN` * :c:macro:`BT_CONN_ROLE_MASTER` and :c:macro:`BT_CONN_ROLE_SLAVE` have been deprecated in favor of :c:macro:`BT_CONN_ROLE_CENTRAL` and :c:macro:`BT_CONN_ROLE_PERIPHERAL` * :c:macro:`BT_LE_SCAN_OPT_FILTER_WHITELIST` has been deprecated in favor of :c:macro:`BT_LE_SCAN_OPT_FILTER_ACCEPT_LIST` * The following whitelist functions have been deprecated: :c:func:`bt_le_whitelist_add` :c:func:`bt_le_whitelist_rem` :c:func:`bt_le_whitelist_clear` in favor of :c:func:`bt_le_filter_accept_list_add` :c:func:`bt_le_filter_accept_list_remove` :c:func:`bt_le_filter_accept_list_clear` Modified in this release * The following Bluetooth macros and structures in :file:`hci.h` have been modified to align with the inclusive naming in the v5.3 specification: * ``BT_LE_FEAT_BIT_SLAVE_FEAT_REQ`` is now ``BT_LE_FEAT_BIT_PER_INIT_FEAT_XCHG`` * ``BT_LE_FEAT_BIT_CIS_MASTER`` is now ``BT_LE_FEAT_BIT_CIS_CENTRAL`` * ``BT_LE_FEAT_BIT_CIS_SLAVE`` is now ``BT_LE_FEAT_BIT_CIS_PERIPHERAL`` * ``BT_FEAT_LE_SLAVE_FEATURE_XCHG`` is now ``BT_FEAT_LE_PER_INIT_FEAT_XCHG`` * ``BT_FEAT_LE_CIS_MASTER`` is now ``BT_FEAT_LE_CIS_CENTRAL`` * ``BT_FEAT_LE_CIS_SLAVE`` is now ``BT_FEAT_LE_CIS_PERIPHERAL`` * ``BT_LE_STATES_SLAVE_CONN_ADV`` is now ``BT_LE_STATES_PER_CONN_ADV`` * ``BT_HCI_OP_LE_READ_WL_SIZE`` is now ``BT_HCI_OP_LE_READ_FAL_SIZE`` * ``bt_hci_rp_le_read_wl_size`` is now ``bt_hci_rp_le_read_fal_size`` * ``bt_hci_rp_le_read_wl_size::wl_size`` is now ``bt_hci_rp_le_read_fal_size::fal_size`` * ``BT_HCI_OP_LE_CLEAR_WL`` is now ``BT_HCI_OP_LE_CLEAR_FAL`` * ``BT_HCI_OP_LE_ADD_DEV_TO_WL`` is now ``BT_HCI_OP_LE_REM_DEV_FROM_FAL`` * ``bt_hci_cp_le_add_dev_to_wl`` is now ``bt_hci_cp_le_add_dev_to_fal`` * ``BT_HCI_OP_LE_REM_DEV_FROM_WL`` is now ``BT_HCI_OP_LE_REM_DEV_FROM_FAL`` * ``bt_hci_cp_le_rem_dev_from_wl`` is now ``bt_hci_cp_le_rem_dev_from_fal`` * ``BT_HCI_ROLE_MASTER`` is now ``BT_HCI_ROLE_CENTRAL`` * ``BT_HCI_ROLE_SLAVE`` is now ``BT_HCI_ROLE_PERIPHERAL`` * ``BT_EVT_MASK_CL_SLAVE_BC_RX`` is now ``BT_EVT_MASK_CL_PER_BC_RX`` * ``BT_EVT_MASK_CL_SLAVE_BC_TIMEOUT`` is now ``BT_EVT_MASK_CL_PER_BC_TIMEOUT`` * ``BT_EVT_MASK_SLAVE_PAGE_RSP_TIMEOUT`` is now ``BT_EVT_MASK_PER_PAGE_RSP_TIMEOUT`` * ``BT_EVT_MASK_CL_SLAVE_BC_CH_MAP_CHANGE`` is now ``BT_EVT_MASK_CL_PER_BC_CH_MAP_CHANGE`` * ``m_`` structure members are now ``c_`` * ``s_`` structure members are now ``p_`` * The ``CONFIG_BT_PERIPHERAL_PREF_SLAVE_LATENCY`` Kconfig option is now :kconfig:option:`CONFIG_BT_PERIPHERAL_PREF_LATENCY` * The ``CONFIG_BT_CTLR_SLAVE_FEAT_REQ_SUPPORT`` Kconfig option is now :kconfig:option:`CONFIG_BT_CTLR_PER_INIT_FEAT_XCHG_SUPPORT` * The ``CONFIG_BT_CTLR_SLAVE_FEAT_REQ`` Kconfig option is now :kconfig:option:`CONFIG_BT_CTLR_PER_INIT_FEAT_XCHG` Changes in this release ========================== Removed APIs in this release * Removed support for the deprecated ``DEVICE_INIT`` and ``DEVICE_AND_API_INIT`` macros. * Removed support for the deprecated ``BUILD_ASSERT_MSG`` macro. * Removed support for the deprecated ``GET_ARG1``, ``GET_ARG2`` and ``GET_ARGS_LESS_1`` macros. * Removed support for the deprecated Kconfig ``PRINTK64`` option. * Removed support for the deprecated ``bt_set_id_addr`` function. * Removed support for the Kconfig ``USB`` option. Option ``USB_DEVICE_STACK`` is sufficient to enable USB device support. * Removed ``CONFIG_OPENTHREAD_COPROCESSOR_SPINEL_ON_UART_ACM`` and ``CONFIG_OPENTHREAD_COPROCESSOR_SPINEL_ON_UART_DEV_NAME`` Kconfig options in favor of chosen node ``zephyr,ot-uart``. * Removed ``CONFIG_BT_UART_ON_DEV_NAME`` Kconfig option in favor of direct use of chosen node ``zephyr,bt-uart``. * Removed ``CONFIG_BT_MONITOR_ON_DEV_NAME`` Kconfig option in favor of direct use of chosen node ``zephyr,bt-mon-uart``. * Removed ``CONFIG_MODEM_GSM_UART_NAME`` Kconfig option in favor of direct use of chosen node ``zephyr,gsm-ppp``. * Removed ``CONFIG_UART_MCUMGR_ON_DEV_NAME`` Kconfig option in favor of direct use of chosen node ``zephyr,uart-mcumgr``. * Removed ``CONFIG_UART_CONSOLE_ON_DEV_NAME`` Kconfig option in favor of direct use of chosen node ``zephyr,console``. * Removed ``CONFIG_UART_SHELL_ON_DEV_NAME`` Kconfig option in favor of direct use of chosen node ``zephyr,shell-uart``. ============================ Stable API changes in this release ================================== * Bluetooth * Added :c:struct:`multiple` to the :c:struct:`bt_gatt_read_params` - this structure contains two members: ``handles``, which was moved from :c:struct:`bt_gatt_read_params`, and ``variable``. * Networking * Added IPv4 address support to the multicast group join/leave monitor. The address parameter passed to the callback function was therefore changed from ``in6_addr`` to ``net_addr`` type. Kernel **** Architectures *********** * ARC * Add SMP support to ARCv3 HS6x * Add MWDT C library support * Add basic C++ support with MWDT toolchain * Add MPUv3 and MPUv6 support * Remove dead PM code from ARC core interrupt controller driver * Add updating arc connect debug mask dynamically * ARM * AARCH32 * Updated CMSIS version to 5.8.0 * Added support for FPU in QEMU for Cortex-M, allowing to build and execute tests in CI with FPU and FPU_SHARING options enabled. * Added MPU support for Cortex-R * AARCH64 * RISC-V * Added support to RISC-V CPU devicetree compatible bindings * Added support to link with ITCM & DTCM sections * x86 Bluetooth ********* * Updated all APIs and internal implementation to be conformant with the new inclusive terminology in version 5.3 of the Bluetooth Core Specification * Audio * Added the Microphone Input Control Service and client. * Changed the connected isochronous API to use a group-based opaque struct * Split the configuration options into connected and broadcast groups * Added support for a new sent callback to be notified when an SDU has been transmitted * Direction Finding * Added configurability for conditional CTE RX support * Added support for CTE periodic advertising chain transmissions * Host * Added support for setting more than 251 bytes of advertising data * Added new callbacks on ATT MTU update * Added a new call to retrieve the handle of an advertising set * Fixed key overwrite algorithm when working with multiple connections * Added configuration support for GATT security re-establishment * Added support for writing a long device name * OTS: Added object name write capability * Mesh * Added return value for opcode callback * Added support for OOB Public Key in the provisionee role * Added a new API to manually store pending RPL entries * Added support for application access to mesh messages * Refactored the Mesh Model Extensions * Bluetooth LE split software Controller * Added support for advertising PDU chaining, implementing advertising trains for Direction Finding * Added support for adding or removing the ACAD field in Common Extended Header Format to support BIGInfo * Refactored the legacy, extended and periodic advertising time reservation slot calculations * Implemented CSA#2 in Extended Advertising and Broadcast ISO sub-events * Added support for Extended Active Scanning * Added support for advertising on the S2 and S8 coding schemes * Added support for the Periodic Advertising channel map update indication * HCI Driver * Removed all ``CONFIG_BT__ON_DEV_NAME`` Kconfig options, use Devicetree instead Boards & SoC Support ******************* * Added support for these SoC series: * Added STM32U5 basic SoC support * Removed support for these SoC series: * Made these changes in other SoC series: * Added Atmel SAM0 pinctrl support * Added Atmel SAM4L USBC device controller * Added Atmel GMAC support for MDIO driver * Added Atmel GMAC support to use generic PHY driver * Added Atmel SAM counter (TC) Driver * Added Atmel SAM DAC (DACC) driver * Enabled Atmel SAM ``clock-frequency`` support from devicetree * Free Atmel SAM TRACESWO pin when unused * Enabled Cypress PSoC-6 Cortex-M4 support * Added low power support to STM32L0, STM32G0 and STM32WL series * STM32: Enabled ART Flash accelerator by default when available (F2, F4, F7, H7, L5) * STM32: Added Kconfig option to enable STM32Cube asserts (CONFIG_USE_STM32_ASSERT) * NXP FRDM-K82F: Added arduino_i2c and arduino_spi aliases * NXP i.MX RT series: Added support for flash controller with XIP * NXP i.MX RT series: Added TRNG support * NXP i.MX RT1170: Added LPSPI driver support * NXP i.MX RT1170: Added ADC driver support * NXP i.MX RT1170: Enabled Segger RTT/SystemView * NXP i.MX RT1170: Added MCUX FlexCan support * NXP i.MX RT1064: Added watchdog driver support * NXP i.MX RT1064: Added DMA driver support * NXP i.MX RT600: Added arduino serial port * NXP i.MX RT600: Add mcuboot flash partitions * NXP i.MX RT600: Added counter support * NXP i.MX RT600: Added PWM support * NXP i.MX RT600: Added disk driver support * NXP i.MX RT600: Added USB driver support * NXP i.MX RT600: Added LPADC driver support * NXP i.MX RT600: Added CTimer Counter support * NXP KE1xF: Added SoC Power Management support * NXP LPC55s69: Added USB driver support * NXP LPC55s69: Added ctimer driver support * NXP LPC55s69: Added I2S driver support * Changes for ARC boards: * Implement 'run' command for SMP nSIM simulation board * Enable upstream verification on QEMU ARCv3 HS6x board (qemu_arc_hs6x) * Implement creg GPIO driver and add it to hsdk and em_starterkit boards * Changes for ARM boards: * Added SPI support on Arduino standard SPI when possible * Added support for these ARM boards: * Dragino NBSN95 NB-IoT Sensor Node * Seeedstudio LoRa-E5 Dev Board * ST B_U585I_IOT02A Discovery kit * ST Nucleo F446ZE * ST Nucleo U575ZI Q * ST STM32H735G Discovery * PJRC Teensy 4 Board * Added support for these ARM64 boards: * Removed support for these ARM boards: * Removed support for these X86 boards: * Made these changes in other boards: * arduino_due: Added support for TC driver * atsame54_xpro: Added support for PHY driver * sam4l_ek: Added support for TC driver * sam4e_xpro: Added support for PHY driver * sam4e_xpro: Added support for TC driver * sam4s_xplained: Added support for TC driver * sam_e70_xplained: Added support for DACC driver * sam_e70_xplained: Added support for PHY driver * sam_e70_xplained: Added support for TC driver * sam_v71_xult: Added support for DACC driver * sam_v71_xult: Added support for PHY driver * sam_v71_xult: Added support for TC driver * sam_v71_xult: Enable pwm on LED0 * cy8ckit_062_ble: Added arduino's nexus map * Added support for these following shields: * 4.2inch epaper display (GDEW042T2) * X-NUCLEO-EEPRMA2 EEPROM memory expansion board Drivers and Sensors ******************* * ADC * Added STM32WL ADC driver * STM32: Added support for oversampling * Added driver for Microchip MEC172x * Audio * Added DMIC driver for nRF PDM peripherals * Bluetooth * CAN * Renesas R-Car driver added * Clock Control * Console * Counter * Add Atmel SAM counter (TC) Driver * Added STM32WL RTC counter driver * Crypto * STM23: Add support for SOCs with AES hardware block (STM32G0, STM32L5 and STM32WL) * DAC * Added Atmel SAM DAC (DACC) driver * Added support for Microchip MCP4725 * Added support for STM32F3 series * Disk * Added SDMMC support on STM32L4+ * STM32 SDMMC now supports SDIO enabled devices * Added USDHC support for i.MX RT685 * Display * Added support for ST7735R * DMA * Added Atmel SAM XDMAC reload support * Added support on STM32F3, STM32G0, STM32H7 and STM32L5 * STM32: Reviewed bindings definitions, "st,stm32-dma-v2bis" introduced. * EEPROM * Added support for EEPROM emulated in flash. * Entropy * Added support for STM32F2, STM32G0, STM32WB and STM32WL * ESPI * Added support for Microchip eSPI SAF * Ethernet * Added Atmel SAM/SAM0 GMAC devicetree support * Added Atmel SAM/SAM0 MDIO driver * Added MDIO driver * Added generic PHY driver * Flash * Added STM32F2, STM32L5 and STM32WL Flash driver support * STM32: Max erase time parameter was moved to device tree * Added quad SPI support for STM32F4 * GPIO * Hardware Info * I2C * I2S * Added Atmel SAM I2S driver support to XDMAC reload * Added driver for nRF I2S peripherals * IEEE 802.15.4 * IPM * STM32: Add HSEM based IPM driver for STM32H7 series * Interrupt Controller * LED * LoRa * lora_send now blocks until the transmission is complete. lora_send_async can be used for the previous, non-blocking behaviour. * Enabled support for STM32WL series * MEMC * Added STM32F4 support * Modem * Added gsm_ppp devicetree support * PCI/PCIe * Fixed an issue that MSI-X was used even though it is not available. * Improved MBAR retrieval for MSI-X. * Added ability to retrieve extended PCI/PCIe capabilities. * Pinmux * Added Atmel SAM0 pinctrl support * STM32: Deprecated definitions like 'STM32F2_PINMUX_FUNC_PA0_UART4_TX' are now removed. * PWM * Property "st,prescaler" of binding "st,stm32-pwm" now defaults to "0". * Added driver for ITE IT8XXX2 series * Added driver for NXP LPC devices * Added driver for Telink B91 * Sensor * Refactored various drivers to use ``_dt_spec``. * Refactored various drivers to support multiple instances. * Enhanced TI HDC20XX driver to support DRDY/INT pin. * Updated temperature conversion formula in TI HDC20XX driver. * Enhanced MS5607 pressure sensor driver to support I2C. * Fixed temperature compensation in MS5607 pressure sensor driver. * Refactored ST LIS2DW12 driver to move range, power, and trigger configuration from Kconfig to dts. * Enhanced TI BQ274XX fuel gauge driver to support power management. * Aligned ST sensor drivers to use STMEMC HAL I/F v2.00. * Added Sensirion SGP40 multipixel gas sensor driver. * Added Sensirion SHTCX humidity sensor driver. * Added Sensirion SHT4X temperature and humidity sensor driver. * Added SiLabs SI7270 hall effect magnetic position and temperature sensor driver. * Added ST I3G4250D gyroscope driver. * Added TI INA219 and INA23X current/power monitor drivers. * Added TI LM75 and LM77 temperature sensor drivers. * Added TI HDC20XX humidity and temperature sensor driver. * Serial * Added kconfig to disable runtime re-configuration of UART to reduce footprint if so desired. * Added ESP32-C3 polling only UART driver. * Added ESP32-S2 polling only UART driver. * Added Microchip XEC UART driver. * SPI * Timer * USB * Added Atmel SAM4L USBC device controller driver * Added support for NXP LPC USB controller * Adapted drivers use new USB framework header * Watchdog * Added STM32L5 watchdog support * WiFi Networking ********** * 802.15.4 L2: * Fixed a bug, where the net_pkt structure contained invalid LL address pointers after being processed by 802.15.4 L2. * Added an optional destination address filtering in the 802.15.4 L2. * CoAP: * Added ``user_data`` field to the :c:struct:`coap_packet` structure. * Fixed processing of out-of-order notifications. * Fixed :c:func:`coap_packet_get_payload` function. * Converted CoAP test suite to ztest API. * Improved :c:func:`coap_packet_get_payload` function to minimize number of RNG calls. * Fixed retransmissions in the ``coap_server`` sample. * Fixed observer removal in the ``coap_server`` sample (on notification timeout). * DHCPv4: * Fixed a bug, where DHPCv4 library removed statically configured gateway before obtaining a new one from the server. * DNS: * Fixed a bug, where the same IP address was used to populate the result address info entries, when multiple IP addresses were obtained from the server. * DNS-SD: * Added Service Type Enumeration support (``_services._dns_sd._udp.local``) * HTTP: * Switched the library to use ``zsock_`` API, to improve compatibility with various POSIX configurations. Fixed a bug, where ``HTTP_DATA_FINAL`` notification was triggered even for intermediate response fragments. * IPv6: * Multiple IPv6 fixes, addressing failures in IPv6Ready compliance tests. * LwM2M: * Added support for notification timeout reporting to the application. * Fixed a bug, where a multi instance resource with only one active instance was incorrectly encoded on reads. * Fixed a bug, where notifications were generated on changes to non-readable resources. * Added mutex protection for the state variable of the ``lwm2m_rd_client`` module. * Removed LWM2M_RES_TYPE_U64 type, as it's not possible to encode it properly for large values. * Fixed a bug, where large unsigned integers were incorrectly encoded in TLV. * Multiple fixes for FLOAT type processing in the LwM2M engine and encoders. * Fix a bug, where IPSO Push Button counter resource was not triggering notification on incrementation. * Fixed a bug, where Register failures were reported as success to the application. * Misc: * Added RX/TX timeout on a socket in ``big_http_download`` sample. * Introduced :c:func:`net_pkt_remove_tail` function. Added IEEE 802.15.4 security-related flags to the :c:struct:`net_pkt` structure. * Added bridging support to the Ethernet L2. * Fixed a bug in mDNS, where an incorrect address type could be set as a response destination. * Added an option to suppress ICMP destination unreachable errors. * Fixed possible assertion in ``net nbr`` shell command. * Major refactoring of the TFTP library. * MQTT: * Added an option to register a custom transport type. * Fixed a bug in :c:func:`mqtt_abort`, where the function could return without releasing a lock. * OpenThread: * Update OpenThread module up to commit ``9ea34d1e2053b6b2a80e1d46b65a6aee99fc504a``. Added several new Kconfig options to align with new OpenThread configurations. * Added OpenThread API mutex protection during initialization. * Converted OpenThread thread to a dedicated work queue. * Implemented missing :c:func:`otPlatAssertFail` platform function. * Fixed a bug, where NONE level OpenThread logs were not processed. * Added possibility to disable CSL sampling, when used. * Fixed a potential bug, where invalid error code could be returned by the platform radio layer to OpenThread. * Reworked UART configuration in the OpenThread Coprocessor sample. * Socket: * Added microsecond accuracy in :c:func:`zsock_select` function. * Reworked :c:func:`zsock_select` into a syscall. * Fixed a bug, where :c:func:`poll` events were not signalled correctly for socketpair sockets. * Fixed a bug, where socket mutex could be used after being initialized by a new owner after being deallocated in :c:func:`zsock_close`. * Fixed a possible assert after enabling CAN sockets. * Fixed IPPROTO_RAW usage in packet socket implementation. * TCP: * Fixed a bug, where ``unacked_len`` could be set to a negative value. * Fixed possible assertion failure in :c:func:`tcp_send_data`. * Fixed a bug, where [FIN, PSH, ACK] was not handled properly in TCP_FIN_WAIT_2 state. * TLS: * Reworked TLS sockets to use secure random generator from Zephyr. * Fixed busy looping during DTLS handshake with offloaded sockets. * Fixed busy looping during TLS/DTLS handshake on non blocking sockets. * Reset mbed TLS session on timed out DTLS handshake, to allow a retry without closing a socket. * Fixed TLS/DTLS :c:func:`sendmsg` implementation for larger payloads. * Fixed TLS/DTLS sockets ``POLLHUP`` notification. * WebSocket: * Fixed :c:func:`poll` implementation for WebSocket, which did not work correctly with offloaded sockets. * Fixed :c:func:`ioctl` implementation for WebSocket, which did not work correctly with offloaded sockets. USB *** * Added new header file where all defines and structures from Chapter 9 (USB Device Framework) should be included. * Revised configuration of USB device support. Removed Kconfig option ``CONFIG_USB`` and introduced Kconfig option ``CONFIG_USB_DEVICE_DRIVER`` to enable USB device controller drivers, which is selected when option ``CONFIG_USB_DEVICE_STACK`` is enabled. * Enhanced verification of the control request in device stack, classes, and samples. * Added support to store alternate interface setting. * Added ``zephyr_udc0`` nodelabel to all boards with USB support to allow generic USB device support samples to be build. * Reworked descriptors, config, and data definitions macros in CDC ACM class. * Changed CDC ACM UART implementation to get configuration from devicetree. With this change, many ``CONFIG__ON_DEV_NAME`` options were removed and applications revised. See :ref:`usb_device_cdc_acm` for more information. Build and Infrastructure *********************** * Devicetree API * New "for-each" macros which work like existing APIs, but take variable numbers of arguments: :c:macro:`DT_FOREACH_CHILD_VARGS`, :c:macro:`DT_FOREACH_CHILD_STATUS_OKAY_VARGS`, :c:macro:`DT_FOREACH_PROP_ELEM_VARGS`, :c:macro:`DT_INST_FOREACH_CHILD_VARGS`, :c:macro:`DT_INST_FOREACH_STATUS_OKAY_VARGS`, :c:macro:`DT_INST_FOREACH_PROP_ELEM_VARGS` * Other new "for-each" macros: :c:macro:`DT_FOREACH_STATUS_OKAY`, :c:macro:`DT_FOREACH_STATUS_OKAY_VARGS` * New macros for converting strings to C tokens: :c:macro:`DT_STRING_TOKEN`, :c:macro:`DT_STRING_UPPER_TOKEN` * New :ref:`devicetree-pinctrl-api` helper macros * Devicetree tooling * Errors are now generated when invalid YAML files are discovered while searching for bindings. See :ref:`dt-where-bindings-are-located` for information on the search path. * File names ending in ``.yml`` are now considered YAML files when searching for bindings. * Errors are now generated if invalid node names are used. For example, the node name ``node?`` now generates an error message ending in ``node?: Bad character '?' in node name``. The valid node names are documented in "2.2.2 Node Names" of the Devicetree specification v0.3. * Warnings are now generated if a :ref:`compatible property <dt-important-props>` in the ``vendor,device`` format uses an unknown vendor prefix. This warning does not apply to the root node. Known vendor prefixes are defined in :file:`dts/bindings/vendor-prefixes.txt` files, which may appear in any directory in :ref:`DTS_ROOT <dts_root>`. These may be upgraded to errors using the edtlib Python APIs; Zephyr's CI now generates such errors. * Devicetree bindings * Various bindings had incorrect vendor prefixes in their :ref:`compatible <dt-important-props>` properties; the following changes were made to fix these. .. list-table:: :header-rows: 1 - * Old compatible * New compatible - * ``nios,i2c`` * :dtcompatible:`altr,nios2-i2c` - * ``cadence,tensilica-xtensa-lx4`` * :dtcompatible:`cdns,tensilica-xtensa-lx4` - * ``cadence,tensilica-xtensa-lx6`` * :dtcompatible:`cdns,tensilica-xtensa-lx6` - * ``colorway,lpd8803`` * :dtcompatible:`greeled,lpd8803` - * ``colorway,lpd8806`` * :dtcompatible:`greeled,lpd8806` - * ``grove,light`` * :dtcompatible:`seeed,grove-light` - * ``grove,temperature`` * :dtcompatible:`seeed,grove-temperature` - * ``max,max30101`` * :dtcompatible:`maxim,max30101` - * ``ublox,sara-r4`` * :dtcompatible:`u-blox,sara-r4` - * ``xtensa,core-intc`` * :dtcompatible:`cdns,xtensa-core-intc` - * ``vexriscv,intc0`` * :dtcompatible:`vexriscv-intc0` Out of tree users of these bindings will need to update their devicetrees. You can support multiple versions of Zephyr with one devicetree by including both the old and new values in your nodes' compatible properties, like this example for the LPD8803:: my-led-strip@0 { compatible = "colorway,lpd8803", "greeled,lpd8803"; ... }; * Other new bindings in alphabetical order: :dtcompatible:`andestech,atcgpio100`, :dtcompatible:`arm,gic-v3-its`, :dtcompatible:`atmel,sam0-gmac`, :dtcompatible:`atmel,sam0-pinctrl`, :dtcompatible:`atmel,sam-dac`, :dtcompatible:`atmel,sam-mdio`, :dtcompatible:`atmel,sam-usbc`, :dtcompatible:`cdns,tensilica-xtensa-lx7`, :dtcompatible:`espressif,esp32c3-uart`, :dtcompatible:`espressif,esp32-intc`, :dtcompatible:`espressif,esp32s2-uart`, :dtcompatible:`ethernet-phy`, :dtcompatible:`fcs,fxl6408`, :dtcompatible:`ilitek,ili9341`, :dtcompatible:`ite,it8xxx2-bbram`, :dtcompatible:`ite,it8xxx2-kscan`, :dtcompatible:`ite,it8xxx2-pinctrl-conf`, :dtcompatible:`ite,it8xxx2-pwm`, :dtcompatible:`ite,it8xxx2-pwmprs`, :dtcompatible:`ite,it8xxx2-watchdog`, :dtcompatible:`lm75`, :dtcompatible:`lm77`, :dtcompatible:`meas,ms5607`, :dtcompatible:`microchip,ksz8863`, :dtcompatible:`microchip,mcp7940n`, :dtcompatible:`microchip,xec-adc-v2`, :dtcompatible:`microchip,xec-ecia`, :dtcompatible:`microchip,xec-ecia-girq`, :dtcompatible:`microchip,xec-gpio-v2`, :dtcompatible:`microchip,xec-i2c-v2`, :dtcompatible:`microchip,xec-pcr`, :dtcompatible:`microchip,xec-uart`, :dtcompatible:`nuvoton,npcx-bbram`, :dtcompatible:`nuvoton,npcx-booter-variant`, :dtcompatible:`nuvoton,npcx-ps2-channel`, :dtcompatible:`nuvoton,npcx-ps2-ctrl`, :dtcompatible:`nuvoton,npcx-soc-id`, :dtcompatible:`nxp,imx-ccm-rev2`, :dtcompatible:`nxp,lpc-ctimer`, :dtcompatible:`nxp,lpc-uid`, :dtcompatible:`nxp,mcux-usbd`, :dtcompatible:`nxp,sctimer-pwm`, :dtcompatible:`ovti,ov2640`, :dtcompatible:`renesas,rcar-can`, :dtcompatible:`renesas,rcar-i2c`, :dtcompatible:`reserved-memory`, :dtcompatible:`riscv,sifive-e24`, :dtcompatible:`sensirion,sgp40`, :dtcompatible:`sensirion,sht4x`, :dtcompatible:`sensirion,shtcx`, :dtcompatible:`silabs,si7055`, :dtcompatible:`silabs,si7210`, :dtcompatible:`snps,creg-gpio`, :dtcompatible:`st,i3g4250d`, :dtcompatible:`st,stm32-aes`, :dtcompatible:`st,stm32-dma`, :dtcompatible:`st,stm32-dma-v2bis`, :dtcompatible:`st,stm32-hsem-mailbox`, :dtcompatible:`st,stm32-nv-flash`, :dtcompatible:`st,stm32-spi-subghz`, :dtcompatible:`st,stm32u5-flash-controller`, :dtcompatible:`st,stm32u5-msi-clock`, :dtcompatible:`st,stm32u5-pll-clock`, :dtcompatible:`st,stm32u5-rcc`, :dtcompatible:`st,stm32wl-hse-clock`, :dtcompatible:`st,stm32wl-subghz-radio`, :dtcompatible:`st,stmpe1600`, :dtcompatible:`syscon`, :dtcompatible:`telink,b91`, :dtcompatible:`telink,b91-flash-controller`, :dtcompatible:`telink,b91-gpio`, :dtcompatible:`telink,b91-i2c`, :dtcompatible:`telink,b91-pinmux`, :dtcompatible:`telink,b91-power`, :dtcompatible:`telink,b91-pwm`, :dtcompatible:`telink,b91-spi`, :dtcompatible:`telink,b91-trng`, :dtcompatible:`telink,b91-uart`, :dtcompatible:`telink,b91-zb`, :dtcompatible:`ti,hdc2010`, :dtcompatible:`ti,hdc2021`, :dtcompatible:`ti,hdc2022`, :dtcompatible:`ti,hdc2080`, :dtcompatible:`ti,hdc20xx`, :dtcompatible:`ti,ina219`, :dtcompatible:`ti,ina23x`, :dtcompatible:`ti,tca9538`, :dtcompatible:`ti,tca9546a`, :dtcompatible:`ti,tlc59108`, :dtcompatible:`xlnx,gem`, :dtcompatible:`zephyr,bbram-emul`, :dtcompatible:`zephyr,cdc-acm-uart`, :dtcompatible:`zephyr,gsm-ppp`, :dtcompatible:`zephyr,native-posix-udc` * West (extensions) * openocd runner: Zephyr thread awareness is now available in GDB by default for application builds with :kconfig:option:`CONFIG_DEBUG_THREAD_INFO` set to ``y`` in :ref:`kconfig`. This applies to ``west debug``, ``west debugserver``, and ``west attach``. OpenOCD version later than 0.11.0 must be installed on the host system. Libraries / Subsystems ********************** * Disk * Management * CMSIS subsystem * Power management * The APIs to set/clear/check if devices are busy from a power management perspective have been moved to the PM subsystem. Their naming and signature has also been adjusted to follow common conventions. Below you can find the equivalence list. * ``device_busy_set`` -> ``pm_device_busy_set`` * ``device_busy_clear`` -> ``pm_device_busy_clear`` * ``device_busy_check`` -> ``pm_device_is_busy`` * ``device_any_busy_check`` -> ``pm_device_is_any_busy`` * The device power management callback (``pm_device_control_callback_t``) has been largely simplified to work based on actions, resulting in simpler and more natural implementations. This principle is also used by other OSes like the Linux Kernel. As a result, the callback argument list has been reduced to the device instance and an action (e.g. ``PM_DEVICE_ACTION_RESUME``). Other improvements include specification of error codes, removal of some unused/unclear states, or guarantees such as avoid calling a device for suspend/resume if it is already at the right state. All these changes together have allowed simplifying multiple device power management callback implementations. * Introduced a new API to allow devices capable of wake up the system register themselves was wake up sources. This permits applications to select the most appropriate way to wake up the system when it is suspended. Devices marked as wake up source are not suspended by the kernel when the system is idle. It is possible to declare a device wake up capable direct in devicetree like this example:: &gpio0 { compatible = "zephyr,gpio-emul"; gpio-controller; wakeup-source; }; * Removed ``PM_DEVICE_STATE_FORCE_SUSPEND`` device power state.because it is an action and not a state. * Removed ``PM_DEVICE_STATE_RESUMING`` and ``PM_DEVICE_STATE_SUSPENDING``. They were transitional states and only used in device runtime. Now the subsystem is using device flag to keep track of a transition. * Implement constraint API as weak symbols so applications or platform can override them. Platforms can have their own way to set/release constraints in their drivers that are not part of Zephyr code base. * Logging * MODBUS * Changed server handler to copy Transaction and Protocol Identifiers to response header. * Random * xoroshiro128+ PRNG deprecated in favor of xoshiro128++ * Shell * Storage * Task Watchdog * Tracing * Debug * OS HALs **** * HALs are now moved out of the main tree as external modules and reside in their own standalone repositories. Trusted Firmware-m ****************** * Renamed psa_level_1 sample to psa_crypto. Extended the use of the PSA Cryptography 1.0 API in the sample code to demonstrate additional crypto functionality. * Added a new sample to showcase the PSA Protecter Storage service. Documentation ************* * Kconfig options need to be referenced using the ``:kconfig:option:`` Sphinx role. Previous to this change, ``:option:`` was used for this purpose. * Doxygen alias ``@config{}`` has been deprecated in favor of ``@kconfig{}``. Tests and Samples *************** Issue Related Items ***************** These GitHub issues were addressed since the previous 2.6.0 tagged release: * :github:`39443` - Be more inclusive * :github:`39419` - STM32WL55 not found st/wl/stm32wl55jcix-pinctrl.dtsi * :github:`39413` - warnings when using newlibc and threads * :github:`39409` - runners: canopen: program download fails with slow flash access and/or congested CAN nets * :github:`39389` - http_get, big_http_download samples fails to build * :github:`39388` - GSM Modem sample fails to build * :github:`39378` - Garbage IQ Data Reports are generated if some check in hci_df_prepare_connectionless_iq_report fails * :github:`39294` - noticing stm32 clock domain naming changes * :github:`39291` - Bluetooth: Periodic advertising * :github:`39284` - mdns + dns_sd: fix regression that breaks ptr queries * :github:`39281` - Undefined references to k_thread_abort related tracing routines * :github:`39270` - example-application CI build fails * :github:`39263` - Bluetooth: controller: DF: wrong handling of max_cte_count * :github:`39260` - [backport v2.7-branch] backport of #38292 failed * :github:`39240` - ARC Kconfig allows so select IRQ configuration which isn't supported in SW * :github:`39206` - lwm2m: send_attempts field does not seem to be used? * :github:`39205` - drivers: wifi: esp_at: cannot connect to open (unsecure) WiFi networks * :github:`39195` - USB: netusb: example echo_server not working as expected * :github:`39190` - tests/subsys/logging/log_core_additional/logging.add.log2 fails * :github:`39188` - tests/bluetooth/mesh/bluetooth.mesh.ext_adv fails * :github:`39185` - tests/subsys/logging/log_core_additional/logging.add.user fails on several platforms * :github:`39180` - samples/subsys/mgmt/osdp/peripheral_device & samples/subsys/mgmt/osdp/control_panel fail to build * :github:`39170` - Can not run correctly on NXP MIMXRT1061 CVL5A. * :github:`39135` - samples/compression/lz4 build failed (lz4.h: No such file or directory) * :github:`39132` - subsys/net/ip/tcp2: Missing feature to decrease Receive Window size sent in the ACK messge * :github:`39123` - ztest: Broken on NRF52840 Platform * :github:`39115` - sensor: fdc2x1x: warnings and compilation errors when PM_DEVICE is used * :github:`39086` - CMake warning during build - depracated roule CMP0079 * :github:`39085` - Ordering of device_map() breaks PCIe config space mapping on ARM64 * :github:`39075` - IPv6 address not set on loopback interface * :github:`39051` - Zephyr was unable to find the toolchain. Is the environment misconfigured? * :github:`39036` - Multicast packet forwarding not working for the coap_server sample and Openthread * :github:`39022` - [backport v2.7-branch] backport of #38834 failed * :github:`39011` - Bluetooth: Mesh: Model extensions walk stops before last model * :github:`39009` - Nordic PWM causing lock up due to infinte loop * :github:`39008` - tests: logging.add.user: build failure on STM32H7 targets * :github:`38999` - [backport v2.7-branch] backport of #38407 failed * :github:`38996` - There is no way to leave a ipv6 multicast group * :github:`38994` - ARP: Replies are sent to multicast MAC address rather than senders MAC address. * :github:`38970` - LWM2M Client Sample with DTLS enabled fail to connect * :github:`38966` - Please add STM32F412VX * :github:`38961` - tests: kernel: sched: schedule_api: instable on disco_l475_iot1 * :github:`38959` - ITE RISCV I2C driver returning positive values for error instead of negative values * :github:`38943` - west: update hal_espressif failure * :github:`38938` - Bluetooth tester application should be able return L2CAP ECFC credits on demand * :github:`38930` - Low Power mode not functional on nucleo_l073rz * :github:`38924` - twister: cmake: Misleading error in Twister when sdk-zephyr 0.13.1 not used * :github:`38904` - [backport v2.7-branch] backport of #38860 failed * :github:`38902` - i2c_nrfx_twim: Error 0x0BAE0002 if sensor is set in trigger mode and reset with nrf device * :github:`38899` - There is no valid date setting function in the RTC driver of the LL Library of STM32 * :github:`38893` - g0b1re + spi_flash_at45 + flash_shell: First write always fails with ``CONFIG_PM_DEVICE`` * :github:`38886` - devicetree/memory.h probably should not exist as-is * :github:`38877` - Running the zephyr elf natively on an arm a53 machine (ThunderX2) with KVM emulation * :github:`38870` - stm32f1: Button callback not fired * :github:`38853` - Bluetooth: host: bt_unpair failed because function [bt_conn_set_state] wont work as expected * :github:`38849` - drivers: i2c: nrf: i2c error with burst write * :github:`38829` - net_buf issue leads to unwanted elem free * :github:`38826` - tests/lib/cmsis_dsp: malloc failed on 128K SRAM targets * :github:`38818` - driver display display_st7789v.c build error * :github:`38815` - kernel/mem_domain: Remove dead case in check_add_partition() * :github:`38807` - stm32: Missing header in power.c files * :github:`38804` - tests\kernel\threads\thread_stack test fail with ARC * :github:`38799` - BLE central_ht only receives 7 notifications * :github:`38796` - Failure building the zephyr\tests\subsys\cpp\libcxx project * :github:`38791` - Example code_relocation not compiling. * :github:`38790` - SD FatFS Sample Build Failure * :github:`38784` - stm32: pm: Debug mode not functional on G0 * :github:`38782` - CONFIG_BT_CTLR_DATA_LENGTH_MAX=250 causes pairing compatibility issues with many devices * :github:`38769` - mqtt: the size of a mqtt payload is limited * :github:`38765` - samples: create an OLED example * :github:`38764` - CBPRINTF_FP_SUPPORT does not work after NEWLIB_LIBC enabled * :github:`38761` - Does zephyr_library_property defines -DTRUE in command-line? * :github:`38756` - Twister: missing testcases with error in report * :github:`38745` - Bluetooth when configured for extended advertising does not limit advertisement packet size if a non-extended avertisement is used * :github:`38737` - drivers: syscon: missing implementation * :github:`38735` - nucleo_wb55rg: Flash space left to M0 binary is not sufficient anymore * :github:`38731` - test-ci: ptp_clock_test : test failure on frdm_k64f platform * :github:`38727` - [RFC] Add hal_gigadevice to support GigaDevice SoC Vendor * :github:`38716` - modem: HL7800: does not work with IPv6 * :github:`38702` - Coap server not properly removing observers * :github:`38701` - Observable resource of coap server seems to not support a restart of an observer * :github:`38700` - Observable resource of coap server seems to not support 2 observers simultaneously * :github:`38698` - stm32f4_disco: Socket CAN sample not working * :github:`38697` - The coap_server sample is missing the actual send in the retransmit routine * :github:`38694` - Disabling NET_CONFIG_AUTO_INIT does not require calling net_config_init() manually in application as mentioned in Zephyr Network Configuration Library documentation * :github:`38692` - samples/tfm_integration: Compilation fails ("unexpected keyword argument 'rom_fixed'") * :github:`38691` - MPU fault with mcumgr bluetooth FOTA started whilst existing FOTA is in progress * :github:`38690` - Wrong initialisation priority on different display drivers (eg. ST7735r) cause exception when using lvgl. * :github:`38688` - bt_gatt_unsubscribe does not remove subscription from internal list/returning BT_GATT_ITER_STOP causes bt_gatt_subscribe to return -ENOMEM / -12 * :github:`38675` - DTS binding create devicetree_unfixed.h build error at v2.7.0 * :github:`38673` - DNS-SD library does not support ``_services._dns-sd._udp.local`` meta-query for service enumeration * :github:`38668` - ESP32s I2S * :github:`38667` - ST LSM6DSO polling mode does not work on nRF52dk_nrf52832 * :github:`38655` - Failing Tests for Regulator API * :github:`38653` - drivers: modem: gsm_ppp: Add support for Quectel modems * :github:`38646` - SIMD Rounding bug while running Assembly addps instruction on Zephyr * :github:`38641` - Arm v8-M '_ns' renaming was applied inconsistently * :github:`38635` - USDHC driver broken on RT10XX after 387e6a676f86c00d1f9ef018e4b2480e0bcad3c8 commit * :github:`38622` - subsys/usb: CONFIG_USB_DEVICE_STACK resulted in 10kb increase in firmware size * :github:`38621` - Drivers: spi: stm32: Transceive lock forever * :github:`38620` - STM32 uart driver prevent system to go to deep sleep * :github:`38617` - HL7800 PSM not working as intended * :github:`38613` - BLE connection parameters updated with inconsistent values * :github:`38612` - Fault with assertions enabled prevents detailed output because of ISR() assertion check in shell function * :github:`38602` - modem gsm * :github:`38601` - nucleo_f103rb: samples/posix/eventfd/ failed since "retargetable locking" addition * :github:`38593` - using RTT console to print along with newlib C library in Zephyr * :github:`38591` - nucleo_f091rc: Linking issue since "align __data_ram/rom_start/end linker" (65a2de84a9d5c535167951bf1cf610c4f7967ea5) * :github:`38586` - olimexino_stm32: "no DEVICE_HANDLE_ENDS inserted" builld issue (samples/subsys/usb/audio/headphones_microphone) * :github:`38581` - tests-ci : kernel: scheduler: multiq test failed * :github:`38582` - tests-ci : kernel: scheduler: test failed * :github:`38578` - STM32L0X ADC hangs * :github:`38572` - Builds with macOS SDK are failing * :github:`38571` - bug: drivers: ethernet: build as static library breaks frdm_k64f gptp sample application * :github:`38563` - ISO broadcast cannot send with callback if CONFIG_BT_CONN=n * :github:`38560` - log v2 with 64-bit integers and threads causes invalid 64-bit value output * :github:`38559` - Shell log backend may hang on qemu_x86_64 * :github:`38558` - CMake warning: CMP0079 * :github:`38554` - tests-ci : kernel: scheduler: test failed * :github:`38552` - stm32: g0b1: garbage output in log and suspected hard fault when configuring modem * :github:`38536` - samples: tests: display: Sample for display.ft800 causes end in timeout * :github:`38535` - drivers: modem: bg9x: Kconfig values compiled into ``autoconf.h`` even if it isn't being used * :github:`38534` - lwm2m: add api to inspect observation state of resource/object * :github:`38532` - samples: audio: tests: Twister fails on samples/drivers/audio/dmic * :github:`38527` - lwm2m: re-register instead of removing observer on COAP reset answer to notification * :github:`38520` - Bluetooth:Host:Scan: "bt_le_per_adv_list_add" function doesn't work * :github:`38519` - stm32: g0b1re: Log/Shell subsys with serial uart buggy after #38432 * :github:`38516` - subsys: net: ip: packet_socket: always returning of NET_CONTINUE caused access to unreferred pkt and causing a crash/segmentation fault * :github:`38514` - mqtt azure sample failing with net_tcp "is waiting on connect semaphore" * :github:`38512` - stm32f7: CAN: STM32F645VE CAN signal seems upside down. * :github:`38500` - tests/kernel/device/kernel.device.pm fails to build on TI platforms * :github:`38498` - net: ipv6: nbr_lock not initialized with CONFIG_NET_IPV6_ND=n * :github:`38480` - Improve samples documentation * :github:`38479` - "west flash" command exiting with error * :github:`38477` - json: JSON Library Orphaned, Request to Become a Maintainer * :github:`38474` - command exited with status 63: nrfjprog --ids * :github:`38463` - check_compliance gives very many Kconfig warnings * :github:`38452` - Some STM32 series require CONFIG_PM_DEVICE if CONFIG_PM=y * :github:`38442` - test-ci: can: twr_ke18f: all can driver test fails with BUS Fault * :github:`38438` - test-ci: test_flash_map:twr_ke18f: test failure * :github:`38437` - stm32: g0b1re: Serial UART timing issue after MCU entered deep sleep * :github:`38433` - gpio_pin_set not working on STM32 with CONFIG_PM_DEVICE_RUNTIME * :github:`38428` - http_client response callback always reports final_data == HTTP_DATA_FINAL * :github:`38427` - mimxrt1050_evk and mimxrt1020_evk boards fail to boot some sample applications * :github:`38421` - HardFault regression detected on Cortex-M0+ following Cortex-R introduction * :github:`38418` - twister: Remove toolchain-depandat filter for native_posix * :github:`38417` - Add support for WeAct-F401CC board * :github:`38414` - Build of http client fails if CONFIG_POSIX_API=y * :github:`38405` - samples/philosophers/sample.kernel.philosopher.stacks fails on xtensa * :github:`38403` - Cleanup ``No SOURCES given to Zephyr library`` warnings * :github:`38402` - module: MCUboot module missing fixes available upstream * :github:`38401` - Builds fail due to a proxy error by launchpadlibrarian * :github:`38400` - mec15xxevb_assy6853: arm_ramfunc and arm_sw_vector_relay tests timeout after the build * :github:`38398` - DT_N_INST error for TMP116 sample * :github:`38396` - RISC-V privilege SoC initialisation code skips the __reset vector * :github:`38382` - stm32 uart finishes Tx before going to PM * :github:`38365` - drivers: gsm_ppp: gsm_ppp_stop fails to lock tx_sem after some time * :github:`38362` - soc: ti cc13x2-cc26x2: PM standby + radio interaction regression * :github:`38354` - stm32: stm32f10x JTAG realated gpio repmap didn't works * :github:`38351` - Custom radio protocol * :github:`38349` - XCC compilation fails on Intel cAVS platforms * :github:`38348` - Bluetooth: Switch to inclusive terminology from the 5.3 specification * :github:`38340` - Bluetooth:DirectionFinding: Disabling the MPU causes some compilation errors * :github:`38332` - stm32g0: power hooks should be define as weak * :github:`38323` - Can not generate code coverage report by running samples/subsys/tracing * :github:`38316` - Synchronize multiple DF TX devices in the DF Connectionless RX Example "Periodic Advertising list" * :github:`38309` - ARC context switch to interrupted thread busted with CONFIG_ARC_FIRQ=y and CONFIG_NUM_IRQ_PRIO_LEVELS=1 * :github:`38303` - The current BabbleSim tests build system based on bash scripts hides warnings * :github:`38290` - net_buf_add_mem() hard-faults when adding buffer from external SDRAM * :github:`38279` - Bluetooth: Controller: assert LL_ASSERT(!radio_is_ready()) in lll_conn.c * :github:`38277` - soc: stm32h7: Fails to boot with LDO power supply, if soc has SMPS support. * :github:`38276` - LwM2M: RD Client: Wrong state if registration fails * :github:`38273` - Support UART4 on STM32F303Xe * :github:`38272` - "west flash" stopped working * :github:`38271` - Expose emulator_get_binding function * :github:`38264` - Modbus over RS485 on samd21g18a re-gpios turning on 1 byte too early * :github:`38259` - subsys/shell: ``[JJ`` escape codes in logs after disabling colors * :github:`38258` - newlib: first malloc call may fail on Xtensa depending on image size * :github:`38246` - samples: drivers: flash_shell: fails on arduino_due due to compilation issue * :github:`38245` - board: bl654_usb project: samples/basic/blinky does not blink LED * :github:`38240` - Connected ISO does not disconnect gracefully * :github:`38237` - [backport v2.6-branch] backport of #37479 failed * :github:`38235` - Please add stm32h723Xe.dtsi to dts/arm/st/h7/ * :github:`38234` - Newlib retargetable lock init fails on qemu_xtensa * :github:`38233` - Build newlib function read() and write() failed when enable userspace * :github:`38219` - kernel: Z_MEM_SLAB_INITIALIZER MACRO not compatible with C++ * :github:`38216` - nxp_adsp_imx8 fails to build a number of tests * :github:`38214` - xtensa builds fail in CI due to running out of ram to link * :github:`38207` - Use of unaligned noinit data hangs qemu_arc_hs * :github:`38202` - mbedtls and littlefs on a STM32L4 * :github:`38197` - Invalid NULL check for ``iso`` in bt_iso_connected * :github:`38196` - net nbr command might crash * :github:`38191` - Unable to connect multiple MQTT clients * :github:`38186` - i.MX RT10xx boards fail to initialize when Ethernet is enabled * :github:`38181` - tests/drivers/uart/uart_basic_api/drivers.uart.cdc_acm fails to build * :github:`38177` - LORA Module crashes SHT3XD sensor. * :github:`38173` - STM32WB: Low power modes entry blocked by C2 when CONFIG_BLE=n * :github:`38172` - modem_context_sprint_ip_addr returns pointer to stack array * :github:`38170` - Shell argument in second position containing a question mark is ignored * :github:`38168` - aarch32: flags value collision between base IRQ layer and GIC interrupt controller driver * :github:`38162` - Upgrade to 2.6 GPIO device_get_binding("GPIO_0") now returns null * :github:`38154` - Error building example i2c_fujitsu_fram * :github:`38153` - Zephyr Native POSIX select() implementation too frequent wakeup on pure timeout based use * :github:`38145` - [backport v2.6-branch] backport of #37787 failed * :github:`38144` - [backport v2.6-branch] backport of #37787 failed * :github:`38141` - Wrong output from printk() with CONFIG_CBPRINTF_NANO=y * :github:`38138` - [Coverity CID: 239554] Out-of-bounds read in /zephyr/include/generated/syscalls/log_msg2.h (Generated Code) * :github:`38137` - [Coverity CID: 239555] Unchecked return value in subsys/mgmt/hawkbit/hawkbit.c * :github:`38136` - [Coverity CID: 239557] Out-of-bounds read in /zephyr/include/generated/syscalls/kernel.h (Generated Code) * :github:`38135` - [Coverity CID: 239560] Out-of-bounds access in subsys/modbus/modbus_core.c * :github:`38134` - [Coverity CID: 239563] Logically dead code in subsys/bluetooth/host/id.c * :github:`38133` - [Coverity CID: 239564] Side effect in assertion in subsys/bluetooth/controller/ll_sw/nordic/lll/lll.c * :github:`38132` - [Coverity CID: 239565] Unchecked return value in drivers/sensor/adxl372/adxl372_trigger.c * :github:`38131` - [Coverity CID: 239568] Out-of-bounds access in subsys/modbus/modbus_core.c * :github:`38130` - [Coverity CID: 239569] Out-of-bounds access in subsys/bluetooth/host/id.c * :github:`38129` - [Coverity CID: 239572] Out-of-bounds read in /zephyr/include/generated/syscalls/kernel.h (Generated Code) * :github:`38127` - [Coverity CID: 239579] Logically dead code in drivers/flash/nrf_qspi_nor.c * :github:`38126` - [Coverity CID: 239581] Out-of-bounds access in subsys/modbus/modbus_core.c * :github:`38125` - [Coverity CID: 239582] Unchecked return value in drivers/display/ssd1306.c * :github:`38124` - [Coverity CID: 239583] Side effect in assertion in subsys/bluetooth/controller/ll_sw/nordic/lll/lll.c * :github:`38123` - [Coverity CID: 239584] Improper use of negative value in subsys/logging/log_msg2.c * :github:`38122` - [Coverity CID: 239585] Side effect in assertion in subsys/bluetooth/controller/ll_sw/nordic/lll/lll.c * :github:`38121` - [Coverity CID: 239586] Side effect in assertion in subsys/bluetooth/controller/ll_sw/nordic/lll/lll.c * :github:`38120` - [Coverity CID: 239588] Unchecked return value in subsys/bluetooth/host/id.c * :github:`38119` - [Coverity CID: 239592] Dereference before null check in subsys/ipc/rpmsg_multi_instance/rpmsg_multi_instance.c * :github:`38118` - [Coverity CID: 239597] Explicit null dereferenced in tests/net/context/src/main.c * :github:`38117` - [Coverity CID: 239598] Unchecked return value in drivers/sensor/adxl362/adxl362_trigger.c * :github:`38116` - [Coverity CID: 239601] Untrusted loop bound in subsys/bluetooth/host/sdp.c * :github:`38115` - [Coverity CID: 239605] Logically dead code in drivers/flash/nrf_qspi_nor.c * :github:`38114` - [Coverity CID: 239607] Missing break in switch in subsys/usb/class/dfu/usb_dfu.c * :github:`38113` - [Coverity CID: 239609] Out-of-bounds access in subsys/random/rand32_ctr_drbg.c * :github:`38112` - [Coverity CID: 239612] Out-of-bounds read in /zephyr/include/generated/syscalls/log_ctrl.h (Generated Code) * :github:`38111` - [Coverity CID: 239615] Out-of-bounds access in subsys/net/lib/sockets/sockets_tls.c * :github:`38110` - [Coverity CID: 239619] Out-of-bounds access in subsys/net/lib/sockets/sockets_tls.c * :github:`38109` - [Coverity CID: 239623] Out-of-bounds access in subsys/net/lib/sockets/sockets_tls.c * :github:`38108` - nxp: usb driver build failure due to d92d1f162af3ba24963f1026fc0a304f1a44d1f3 * :github:`38104` - kheap buffer own section attribute causing memory overflow in ESP32 * :github:`38101` - bt_le_adv_update_data() assertion fail * :github:`38093` - preempt_cnt not reset in each test case in tests/lib/ringbuffer/libraries.data_structures * :github:`38090` - LPS22HH: int32_t overflow in pressure calculations * :github:`38082` - Hawkbit (http request) and MQTT can't seem to work together * :github:`38078` - RT6XX I2S test fails after d92d1f162af3ba24963f1026fc0a304f1a44d1f3 * :github:`38069` - stm32h747i_disco M4 not working following merge of 9fa5437447712eece9c88e728ac05ac10fb01c4a * :github:`38065` - Bluetooth: Direction Finding: Compiler warning when included in other header files * :github:`38059` - automount configuration in nrf52840dk_nrf52840.overlay causes error: mount point already exists!! in subsys/fs/littlefs sample * :github:`38054` - Bluetooth: host: Local Host terminated but send host number of completed Packed * :github:`38047` - twister: The --board-root parameter doesn't appear to work * :github:`38046` - twister: The --device-serial only works at 115200 baud * :github:`38044` - tests: newlib: Scenarios from tests/lib/newlib/thread_safety fail on nrf9160dk_nrf9160_ns * :github:`38031` - STM32WB - Problem with data reception on LPUART when PM and LPTIM are enabled * :github:`38026` - boards: bl654_usb: does not support samples/bluetooth/hci_uart * :github:`38022` - thread: k_float_enable() API can't build on x86_64 platforms, fix that API and macro documentation * :github:`38019` - nsim_sem_mpu_stack_guard board can't run * :github:`38017` - [Coverity CID: 237063] Untrusted value as argument in tests/net/lib/coap/src/main.c * :github:`38016` - [Coverity CID: 238375] Uninitialized pointer read in subsys/bluetooth/mesh/shell.c * :github:`38015` - [Coverity CID: 237072] Uninitialized pointer read in subsys/bluetooth/controller/ll_sw/ull_adv_aux.c * :github:`38014` - [Coverity CID: 237071] Unexpected control flow in subsys/bluetooth/host/keys.c * :github:`38013` - [Coverity CID: 237070] Unchecked return value in subsys/bluetooth/shell/gatt.c * :github:`38012` - [Coverity CID: 236654] Unchecked return value in subsys/bluetooth/host/gatt.c * :github:`38011` - [Coverity CID: 236653] Unchecked return value in drivers/sensor/bmi160/bmi160_trigger.c * :github:`38010` - [Coverity CID: 236652] Unchecked return value in drivers/sensor/fxas21002/fxas21002_trigger.c * :github:`38009` - [Coverity CID: 236651] Unchecked return value in drivers/sensor/bmg160/bmg160_trigger.c * :github:`38008` - [Coverity CID: 236650] Unchecked return value in drivers/sensor/fxos8700/fxos8700_trigger.c * :github:`38007` - [Coverity CID: 236649] Unchecked return value in drivers/sensor/adt7420/adt7420_trigger.c * :github:`38006` - [Coverity CID: 236648] Unchecked return value in drivers/sensor/sx9500/sx9500_trigger.c * :github:`38005` - [Coverity CID: 236647] Unchecked return value in drivers/sensor/bmp388/bmp388_trigger.c * :github:`38004` - [Coverity CID: 238360] Result is not floating-point in drivers/sensor/sgp40/sgp40.c * :github:`38003` - [Coverity CID: 238343] Result is not floating-point in drivers/sensor/sgp40/sgp40.c * :github:`38002` - [Coverity CID: 237060] Out-of-bounds access in subsys/bluetooth/host/gatt.c * :github:`38001` - [Coverity CID: 238371] Negative array index read in tests/lib/cbprintf_package/src/test.inc * :github:`38000` - [Coverity CID: 238347] Negative array index read in tests/lib/cbprintf_package/src/test.inc * :github:`37999` - [Coverity CID: 238383] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37998` - [Coverity CID: 238381] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37997` - [Coverity CID: 238380] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37996` - [Coverity CID: 238379] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37995` - [Coverity CID: 238378] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37994` - [Coverity CID: 238377] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37993` - [Coverity CID: 238376] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37992` - [Coverity CID: 238374] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37991` - [Coverity CID: 238373] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37990` - [Coverity CID: 238372] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37989` - [Coverity CID: 238370] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37988` - [Coverity CID: 238369] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37987` - [Coverity CID: 238368] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37986` - [Coverity CID: 238367] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37985` - [Coverity CID: 238366] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37984` - [Coverity CID: 238364] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37983` - [Coverity CID: 238363] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37982` - [Coverity CID: 238362] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37981` - [Coverity CID: 238361] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37980` - [Coverity CID: 238359] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37979` - [Coverity CID: 238358] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37978` - [Coverity CID: 238357] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37977` - [Coverity CID: 238356] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37976` - [Coverity CID: 238355] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37975` - [Coverity CID: 238354] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37974` - [Coverity CID: 238353] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37973` - [Coverity CID: 238352] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37972` - [Coverity CID: 238351] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37971` - [Coverity CID: 238350] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37970` - [Coverity CID: 238349] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37969` - [Coverity CID: 238348] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37968` - [Coverity CID: 238346] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37967` - [Coverity CID: 238345] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37966` - [Coverity CID: 238344] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37965` - [Coverity CID: 238342] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37964` - [Coverity CID: 238341] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37963` - [Coverity CID: 238340] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37962` - [Coverity CID: 238339] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37961` - [Coverity CID: 238337] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37960` - [Coverity CID: 238336] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37959` - [Coverity CID: 238335] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37958` - [Coverity CID: 238334] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37957` - [Coverity CID: 238333] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37956` - [Coverity CID: 238332] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37955` - [Coverity CID: 238331] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37954` - [Coverity CID: 238330] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37953` - [Coverity CID: 238328] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37952` - [Coverity CID: 238327] Logically dead code in tests/bluetooth/tester/src/mesh.c * :github:`37951` - [Coverity CID: 238365] Logical vs. bitwise operator in drivers/i2s/i2s_nrfx.c * :github:`37950` - [Coverity CID: 237067] Division or modulo by zero in tests/benchmarks/latency_measure/src/heap_malloc_free.c * :github:`37949` - [Coverity CID: 238382] Dereference before null check in subsys/bluetooth/mesh/cfg_cli.c * :github:`37948` - [Coverity CID: 238338] Dereference before null check in subsys/bluetooth/mesh/cfg_cli.c * :github:`37947` - [Coverity CID: 237069] Dereference before null check in subsys/bluetooth/host/att.c * :github:`37946` - [Coverity CID: 237066] Calling risky function in tests/lib/c_lib/src/main.c * :github:`37945` - [Coverity CID: 237064] Calling risky function in tests/lib/c_lib/src/main.c * :github:`37944` - [Coverity CID: 237062] Calling risky function in tests/lib/c_lib/src/main.c * :github:`37940` - Unconsistent UART ASYNC API * :github:`37927` - tests-ci: net-lib: test/net/lib : build missing drivers__net and application has no console output * :github:`37916` - [Coverity CID :219656] Uninitialized scalar variable in file /tests/kernel/threads/thread_stack/src/main.c * :github:`37915` - led_pwm driver not generating correct linker symbol * :github:`37896` - samples: bluetooth: mesh: build failed for native posix * :github:`37876` - Execution of twister in makefile environment * :github:`37865` - nRF Battery measurement issue * :github:`37861` - tests/lib/ringbuffer failed on ARC boards * :github:`37856` - tests: arm: uninitialized FPSCR * :github:`37852` - RISC-V machine timer time-keeping question * :github:`37850` - Provide macros for switching off Zephyr kernel version * :github:`37842` - TCP2 statemachine gets stuck in TCP_FIN_WAIT_2 state * :github:`37839` - SX1272 LoRa driver is broken and fails to build * :github:`37838` - cmake 3.20 not supported (yet) by recent Ubuntu * :github:`37830` - intel_adsp_cavs15: run queue testcases failed on ADSP * :github:`37827` - stm32h747i_disco M4 not working, if use large size(>1KB) global array * :github:`37821` - pm: ``pm_device_request`` incorrectly returns errors * :github:`37797` - Merge vendor-prefixes.txt from all modules with build.settings.dts_root in zephyr/module.yml * :github:`37790` - Bluetooth: host: Confusion about periodic advertising interval * :github:`37786` - Example for tca9546a multiplexor driver * :github:`37784` - MPU6050 accel and gyro values swapped * :github:`37781` - nucleo_l496zg lpuart1 driver not working * :github:`37779` - adc sam0 interrupt mapping, RESRDY maps to second interrupt in samd5x.dtsi * :github:`37772` - samples: subsys: usb: mass: Use &flash0 storage_partition for USB mass storage * :github:`37768` - tests/lib/ringbuffer/libraries.data_structures fails to build on number of platforms due to CONFIG_SYS_CLOCK_TICKS_PER_SEC=100000 * :github:`37765` - cmake: multiple ``No SOURCES given to Zephyr library:`` warnings * :github:`37746` - qemu_x86_64 fails samples/hello_world/sample.basic.helloworld.uefi in CI * :github:`37735` - Unsigned types are incorrectly serialized when TLV format is used in LWM2M response * :github:`37734` - xtensa xcc build spi_nor.c fail * :github:`37720` - net: dtls: received close_notify alerts are not properly handled by DTLS client sockets * :github:`37718` - Incompatible (u)intptr_t type and PRIxPTR definitions * :github:`37709` - x86 PCIe ECAM does not work as expected * :github:`37701` - stm32: conflicts with uart serial DMA * :github:`37696` - Modbus TCP: wrong transaction id in response * :github:`37694` - Update CMSIS-DSP version to 1.9.0 (CMSIS 5.8.0) * :github:`37693` - Update CMSIS-Core version to 5.5.0 (CMSIS 5.8.0) * :github:`37691` - samples/subsys/canbus/isotp/sample.subsys.canbus.isotp fails to build on mimxrt1170_evk_cm7 * :github:`37687` - Support MVE on ARMv8.1-M * :github:`37684` - Add State Machine Framework to Zephyr * :github:`37676` - tests/kernel/device/kernel.device.pm (and tests/subsys/pm/power_mgmt/subsys.pm.device_pm) fails to build on mec172xevb_assy6906 & mec1501modular_assy6885 * :github:`37675` - tests/kernel/device/kernel.device.pm fails on bt510/bt6x0 * :github:`37672` - Board qemu_x86 is no longer working with shell * :github:`37665` - File system: wrong type for ssize_t in fs.h for CONFIG_ARCH_POSIX * :github:`37660` - Changing zephyr,console requires a clean build * :github:`37658` - samples: boards/stm32/backup_sram : needs backup sram enabled in DT to properly display memory region * :github:`37652` - bluetooth: tests/bluetooth/bsim_bt/bsim_test_advx reported success but still reported failed. * :github:`37637` - Infinite configuring loop for samples\drivers\led_ws2812 sample * :github:`37619` - RT6xx TRNG reports error on first request after reset * :github:`37611` - Bluetooth: host: Implement L2CAP ecred reconfiguration request as initiator * :github:`37610` - subsys/mgmt/hawkbit: Unable to parse json if the payload is split into 2 packets * :github:`37600` - Invalidate TLB after ptables swap * :github:`37597` - samples: bluetooth: scan_adv * :github:`37586` - get_maintainer.py is broken * :github:`37581` - Bluetooth: controller: radio: Change CTE configuration method * :github:`37579` - PWM: Issue compiling project when CONFIG_PWM and CONFIG_PWM_SAM is used with SAME70 * :github:`37571` - Bluetooth: Extended advertising assertion * :github:`37556` - Schedule or timeline of LE audio in zephyr * :github:`37547` - Bluetooth: Direction Finding: Channel index of received CTE packet is incorrect * :github:`37544` - Change partition name using .overlay * :github:`37543` - Using STM32Cube HAL function results in linker error * :github:`37536` - _pm_devices() skips the very first device in the list and suspend() is not called. * :github:`37530` - arc smp build failed with mwdt toolchain. * :github:`37527` - Replace mqtt-azure example with azure-sdk-for-c * :github:`37526` - ehl_crb: edac tests are failing * :github:`37520` - Is zephyr can run syscall or extrenal program * :github:`37519` - friend.c:unseg_app_sdu_decrypt causes assert: net_buf_simple_tailfroom(buf) >= len when payload + opcode is 10 or 11 bytes long * :github:`37515` - drivers: flash_sam: Random failures when writing large amount of data to flash * :github:`37502` - OPENTHREAD_CUSTOM_PARAMETERS does not seem to work * :github:`37495` - mcuboot: Booting an image flashed on top of a Hawkbit updated ones results in hard fault * :github:`37491` - wrong documentation format on DMA peripheral API reference * :github:`37482` - 'cmd.exe' is not recognized as an internal or external command, operable program or batch file. * :github:`37475` - twister: wrong test statuses in json report * :github:`37472` - Corrupted timeout on poll for offloaded sockets * :github:`37467` - Bluetooth: host: Incorrect advertiser timeout handling when using Limited Discoverable flag * :github:`37465` - samples/bluetooth/iso_receive fails on nrf5340dk target * :github:`37462` - Bluetooth: Advertising becomes scannable even if BT_LE_ADV_OPT_FORCE_NAME_IN_AD is set * :github:`37461` - Schedule of LE audio in zephyr * :github:`37460` - tests/kernel/sched/schedule_api/kernel.scheduler and tests/kernel/fifo/fifo_timeout/kernel.fifo.timeout failed on nsim_hs_smp board * :github:`37456` - script: Unaccounted size in ram/rom reports * :github:`37454` - Sensor driver: sht4x, sgp40, invalid include path * :github:`37446` - Sensor driver: ST LPS22HH undeclared functions and variables * :github:`37444` - MSI-X: wrong register referenced in map_msix_table() * :github:`37441` - Native POSIX Flash Storage Does not Support Multiple Instances * :github:`37436` - Delayed startup due to printing over not ready console * :github:`37412` - IQ samples are not correct during the "reference period" of CTE signal * :github:`37409` - Allow dual controller on usb * :github:`37406` - ISO disconnect complete event doesn't reach the application * :github:`37400` - esp32 build * :github:`37396` - DHCP issue with events not triggering on network with microsoft windows DHCP server * :github:`37395` - stm32h747i_disco board M4 core not working * :github:`37391` - Bluetooth: 4 Bits of IQ Samples Are Removed (Direction Finding Based on CTE) * :github:`37386` - bt_vcs_register() enhancement for setting default volume and step * :github:`37379` - drivers: adc for stm32h7 depends on the version for oversampling * :github:`37376` - samples/subsys/usb/dfu/sample.usb.dfu fails on teensy41/teensy40 * :github:`37375` - tests/drivers/adc/adc_api/drivers.adc fails to build on nucleo_h753zi * :github:`37371` - logging.log2_api_deferred_64b_timestamp tests fails running on several qemu platforms * :github:`37367` - Bluetooth: Host: Support setting long advertising data * :github:`37365` - STM32 :DTCM: incorrect buffer size utilization * :github:`37346` - STM32WL LoRa increased the current in "suspend_to_idle" state * :github:`37338` - west flash to teensy 41 fail, use blinky with west build * :github:`37332` - Increased power consumption for STM32WB55 with enabled PM and Bluetooth * :github:`37327` - subsys/mgmt/hawkbit: hawkbit run can interrupt a running instance * :github:`37319` - West 0.11.0 fails in Zephyr doc build under other manifest repo & renamed Zephyr fork * :github:`37309` - ARC: add MPU v6 (and others) support * :github:`37307` - Use XOSHIRO random number generator on NXP i.MX RT platform * :github:`37306` - revert commit with bogus commit message * :github:`37305` - Bluetooth Direction Finding Support of "AoA RX 1us" * :github:`37304` - k_timer_status_sync can lock forever on qemu_x86_64 * :github:`37303` - tests: drivers: i2s: drivers.i2s.speed scenario fails on nrf platforms * :github:`37294` - RTT logs not found with default west debug invocation on jlink runner * :github:`37293` - Native POSIX MAC addresses are not random and are duplicate between multiple instances * :github:`37272` - subsys/mgmt/hawkbit: Falsely determine that an update is installed successfully * :github:`37270` - stm32l4 System Power Management issue * :github:`37264` - tests-ci : can: isotp: implemmentation test report FATAL ERROR when do not connect can loopback test pins * :github:`37265` - tests-ci : kernel: scheduler: multiq test failed * :github:`37266` - tests-ci : kernel: memory_protection: userspace test Timeout * :github:`37267` - tests-ci : kernel: threads: apis test Timeout * :github:`37263` - lib: timeutil: conversion becomes less accurate as time progresses * :github:`37260` - STM32WL does not support HSE as RCC source and HSEDiv * :github:`37258` - symmetric multiprocessing failed in user mode * :github:`37254` - Run Coverity / Generate GitHub Issues * :github:`37253` - west flash is failed with openocd for on macOS * :github:`37236` - ESP32 will not start when CONFIG_ASSERT=y is enabled * :github:`37231` - BME280 faulty measurement after power cycle * :github:`37228` - Bluetooth SMP does not complete pairing * :github:`37226` - PM: soc: Leftover in conversion of PM hooks to __weak * :github:`37225` - subsys/mgmt/hawkbit & sample: Bugs/improvements * :github:`37222` - k_queue data corruption, override user data after reserved heading word * :github:`37221` - nRF5340: SPIM4 invalid clock frequency selection * :github:`37213` - ESP32: can't write to SD card over SPI (CRC error) * :github:`37207` - drivers: serial: convert uart_altera_jtag_hal to use devicetree * :github:`37206` - counter: stm32: Missing implementation of set_top_value * :github:`37205` - openocd: Configure thread awareness by default * :github:`37202` - esp32c3 build error * :github:`37189` - Bug "Key 'name', 'cmake-ext' and 'kconfig-ext' were not defined" when build a zephyr application * :github:`37188` - Get an error of "Illegal load of EXC_RETURN into PC" when print log in IO interrupt callback * :github:`37182` - cmsis_v1 osSignalWait doesn't clear the signals properly when any signal mask is set * :github:`37180` - Led driver PCA9633 does nok take chip out from sleep * :github:`37175` - nucleo-f756zg: rtos aware debugging not working * :github:`37174` - Zephyr's .git directory is 409 MiB, can it be squashed? * :github:`37173` - drivers: clock_control: stm32: AHB prescaler usable for almost all stm32 series * :github:`37170` - LwM2M lwm2m_rd_client_stop() not working when called during bootstrapping/registration * :github:`37160` - [Moved] Bootloader should provide the version of zephyr, mcuboot and a user defined version to the application * :github:`37159` - osThreadTerminate does not decrease the instances counter * :github:`37153` - USB serial number is not unique for STM32 devices * :github:`37145` - sys: ring_buffer: ring_buf_peek() and ring_buf_size_get() * :github:`37140` - Twister: Cmake error wrongly counted in the report * :github:`37135` - Extend the HWINFO API to provide variable length unique ID * :github:`37134` - Add support for the Raspberry Pi Compute Module 4 * :github:`37132` - Assert on enabling Socket CAN * :github:`37120` - Documentation on modules * :github:`37119` - tests: kernel tests hardfault on nucleo_l073rz * :github:`37115` - tests/bluetooth/shell fails to builds on a lot of platforms * :github:`37109` - Zephyr POSIX layer uses swapping with an interrupt lock held * :github:`37105` - mcumgr: BUS FAULT when starting dfu with mcumgr CLI * :github:`37104` - tests-ci : kernel: scheduler: multiq test failed * :github:`37075` - PlatformIO: i cannot use the Wifi Shield ESP8266 to build the sample wifi project with the Nucleo F429ZI * :github:`37070` - NXP mcux ADC16 reading 65535 * :github:`37057` - PWM-blinky for Silabs MCU * :github:`37038` - stm32f4 - DMA tx interrupt doesn't trigger * :github:`37032` - document: API reference missing: In clock of zephyr document * :github:`37029` - drivers: sensor: sensor_value_to_double requieres non const sensor_value pointer * :github:`37028` - ipv6 multicast addresses vanish after iface down/up sequence * :github:`37024` - Compile error if we only use VCS without VOCS and AICS * :github:`37023` - zephyr_prebuilt.elf and zephyr.elf has inconsistent symbol address in RISC-V platform * :github:`37007` - Problem with out of tree driver * :github:`37006` - tests: kernel: mem_protect: stack_random: enable qemu_riscv32 * :github:`36998` - TF-M: does not allow PSA Connect to proceed with IRQs locked * :github:`36990` - Memory misalignment ARM Cortex-M33 * :github:`36971` - ESP32: wifi station sample does not get IP address by DHCP4 * :github:`36967` - Bluetooth: public API to query controller public address * :github:`36959` - Direction Finding - CTE transmitted in connectionless mode has wrong length * :github:`36953` - <err> lorawan: MlmeConfirm failed : Tx timeout * :github:`36948` - Cluttering of logs on USB Console in Zephyr when CDC Shell is enabled * :github:`36947` - Tensorflow: Dedicated tflite-micro repository * :github:`36929` - Failure to build OpenThread LwM2M client on nrf52840dk * :github:`36928` - Disconnecting ISO mid-send giver error in hci_num_completed_packets * :github:`36927` - LWM2M: Writing to Write-Only resource causes notification * :github:`36926` - samples/boards/nrf/system_off wouldn't compile on Particle Xenon board * :github:`36924` - embARC Machine Learning Inference Library from Synopsys * :github:`36917` - Runtime device PM is broken on STM32 * :github:`36909` - Shell log` commands crash the system if CONFIG_SHELL_LOG_BACKEND is not defined * :github:`36896` - tests: net: select: still failing occasionally due to FUZZ * :github:`36891` - Significant TCP perfomance regression * :github:`36889` - string.h / strcasestr() + strtok() * :github:`36885` - Update ISO API to better support TWS * :github:`36882` - MCUMGR: fs upload fail for first time file upload * :github:`36873` - USB AUDIO Byte alignment issues * :github:`36869` - Direction Finding Connectionless porting to nrf52811 * :github:`36866` - CONFIG_NO_OPTIMIZATIONS=y MPU fault on Zephyr 2.6 * :github:`36865` - k_work_q seems to check uninitialized flag on start * :github:`36859` - Possible Advertising PDU Corruption if bt_enable called in SYS_INIT function * :github:`36858` - Static object constructors execute twice on the NATIVE_POSIX target * :github:`36857` - i2c_samd0.c burst write not compatible with ssd1306.c * :github:`36851` - FS logging backend assumes littlefs * :github:`36823` - Build excludes paths to standard C++ headers when using GNUARMEMB toolchain variant * :github:`36819` - qemu_leon3 samples/subsys/portability/cmsis_rtos_v2 samples failing * :github:`36814` - Wrong format type for uint32_t * :github:`36811` - Clarify ``Z_`` APIs naming conventions and intended scope * :github:`36802` - MCUboot doesn't work with encrypted images on external flash * :github:`36796` - Build failure: samples/net/civetweb/http_server using target stm32h735g_disco * :github:`36794` - Build failure: tests/drivers/adc using stm32l562e_dk * :github:`36790` - sys: ring_buffer: correct space calculation when tail is less than head * :github:`36789` - [ESP32] samples blinky / gpio / custom board * :github:`36783` - drivers: modem: hl7800 gpio init failed with interrupt flags * :github:`36782` - drivers: serial: nrfx: Enforced pull-ups on RXD and CTS conflict on many custom boards * :github:`36781` - source_periph incorrectly set in dma_stm32 * :github:`36778` - firmware update using mcumgr displays information for only slot 0 and not slot 1. * :github:`36770` - docMissing description for deadline scheduling * :github:`36769` - Zephyr assumes Interrupt Line config space register is RW, while ACRN hardwired it to 0. * :github:`36767` - tests-ci :arch.arm.irq_advanced_features.arm_irq_target_state : test failed * :github:`36768` - tests-ci :coredump.logging_backend : test failed * :github:`36765` - [PCI] ACRN sets Interrupt Line config space register to 0 and ReadOnly. * :github:`36764` - Bluetooth Require paired after disconnected work with iphone * :github:`36755` - NTP client faults module when it fails * :github:`36748` - Zephyr IP Stack Leaks when using PROMISCUOUS socket along with POSIX sockets based implementation. * :github:`36747` - Adding Board Support for STEVAL-STWINKT1B * :github:`36745` - Zephyr IP Stack Limited to 1514 bytes on the wire - no ICMPs beyond this limit * :github:`36739` - coap_packet_get_payload() returns the wrong size * :github:`36737` - Cortex M23: "swap_helper.S:223: Error: invalid offset, value too big (0x0000009C)" * :github:`36736` - kernel: SMP global lock (and therefore irq_lock) works incorrectly on SMP platforms * :github:`36718` - st_ble_sensor sample references wrong attribute * :github:`36716` - zephyr - ADC - ATSAMD21G18A * :github:`36713` - nrf5 ieee802154 driver does not compile and breaks CI * :github:`36711` - Enable "template repository" for zephyrproject-rtos/example-application * :github:`36696` - Json on native_posix_64 board * :github:`36695` - net: ieee802154: cc13xx_26xx: Sub-GHz RF power saving * :github:`36692` - Release Notes for 2.6.0 not useful (BLE API changes) * :github:`36679` - Bluetooth - notifications not sending (bonded, CONFIG_BT_MAX_CONN=4, after disconnection then reconnection) * :github:`36678` - Zephyr Throws Exception for Shell "log status" command when Telnet is shell backend and log is UART backend * :github:`36668` - LittleFS example overwrite falsh memory * :github:`36667` - logger: Filesystem backend doesn't work except for first time boot * :github:`36665` - l2cap cids mixed up in request * :github:`36661` - xtensa xcc does not support "-Warray-bounds" * :github:`36659` - samples/net/sockets small bugs * :github:`36655` - twister: sometimes the twister fails because the error ``configparser.NoSectionError: No section: 'manifest'`` * :github:`36652` - deadlock in pthread implementation on SMP platforms * :github:`36646` - sample.shell.shell_module.minimal_rtt fails to build on mimxrt1170_evk_cm4/mimxrt1170_evk_cm7 * :github:`36644` - Toolchain C++ headers can be included when libstdc++ is not selected * :github:`36631` - Turn on GPIO from DTS * :github:`36625` - compilation fails while building samples/net/openthread/coprocessor for Arduino nano 33 ble * :github:`36613` - LoRaWAN - Provide method to register a callback for received data * :github:`36609` - could not mount fatfs on efm32pg_stk3402a * :github:`36608` - Unable to compile USB console example with uart_mux * :github:`36606` - Regression in udp socket performance from zephyr v2.3.0 to v2.6.0 * :github:`36600` - Bluetooth: Peripheral: Bond issue when using secure connection * :github:`36598` - Lora driver TX done wait/synchronous call * :github:`36593` - Failing IPv6 Ready compliance (RFC 2460) * :github:`36590` - NVS sector size above 65535 not supported * :github:`36578` - net: ip: Assertion fails when tcp_send_data() with zero length packet * :github:`36575` - Modbus RTU Client on ESP32 * :github:`36572` - kernel: Negative mutex lock_count value * :github:`36570` - Use a custom role for Kconfig configuration options * :github:`36569` - '.. only:' is not working as expected in documentation * :github:`36568` - net: lib: sockets: Assertion fails when zsock_close() * :github:`36565` - ehl_crb: Only boot banner is printed but not the test related details for multiple tests due to PR #36191 is not backported to v2.6.0 release * :github:`36553` - LoRaWAN Sample: join accept but "Join failed" * :github:`36552` - Bluetooth v2.6.0 connectable advertising leak/loss * :github:`36540` - LoRaWAN otaa.app_key belongs to mib_req.Param.AppKey * :github:`36524` - HSE clock doesn't initialize and blinky doesn't run on custom board when moving from zephyr v2.3.0 to v2.6.0 * :github:`36520` - tests/kernel/timer/timer_api/kernel.timer.tickless fails to build on npcx9m6f_evb * :github:`36500` - espressif: cannot install toolchain on Darwin-arm64 * :github:`36496` - bluetooth: only the first Extended Advertising Report with data status "incomplete, more data to come" is issued * :github:`36495` - dtc generates missing #address-cells in interrupt provider warning * :github:`36486` - LOG2 - self referential macro * :github:`36467` - runner mdb-hw not work with arc hsdk board * :github:`36466` - tests/kernel/mem_protect/mem_protect failed with arcmwdt toolchain * :github:`36465` - samples/compression/lz4 failed with arcmwdt toolchian * :github:`36462` - [bluetooth stack][limited_discoverable_advertising timeout] Some problems about the lim_adv_timeout * :github:`36448` - samples: subsys: fs: fat_fs: adafruit_2_8_tft_touch_v2: buildkite compilation failed when no i2c defined * :github:`36447` - net: socket: socketpair: Poll call resetting all events * :github:`36435` - RFC: API Change: Mesh: Add return value for opcode callback * :github:`36427` - test: kernel.common.nano32: zephyr-v2.6.0-286-g46029914a7ac: mimxrt1060_evk: test fails * :github:`36419` - test-ci: net.ethernet_mgmt: zephyr-v2.6.0-286-g46029914a7ac: frdm_k64f: test fails * :github:`36418` - test-ci: net.socket.tls: zephyr-v2.6.0-286-g46029914a7ac: frdm_k64f: test fail * :github:`36417` - tests-ci :coredump.logging_backend : zephyr-v2.6.0-286-g46029914a7ac: lpcxpresso55s28: test failed * :github:`36416` - tests-ci :arch.arm.irq_advanced_features.arm_irq_target_state : zephyr-v2.6.0-286-g46029914a7ac: lpcxpresso55s28: test failed * :github:`36414` - ESP32 with samples/net/wifi gives: net_if: There is no network interface to work with! * :github:`36412` - Blinky on ESP32: Unsupported board: led0 devicetree alias is not defined" * :github:`36410` - board: cc1352r_sensortag: add dts entry for hdc2080 * :github:`36408` - ARM_MPU on boards ``stm32_min_dev_`` without MPU enabled :github:`36398` - [Video API] Erroneous function pointer validation * :github:`36390` - net: ip: Negative TCP unacked_len value * :github:`36388` - ARM: Architecture Level user guide * :github:`36382` - segfault when hardware isn't emulated * :github:`36381` - Bluetooth ASSERTION FAIL [evdone] Zephyr v2.6.0 * :github:`36380` - missing auto-dependency on CONFIG_EMUL * :github:`36357` - tests: samples: watchdog: sample.subsys.task_wdt fails on nrf platforms * :github:`36356` - Network fails to transmit STM32H747DISC0 board zephyr v2.6.0 * :github:`36351` - nRF: we do not always guarantee that SystemInit is inlined * :github:`36347` - Zephyr Wifi IoT device - whats a good board to start with? * :github:`36344` - Zephyr 2.6.0 st_ble_sensor sample is broken when compiled for nucleo_wb55rg * :github:`36339` - samples/subsys/logging/dictionary doesn't build under MS Windows environment * :github:`36329` - Support for CC3120 WiFi module * :github:`36324` - add project groups to upsteam west manifest * :github:`36323` - Don't set TFM_CMAKE_BUILD_TYPE_DEBUG by default on LPC55S69-NS if DEBUG_OPTIMIZATIONS * :github:`36319` - Help: Asking for Help Tips page gets 404 error * :github:`36318` - [Coverity CID: 236600] Unused value in drivers/ieee802154/ieee802154_nrf5.c * :github:`36317` - [Coverity CID: 236599] Unused value in drivers/ieee802154/ieee802154_nrf5.c * :github:`36316` - [Coverity CID: 236597] Unused value in drivers/ieee802154/ieee802154_nrf5.c * :github:`36315` - [Coverity CID: 236604] Untrusted value as argument in subsys/net/lib/lwm2m/lwm2m_engine.c * :github:`36314` - [Coverity CID: 236610] Uninitialized pointer read in subsys/bluetooth/mesh/proxy.c * :github:`36313` - [Coverity CID: 236602] Unchecked return value in drivers/modem/gsm_ppp.c * :github:`36312` - [Coverity CID: 236608] Out-of-bounds access in subsys/bluetooth/audio/mics_client.c * :github:`36311` - [Coverity CID: 236598] Out-of-bounds access in subsys/bluetooth/audio/mics_client.c * :github:`36310` - [Coverity CID: 236607] Missing break in switch in drivers/ieee802154/ieee802154_nrf5.c * :github:`36309` - [Coverity CID: 236606] Missing break in switch in drivers/ieee802154/ieee802154_nrf5.c * :github:`36308` - [Coverity CID: 236601] Missing break in switch in drivers/ieee802154/ieee802154_nrf5.c * :github:`36307` - [Coverity CID: 236605] Logically dead code in subsys/bluetooth/audio/mics.c * :github:`36306` - [Coverity CID: 236596] Logically dead code in subsys/bluetooth/audio/mics.c * :github:`36305` - [Coverity CID: 236595] Logically dead code in samples/drivers/eeprom/src/main.c * :github:`36304` - [Coverity CID: 236609] Explicit null dereferenced in subsys/bluetooth/audio/mics_client.c * :github:`36303` - [Coverity CID: 236603] Dereference after null check in subsys/bluetooth/audio/vcs_client.c * :github:`36301` - soc: cypress: Port Zephyr to Cypress CYW43907 * :github:`36298` - TF-M integration: add a brief user guide * :github:`36291` - ADC and math library functions use for stm32l496 * :github:`36289` - eswifi gets a deadlock on b_l4s5i_iot01a target * :github:`36282` - Overwrite mode for RTT logging * :github:`36278` - ARM: Cortex-M: SysTick priority is not initialized if the SysTick is not used * :github:`36276` - NULL pointer access in check_used_port() * :github:`36270` - TF-M: introduce uniformity in Non-Secure target names * :github:`36267` - net: ieee802154: software address filtering * :github:`36263` - up_squared: kernel.memory_protection.mem_map.x86_64 failed. * :github:`36256` - SPI4 & 3 MISO not working on nRF5340 * :github:`36255` - tests/subsys/logging/log_core failed on hsdk board * :github:`36254` - Zephyr shell subsystem not work with ARC hardware boards. * :github:`36250` - tests/subsys/cpp/cxx - doesn't compile on native_posix when CONFIG_EXCEPTIONS=y * :github:`36247` - samples: usb: testusb: Problems with using with cdc-acm * :github:`36242` - Zephyr Upstream + sdk-nrf BLE NUS SHELL LOG/CBPRINTF build problem. * :github:`36238` - net_if.c: possible mutex deadlock * :github:`36237` - fs_open returns 0 on existing file with FS_O_CREATE \| FS_O_WRITE * :github:`36197` - BOSSA flashing on Arduino Nano 33 BLE (NRF52840) * :github:`36185` - CMP0116 related warnings * :github:`36172` - net: ieee802154: LL src/dst address is lost from received net_pkt (when using 6LO) * :github:`36163` - nvs no longer supports the use of id=0xffff * :github:`36131` - Occasionally unable to scan for extended advertisements when connected * :github:`36117` - toolchain: The added abstraction for llvm, breaks builds with off-tree llvm based toolchains * :github:`36107` - ehl_crb: Multiple tests are failing and board is not booting up. * :github:`36101` - tfm related build rebuild even if nothing changes * :github:`36100` - pb_gatt buf_send does not call callback * :github:`36095` - drivers: pwm: sam: compilation failure for sam_v71b_xult * :github:`36094` - BLE wrong connections intervals on multible connections * :github:`36093` - Fix dt_compat_enabled_with_label behavior (or usage) * :github:`36089` - intel_adsp_cavs25: support more than 2 DSP cores * :github:`36088` - intel_adsp_cavs25: secondary boot fails in arch_start_cpu() * :github:`36084` - Arduino Nano 33 BLE: USB gets disconnected after flashing * :github:`36078` - coredump.logging_backend: lpcxpresso55s28: test failure assertion fail * :github:`36077` - net: lib: coap: Impossible to get socket info from incoming packet * :github:`36075` - drivers: can: stm32fd: can2 does not work * :github:`36074` - LoRaWAN: sx126x: infinite loop on CRC error * :github:`36061` - Undefined reference to ``z_priq_rb_lessthan(rbnode, rbnode)`` when using k_timer_start in cpp file. * :github:`36057` - Zephyr Shell Console and Logging Targeting Isolated Different Device Interfaces * :github:`36048` - Cannot establish ISO CIS connection properly after ACL disconnected several times * :github:`36038` - iotdk: the testcase samples/modules/nanopb can't build * :github:`36037` - bt_init returning success when Bluetooth initialization does not get finalized. * :github:`36035` - struct devices should be allocated in ROM, not RAM * :github:`36033` - Mere warnings slow down incremental documentation build from seconds to minutes * :github:`36030` - West warnings (and others?) are ignored when building documentation * :github:`36028` - More Description in Example Documentation * :github:`36026` - wolfssl / wolfcrypt * :github:`36022` - Wrong channel index in connectionless IQ samples report * :github:`36014` - stm32g050: Missing closing parenthesis for soc prototype * :github:`36013` - arm: qemu: run cmsis-dsp tests on the qemu target with FPU * :github:`35999` - Unexpected Bluetooth disconnection and removal of bond * :github:`35992` - stm32f303k8 device tree missing DACs * :github:`35986` - POSIX: multiple definition of posix_types * :github:`35983` - [backport v1.14-branch] backport of #35935 failed * :github:`35978` - ESP32 SPI send data hangup * :github:`35972` - C++ exceptions do not work when building with GNU Arm Embedded * :github:`35971` - ehl_crb: test_nop is failing under tests/kernel/common/ * :github:`35970` - up_squared: samples/boards/up_squared/gpio_counter/ is failing * :github:`35964` - shell_uart hangs when putting UART into PM_LOW_POWER_STATE / PM_DEVICE_STATE_LOW_POWER * :github:`35962` - drivers using deprecated Kconfigs * :github:`35955` - Bluetooth: Controller: Regression in connection setup * :github:`35949` - can: mcan: sjw-data devicetree configuration is not written correctly * :github:`35945` - SPI4 on nRF5340 not working when using k_sleep() in main * :github:`35941` - subsys: tracing: sysview: No SEGGER_SYSVIEW.h in path * :github:`35939` - enc424j600 driver unusable/broken on stm32l552 * :github:`35931` - Bluetooth: controller: Assertion in ull_master.c * :github:`35930` - nRF Dongle as BLE Central Unstable Connectivity at Long-ish Range * :github:`35926` - Shell tab-completion with more than two levels of nested dynamic commands fails * :github:`35916` - drivers: TI cc13xx_cc26xx: build error when PM is enabled (serial, entropy, spi, i2c modules) * :github:`35908` - Stopping DHCP with network interface goes down leaves networking state in a broken state * :github:`35897` - Bluetooth: PTS Tester on native posix * :github:`35890` - Build system ignores explicit ZephyrBuildConfiguration_ROOT variable * :github:`35880` - PSA tests run indefinitely when CONFIG_TFM_IPC=y * :github:`35870` - Build failure with gcc 11.x on native_posix * :github:`35857` - intel_adsp_cavs15: run msgq testcases failed on ADSP * :github:`35856` - intel_adsp_cavs15: run semaphore testcases failed on ADSP * :github:`35850` - the sample kernel/metairq_dispatch fails on nucleo_g474re * :github:`35835` - ADC support for STM32l496_disco board * :github:`35809` - sample: USB audio samples are not working on STM32 * :github:`35793` - kernel.scheduler.multiq: Failed since #35276 ("cooperative scheduling only" special cases removal) * :github:`35789` - sockets_tls: receiving data on offloaded socket before handshake causes pollin \| pollerr and failed recvfrom (SARA-R4) * :github:`35721` - Atmel sam0 Async and/or DMA may not work * :github:`35720` - tests:kernel timer fails on test_sleep_abs with TICKLESS_KERNEL and PM on nucleo_wb55rg * :github:`35718` - Excessive error messages from filesystem interface * :github:`35711` - net: sockets: dtls: handshake not reset as it ought to be * :github:`35707` - AssertionError: zephyr/tests/kernel/common test case is failing with gcc-11 (Yocto) * :github:`35703` - posix_apis: fails at test_posix_realtime for mimxrt1024_evk * :github:`35681` - Unable to get output for samples/subsys/logging/logger and samples/philosophers * :github:`35668` - The channel selection of auxiliary advertisments in extended advertisments * :github:`35663` - STM32H7: Support memory protection unit(MPU) to enable shared memory * :github:`35658` - arch.interrupt.arm.irq_vector_table.arm_irq_vector_table: MPU FAULT Halting system for mximxrt685_evk_cm33 * :github:`35656` - arch.interrupt.arm.arm_interrupt: hangs on mimxrt685_evk_cm33 * :github:`35581` - stm32 SPI problems with DMA and INTR set-up * :github:`35550` - nRF91: DPS310 I2C driver not working * :github:`35532` - SSL Handshake error with modified http(s) client example * :github:`35529` - STM32: STM32H7 ADC calibration must be performed on startup * :github:`35429` - subsys: settings: Encryption * :github:`35377` - add creg_gpio driver for ARC HSDK board * :github:`35354` - Adding support for measurement of Ultraviolet(UV) Light. * :github:`35293` - Sporadic boot failure * :github:`35256` - DOC: DATA PASSING TABLE MISSING THE OBJECT QUEUES * :github:`35250` - Twister is not reading the serial line output completely * :github:`35244` - twister: build failure for native_posix with GNU binutils 2.35 * :github:`35238` - ieee802.15.4 support for stm32wb55 * :github:`35229` - twister log mixing between tests * :github:`35190` - echo_server sample non-functional rails all CPUs on native_posix_64 board build * :github:`35055` - STM32L432KC Nucleo Reference board SWD problem after programming with Zephyr * :github:`34917` - arch.interrupt.arm\| arch.interrupt.extra_exception_info: lpcxpresso55s28 series: test failure * :github:`34913` - ModuleNotFoundError: No module named 'elftools' * :github:`34879` - mec15xxevb_assy6853: 2 GPIO test failures * :github:`34855` - FANSTEL BT840X * :github:`34832` - Coding Guideline - MISRA rule 14.4 not applied properly * :github:`34829` - Bluetooth: ISO: Don't attempt to remove the ISO data path of a disconnected ISO channel * :github:`34767` - C++ support on ESP boards * :github:`34760` - Hawkbit not downloading large files * :github:`34659` - Bluetooth: HCI cmd response timeout * :github:`34571` - Twister mark successfully passed tests as failed * :github:`34557` - upgrade fatfs to 0.14b * :github:`34554` - Settings FS: Duplicate finding is extremely slow when dealing with larger number of settings entries * :github:`34544` - lib: gui: lvgl: buffer overflow bug on misconfiguration * :github:`34543` - STM32F1 failed to compile with CONFIG_UART_ASYNC_API * :github:`34392` - [backport v2.5-branch] backport of #34237 failed * :github:`34391` - [backport v1.14-branch] backport of #34237 failed * :github:`34390` - i2s: bitrate is wrongly configured on STM32 * :github:`34372` - CPU Lockups when using own Log Backend * :github:`34354` - Please investigate adding DMA support to STM32 I2C! * :github:`34324` - RTT is not working on STM32 * :github:`34315` - BMI270 configuration file sending to I2C seems to be not handling the last part of the configuration properly. * :github:`34305` - Shell [modem send] command causes shell to hang after about 10 seconds, Sara R4 - Particle Boron * :github:`34282` - HAL Module Request: hal_telink * :github:`34273` - mqtt_publisher: Unable to connect properly on EC21 modem with bg9x driver * :github:`34269` - LOG_MODE_MINIMAL BUILD error * :github:`34268` - Bluetooth: Mesh: Sample is stuck in init process on disco_l475_iot * :github:`34259` - Problem running code with memory domain * :github:`34239` - Call settings_save_one in the system work queue, which will cause real-time performance degradation. * :github:`34236` - External source code integration request: Raspberry Pi Pico SDK * :github:`34231` - uzlib (decompression library) * :github:`34226` - Compile error when building civetweb http_server sample for posix_native * :github:`34222` - Commit related to null pointer exception detection causing UART issues * :github:`34218` - Civetweb server crashing when trying to access invalid resource * :github:`34204` - nvs_write: Bad documented return value. * :github:`34192` - Sensor BME680: Add support for SPI operation * :github:`34134` - USB do not works if bootloader badly use the device before * :github:`34131` - TFTP client ignores incoming data packets * :github:`34121` - Unable to generate pdf according to the documentation steps on windows * :github:`34105` - Convert tests/kernel/workq to new kwork API * :github:`34049` - Nordic nrf9160 switching between drivers and peripherals * :github:`34015` - cfb sample "Device not found" for esp32 when SSD1306 is enabled * :github:`33994` - kscan_ft5336 doesn't provide proper up/down information when polling, and hogs resources in interrupt mode * :github:`33960` - Zephyr for Briey SoC * :github:`33937` - [backport v1.14-branch] backport of #26712 failed * :github:`33932` - [backport v1.14-branch] backport of #26083 failed * :github:`33910` - sam_v71_xult -> I2C_1 hang during scanning i2c devices * :github:`33901` - tests: interrupt: irq_enable() and irq_disable() do not work with direct and regular interrupt on x86 * :github:`33895` - Device tree: STM32L412 and STM32L422 are missing nodes * :github:`33883` - [backport v2.5-branch] backport of #33340 failed * :github:`33876` - Lora sender sample build error for esp32 * :github:`33873` - arm_arch_timer: Too many clock announcements with CONFIG_TICKLESS_KERNEL=n on SMP * :github:`33862` - [backport v2.5-branch] backport of #33771 failed * :github:`33753` - LVGL output doesn't match the LVGL TFT simulator for gauge widget * :github:`33652` - Monitoring the BLE connection * :github:`33573` - JSON_OBJ_DESCR_ARRAY_ARRAY is dangerously broken * :github:`33554` - Request to add OM13056 board (LPC1500 family or specifically SoC LPC1519) support to Zephyr * :github:`33544` - ehl_crb: portability.posix.common.posix_realtime failed. * :github:`33485` - Issue with DMA transfers outside of the Zephyr DMA driver on STM32F767 * :github:`33483` - TIMESLICE and PM interaction and expected behavior * :github:`33449` - Remove deprecated items in 2.7 * :github:`33440` - lsm6dso sensor driver not working on nRF5340 * :github:`33435` - armclang / armlinker * :github:`33337` - twister: Find and fix all "dead" samples/tests * :github:`33275` - ehl_crb: samples/subsys/shell/shell_module does not work * :github:`33265` - Power Management Overhaul * :github:`33192` - LoRaWAN - Application fails to start if module is not powered * :github:`33113` - Improve code coverage for new feature or code change in kernel * :github:`33104` - Updating Zephyr to fix Work Queue Problems * :github:`33099` - ppp: termination packet not sent * :github:`33052` - [Coverity CID :219624] Untrusted loop bound in subsys/bluetooth/host/sdp.c * :github:`33041` - [Coverity CID :219645] Untrusted loop bound in subsys/bluetooth/host/sdp.c * :github:`33016` - spi_nor: CONFIG_SPI_NOR_SFDP_RUNTIME leaves flash in Standby after spi_nor_configure() * :github:`33015` - spi_nor driver: SPI_NOR_IDLE_IN_DPD breaks SPI_NOR_SFDP_RUNTIME * :github:`32997` - Improve documentation search experience * :github:`32990` - FS/littlefs: it is possible to write to already deleted file * :github:`32984` - West: openocd runner: Don't let debug mode on by default * :github:`32875` - Benchmarking Zephyr vs. RIOT-OS * :github:`32836` - Remaining integration failures on intel_adsp_cavs15 * :github:`32822` - Code doesn't compile after changing the PWM pin on example "blinky_pwm" on NRF52 * :github:`32803` - Extend mcux uart drivers to support async API * :github:`32789` - USB DFU support w/o MPU support * :github:`32733` - RS-485 support * :github:`32669` - [Bluetooth] sample code for Periodic Advertising Sync Transfer * :github:`32603` - acrn_ehl_crb: test case of arch.interrupt.prevent_interruption failed * :github:`32564` - net_buf reference count not protected * :github:`32545` - It seems that CONFIG_IMG_MGMT_VERBOSE_ERR does not work * :github:`32531` - get_maintainer.py cannot parse MAINTAINERS.yml * :github:`32293` - Zephyr 2.6 Release Checklist * :github:`32289` - USDHC: Fails after reset * :github:`32282` - x86 ACPI images are much too large * :github:`32261` - problem with CONFIG_STACK_SENTINEL * :github:`32133` - Current atomics are subtly broken on AArch64 due to memory ordering * :github:`32111` - Zephyr build fail with LLVM on Windows * :github:`32035` - Bluetooth: application notification when MTU updated * :github:`31993` - Add west extension to parse yml file * :github:`31985` - riscv: Long execution time when TICKLESS_KERNEL=y * :github:`31943` - drivers: flash: stm32: harmonization of flash erase implementation across STM32 series * :github:`31739` - Convert CoAP unit tests to use ztest API * :github:`31593` - civetweb hangs when there are no free filedescriptors * :github:`31499` - lwm2m : Add visibility into observer notification success/fail * :github:`31475` - TCP keepalive * :github:`31473` - Failed phy request not retried and may prevent DLE procedure during auto-initiation * :github:`31447` - MQTT idling gets disconnected when using TCP2 * :github:`31290` - dts: arm: st: standardize pwm default property st,prescaler to 0 * :github:`31253` - lis3dh driver support is confusing * :github:`31162` - Mapping between existing and new system power management states * :github:`31107` - libc: minimal: add qsort routine * :github:`31043` - Infinite loop in modem cmd_handler_process * :github:`30921` - west flash failed with an open ocd error * :github:`30861` - drivers: uart: increase timeout precision in uart_rx_enable * :github:`30635` - cpu_stats: Change from printk to ``LOG_`` :github:`30429` - Thread Border Router with NRC/RCP sample and nrf52840dk not starting * :github:`30367` - TCP2 does not send our MSS to peer * :github:`30245` - Bluetooth: controller: event scheduling pipeline preemption by short schedule * :github:`30244` - Bluetooth: controller: Extended scan window time reservation prevents auxiliary channel reception * :github:`30243` - Bluetooth: controller: IRK resolution in extended scanning breaks auxiliary PDU reception * :github:`30236` - Main thread sometimes looping forever before user application is reached when using UDP and IPv6 on Nucleo F767ZI * :github:`30209` - TCP2 : How to add MSS option on sending [SYN, ACK] to client? * :github:`30066` - CI test build with RAM overflow * :github:`30026` - Can not make multiple BLE IPSP connection to the same host * :github:`29545` - samples: tfm_integration: tfm_ipc: No module named 'cryptography.hazmat.primitives.asymmetric.ed25519' * :github:`29535` - riscv: stack objects are mis-aligned * :github:`29520` - make k_current_get() work without a system call * :github:`29397` - Build all tests of module mcuboot * :github:`28872` - Support ESP32 as Bluetooth controller * :github:`28819` - memory order and consistency promises for Zephyr atomic API? * :github:`28729` - ARM: Core Stack Improvements/Bug fixes for 2.6 release * :github:`28716` - 2.5 Release Checklist * :github:`28312` - Add option to enable ART Accelerator on STM32 FLASH controller * :github:`27992` - stm32f7: usb: Bursting HID Get and Set report requests leads to unresponding Control endpoint. * :github:`27525` - Including STM32Cube's USB PD support to Zephyr * :github:`27415` - Decide if we keep a single thread support (CONFIG_MULTITHREADING=n) in Zephyr * :github:`27176` - [v1.14] Restore socket descriptor permission management * :github:`27015` - Add custom transport support for MQTT * :github:`26981` - Problem with PPP + GSM MUX with SIMCOM7600E * :github:`26585` - IPv4 multicast datagrams can't be received for mimxrt1064_evk board (missing ethernet API) * :github:`26256` - NRF51822 BLE Micro module: hangs on k_msleep() (RTC counter not working) * :github:`26136` - CMake Error in Windows Environment * :github:`26051` - shell: uart: Allow a change in the shell initalisation to let routing it through USB UART * :github:`25832` - [test][kernel][lpcxpresso55s69_ns] kernel cases meet ESF could not be retrieved successfully * :github:`25182` - Raspberry Pi 4B Support * :github:`25015` - Bluetooth Isochronous Channels Support * :github:`24854` - docs: Using third-party libraries not well documented in Memory partitions docs * :github:`24733` - Misconfigured environment * :github:`24200` - USB GET_INTERFACE response always 0, even when an alternate setting is used * :github:`24051` - double to sensor_val * :github:`23745` - Align PS/2 handlers with the handlers found in other drivers * :github:`23723` - Poor sinf/cosf performance compared to the Segger math libraries * :github:`23349` - Question: How to add external soc, board, DTS, drivers and libs? * :github:`22731` - Improve docker CI documentation * :github:`22705` - Implement counter driver for lpcxpresso55s69 * :github:`22702` - Implement I2S driver for lpcxpresso55s69 * :github:`22455` - How to assign USB endpoint address manually in stm32f4_disco for CDC ACM class driver * :github:`22210` - Bluetooth - bt_gatt_get_value_attr_by_uuid * :github:`22131` - ARM Cortex_R: CONFIG_USERSPACE: external interrupts are disabled during system calls * :github:`21869` - IPv6 neighbors get added too eagerly * :github:`21648` - improve documentation on meta-IRQ threads * :github:`21519` - RFC: libc: thread-safe newlib * :github:`21339` - Expired IPv6 router causes an infinite loop * :github:`21293` - adding timeout the I2C read/write functions for the stm32 port * :github:`21205` - get_device_list only available if power management invoked * :github:`21167` - libraries.libc.newlib test fails * :github:`20576` - DTS overlay files must include full path name * :github:`20409` - USB: Create webusb shell * :github:`20236` - usb: api: Cleanup of current inclusion path for USB * :github:`20171` - support external spi nor flash on mimxrt1060-evk * :github:`19882` - Add support for multiple channel sampling to STM32 ADC driver * :github:`19328` - Logger could block in thread at certain log message pool usage * :github:`18960` - [Coverity CID :203908]Error handling issues in /lib/libc/newlib/libc-hooks.c * :github:`18896` - Concurrent Multi-Protocol Support NRF52840 * :github:`18850` - Bluetooth: controller: Advertiser following directed advertiser will have corrupt data * :github:`18386` - [Coverity CID :203443]Memory - corruptions in /subsys/bluetooth/host/rfcomm.c * :github:`18351` - logging: 32 bit float values don't work. * :github:`18316` - Support for unregistering bt_conn callbacks * :github:`18042` - Only corporate members can join the slack channel * :github:`17748` - stm32: clock-control: Remove usage of SystemCoreClock * :github:`17692` - Proper way for joining a multicast group (NRF52840/OpenThread) * :github:`17375` - Add VREF, TEMPSENSOR, VBAT internal channels to the stm32 adc driver * :github:`17021` - revise concurrency control in kernel/userspace.c * :github:`16761` - nrf52840 usb driver with openthread * :github:`16671` - ideas for future of the settings * :github:`16231` - Add CONFIG_UART_DYNAMIC_SETTINGS option * :github:`15841` - Support AT86RF233 * :github:`15793` - Unable to load binaries into iotdk * :github:`15676` - Support instrumentation for time spent in various power states * :github:`15555` - Counter Docs Missing Callback Context Note * :github:`14308` - Better integration between system and device power modes. * :github:`12405` - add test to catch issues fixed in PR #12384 * :github:`11773` - Add Bluetooth support for Silicon Labs EFR32MG12 * :github:`11702` - Add support for nrfx i2s driver * :github:`11519` - Add at least build test for cc1200 * :github:`11193` - ARM V8M Trusted Execution Environments and Zephyr * :github:`11028` - CONFIG_LOAPIC_SPURIOUS_VECTOR not being tested * :github:`11000` - USB 2.0 high-speed support in Zephyr * :github:`10930` - Extending string formatting function * :github:`10676` - Feature Required: DFU over Thread network * :github:`10378` - watchdog: Limitation with the current watchdog API for Nordic devices * :github:`10324` - Publish PDF with the release doc build * :github:`10198` - Add support for FRDM-STBC-AGM01 sensor shield * :github:`8876` - Adapt net/l2/ieee802154 subsystem to new shell subsystem * :github:`8275` - when zephyr can support popular IDE develop? * :github:`7001` - ST Sensors: Driver factorization * :github:`6777` - Add copyright handling to contributing doc * :github:`6657` - Question: Is Bluetooth avrcp supported in Zephyr? Or any plan? * :github:`6493` - need APIs for ranged random number generation * :github:`6450` - Several devices of same type on same bus - how to address? * :github:`6117` - Make sanitycheck aware of DTS and HW support * :github:`4911` - Filesystem support for qemu * :github:`1392` - No module named 'elftools' * :github:`3886` - Add mutual authentication to net/crypto examples * :github:`3885` - Add real entropy to crypto-based net samples * :github:`3884` - Improve the TLS and DTLS examples to use best practices on security * :github:`3879` - k_thread_abort vs k_thread->fn_abort() * :github:`3677` - Implement HCI Zephyr extensions * :github:`3199` - xtensa: simplify linker scripts * :github:`2811` - Investigate having timeout code track tick deadlines instead of deltas * :github:`2619` - Define APIs for hashing/ Message Authentication * :github:`2248` - Split LE Controller: style fixes ```	/content/code_sandbox/doc/releases/release-notes-2.7.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	32,711
```restructuredtext :orphan: .. _zephyr_2.6: Zephyr 2.6.0 ############ We are pleased to announce the release of Zephyr RTOS version 2.6.0. Major enhancements with this release include: * Logging subsystem overhauled * Added support for 64-bit ARCv3 * Split ARM32 and ARM64, ARM64 is now a top-level architecture * Added initial support for Arm v8.1-m and Cortex-M55 * Removed legacy TCP stack support which was deprecated in 2.4 * Tracing subsystem overhaul including expansion for tracing points and added support for Percepio Tracealyzer * Device runtime power management (PM), former IDLE runtime, was completely overhauled. * Added an example standalone Zephyr application in its own Git repository: path_to_url 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: path_to_url * CVE-2021-3581: Under embargo until 2021-09-04 Known issues ********** You can check all currently known issues by listing them using the GitHub interface and listing all issues with the `bug label <path_to_url`_. API Changes ********* * Driver APIs now return ``-ENOSYS`` if optional functions are not implemented. If the feature is not supported by the hardware ``-ENOTSUP`` will be returned. Formerly ``-ENOTSUP`` was returned for both failure modes, meaning this change may require existing code that tests only for that value to be changed. * The :c:func:`wait_for_usb_dfu` function now accepts a ``k_timeout_t`` argument instead of using the ``CONFIG_USB_DFU_WAIT_DELAY_MS`` macro. * Added disconnect reason to the :c:func:`disconnected` callback of :c:struct:`bt_iso_chan_ops`. * Align error handling of :c:func:bt_l2cap_chan_send and :c:func:`bt_iso_chan_send` so when an error occur the buffer is not unref. * Added :c:func:`lwm2m_engine_delete_obj_inst` function to the LwM2M library API. Deprecated in this release * :c:macro:`DT_CLOCKS_LABEL_BY_IDX`, :c:macro:`DT_CLOCKS_LABEL_BY_NAME`, :c:macro:`DT_CLOCKS_LABEL`, :c:macro:`DT_INST_CLOCKS_LABEL_BY_IDX`, :c:macro:`DT_INST_CLOCKS_LABEL_BY_NAME`, and :c:macro:`DT_INST_CLOCKS_LABEL` was deprecated in favor of utilizing :c:macro:`DT_CLOCKS_CTLR` and variants. * :c:macro:`DT_PWMS_LABEL_BY_IDX`, :c:macro:`DT_PWMS_LABEL_BY_NAME`, :c:macro:`DT_PWMS_LABEL`, :c:macro:`DT_INST_PWMS_LABEL_BY_IDX`, :c:macro:`DT_INST_PWMS_LABEL_BY_NAME`, and :c:macro:`DT_INST_PWMS_LABEL` was deprecated in favor of utilizing :c:macro:`DT_PWMS_CTLR` and variants. * :c:macro:`DT_IO_CHANNELS_LABEL_BY_IDX`, :c:macro:`DT_IO_CHANNELS_LABEL_BY_NAME`, :c:macro:`DT_IO_CHANNELS_LABEL`, :c:macro:`DT_INST_IO_CHANNELS_LABEL_BY_IDX`, :c:macro:`DT_INST_IO_CHANNELS_LABEL_BY_NAME`, and :c:macro:`DT_INST_IO_CHANNELS_LABEL` were deprecated in favor of utilizing :c:macro:`DT_IO_CHANNELS_CTLR` and variants. * :c:macro:`DT_DMAS_LABEL_BY_IDX`, :c:macro:`DT_DMAS_LABEL_BY_NAME`, :c:macro:`DT_INST_DMAS_LABEL_BY_IDX`, and :c:macro:`DT_INST_DMAS_LABEL_BY_NAME` were deprecated in favor of utilizing :c:macro:`DT_DMAS_CTLR` and variants. * USB HID specific macros in ``<include/usb/class/usb_hid.h>`` are deprecated in favor of new common HID macros defined in ``<include/usb/class/hid.h>``. * USB HID Kconfig option USB_HID_PROTOCOL_CODE is deprecated. USB_HID_PROTOCOL_CODE does not allow to set boot protocol code for specific HID device. USB HID API function usb_hid_set_proto_code() can be used instead. * USB HID class API is changed by removing get_protocol/set_protocol and get_idle/set_idle callbacks. These callbacks are redundant or do not provide any additional value and have led to incorrect usage of HID class API. * The ``CONFIG_OPENOCD_SUPPORT`` Kconfig option has been deprecated in favor of ``CONFIG_DEBUG_THREAD_INFO``. * Disk API header ``<include/disk/disk_access.h>`` is deprecated in favor of ``<include/storage/disk_access.h>``. * :c:func:`flash_write_protection_set()`. * The ``CONFIG_NET_CONTEXT_TIMESTAMP`` is removed as it was only able to work with transmitted data. The same functionality can be achieved by setting ``CONFIG_NET_PKT_RXTIME_STATS`` and ``CONFIG_NET_PKT_TXTIME_STATS`` options. These options are also able to calculate the RX & TX times more accurately. This means that support for the SO_TIMESTAMPING socket option is also removed as it was used by the removed config option. * The device power management (PM) APIs and data structures have been renamed from ``device_pm_`` to ``pm_device_`` since they are not device APIs but PM subsystem APIs. The same applies to enumerations and definitions, they now follow the ``PM_DEVICE_`` convention. Some other API calls such as ``device_set_power_state`` and ``device_get_power_state`` have been renamed to ``pm_device_state_set`` and ``pm_device_state_get`` in order to align with the naming of other device PM APIs. The runtime device power management (PM) APIs is now synchronous by default and the asynchronous API has the _async sufix. This change aligns the API with the convention used in Zephyr. The affected APIs are ``pm_device_put`` and ``pm_device_get``. * The following functions, macros, and structures related to the kernel work queue API: * :c:func:`k_work_pending()` replace with :c:func:`k_work_is_pending()` * :c:func:`k_work_q_start()` replace with :c:func:`k_work_queue_start()` * :c:struct:`k_delayed_work` replace with :c:struct:`k_work_delayable` * :c:func:`k_delayed_work_init()` replace with :c:func:`k_work_init_delayable` * :c:func:`k_delayed_work_submit_to_queue()` replace with :c:func:`k_work_schedule_for_queue()` or :c:func:`k_work_reschedule_for_queue()` * :c:func:`k_delayed_work_submit()` replace with :c:func:`k_work_schedule()` or :c:func:`k_work_reschedule()` * :c:func:`k_delayed_work_pending()` replace with :c:func:`k_work_delayable_is_pending()` * :c:func:`k_delayed_work_cancel()` replace with :c:func:`k_work_cancel_delayable()` * :c:func:`k_delayed_work_remaining_get()` replace with :c:func:`k_work_delayable_remaining_get()` * :c:func:`k_delayed_work_expires_ticks()` replace with :c:func:`k_work_delayable_expires_get()` * :c:func:`k_delayed_work_remaining_ticks()` replace with :c:func:`k_work_delayable_remaining_get()` * :c:macro:`K_DELAYED_WORK_DEFINE` replace with :c:macro:`K_WORK_DELAYABLE_DEFINE` ========================== Removed APIs in this release * Removed support for the old zephyr integer typedefs (u8_t, u16_t, etc...). * Removed support for k_mem_domain_destroy and k_mem_domain_remove_thread * Removed support for counter_read and counter_get_max_relative_alarm * Removed support for device_list_get ============================ Stable API changes in this release ================================== Kernel ****** * Added :c:func:`k_mem_unmap()` so anonymous memory mapped via :c:func:`k_mem_map()` can be unmapped and virtual address reclaimed. * Added the ability to gather more statistics for demand paging, including execution time histograms for eviction algorithms and backing stores. Architectures ************* * ARC * Added new ARCv3 64bit ISA support and corresponding HS6x processor support * Hardened SMP support * Various minor fixes/improvements for ARC MWDT toolchain infrastructure * Refactor of ARC Kconfig * ARM * AARCH32 * Added support for null pointer dereferencing detection in Cortex-M. * Added initial support for Arm v8.1-m and Cortex-M55. * Added support for preempting threads while they are performing secure calls in Cortex-M. * Added support for memory region generation by the linker based on device tree node information in Cortex-M. * Cleaned up definitions of SoC-specific memory regions in the common Cortex-M linker script. * Added support for clearing NXP MPU region configuration during Zephyr early boot stage. * Disallowed fpu hard ABI when building Non-Secure applications with TF-M on Cortex-M33. * Enhanced register information dump in fault exceptions in Cortex-R. * Fixed spurious interrupt handling in Cortex-R. * AARCH64 * SMP support * MMU dynamic mappings with page table sharing. * Userspace (unprivileged) thread support. * Standalone SMCCC support. * XIP support. * ARM64 is now a top-level standalone architecture. * Support for Cortex-R82 and Armv8-R AArch64 MPU. * Cache management support. * Revamped boot code. * Full FPU context switching. * x86 * Added SoC configuration for Lakemont SoC. * Removed kconfig ``CONFIG_CPU_MINUTEIA`` as there is no user of this option. * Renamed kconfig ``CONFIG_SSE`` to ``CONFIG_X86_SSE``. * Extended the pagetable generation script to allow specifying additional memory mapping during build. * x86-32 * Added support for kernel image to reside in virtual address space, allowing code execution and data manipulation via virtual addresses. Bluetooth ********* * Audio * Split up ISO handling from audio handling, and moved the latter to its own directory. * Added the Volume Offset Control Service and client. * Added the Audio Input Control Service and client. * Added the Volume Control Service and client. * Host * Added basic support for Direction Finding. * Added support for CTE connectionless transimission and reception over periodic advertising. * Refactored the HCI and ECC handling implementations. * Stopped auto updating the device name in the adv data. * Added support for logging security keys to be used by an air sniffer. * Fixed a bonding issue where the local bond data was not being updated after the remote device had removed it when the peer was not using the IRK stored in the bonding information. * Implemented the directory listing object to OTS. * Added a function to access the ``bt_conn_iso`` object. * Added a new configuration option for writeable device name. * Added a new configuration option for minimum encryption key size. * Added support for keypress notifications as an SMP responder. * Added a new option, ``BT_LE_ADV_OPT_FORCE_NAME_IN_AD``, which forces the device name to appear in the adv packet instead of the scan response. * Added a security level check when sending a notification or indication. * Added the ability to send HCI monitor traces over RTT. * Refactored the Bluetooth buffer configuration for simplicity. See the commit message of 6483e12a8ac4f495b28279a6b84014f633b0d374 for more info. Note however that the aforementioned commit message has two typos; * ``BT_CTLR_TX_BUFFER`` should be ``BT_CTLR_TX_BUFFERS`` * ``BT_CTLR_TX_BUFFERS_SIZE`` should be ``BT_CTLR_TX_BUFFER_SIZE`` * Added support for concurrent advertising with multiple identities. * Changed the logic to disable scanning before setting the random address. * Fixed a crash where an ATT timeout occurred on a disconnected ATT channel. * Changed the pairing procedure to fail pairing when both sides have the same public key. * Fixed an issue where GATT requests could deadlock the RX thread. * Fixed an issue where a fixed passkey that was previously set could not be cleared. * Fixed an issue where callbacks for "security changed" and "pairing failed" were not always called. * Changed the pairing procedure to fail early if the remote device could not reach the required security level. * Fixed an issue where GATT notifications and Writes Without Response could be sent out of order. * Changed buffer ownership of ``bt_l2cap_chan_send``. The application must now release the buffer for all returned errors. * Mesh * Added CDB handle key refresh phase. * Added the ability to perform replay checks on SeqAuth. * Added the sending of a Link Close message when closing a link. * Added a Proxy callback structure for Node ID enabling and disabling. * Added a check for the response address in the Configuration Client. * Introduced a new acknowledged messages API. * Reworked the periodic publication timer and poll timeout scheduling logic. * Added reporting configured ``LPNTimeout`` in ``cfg_srv``. * Ensured that provisioning output count number is at least 1. * Ensured to encrypt initial friend poll with friend credentials. * Stopped resetting the PB ADV reliable timer on retransmission. * Bluetooth LE split software Controller * Removed support for the nRF5340 PDK. Use the nRF5340 DK instead. * Added basic support for Direction Finding. * Added support for CTE connectionless transimission and reception over periodic advertising. * Added support for antenna switching in the context of Direction Finding. * Added an invalid ACL data length check. * Added basic support for the ISO Adaptation Layer. * Added experimental support for Broadcast Isochronous Groups and Streams. * Added partial experimental support for Connected Isochronous Groups and Streams. * Implemented extended connection creation and cancellation. * Changed the policy to ignore connection requests from an already-connected peer. * Added a control procedure locking system. * Added GPIO PA/LNA support for the Nordic nRF53x SoC series. * Added FEM support for the nRF21540 IC. * Added a new radio API to configure the CTE RX path. * HCI Driver * Added support for the Espressif ESP32 platform. Boards & SoC Support ******************** * Added support for these SoC series: * STM32F205xx * STM32G03yxx, STM32G05yxx, STM32G070xx and STM32G0byxx * STM32G4x1, STM32G4x3 and STM32G484xE * STM32WL55xx * Nuvoton npcx7m6fc, and npcx7m6fc * Renesas R-Car Gen3 * Silicon Labs EFR32FG13P * ARM MPS3-AN547 * ARM FVP-AEMv8A * ARM FVP-AEMv8R * NXP LS1046A * X86 Lakemont * Removed support for these SoC series: * ARM Musca-A * Made these changes in other SoC series: * Added Cypress PSoC-6 pinctrl support. * STM32 L4/L5/WB series were updated for better power management support (CONFIG_PM=y). * Backup SRAM added on a selection of STM32 series (F2/F4/F7/H7) * Set TRACE_MODE to asynchronous and enable trace output pin on STM32 SoCs * Changes for ARC boards: * Added nSIM and QEMU simulation boards (nsim_hs6x and qemu_arc_hs6x) with ARCv3 64bit HS6x processors * Enabled MPU on qemu_arc_hs and qemu_arc_em boards * Added cy8c95xx GPIO expander support to HSDK board * Added support for these ARM boards: * Actinius Icarus * Actinius Icarus SoM * Laird Connectivity BL654 Sensor Board * Laird Connectivity Sentrius BT6x0 Sensor * EFR32 Radio BRD4255A Board * MPS3-AN547 * RAK4631 * Renesas R-Car H3ULCB * Ronoth LoDev (based on AcSIP S76S / STM32L073) * nRF9160 Thing Plus * ST Nucleo F030R8 * ST Nucleo G0B1RE * ST Nucleo H753ZI * ST Nucleo L412RP-P * ST Nucleo WL55JC * ST STM32G071B Discovery * Thingy:53 * u-blox EVK-BMD-30/35: BMD-300-EVAL, BMD-301-EVAL, and BMD-350-EVAL * u-blox EVK-BMD-330: BMD-330-EVAL * u-blox EVK-BMD-34/38: BMD-340-EVAL and BMD-341-EVAL * u-blox EVK-BMD-34/38: BMD-345-EVAL * u-blox EVK-BMD-360: BMD-360-EVAL * u-blox EVK-BMD-34/48: BMD-380-EVAL * u-blox EVK-ANNA-B11x * u-blox EVK NINA-B11x * u-blox EVK-NINA-B3 * u-blox EVK NINA-B40x * Added support for these ARM64 boards: * fvp_base_revc_2xaemv8a * fvp_baser_aemv8r * nxp_ls1046ardb * Removed support for these ARM boards: * ARM V2M Musca-A * Nordic nRF5340 PDK * Removed support for these X86 boards: * up_squared_32 * qemu_x86_coverage * minnowboard * Made these changes in other boards: * cy8ckit_062_ble: Refactored to configure by pinctrl. * cy8ckit_062_ble: Added support to SCB[uart] with interrupt. * cy8ckit_062_ble: Added support to SCB[spi]. * cy8ckit_062_ble: Added board revision schema. * cy8ckit_062_wifi_bt: Refactored to configure by pinctrl. * cy8ckit_062_wifi_bt: Added support to SCB[uart] with interrupt. * lpcxpresso55s16: Board renamed from lpcxpresso55s16_ns to lpcxpresso55s16 since the board does not have Trusted Firmware M (TF-M) support. * lpcxpresso55s28: Removed lpcxpresso55s28_ns config since the board does not have Trusted Firmware M (TF-M) support. * mimxrt685_evk: Added support for octal SPI flash storage, LittleFS, I2S, OS timer, and power management. * mimxrt1060_evk: Added support for QSPI flash storage, LittleFS, and mcuboot. * mimxrt1064_evk: Added support for mcuboot. * Added support for these following shields: * FTDI VM800C Embedded Video Engine Board * Generic ST7735R Display Shield * NXP FRDM-STBC-AGM01 * Semtech SX1272MB2DAS LoRa Shield Drivers and Sensors ******************* * ADC * Added support on TI CC32xx. * Added support on ITE IT8xxx2. * Added support for DMA and HW triggers in the MCUX ADC16 driver. * Added ADC emulator. * Moved definitions of ADC acquisition time macros so that those macros can be used in dts files. * Bluetooth * The Kconfig option ``CONFIG_BT_CTLR_TO_HOST_UART_DEV_NAME`` was removed. Use the :ref:`zephyr,bt-c2h-uart chosen node <devicetree-chosen-nodes>` directly instead. * CAN * A driver for CAN-FD based on the Bosch M_CAN IP was added. The driver currently supports STM32G4 series MCUs. Additional support for Microchip SAM and NXP chips is in progress. * The CAN ISO-TP subsystem was enhanced to allow padding and fixed addressing. * Clock Control * On STM32 series, system clock configuration has been moved from Kconfig to DTS. Usage of existing Kconfig dedicated symbols (CONFIG_CLOCK_STM32_FOO) is now deprecated. * Added clock control driver for Renesas R-Car platform * Console * Added ``UART_CONSOLE_INPUT_EXPIRED`` and ``UART_CONSOLE_INPUT_EXPIRED_TIMEOUT`` Kconfig options to notify the power management module that UART console is in use now and forbid it to enter low-power states. * Counter * Added support for ESP32 Counter * DAC * Added support for Microchip MCP4725 * Disk * Added SDMMC support on STM32L4+ * Display * Added support for ST7735R * Disk * Moved disk drivers (``disk_access_.c``) to ``drivers/disk`` and renamed according to their function. Fixed CMD6 support in USDHC driver. * Fixed clock frequency switching after initialization in ``sdmmc_spi.c`` driver. * DMA * Added support on STM32G0 and STM32H7 * EEPROM * Added support for EEPROM emulated in flash. * ESPI * Added support for Microchip eSPI SAF * Ethernet * Added simulated PTP clock to e1000 Ethernet controller. This allows simple PTP clock testing with Qemu. * Separated PTP clock from gPTP support in mcux and gmac drivers. This allows application to use PTP clock without enabling gPTP support. * Converted clock control to use DEVICE_DT_GET in mcux driver. * Changed to allow changing MAC address in gmac driver. * Driver for STM32H7 is now using specific memory layout to fit DMA constraints for RAM accesses. * Flash * flash_write_protection_set() has been deprecated and will be removed in Zephyr 2.8. Responsibility for write/erase protection management has been moved to the driver-specific implementation of the flash_write() and flash_erase() API calls. All in-tree flash drivers have been updated, and the protect implementation removed from their API tables. During the deprecation period user code invoking flash_write_protection_set() will have no effect, but the flash_write() and flash_erase() driver shims will wrap their calls with calls to the protect implementation if it is present in the API table. Out-of-tree drivers must be updated before the wrapping in the shims is removed when the deprecation period ends. * Added QSPI support on STM32F7. * GPIO * :c:struct:`gpio_dt_spec`: a new structure which makes it more convenient to access GPIO configuration in the :ref:`devicetree <dt-guide>`. * New macros for initializing ``gpio_dt_spec`` values: :c:macro:`GPIO_DT_SPEC_GET_BY_IDX`, :c:macro:`GPIO_DT_SPEC_GET_BY_IDX_OR`, :c:macro:`GPIO_DT_SPEC_GET`, :c:macro:`GPIO_DT_SPEC_GET_OR`, :c:macro:`GPIO_DT_SPEC_INST_GET_BY_IDX`, :c:macro:`GPIO_DT_SPEC_INST_GET_BY_IDX_OR`, :c:macro:`GPIO_DT_SPEC_INST_GET`, and :c:macro:`GPIO_DT_SPEC_INST_GET_OR` * New helper functions for using ``gpio_dt_spec`` values: :c:func:`gpio_pin_configure_dt`, :c:func:`gpio_pin_interrupt_configure_dt` * Remove support for ``GPIO_INT_`` flags in :c:func:`gpio_pin_configure()`. The feature has been deprecated in the Zephyr 2.2 release. The interrupt flags are now accepted by :c:func:`gpio_pin_interrupt_configure()` function only. STM32 GPIO driver now supports clock gating using PM_DEVICE and PM_DEVICE_RUNTIME * Added GPIO driver for Renesas R-Car platform * Hardware Info * Added support on Silicon Labs Gecko SoCs * I2C * Added support on STM32F2 * I2S * Added support for NXP LPC devices * IEEE 802.15.4 * Fixed various issues in IEEE 802.15.4 L2 driver. * nrf5: * Made HW Radio Capabilities runtime. * Enabled CSMA-CA on serialized host. * Changed driver to load EUI64 from UICR. * rf2xx: * Added support for tx mode direct. * Added support for tx mode CCA. * Added support to enable promiscuous mode. * Added support to enable pan coordinator mode. * Interrupt Controller * Moved shared interrupt controller configuration to be based on devicetree. * LED * Add support for LED GPIO * Added power management support for LED PWM * LoRa * Added support for SX1272 * Modem * Converted wncm14a2a, quectel-bg9x, hl7800 and ublox-sara-r4 drivers to use new DT device macros. * Changed GSM modem to optionally do a factory reset when booting. * Added autostarting support to GSM modem. * Added wait for RDY instead of polling AT in BG9X. * Fixed PDP context management for BG9X. * Added TLS offload support to ublox-sara-r4. * Made reset pin optional in ublox-sara-r4. * Fixed potential buffer overrun in hl7800. * Fixed build errors on 64-bit platforms. * Added support for dialup modem in PPP driver. * PWM * Added support on STM32F2 and STM32L1. * Added support on Silicon Labs Gecko SoCs. * Sensor * Added support for STM32 internal (CPU) temperature sensor. * Refactored multiple ST sensor drivers to use gpio_dt_spec macros and common stmemc routines, support multiple instances, and configure ODR/range properties in device tree. * Added SBS 1.1 compliant fuel gauge driver. * Added MAX17262 fuel gauge driver. * Added BMP388 pressure sensor driver. * Added Atmel SAM QDEC driver. * Added TI FDC2X1X driver. * Added support for MPU9250 to existing MPU6050 6-axis motion tracking driver. * Refactored BME280 temperature/pressure sensor driver. * Added BMI270 IMU driver. * Added Nuvoton tachometer sensor driver. * Added MAX6675 cold-junction-compensated K-thermocouple to digital converter. * Serial * Extended Cypress PSoC-6 SCB[uart] driver to support interrupts. * Added UART driver for Renesas R-Car platform * SPI * Added Cypress PSoC-6 SCB[spi] driver. * Default SPI_SCK configuration is now pull-down for all STM32 to minimize power consumption in stop mode. * Timer * Added x86 APIC TSC_DEADLINE driver. * Added support for NXP MCUX OS Timer. * Added support for Nuvoton NPCX system timer. * Added CMT driver for Renesas R-Car platform. * USB * Added support on STM32H7 * Added attached event delay to usb_dc_nrfx driver * Watchdog * Added support for TI CC32xx watchdog. * WiFi * Converted eswifi and esp drivers to new DT device macros * esp: * Fixed hostname configuration. * Removed POSIX API dependency. * Renamed offloading driver from esp to esp_at. * Added esp32 wifi driver support. Networking ********** * CoAP: * Fixed coap_find_options() to return 0 when options are empty. * DHCPv4: * Fixed DHCPv4 dependency to network event management options. * DNS: * Added locking to DNS library prevent concurrent access. * Added 10ms delay when rescheduling query timeout handler in DNS. This allows applications to run and handle the timeout gracefully. * Added support for reconfiguring DNS resolver when DNS servers are changed. This is supported by DHCPv4 and PPP. * HTTP: * Added support for storing numeric HTTP error code in client API. * IPv4: * Added IGMPv2 support to IPv4. * Removed IPv4 multicast address check when selecting source address during TX. * LwM2M: * Fixed query buffer size so that it is large enough to encode all query strings. * Added data validation callback. * Fixed Register/Update to use link_format writer. * Added application/link-format content writer. * Removed .well-known/core handling. * Introduced attribute handling helper functions. * Removed obsolete LWM2M_IPSO_TIMESTAMP_EXTENSIONS option. * Added IPSO Buzzer, Push Button, On/Off Switch, Accelerometer, Pressure Sensor, Humidity, Generic Sensor and Temperature object implementation to support object model in version 1.1 * Unified reusable resources creation. * Added support for object versioning. * Changed to allow cancel-observe to match path. * Made pmin and pmax attributes optional. * Added API function to delete object instance. * Fixed Registration Update send on object creation. * Changed to only parse TLV from the first block. * Changed to trigger registration update only when registered. * Misc: * Added UDP packet sending support to net-shell. * Fixed source network interface setting when sending and when there are multiple network interfaces. * Changed connection managed to ignore not used network interfaces. * Added locking to network interface API function calls. * Changed to allow application to disable IPv4 or IPv6 support for a network interface. * Added support for virtual network interfaces. * Added support for IPv4/v6 tunneling network interface. * Added net events notification for PPP dead and running states. * Added PPP LCP MRU option support. * Added PPP IPCP IP and DNS address peer options support. * Added support for network packet capturing and sending data to external system for analysis. * Enabled running without TX or RX threads. By default, one RX thread and no TX thread is created. If userspace support is enabled, then one RX and one TX thread are created. This improves the network transmit latency when a packet is sent from application. * Changed to push highest priority net_pkt directly to driver when sending and if there is at least one TX thread. * Changed to use k_fifo instead of k_work in RX and TX processing. This prevents k_work from accessing already freed net_pkt struct. This also improves the latency of network packets when the data is passed between different network threads. * Changed to check network interface status when sending and return ENETDOWN to the application if data cannot be sent. * Fixed echo-server sample application and set netmask properly when VLAN is enabled. * OpenThread: * Added microseconds timer API support. * Changed to switch radio off when stopping diagnostics. * Enabled CSL delayed transmissions. * Added CSL transmitter and receiver API support. * Changed to init NCP after USB communication is established. * Aligned with the new NCP API. * Aligned with the new CLI API. * Introduced new OpenThread options. * Added Link Metrics API support. * Selected ECDSA when SRP is enabled. * Made child related options only visible on FTD. * Changed OT shell not to execute OT commands when shell is not ready. * Socket: * Added SO_PROTOCOL and SO_TYPE get socket option. * Added MSG_WAITALL receive socket option flag. * Added MSG_TRUNC socket option flag. * Added support for close method for packet sockets. * Added locking to socket API function calls. * Added support for SO_BINDTODEVICE socket option. * Added support for SO_SNDTIMEO socket option. * Made NET_SOCKETS_POSIX_NAMES be on by default. This allows application to use normal BSD socket API calls without adding the zsock prefix. * Added sample application to use SO_TXTIME socket option. * TCP: * Implemented ISN calculation according to RFC6528 in TCP. This is optional and enabled by default, and can be disabled if needed. * Removed legacy TCP stack support. * Changed TCP to use private work queue in order not to block system work queue. * TLS: * Fixed userspace access to TLS socket. * Added socket option support for setting and getting DTLS handshake timeout. USB *** * Reworked USB classes configuration. Various minor fixes in USB DFU class. * USB HID class * Removed get_protocol/set_protocol from USB HID class API. * Allowed boot interface Protocol Code to be set per device. * Rework idle report implementation. * Samples * Allowed to build USB Audio sampe for different platforms. * Added SD card support to USB MSC sample. * Reworked USB HID sample. Build and Infrastructure ************************ * Improved support for additional toolchains: * Support for the Intel oneApi toolchain. * Devicetree - :c:macro:`DT_COMPAT_GET_ANY_STATUS_OKAY`: new macro - the ``96b-lscon-3v3`` and ``96b-lscon-1v8`` :ref:`compatible properties <dt-important-props>` now have ``linaro,`` vendor prefixes, i.e. they are now respectively :dtcompatible:`linaro,96b-lscon-3v3` and :dtcompatible:`linaro,96b-lscon-1v8`. This change was made to bring Zephyr's devicetrees into compliance with an upstream Linux regular expression used to validate compatible properties. This regular expression requires a letter as the first character. * West (extensions) * This section only covers west :ref:`west-extensions` maintained in the zephyr repository. For release notes on west's built-in features, see :ref:`west-release-notes`. * Changes to the runners backends used for :ref:`flashing and debugging commands <west-build-flash-debug>`: * bossac runner: added legacy mode option into extended SAM-BA bootloader selection. This extends compatibility between Zephyr and some Arduino IDE bootloaders. * jlink runner: Zephyr thread awareness is now available in GDB by default for application builds with :kconfig:option:`CONFIG_DEBUG_THREAD_INFO` set to ``y`` in :ref:`kconfig`. This applies to ``west debug``, ``west debugserver``, and ``west attach``. JLink version 7.11b or later must be installed on the host system, with JLink 7.20 or later strongly recommended. * jlink runner: default ``west flash`` output is less verbose. The old behavior is still available when run as ``west --verbose flash``. * jlink runner: when flashing, this runner now prefers a ``.hex`` file generated by the build system to a ``.bin``. Unlike ``.bin``, the HEX format includes information on the image's address range in flash, so this works better when flashing Zephyr images linked for locations other than the target's boot address, e.g. images meant to be run by bootloaders. The ``.bin`` file is still used as a fallback if a HEX File is not present. * openocd runner: support for ``west debug`` and ``west attach`` has been fixed. Previously with this runner, ``west debug`` behaved like ``west attach`` should, and ``west attach`` behaved like ``west debugserver`` should. * pyocd runner: board-specific pyOCD configuration files in YAML can now be placed in :file:`support/pyocd.yaml` inside the board directory. See :zephyr_file:`boards/arm/reel_board/support/pyocd.yaml` for an example, and the pyOCD documentation for details on its configuration format. * ``west spdx``: new command which can be used to generate SPDX software bills of materials for a Zephyr application build. See :ref:`west-spdx`. Libraries / Subsystems ********************** * Disk * Disk drivers (``disk_access_.c``) are moved to ``drivers/disk`` and renamed according to their function. Driver's Kconfig options are revised and renamed. SDMMC host controller drivers are selected when the corresponding node in devicetree is enabled. Following application relevant Kconfig options are renamed: ``CONFIG_DISK_ACCESS_RAM`` -> `CONFIG_DISK_DRIVER_RAM`, ``CONFIG_DISK_ACCESS_FLASH`` -> `CONFIG_DISK_DRIVER_FLASH`, ``CONFIG_DISK_ACCESS_SDHC`` -> `CONFIG_DISK_DRIVER_SDMMC`. Management * MCUmgr * Fixed an issue with the file system management failing to open files due to missing initializations of :c:type:`fs_file_t` structures. * Fixed an issue where multiple SMP commands sent one after the other would corrupt CBOR payload. * Fixed problem where mcumgr over shell would stall and wait for retransmissions of frames. * CMSIS subsystem * Moved CMSIS portability layer headers to include/portability/cmsis_os.h and include/portability/cmsis_os2.h * Power management * ``device_pm_control_nop`` has been removed in favor of ``NULL`` when device PM is not supported by a device. In order to make transition easier for out-of-tree users a macro with the same name is provided as an alias to ``NULL``. The macro is flagged as deprecated to make users aware of the change. * Devices set as busy are no longer suspended by the system power management. * The time necessary to exit a sleep state and return to the active state was added in ``zephyr,power-state`` binding and accounted when the system changes to a power state. * Device runtime power management (PM), former IDLE runtime, was completely overhauled. * Multiple threads can wait an operation (``pm_device_get_async`` and ``pm_device_put_async``) to finish. * A new API ``pm_device_wait`` was added so that drivers can easily wait for an async request to finish. * The API can be used in :ref:`pre-kernel <api_term_pre-kernel-ok>` stages. * Several concurrence issues related with atomics access and the usage of the polling API have been fixed. Condition variables are now used to handle notification. * Logging * Introduced logging v2 which allows logging any variable types (including floating point variables). New version does not require transient string duplication (``log_strdup()``). Legacy mode remains and is still the default but user API is not changed and modes are interchangeable. ``CONFIG_LOG2_MODE_DEFERRED`` or ``CONFIG_LOG2_MODE_IMMEDIATE`` enable logging v2. Logging backend API is extended to support v2 and the most popular backends (UART, shell) are updated. * Shell * Added ``CONFIG_SHELL_BACKEND_DUMMY_BUF_SIZE`` option that allows to set size of the dummy backend buffer; changing this parameter allows to work around issue, where output from command, shell that is gathered by the dummy backend, gets cut to the size of buffer. * Storage * Added persistent write progress to stream_flash. * Task Watchdog * This new subsystem was added with this release and allows supervision of individual threads. It is based on a regularly updated kernel timer, whose ISR is never actually called in regular system operation. An existing hardware watchdog can be used as an optional fallback if the task watchdog itself gets stuck. * Tracing * ``CONFIG_TRACING_CPU_STATS`` was removed in favor of ``CONFIG_THREAD_RUNTIME_STATS`` which provides per thread statistics. The same functionality is also available when Thread analyzer is enabled with the runtime statistics enabled. * Expanded and overhauled tracing hooks with more coverage and support for tracing all kernel objects and basic power management operations. * Added support for Percepio Tracealyzer, a commercial tracing tool which now has built-in support for Zephyr. We now have the Percepio tracerecorder integrated as a module. * Expanded support for the new hooks in SEGGER Systemview and enhanced the description file with support for all APIs. * Debug * SEGGER Systemview and RTT SDK updated to version v3.30 * OS * Reboot functionality has been moved to ``subsys/os`` from ``subsys/power``. A consequence of this movement is that the ``<power/reboot.h>`` header has been moved to ``<sys/reboot.h>``. ``<power/reboot.h>`` is still provided for compatibility, but it will produce a warning to inform users of the relocation. HALs **** * HALs are now moved out of the main tree as external modules and reside in their own standalone repositories. Trusted Firmware-m ****************** * Synchronized Trusted-Firmware-M module to the upstream v1.3.0 release. * Configured QEMU to run Zephyr samples and tests in CI on mps2_an521_nonsecure (Cortex-M33 Non-Secure) with TF-M as the secure firmware component. * Added Kconfig options for selecting the desired TF-M profile and build type * Added Kconfig options for enabling the desired TF-M secure partitions * Added a new sample to run the PSA tests with Zephyr * Added a new sample to run the TF-M regression tests using the Zephyr build system * Added support for new platforms * BL5340 DVK * STM32L562E DK * NOTE: Trusted-Firmware-M can not currently be used with mbedtls 2.26.0 when PSA APIs are enabled in mbedtls (``MBEDTLS_USE_PSA_CRYPTO`` and ``MBEDTLS_PSA_CRYPTO_C``). If both TF-M and mbedtls are required, mbedtls must be used without the PSA APIs. This will be resolved in a future update to mbedtls. Documentation ************* * Documentation look and feel has been improved by using a new stylesheet. * Doxygen is now run by Sphinx using the ``doxyrunner`` custom extension. The new extension centralizes multiple scattered workarounds that existed before in a single place. * Doxygen now runs with ``WARN_AS_ERROR`` enabled. * Documentation known warnings are now filtered using a custom Sphinx extension: ``warnings_filter``. This extension removes the need of post-processing the Sphinx output and allows to use the ``-W`` option (treat warnings as errors) which has been enabled by default. * External content, e.g. samples and boards documentation is now handled by the ``external_content`` extension. * Sphinx is now run in parallel mode by default (``-j auto``). * The documentation helper ``Makefile`` has been moved from the repository root to the ``doc`` folder. Tests and Samples ***************** * Twister's ``dt_compat_enabled_with_alias()`` test case filter was deprecated in favor of a new ``dt_enabled_alias_with_parent_compat()`` filter. The old filter is still supported, but it may be removed in a future release. To update, replace uses like this: .. code-block:: yaml filter: dt_compat_enabled_with_alias("gpio-leds", "led0") with: .. code-block:: yaml filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds") * Add a feature which handles pytest script in twister and provide an example. * Provide test execution time per ztest testcase. * Added and refined some testcases, most of them are negative testcases, to improve the test code coverage: * Testcases of x86's regular/direct interrupts and offload job from ISR. * Testcases of SMP, and enabled SMP for existed testing of semaphore, condvar, etc. * Testcases of memory protection, userspace and memory heap. * Testcases of data structure include stack, queue, ringbuffer and rbtree. * Testcases of IPC include pipe, poll, mailbox, message queue. * Testcases of synchronization include mutex, semaphore, atomic operations. * Testcases of scheduling and thread. * Testcases of testing for arch_nop() and errno. * Testcases of libc and posix API. * Testcases of log and sensor subsystem. Issue Related Items ******************* These GitHub issues were addressed since the previous 2.5.0 tagged release: * :github:`35962` - drivers using deprecated Kconfigs * :github:`35955` - Bluetooth: Controller: Regression in connection setup * :github:`35949` - can: mcan: sjw-data devicetree configuration is not written correctly * :github:`35941` - subsys: tracing: sysview: No SEGGER_SYSVIEW.h in path * :github:`35926` - Shell tab-completion with more than two levels of nested dynamic commands fails * :github:`35924` - Help with Configuring Custom GPIO Pins * :github:`35916` - drivers: TI cc13xx_cc26xx: build error when PM is enabled (serial, entropy, spi, i2c modules) * :github:`35911` - shield sample sensorhub does not produce and meaningful data * :github:`35910` - LIS2MDL reporting wrong temperature * :github:`35896` - frdm_k64f: build failure missing dt-bindings/clock/kinetis_sim.h: No such file or directory * :github:`35890` - Build system ignores explicit ZephyrBuildConfiguration_ROOT variable * :github:`35882` - Fixed width documentation makes DT bindings docs unreadable * :github:`35876` - Bluetooth: host: CCC store not correctly handled for multiple connections * :github:`35871` - LPS22HH sensor reporting wrong pressure data * :github:`35840` - Bluetooth: host: L2CAP enhanced connection request conformance test issues * :github:`35838` - Bluetooth: ISO: BIG termination doesn't fully unref the connection * :github:`35826` - LORAWAN Compatibility with nrf52832 and sx1262 * :github:`35813` - Zephyr Native Posix Build Uses Linux Build Machine Headers out of Sandbox * :github:`35812` - ESP32 Factory app partition is not bootable * :github:`35781` - Missing response parameter for HCI_LE_Set_Connectionless_IQ_Sampling_Enable HCI command * :github:`35772` - Support C++ exceptions on NIOS2 * :github:`35764` - tests: kernel: threads: no multithreading: fails with CONFIG_STACK_SENTINEL=y * :github:`35762` - SAMPLES: shell_module gives no console output on qemu_leon3 * :github:`35756` - ESP32 Ethernet Support * :github:`35737` - drivers: can: mcan: sjw not initialized when CAN_FD_MODE is enabled * :github:`35714` - samples: subsys: testusb: I want to know how to test in window10. * :github:`35713` - tests: kernel.scheduler.multiq: test_k_thread_suspend_init_null failure * :github:`35694` - No console output from NIOS2 Max10 * :github:`35693` - gpio_mcux_lpc.c uses devicetree instance numbers incorrectly * :github:`35686` - Bluetooth: Crash in bt_gatt_dm_attr_chrc_val when BLE device is disconnected during discovery process * :github:`35681` - Unable to get ouput for samples/subsys/logging/logger and samples/philosophers * :github:`35677` - samples/subsys/console/getchar and samples/subsys/console/getline build breaks for arduino_nano_33_ble * :github:`35655` - Arm64: Assertion failed when CONFIG_MP_CPUS >= 3. * :github:`35653` - ARC MWDT toolchain put __start and __reset at different address * :github:`35633` - Out of bound read: Multiple Coverity sightings in generated code * :github:`35631` - [Coverity CID: 205610] Out-of-bounds read in /zephyr/include/generated/syscalls/kernel.h (Generated Code) * :github:`35630` - [Coverity CID: 205657] Out-of-bounds read in /zephyr/include/generated/syscalls/sample_driver.h (Generated Code) * :github:`35629` - [Coverity CID: 207968] Out-of-bounds read in /zephyr/include/generated/syscalls/counter.h (Generated Code) * :github:`35628` - [Coverity CID: 207976] Out-of-bounds read in /zephyr/include/generated/syscalls/counter.h (Generated Code) * :github:`35627` - [Coverity CID: 208195] Out-of-bounds read in /zephyr/include/generated/syscalls/gpio.h (Generated Code) * :github:`35626` - [Coverity CID: 210588] Out-of-bounds read in /zephyr/include/generated/syscalls/dac.h (Generated Code) * :github:`35625` - [Coverity CID: 211042] Out-of-bounds read in /zephyr/include/generated/syscalls/socket.h (Generated Code) * :github:`35624` - [Coverity CID: 214226] Out-of-bounds read in /zephyr/include/generated/syscalls/uart.h (Generated Code) * :github:`35623` - [Coverity CID: 215223] Out-of-bounds read in /zephyr/include/generated/syscalls/net_ip.h (Generated Code) * :github:`35622` - [Coverity CID: 215238] Out-of-bounds read in /zephyr/include/generated/syscalls/net_ip.h (Generated Code) * :github:`35621` - [Coverity CID: 219477] Out-of-bounds read in /zephyr/include/generated/syscalls/pwm.h (Generated Code) * :github:`35620` - [Coverity CID: 219482] Out-of-bounds read in /zephyr/include/generated/syscalls/pwm.h (Generated Code) * :github:`35619` - [Coverity CID: 219496] Out-of-bounds read in /zephyr/include/generated/syscalls/ztest_error_hook.h (Generated Code) * :github:`35618` - [Coverity CID: 219506] Out-of-bounds read in /zephyr/include/generated/syscalls/log_ctrl.h (Generated Code) * :github:`35617` - [Coverity CID: 219568] Out-of-bounds read in /zephyr/include/generated/syscalls/net_if.h (Generated Code) * :github:`35616` - [Coverity CID: 219586] Out-of-bounds read in /zephyr/include/generated/syscalls/net_if.h (Generated Code) * :github:`35615` - [Coverity CID: 219648] Uninitialized scalar variable in /zephyr/include/generated/syscalls/test_syscalls.h (Generated Code) * :github:`35614` - [Coverity CID: 219725] Out-of-bounds read in /zephyr/include/generated/syscalls/kernel.h (Generated Code) * :github:`35613` - [Coverity CID: 225900] Out-of-bounds access in tests/net/lib/dns_addremove/src/main.c * :github:`35612` - [Coverity CID: 229325] Out-of-bounds read in /zephyr/include/generated/syscalls/log_msg2.h (Generated Code) * :github:`35611` - [Coverity CID: 230223] Out-of-bounds read in /zephyr/include/generated/syscalls/log_msg2.h (Generated Code) * :github:`35610` - [Coverity CID: 232755] Out-of-bounds read in /zephyr/include/generated/syscalls/log_ctrl.h (Generated Code) * :github:`35609` - [Coverity CID: 235917] Out-of-bounds read in /zephyr/include/generated/syscalls/log_msg2.h (Generated Code) * :github:`35608` - [Coverity CID: 235923] Out-of-bounds read in /zephyr/include/generated/syscalls/log_msg2.h (Generated Code) * :github:`35607` - [Coverity CID: 235933] Out-of-bounds read in /zephyr/include/generated/syscalls/gpio.h (Generated Code) * :github:`35606` - [Coverity CID: 235951] Out-of-bounds read in /zephyr/include/generated/syscalls/log_ctrl.h (Generated Code) * :github:`35605` - [Coverity CID: 236005] Out-of-bounds read in /zephyr/include/generated/syscalls/log_ctrl.h (Generated Code) * :github:`35604` - [Coverity CID: 236129] Unused value in drivers/adc/adc_lmp90xxx.c * :github:`35603` - [Coverity CID: 236130] Wrong sizeof argument in drivers/adc/adc_lmp90xxx.c * :github:`35596` - Bluetooth: Cannot connect if extended advertising is enabled in ``prj.conf`` * :github:`35586` - Timer based example on docu using nrf52-dk compile error. * :github:`35580` - Fault when logging * :github:`35569` - tests/lib/mem_alloc failed with arcmwdt toolchain * :github:`35567` - some mwdt compiler options can't be recognized by zephyr_cc_option * :github:`35561` - Issue with fat_fs example on nucleo_f767zi * :github:`35553` - all menuconfig interfaces contain sound open firmware/SOF text * :github:`35543` - samples: subsys: display: lvgl: is run on nucleo_f429zi and nucleo_f746zg but should be skipped * :github:`35541` - sockets_tls: when using dtls with sara-r4 modem, handshake hangs if no reply * :github:`35540` - tests: ztest: error_hook: fails on nucleo_g071rb and nucleo_l073rz * :github:`35539` - tests: drivers: spi: spi_loopback: test failed since #34731 is merged * :github:`35524` - tests: samples: led: LED PWM sample fails on nrf platforms * :github:`35522` - doc: Current section is not shown in the side pane nor the page top cookie * :github:`35512` - OpenThread can't find TRNG driver on nRF5340 * :github:`35509` - tests: timer: Unstable tests using timer at nrf platforms * :github:`35489` - samples: net: gsm_modem: build fails if CONFIG_GSM_MUX=y * :github:`35480` - pm: device_runtime: ``pm_device_request`` can block forever * :github:`35479` - address is not a known kernel object exception with arcmwdt toolchain * :github:`35476` - bluetooth: controller assertion when scanning with multiple active connections * :github:`35474` - The dma-stm32 driver don't build for STM32F0 MCUs * :github:`35444` - drivers: sensor: sbs-gauge: The sbs-gauge cannot be read from sensor shell * :github:`35401` - Enabling POSIX_API leads to SSL handshake error * :github:`35395` - STM32F4: Infinite reboot loop due to Ethernet initialization * :github:`35390` - net.socket.tls.tls_ext: frdm_k64f test failure * :github:`35383` - Can't setup ISO Broadcast Demo on nrf53dk * :github:`35380` - sys: timeutil: inconsistent types for local times * :github:`35363` - bt_gatt_discover() retunrs incorrect handle (offset by -1) * :github:`35360` - Power consumption nRF52 * :github:`35352` - [Coverity CID: 215376] Out-of-bounds access in drivers/sensor/lis2dh/lis2dh_trigger.c * :github:`35351` - [Coverity CID: 219472] Unrecoverable parse warning in tests/kernel/mem_protect/mem_protect/src/mem_domain.c * :github:`35350` - [Coverity CID: 236055] Out-of-bounds access in subsys/modbus/modbus_core.c * :github:`35349` - [Coverity CID: 236057] Unrecoverable parse warning in tests/kernel/mem_protect/mem_protect/src/mem_domain.c * :github:`35348` - [Coverity CID: 236060] Out-of-bounds access in subsys/net/l2/ppp/ppp_l2.c * :github:`35347` - [Coverity CID: 236064] Dereference null return value in subsys/bluetooth/controller/ll_sw/ull.c * :github:`35346` - [Coverity CID: 236069] Out-of-bounds access in tests/lib/c_lib/src/main.c * :github:`35345` - [Coverity CID: 236074] Out-of-bounds access in tests/lib/c_lib/src/main.c * :github:`35344` - [Coverity CID: 236075] Out-of-bounds access in subsys/bluetooth/controller/hci/hci.c * :github:`35343` - [Coverity CID: 236079] Untrusted divisor in subsys/bluetooth/controller/hci/hci.c * :github:`35342` - [Coverity CID: 236085] Dereference after null check in samples/userspace/prod_consumer/src/app_a.c * :github:`35341` - twister: Hardware map creation is buggy (+ inaccurate docs) * :github:`35338` - USB: ethernet CDC ECM/EEM support is broken * :github:`35336` - tests: samples: power: samples/subsys/pm/device_pm/sample.power.ospm.dev_idle_pm fails on nrf52 platforms * :github:`35329` - samples: gsm_modem: Compilation failed, likely related to logging changes * :github:`35327` - Sensor Code for CC3220sf * :github:`35325` - Shell: Kernel: Reboot: echo is abruptly terminated * :github:`35321` - Improve STM32: Serial Driver,Handle uart mode per instance * :github:`35307` - ARM64 system calls are entered with interrupts masked * :github:`35305` - Linking order when using both TF-M and Mbed TLS * :github:`35299` - PM suspend IPC message sporadically not being delivered * :github:`35297` - STM32 SPI - wrong behavior after PR 34731 * :github:`35286` - New logging breaks eclipse * :github:`35278` - LittleFs Sample will not build for qemu_riscv64 sample target * :github:`35263` - device_pm_control_nop is used in dac_mcp4725.c * :github:`35242` - intel_adsp_cavs15: run kernel common testcases failed on ADSP * :github:`35241` - intel_adsp_cavs15: run interrupt testcases failed on ADSP * :github:`35236` - tests: doc: Document generation process FAILS with valid module ``samples:`` * :github:`35223` - Coverity [CID 221772]: Wrong operator used in logging subsystem, multiple violations * :github:`35220` - tests: dma: memory-to-memory transfer fails on stm32f746zg nucleo board * :github:`35219` - tests: driver: dma test case loop_transfer fails on stm32 with dmamux * :github:`35215` - tests/kernel/msgq/msgq_usage failed on hsdk board * :github:`35209` - tests/kernel/mem_heap/mheap_api_concept failed on hsdk board * :github:`35204` - PPI channel assignment for Bluetooth controller is incorrect for nRF52805 * :github:`35202` - smp atomic_t global_lock will never be cleared when a thread oops with global_lock is set * :github:`35200` - tests/kernel/smp failed on hsdk board * :github:`35199` - Queues: there is no documentation about queue's implementation. * :github:`35198` - subsys.pm.device_pm: frdm_k64f leave idel fails * :github:`35197` - Zephyr Project Development with 2 Ethernet Interfaces Supported (eth0, and eth1) * :github:`35195` - doc, coding guidelines: broken CERT-C links * :github:`35191` - GIT Checkout of Master Branch is 2.6.0rc1 versus west update as 2.5.99 * :github:`35189` - Coding Guidelines: Resolve the issues under Rule 21.2 * :github:`35187` - Version selection not working * :github:`35176` - strtol crashes * :github:`35175` - quectel-bg9x crashes in modem_rssi_query_work * :github:`35169` - esp32: uart_poll_in never ready for UART2 only * :github:`35163` - [Coverity CID: 236009] Wrong sizeof argument in tests/lib/cbprintf_package/src/test.inc * :github:`35162` - [Coverity CID: 235972] Wrong sizeof argument in tests/lib/cbprintf_package/src/test.inc * :github:`35161` - [Coverity CID: 235962] Unused value in tests/kernel/mem_protect/mem_map/src/main.c * :github:`35160` - [Coverity CID: 235930] Unused value in kernel/mmu.c * :github:`35159` - [Coverity CID: 232698] Uninitialized scalar variable in samples/net/sockets/txtime/src/main.c * :github:`35158` - [Coverity CID: 224630] Uninitialized scalar variable in subsys/net/ip/igmp.c * :github:`35157` - [Coverity CID: 221380] Uninitialized scalar variable in subsys/bluetooth/controller/ll_sw/ull_iso.c * :github:`35156` - [Coverity CID: 235979] Unchecked return value in drivers/sensor/iis2mdc/iis2mdc_trigger.c * :github:`35155` - [Coverity CID: 235677] Unchecked return value in drivers/gpio/gpio_cy8c95xx.c * :github:`35154` - [Coverity CID: 233524] Unchecked return value in include/drivers/dma.h * :github:`35153` - [Coverity CID: 236006] Structurally dead code in tests/subsys/logging/log_api/src/test.inc * :github:`35152` - [Coverity CID: 235986] Structurally dead code in tests/subsys/logging/log_api/src/test.inc * :github:`35151` - [Coverity CID: 235943] Reliance on integer endianness in include/sys/cbprintf_cxx.h * :github:`35150` - [Coverity CID: 225136] Out-of-bounds write in tests/kernel/sched/deadline/src/main.c * :github:`35149` - [Coverity CID: 234410] Out-of-bounds read in tests/kernel/sched/preempt/src/main.c * :github:`35148` - [Coverity CID: 236015] Out-of-bounds access in tests/subsys/logging/log_api/src/mock_backend.c * :github:`35147` - [Coverity CID: 236012] Out-of-bounds access in subsys/bluetooth/audio/vcs_client.c * :github:`35146` - [Coverity CID: 235994] Out-of-bounds access in tests/kernel/interrupt/src/interrupt_offload.c * :github:`35145` - [Coverity CID: 235984] Out-of-bounds access in include/sys/cbprintf_cxx.h * :github:`35144` - [Coverity CID: 235944] Out-of-bounds access in subsys/bluetooth/audio/vcs_client.c * :github:`35143` - [Coverity CID: 235921] Out-of-bounds access in include/sys/cbprintf_cxx.h * :github:`35142` - [Coverity CID: 235914] Out-of-bounds access in subsys/bluetooth/audio/vcs.c * :github:`35141` - [Coverity CID: 235913] Out-of-bounds access in subsys/bluetooth/audio/vcs.c * :github:`35140` - [Coverity CID: 231072] Out-of-bounds access in tests/kernel/sched/preempt/src/main.c * :github:`35139` - [Coverity CID: 229646] Out-of-bounds access in subsys/bluetooth/audio/vocs.c * :github:`35138` - [Coverity CID: 229545] Out-of-bounds access in tests/subsys/canbus/isotp/conformance/src/main.c * :github:`35137` - [Coverity CID: 225993] Out-of-bounds access in tests/subsys/canbus/isotp/conformance/src/main.c * :github:`35136` - [Coverity CID: 235916] Operands don't affect result in drivers/adc/adc_stm32.c * :github:`35135` - [Coverity CID: 235911] Negative array index write in tests/subsys/logging/log_api/src/mock_backend.c * :github:`35134` - [Coverity CID: 222151] Negative array index write in tests/subsys/logging/log_msg2/src/main.c * :github:`35133` - [Coverity CID: 232501] Missing varargs init or cleanup in subsys/logging/log_msg2.c * :github:`35132` - [Coverity CID: 236003] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35131` - [Coverity CID: 235998] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35130` - [Coverity CID: 235997] Logically dead code in drivers/adc/adc_stm32.c * :github:`35129` - [Coverity CID: 235990] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35128` - [Coverity CID: 235970] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35127` - [Coverity CID: 235965] Logically dead code in tests/subsys/logging/log_api/src/test.inc * :github:`35126` - [Coverity CID: 235961] Logically dead code in tests/subsys/logging/log_api/src/test.inc * :github:`35125` - [Coverity CID: 235956] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35124` - [Coverity CID: 235955] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35123` - [Coverity CID: 235954] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35122` - [Coverity CID: 235952] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35121` - [Coverity CID: 235950] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35120` - [Coverity CID: 235934] Logically dead code in subsys/bluetooth/audio/vcs.c * :github:`35119` - [Coverity CID: 235932] Logically dead code in samples/sensor/adxl372/src/main.c * :github:`35118` - [Coverity CID: 235919] Logically dead code in samples/sensor/bmg160/src/main.c * :github:`35117` - [Coverity CID: 235945] Incorrect sizeof expression in include/sys/cbprintf_cxx.h * :github:`35116` - [Coverity CID: 235987] Incompatible cast in include/sys/cbprintf_cxx.h * :github:`35115` - [Coverity CID: 236000] Improper use of negative value in tests/lib/cbprintf_package/src/test.inc * :github:`35114` - [Coverity CID: 221976] Division or modulo by zero in tests/drivers/can/timing/src/main.c * :github:`35113` - [Coverity CID: 235985] Dereference before null check in subsys/bluetooth/audio/vcs_client.c * :github:`35112` - [Coverity CID: 235983] Dereference after null check in samples/sensor/max17262/src/main.c * :github:`35111` - [Coverity CID: 234630] Dereference after null check in tests/net/dhcpv4/src/main.c * :github:`35110` - [Coverity CID: 220616] Arguments in wrong order in tests/subsys/canbus/isotp/conformance/src/main.c * :github:`35108` - tests: drivers: pwm: pwm_api: failed on nucleo_f207zg * :github:`35107` - Atmel SAM E70 / Cortex-M7 fails to boot if CONFIG_NOCACHE_MEMORY=y * :github:`35104` - arch.interrupt.gen_isr_table.arm_mainline: fails on lpcxpresso55s16_ns * :github:`35102` - testing.ztest.error_hook: fails on lpcxpresso55s16_ns * :github:`35100` - libraries.libc.sprintf_new: fails on lpcxpresso55s16_ns and lpcxpresso55s69_ns * :github:`35099` - benchmark.kernel.application.fp.arm: Illegal load of EXC_RETURN into PC on lpcxpresso55s16_ns and lpcxpresso55s69_ns * :github:`35097` - arch.interrupt: fails on NXP Cortex-M0+ platforms * :github:`35091` - enc424j600 does not work * :github:`35089` - stm32h7: systematic crash at each second boot with NETWORKING=y * :github:`35083` - dts: stm32mp1: SPI2 mixup with SAI2, SPI3 mixup with SAI3 * :github:`35082` - intel_adsp_cavs15: All the testcases run failed on ADSP * :github:`35079` - acrn_ehl_crb: build warnings for old APIC_TIMER configs * :github:`35076` - acrn_ehl_crb does not work with CPUs >1 * :github:`35075` - .west/config west.yml and zephyr versioning during project development * :github:`35073` - timer: cortex_m_systick: uptime drifting in tickless mode * :github:`35060` - tests/kernel/common: test_nop failed on ARMV7_M_ARMV8_M_MAINLINE * :github:`35058` - Bluetooth: deadlock when canceling db_hash.work from settings commit handler * :github:`35051` - CONFIG_LOG2 fails for floating point output with warning and bad output * :github:`35048` - mcuboot with enabled serial recovery does not compile * :github:`35046` - Tracing shows k_busy_wait() being executed very often on nRF platforms * :github:`35043` - NXP: Build error : ModuleNotFoundError: No module named 'elftools' * :github:`35041` - Crash in net-shell when invoking "net dns" command * :github:`35036` - STM32: Wrong uart_event_tx len calculation * :github:`35033` - samples/boards: stm32 pm blinky fails when run with twister * :github:`35028` - frdm_k64f: failed to run tests/subsys/pm/power_mgmt/ * :github:`35027` - frdm_k64f: failed to run testcase tests/drivers/adc/adc_emul/ * :github:`35026` - sam_e70b_xplained: failed to run testcases tests/drivers/adc/adc_emul/ * :github:`35013` - Bluetooth: Controller: Out-of-Bound ULL context access during connection completion * :github:`34999` - Using BT_ISO bluetooth hci_usb sample, and enable, but still shows no command supported * :github:`34989` - Implement arch_page_phys_get() for ARM64 * :github:`34979` - MIMRT685-EVK board page has broken links * :github:`34978` - misleading root folder size in footprint reports * :github:`34969` - Documentation still mentions deprecated macro DT_INST_FOREACH_STATUS_OKAY * :github:`34964` - net regression: Connection to Zephyr server non-deterministically leads to client timeout, ENOTCONN on server side * :github:`34962` - tfm: cmake: Toolchain not being passed into psa-arch-tests * :github:`34950` - xtensa arch The source code version is too old * :github:`34948` - SoF module is not pointing at Zehpyr repo * :github:`34935` - LwM2M: Block transfer with TLV format does not work * :github:`34932` - drvers/flash/nrf_qspi_nor: high power consumption on nrf52840 * :github:`34931` - dns resolve timeout leads to CPU memory access violation error * :github:`34925` - tests/lib/cbprintf_package fails to build * :github:`34923` - net.socket.get_addr_info: frdm_k64f test fails * :github:`34917` - arch.interrupt.arm\| arch.interrupt.extra_exception_info: lpcxpresso55s28 series: test failure * :github:`34915` - arch.interrupt.gen_isr_table.arm_mainline:lpcxpresso55s16_ns/lpcxpresso55s28: interrupt 57 does not work * :github:`34911` - tests/kernel/mem_protect/mem_protect: frdm_k82f/frdm_k64f unexpected fatal error * :github:`34909` - dma_loopback:lpcxpresso55s28_ns driver test failure * :github:`34904` - uart_mcux_lpuart: Enable driver to work with ``CONFIG_MULTITHREADING=n`` * :github:`34903` - doc: Target name is wrong for rcar_h3ulcb board * :github:`34891` - mcumgr timeout due to smp_shell_process stalling * :github:`34880` - Convert SoF Module to new kwork API * :github:`34865` - CONFIG_NET_SOCKETS_PACKET interferes with other network traffic (gptp, IP) * :github:`34862` - CAN ISO-TP implementation not using local work queue * :github:`34852` - Some bluetooth advertising packages never get transmitted over-air (Bluetooth Mesh application) * :github:`34844` - qemu_cortex_a53_smp: tests/ztest/error_hook failed after enabling the FPU context switching support * :github:`34840` - CONFIG_MULTITHREADING=n is not tested on hardware platforms * :github:`34838` - tests/subsys/logging/log_msg2 failes on qemu_cortex_a53 * :github:`34837` - Unstable multi connections between NRF52840 * :github:`34827` - tests: power management: test_power_state_trans fails on nrf boards * :github:`34796` - x86 jlink runner fails on M1 macs * :github:`34794` - LIS2DH Hard Fault when INT2 is not defined * :github:`34788` - APIC timer does not support SMP * :github:`34777` - semaphore and condvar_api tests fails after ARM64 FPU context switch commit on qemu_cortex_a53_smp * :github:`34772` - Mixed usage of signed/unsigned integer by the logging subsystem * :github:`34757` - west update: Default behavior should fetch only --depth 1 * :github:`34753` - Building and Debugging Zephyr for Native Platform on Linux using VSCode and/or QtCreator * :github:`34748` - Native posix: Segmentation fault in case of allocations without explicit heap assignment * :github:`34739` - tests/arch/arm/arm_no_multithreading/arch.arm.no_multithreading fails to build on a number of platforms * :github:`34734` - Can handler doesn't compile with CONFIG_USERSPACE * :github:`34722` - nvs: possibility of losing data * :github:`34716` - flash: spi_nor: build fails when CONFIG_SPI_NOR_SFDP_RUNTIME is enabled * :github:`34696` - Unable to select LOG_DICTIONARY_SUPPORT when TEST_LOGGING_DEFAULTS=y * :github:`34690` - net: process_rx_packet() work handler violates requirements of Workqueue Threads implementation * :github:`34687` - intel_adsp_cavs15: run tests/kernel/semaphore/semaphore/ failed on ADSP * :github:`34683` - MCUboot not confirm image when using 'west flash' * :github:`34672` - stm32h7: issue with CONFIG_UART_ASYNC_API=y * :github:`34670` - smp_svr sample configured for serial port with shell management enabled does not work * :github:`34669` - uart_read_fifo() reads only 2 chars on nucleo STM32L43KC and nRF52840-DK * :github:`34668` - i2c_ite_it8xxx2.c fails to build - possibly related to device_pm_control_nop changes * :github:`34667` - posix_apis:mimxrt685_evk_cm33 timeout in test_posix_realtime * :github:`34662` - many udp networking cases fail on nxp platforms * :github:`34658` - TF-M integration samples do not work with GNU ARM Embedded having GCC v10.x.x * :github:`34656` - STM32 ADC - read of multiple channels in a sequence * :github:`34644` - CAN - Bus Driver Sample * :github:`34635` - BME280 build error * :github:`34633` - STM32: Mass conversion of boards to dts based clock control configuration * :github:`34624` - Coding guidelines 15.7 PR causes tests failures * :github:`34605` - flash_stm32h7x.c fails to build * :github:`34601` - sample: bluetooth: beacon: USAGE FAULT after few seconds on board b_l4s5i_iot01a * :github:`34597` - Mismatch between ``ot ping`` and ``net ping`` * :github:`34593` - Using hci_usb with Bluez 5.55 or 5.58 * :github:`34585` - mec15xxevb_assy6853: test_timeout_order in tests/kernel/common assertion failed * :github:`34584` - kernel: workqueue thread is occasionally not invoked when kernel is run in cooperative mode only * :github:`34583` - twister failing: fails platform native_posix, test lib/cmsis_dsp/filtering * :github:`34581` - Unable to work with SX1276 Lora module. * :github:`34570` - IPC samples running secure but configured nonsecure (AN521) * :github:`34568` - Compilation error with zephyr 2.3.0 * :github:`34563` - net: lib: sockets: Unable to select() file descriptors with number >= 32 * :github:`34558` - Compilation error with Log v2 and CONFIG_LOG_PRINTK * :github:`34541` - per-adv-sync-create doesn't work on nRF52840, ./tests/bluetooth/shell/ * :github:`34538` - STM32 temperature sensor * :github:`34534` - west sign regression when HEX file not exists * :github:`34527` - Cpp compiling error: expected primary-expression before 'char'. _Generic macros problem * :github:`34526` - logging tests fails to build on a number of platforms * :github:`34515` - samples: net: syslog_net: hard fault when running on frdm_k64f * :github:`34505` - mimxrt1050_evk:failed to run testcases tests/net * :github:`34503` - up_squared and ehl_crb: test fails from timeout in application_development.cpp.libcxx.exceptions * :github:`34500` - thingy52 lis2dh12 sensor values too large * :github:`34495` - logger: Logger API cannot be compiled with C++ * :github:`34492` - Logging still broken with SOF * :github:`34482` - net_tunnel_virtual:frdm_k64f: build failure * :github:`34474` - MPS2-AN385 SRAM does not match what the documentation page says * :github:`34473` - Add Requirements repository with infrastructure and placeholder requirements * :github:`34469` - nrf53: nrf5340dk_nrf5340_cpunet not executing. * :github:`34463` - LwM2M bootstrap DELETE operation not working * :github:`34462` - samples: net: sockets: packet: reception stops working after a while * :github:`34461` - Unable to use PWM pins with STM Nucleo H743ZI * :github:`34443` - Document font display is incomplete * :github:`34439` - Logging subsystem causes build to fail with LLVM * :github:`34434` - subsys: testsuite: ztest framework breaks if run in cooperative mode only * :github:`34426` - RFC: API Change: USB HID remove get_protocol/set_protocol/get_idle/set_idle callbacks * :github:`34423` - twister build issue with arm64 * :github:`34419` - significant build time increase with new logging subsystem * :github:`34416` - Configuration HAS_DTS has no function, preventing compile for vendors without device tree * :github:`34409` - mDNS response on link local when using DHCPv4 and AutoIP/Static IP * :github:`34403` - Logging disable function causes Zephyr hard lockup * :github:`34402` - spi: spi_nrfx_spim: wrong clock frequency selected * :github:`34397` - Update getting started docs to reflect gdb python requirements * :github:`34387` - Error message in include/linker/kobject-text.ld is unclear * :github:`34382` - fs/nvs: if closing ATE has to high offset NVS iterates up to the end of flash. * :github:`34372` - CPU Lockups when using own Log Backend * :github:`34369` - Driver esp for wifi got a dead lock. * :github:`34368` - Cmake's Python path breaks after using west build --pristine * :github:`34363` - k_work: incorrect return values for synchronous cancel * :github:`34355` - LittleFS sample code catch an "undefined symbol 'ITCM_ADDR' referenced in expression" in linker step * :github:`34345` - samples/net/civetweb/websocket_server fails to build * :github:`34342` - No output on SWO pin (STM32L4) * :github:`34341` - SWO logging and DWT timing collision * :github:`34329` - lwm2m: pmin and pmax attributes should be optional * :github:`34325` - hal: microchip: Missing Wake bit definitions * :github:`34309` - unable to connect to azure iot hub via mqtt protocol * :github:`34308` - SPI transceive function only transmitting first tx_buffer on Sifive's MCU * :github:`34304` - intel_adsp_cavs15: run tests/kernel/queue/ failed on ADSP * :github:`34295` - TensorFlow Lite Micro Module * :github:`34280` - Add USB to LPCXpresso55S69 board * :github:`34275` - drivers: led_pwm: Improper label assignment * :github:`34272` - twister: Add memory footprint info to json report * :github:`34270` - NVS read after consecutive restarts. * :github:`34265` - BME280 Pressure calculation * :github:`34264` - CI: twister: Add merged report from all sub-builds to buildkite build artifacts * :github:`34262` - Unable to find detailed documentation on pinmux driver development * :github:`34249` - Unable to initialize on STM32F103RE + Quectel EC21 using BG9x driver * :github:`34246` - LoRa driver sending opcode of commands without parameters * :github:`34234` - UART NS16550 Underflow Issue During Clearing Port * :github:`34233` - OpenThread build issues * :github:`34231` - uzlib (decompression library) * :github:`34229` - C++ Exception Support in qemu_riscv32 emulation * :github:`34225` - BBC micro:bit v1.5 LSM303AGR-ACCEL * :github:`34216` - Using nrfx_gpiote library with spi(nrf52840) * :github:`34214` - codes reference weak variable are optimized out * :github:`34209` - BLE Mesh Provisioning generates value 0 outside of Specification for Blink, Beep, or Vibrate * :github:`34206` - Question: Is zephyrproject actively maintaining the windows-curses sub-project? * :github:`34202` - MPU Fault when running central coded bluetooth and ENC28J60 dhcpv4_client * :github:`34201` - Fatal error when perform "bt phy-update" if there is not any connections at ./tests/bluetooth/shell * :github:`34197` - samples: telnet: Tab completion not working in telnet shell * :github:`34196` - st_lis2mdl: LSM303AGR-MAGN not detected * :github:`34190` - Newbie: Simple C++ List App Builds for QEMU but not Native Posix Emulation * :github:`34184` - video samples fail to build * :github:`34178` - apds9960 sensor sample does not build on STM32 * :github:`34165` - SNTP fails to close the used socket * :github:`34154` - AArch64 PR reviews and merges are lagging behind * :github:`34152` - intel_adsp_cavs15: run tests/kernel/smp/ failed on ADSP * :github:`34149` - Invalid link in Zephyr document to ACRN page * :github:`34145` - Convert NXP kinetis boards to have pindata in devicetree * :github:`34134` - USB do not works if bootloader badly use the device before * :github:`34117` - ehl_crb: tests/kernel/context tests failed * :github:`34116` - mec15xxevb_assy6853: tests/kernel/mutex/sys_mutex/ * :github:`34107` - Convert tests/benchmarks/mbedtls/src/benchmark.c to new kwork API * :github:`34106` - Convert tests/kernel/pending/src/main.c to new kwork API * :github:`34104` - Convert tests/benchmarks/footprints/src/workq.c to new kwork API * :github:`34103` - Convert drivers/console/uart_mux.c to new kwork API * :github:`34102` - Convert drivers/serial/uart_sam0.c to new kwork API * :github:`34101` - Convert subsys/mgmt to new kwork API * :github:`34100` - Convert subsys/shell/shell_telnet to new kwork API * :github:`34099` - Convert subsys/tracing/cpu_stats.c to new kwork API * :github:`34098` - Convert samples/drivers/led_sx1509b_intensity to new kwork API * :github:`34097` - Convert samples/boards/reel_board/mesh_badge to new kwork API * :github:`34096` - Convert samples nrf clock_skew to new kwork API * :github:`34095` - Convert CAN to new kwork API * :github:`34094` - Convert ubsys/ipc/rpmsg_service/rpmsg_backend.c to new kwork API * :github:`34093` - Convert bluetooth to new kwork API * :github:`34092` - Convert usb to new kwork API * :github:`34091` - Convert uart_stm32.c to new kwork API * :github:`34090` - Convert video_sw_generator.c to new kwork API * :github:`34082` - Bullets are broken in documentation * :github:`34076` - Unrecognized characters generated during document construction * :github:`34068` - DOC BUILD FAIL * :github:`34046` - Failed to build arm64 architecture related board * :github:`34045` - samples: subsys: mgmt: smp_srv: UDP sample does not boot on frdm_k64f * :github:`34026` - RISCV32 QEMU illegal instruction exception / floating point support * :github:`34023` - test_prevent_interruption has wrong data type for key * :github:`34014` - Toolchain Compile Error of RISC-V(rv32m1-vega board) * :github:`34011` - NRF52840 DTS questions * :github:`34010` - [Coverity CID: 220531] Copy into fixed size buffer in tests/net/socket/misc/src/main.c * :github:`34009` - [Coverity CID: 220532] Unrecoverable parse warning in subsys/bluetooth/controller/ll_sw/ull_peripheral_iso.c * :github:`34008` - [Coverity CID: 220533] Improper use of negative value in tests/net/socket/misc/src/main.c * :github:`34007` - [Coverity CID: 220534] Out-of-bounds access in tests/arch/arm/arm_no_multithreading/src/main.c * :github:`34006` - [Coverity CID: 220535] Dereference before null check in subsys/net/l2/virtual/virtual.c * :github:`34005` - [Coverity CID: 220536] Pointer to local outside scope in subsys/net/lib/lwm2m/lwm2m_engine.c * :github:`34004` - [Coverity CID: 220537] Uninitialized pointer read in tests/net/virtual/src/main.c * :github:`34003` - [Coverity CID: 220538] Logically dead code in subsys/net/l2/virtual/virtual.c * :github:`34002` - [Coverity CID: 220539] Improper use of negative value in tests/net/socket/misc/src/main.c * :github:`34001` - [Coverity CID: 220540] Uninitialized scalar variable in samples/drivers/flash_shell/src/main.c * :github:`34000` - [Coverity CID: 220541] Dereference before null check in subsys/net/lib/capture/capture.c * :github:`33986` - TCP stack doesn't handle data received in FIN_WAIT_1 * :github:`33983` - example-application module: add trivial driver * :github:`33981` - example-application module: add board zxa_board_stub * :github:`33978` - MCP2515 wrong BRP value * :github:`33977` - Question: How best to contribute drivers upstream? * :github:`33974` - The stm32wb55rc MCU does not operate on zephyr * :github:`33969` - Hardfault error caused by ARM Cortex m0 non-4-byte alignment * :github:`33968` - ESP32 Porting GSM Module Compile Error * :github:`33967` - The printed total size differs from calculated from .json * :github:`33966` - STM32: I-cache & D-cache * :github:`33965` - example-application module: add trivial project * :github:`33956` - tests: kernel: fpu: Several tests related to fpu fail on nrf5340dk_nrf5340_cpuappns * :github:`33954` - I2C scan in UART shell is not detecting any I2C devices on ESP32 * :github:`33951` - periodic_adv not working with nRF5340 DK * :github:`33950` - periodic_adv not working with nRF5340 DK * :github:`33929` - subsys: logging: Sample app doesn't build if using Werror and logging with latest SDK * :github:`33925` - Rework hl7800 driver to use new work queue APIs * :github:`33923` - GSM modem automatic operation selection mode problems * :github:`33911` - test:twr_ke18f: tests/kernel/sched/schedule_api - kernel_threads_sched_userspace cases meet out our space * :github:`33904` - having issue compile a shell program and it is bug likely * :github:`33898` - intel_adsp_cavs15: running testcases failed tests/kernel/workq/work on adsp * :github:`33897` - Bluetooth: extended advertising can't restart after connection * :github:`33896` - Device tree: STM32L4 defines can1 node for chips which do not support CAN peripheral * :github:`33895` - Device tree: STM32L412 and STM32L422 are missing nodes * :github:`33890` - Continuous Integration check patch false warnings * :github:`33884` - CORTEX_M_DEBUG_NULL_POINTER_EXCEPTION_DETECTION_NONE is way too long * :github:`33874` - twister: Add skip as error feature * :github:`33868` - Bluetooth: controller: connectable advertisement disable race condition * :github:`33866` - uart: TX_DONE occurs before transmission is complete. * :github:`33860` - DEPRECATED, a replacement suggestion should be found somewhere * :github:`33858` - tests: ztest: test trigger_fault_access from tests/ztest/error_hook fails on em_starterkit_em7d_v22 * :github:`33857` - atomic xtensa build fail * :github:`33843` - ESP32 example does not connect to WiFi * :github:`33840` - [Coverity CID: 220301] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33839` - [Coverity CID: 220302] Uninitialized scalar variable in subsys/net/lib/lwm2m/lwm2m_rw_link_format.c * :github:`33838` - [Coverity CID: 220304] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33837` - [Coverity CID: 220305] Logically dead code in drivers/gpio/gpio_nrfx.c * :github:`33836` - [Coverity CID: 220306] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33835` - [Coverity CID: 220309] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33834` - [Coverity CID: 220310] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33833` - [Coverity CID: 220311] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33832` - [Coverity CID: 220312] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33831` - [Coverity CID: 220313] Logically dead code in subsys/bluetooth/services/ots/ots_obj_manager.c * :github:`33830` - [Coverity CID: 220314] Untrusted value as argument in subsys/bluetooth/services/ots/ots_dir_list.c * :github:`33829` - [Coverity CID: 220315] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33828` - [Coverity CID: 220316] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33827` - [Coverity CID: 220317] Unchecked return value in tests/kernel/pipe/pipe_api/src/test_pipe_contexts.c * :github:`33826` - [Coverity CID: 220318] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33825` - [Coverity CID: 220319] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33824` - [Coverity CID: 220320] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33823` - [Coverity CID: 220321] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33822` - [Coverity CID: 220413] Explicit null dereferenced in tests/lib/sprintf/src/main.c * :github:`33821` - [Coverity CID: 220414] Unused value in tests/subsys/logging/log_backend_fs/src/log_fs_test.c * :github:`33820` - [Coverity CID: 220415] Uninitialized scalar variable in tests/posix/common/src/pthread.c * :github:`33819` - [Coverity CID: 220417] Out-of-bounds access in subsys/modbus/modbus_core.c * :github:`33818` - [Coverity CID: 220418] Destination buffer too small in subsys/modbus/modbus_raw.c * :github:`33817` - [Coverity CID: 220419] Unchecked return value in subsys/bluetooth/host/gatt.c * :github:`33816` - [Coverity CID: 220420] Out-of-bounds access in tests/subsys/modbus/src/test_modbus_raw.c * :github:`33815` - [Coverity CID: 220421] Incorrect sizeof expression in tests/lib/cbprintf_package/src/main.c * :github:`33814` - [Coverity CID: 220422] Extra argument to printf format specifier in tests/lib/sprintf/src/main.c * :github:`33813` - [Coverity CID: 220423] Out-of-bounds access in subsys/net/l2/ppp/ppp_l2.c * :github:`33812` - [Coverity CID: 220424] Out-of-bounds access in drivers/watchdog/wdt_mcux_imx_wdog.c * :github:`33811` - [Coverity CID: 220425] Destination buffer too small in tests/subsys/modbus/src/test_modbus_raw.c * :github:`33810` - [Coverity CID: 220426] Out-of-bounds access in tests/lib/c_lib/src/main.c * :github:`33809` - [Coverity CID: 220427] Unchecked return value in tests/posix/common/src/pthread.c * :github:`33808` - [Coverity CID: 220428] Out-of-bounds access in subsys/bluetooth/audio/vocs.c * :github:`33807` - [Coverity CID: 220429] Out-of-bounds access in subsys/net/l2/ppp/ppp_l2.c * :github:`33806` - [Coverity CID: 220430] Operands don't affect result in tests/lib/c_lib/src/main.c * :github:`33805` - [Coverity CID: 220431] Extra argument to printf format specifier in tests/lib/sprintf/src/main.c * :github:`33804` - [Coverity CID: 220432] Out-of-bounds access in subsys/net/l2/ethernet/ethernet.c * :github:`33803` - [Coverity CID: 220433] Printf arg count mismatch in tests/lib/sprintf/src/main.c * :github:`33802` - [Coverity CID: 220434] Resource leak in tests/lib/mem_alloc/src/main.c * :github:`33801` - [Coverity CID: 220435] Extra argument to printf format specifier in tests/lib/sprintf/src/main.c * :github:`33800` - [Coverity CID: 220436] Explicit null dereferenced in tests/lib/sprintf/src/main.c * :github:`33799` - [Coverity CID: 220437] Wrong size argument in tests/lib/mem_alloc/src/main.c * :github:`33798` - [Coverity CID: 220438] Out-of-bounds access in subsys/bluetooth/audio/vocs_client.c * :github:`33797` - [Coverity CID: 220439] Destination buffer too small in tests/subsys/modbus/src/test_modbus_raw.c * :github:`33796` - [Coverity CID: 220440] Out-of-bounds access in tests/subsys/modbus/src/test_modbus_raw.c * :github:`33795` - [Coverity CID: 220441] Untrusted loop bound in subsys/modbus/modbus_client.c * :github:`33794` - [Coverity CID: 220442] Pointless string comparison in tests/lib/c_lib/src/main.c * :github:`33793` - [Coverity CID: 220443] Out-of-bounds access in tests/subsys/modbus/src/test_modbus_raw.c * :github:`33792` - [Coverity CID: 220444] Out-of-bounds access in subsys/modbus/modbus_raw.c * :github:`33791` - [Coverity CID: 220445] Unchecked return value in subsys/logging/log_backend_fs.c * :github:`33790` - [Coverity CID: 220446] Printf arg count mismatch in tests/lib/sprintf/src/main.c * :github:`33789` - [Coverity CID: 220447] Out-of-bounds access in subsys/modbus/modbus_raw.c * :github:`33788` - [Coverity CID: 220448] Out-of-bounds access in tests/subsys/modbus/src/test_modbus_raw.c * :github:`33787` - [Coverity CID: 220449] Unused value in tests/subsys/logging/log_backend_fs/src/log_fs_test.c * :github:`33786` - [Coverity CID: 220450] Untrusted loop bound in subsys/modbus/modbus_client.c * :github:`33785` - [Coverity CID: 220451] Resource leak in tests/lib/mem_alloc/src/main.c * :github:`33784` - [Coverity CID: 220452] Out-of-bounds access in subsys/net/l2/ethernet/ethernet.c * :github:`33783` - [Coverity CID: 220453] Extra argument to printf format specifier in tests/lib/sprintf/src/main.c * :github:`33768` - Rpmsg initialisation on nRF53 may fail * :github:`33765` - Regular loss of a few connection intervals * :github:`33761` - Documentation: K_WORK_DEFINE usage is not shown in workqueue doc * :github:`33754` - xtensa sys timer Interrupt bug * :github:`33745` - ``west attach`` silently downgrades to ``debugserver`` for openocd runner * :github:`33729` - flash_write() in STM32L0 MCU throws hard fault * :github:`33727` - mec15xxevb_assy6853: multiple tests failed due to assertion failure at kernel/sched.c:841 * :github:`33726` - test:mimxrt1010_evk: tests/kernel/sched/schedule_api - kernel_threads_sched_userspace cases meet out our space * :github:`33721` - STM32 serial driver configure api doesn't set correct datalength when even or odd parity is used. * :github:`33712` - kernel/poll: no error happened when mutil-threads poll a same event at a same time. * :github:`33702` - cfb sample build error for esp32 when SSD1306 is enabled * :github:`33697` - dts:dt-bindings No OCTOSPIM dt-bindings available for stm32h723 * :github:`33693` - cmake -E env: unknown option '-Wno-unique_unit_address_if_enabled' * :github:`33667` - tests: kernel: timer: Test timeout_abs from tests/kernel/timer/timer_api hangs causing test scenarios to fail * :github:`33665` - tests: kernel: timer_api fails with hard fault in CONFIG_TICKLESS_KERNEL * :github:`33662` - Make twister dig deeper in directory structure to find additional .yaml files * :github:`33658` - Question: How is NUM_IRQS determined for example for STM32F401xC * :github:`33655` - Add support for board: Nucleo-L412RB-P * :github:`33646` - Expose net_ipv4_create, net_ipv6_create, and net_udp_create in standard header * :github:`33645` - Random MAC after RESET - NRF52832 * :github:`33641` - API Meeting Minutes * :github:`33635` - subsys/ipc/openamp sample on QEMU not working when debugging * :github:`33633` - NXP imx rt1064 evk: Application does not boot when flash/flexSPI driver is enabled * :github:`33629` - tests: subsys: logging: Tests from /tests/subsys/logging/log_backend_fs fail on nrf52840dk * :github:`33625` - NVS: replace dev_name parameter by device reference in nvs_init() * :github:`33612` - Add support to get adv address of a per_adv_sync object and lookup per_adv_sync object from adv address * :github:`33610` - ARC: add ARCv3 HS6x support * :github:`33609` - Question about memory usage of the binary zephyr.exe * :github:`33600` - Master is broken at build-time when SRAM is mapped at an high address * :github:`33593` - acrn_ehl_crb: general tests and samples execution slowdown * :github:`33591` - wordlist (kobject hash) is not generated correctly when using high addresses for SRAM on 64-bit platforms * :github:`33590` - nrf: Debugging any test fails when CORTEX_M_DEBUG_NULL_POINTER_EXCEPTION_DETECTION_DWT is enabled * :github:`33589` - SSD1306 driver no longer works for I2C displays * :github:`33583` - nRF SPI CS control: CS set / release delay is longer than configured * :github:`33572` - <err> esp_event: SYSTEM_EVENT_STA_DISCONNECTED for wifi sample for esp32 board * :github:`33568` - Test tests/arch/x86/info fails for ehl_crb * :github:`33567` - sof: framework is redefnining MAX, MIN to version with limited capabilities * :github:`33559` - pin setting error on frdm_kl25z boards * :github:`33558` - qemu_cortex_a53_smp and qemu_x86_64 failed in tests/kernel/condvar/condvar while enabling for SMP * :github:`33557` - there is no network interface to work with for wifi sample for esp32 board * :github:`33551` - tests: SMP: Two threads synchronize failed using mutex or semaphore while both doing irq_lock() * :github:`33549` - xt-xcc unknown field 'obj' specified in initializer * :github:`33548` - xt-xcc does not support deprecated attribute * :github:`33545` - ehl_crb: tests/arch/x86/info failed. * :github:`33544` - ehl_crb: portability.posix.common.posix_realtime failed. * :github:`33543` - ehl_crb: tests/subsys/edac/ibecc failed. * :github:`33542` - reel_board: samples/subsys/usb/hid/ timeout failure * :github:`33539` - ehl_crb: tests/kernel/mem_heap/mheap_api_concept failed. * :github:`33529` - adafruit_feather_nrf52840 dts not setting I2C controller compat (was: SSD1306 DTS properties not being generated in devicetree_unfixed.h) * :github:`33526` - boards: Optimal way to have customized dts for my project. * :github:`33525` - ST Nucleo G071RB board support issue * :github:`33524` - minor: kswap.h is included twice in kernel/init.c * :github:`33523` - Bossac runner flashes at an incorrect offset * :github:`33516` - socket: tcp application crashes when there are no more net buffers in case of reception * :github:`33515` - arm64/mmu: Are you sure it's OK to use atomic_cas before the MMU is initialized? * :github:`33512` - build: build target is always out-of-date * :github:`33509` - samples: tests: watchdog: samples/subsys/task_wdt breaks nrf platforms performace * :github:`33505` - WS2812 SPI LED driver with DMA on nrf52 bad SPI data * :github:`33498` - west: Question on ``west flash --hex-file`` behavior with build.dir-fmt * :github:`33491` - fwrite() function will cause the program to crash when wrong parameters passed * :github:`33488` - Ring buffer makes it hard to discard items * :github:`33479` - disk_access_spi_sdhc: Missing stop/end bit * :github:`33475` - Need to add device node for UART10 in dts/arm/st/h7/stm32h723.dtsi * :github:`33464` - SYS_INIT initialize priority "2-9" ordering error * :github:`33459` - Divide zero exception is not enabled in ARC * :github:`33457` - Fail to build ARC zephyr with MetaWare toolchain * :github:`33456` - lorawan: unconfirmed messages leave stack in busy state * :github:`33426` - a few failures with CONFIG_HCI_ACL_DATA_SIZE in nightly builds * :github:`33424` - tests: ztest: Test from tests/ztest/error_hook fails on nrf5340dk_nrf5340_cpuappns * :github:`33423` - tests: portability: tests/portability/cmsis_rtos_v2 fails on nrf5340dk_nrf5340_cpuappns * :github:`33422` - samples/subsys/usb/dfu/sample.usb.dfu fails on multiple platforms in daily build * :github:`33421` - Add BT_LE_FEAT_BIT_PER_ADV checks for periodic advertising commands * :github:`33403` - trigger_fault_divide_zero test case didn't run divide instruction * :github:`33381` - West debug does not work with Bluetooth shell and nRF52840 DK * :github:`33378` - Extended advertising switch on / switch off loop impossible * :github:`33374` - Network interface routines are not thread safe * :github:`33371` - mec15xxevb_assy6853: tests/drivers/gpio/gpio_basic_api/ failed * :github:`33365` - Add STM32H7 Series USB Device Support * :github:`33363` - Properly indicate ISR number in SystemView * :github:`33356` - Using AT HOST fails build * :github:`33353` - work: k_work_schedule from running work item does not schedule * :github:`33352` - Arduino Nano 33 BLE sense constantly resetting. * :github:`33351` - uart peripheral outputs 7 bits when configured in 8 bits + parity on stm32 * :github:`33348` - ip/dhcpv4 is not thread-safe in SMP/preemptive thread configurations * :github:`33342` - disco_l475_iot1: Multiple definitions of z_timer_cycle_get_32, etc. * :github:`33339` - API/functions to get remaining free heap size * :github:`33330` - Poll on DTLS socket returns -EAGAIN if bind & receive any data. * :github:`33326` - The gpio-map for adafruit_feather_stm32f405 looks like it contains conflicts * :github:`33324` - Using bluetooth hci_usb sample, and set periodic adv enable, but bluez still shows no command supported * :github:`33322` - Questions on ztest : 1) Can twister/ztests run on windows? 2) Project structure * :github:`33319` - Kernel doesn't validate lock state on swap * :github:`33318` - [Coverity CID: 219722] Resource leak in tests/lib/mem_alloc/src/main.c * :github:`33317` - [Coverity CID: 219727] Improper use of negative value in tests/lib/cbprintf_package/src/main.c * :github:`33316` - [Coverity CID: 219724] Side effect in assertion in tests/kernel/queue/src/test_queue_contexts.c * :github:`33315` - [Coverity CID: 219723] Side effect in assertion in tests/kernel/queue/src/test_queue_contexts.c * :github:`33314` - [Coverity CID: 219726] Side effect in assertion in tests/kernel/lifo/lifo_usage/src/main.c * :github:`33313` - [Coverity CID: 219728] Untrusted array index read in subsys/bluetooth/host/iso.c * :github:`33312` - [Coverity CID: 219721] Untrusted array index read in subsys/bluetooth/host/iso.c * :github:`33311` - [Coverity CID: 219729] Logically dead code in lib/os/cbprintf_packaged.c * :github:`33303` - __ASSERT does not display message or register info in v2.5.0 * :github:`33291` - Using both NET_SOCKETS_SOCKOPT_TLS and POSIX_API fails build * :github:`33280` - drivers: serial: nrf uarte: The application receives one more byte that was received over UART * :github:`33273` - The z_smp_reacquire_global_lock() internal API is not used any where inside zephyr code base * :github:`33269` - ILI9341 (ILI9XXX) set orientation function fails to update the display area correctly * :github:`33265` - Power Management Overhaul * :github:`33261` - gatt_notify too slow on Broadcast * :github:`33253` - STM32G4 with USB-C PD: Some pins cannot be used as input by default * :github:`33239` - lib/rbtree: Remove dead case in rb_remove() * :github:`33238` - tests: drivers: pwm api fails on many boards * :github:`33233` - uart9 missing from <st/h7/stm32h7.dtsi> * :github:`33218` - Incorrect documentation CONFIG_LOG_STRDUP_MAX_STRING * :github:`33213` - Configuring a project with a sub-project (e.g. nRF5340) and an overlay causes an infinite configuring loop * :github:`33212` - GUI configuration system (ninja menuconfig) exists with an error when the windows key is pressed * :github:`33208` - cbprintf: Package size calculation is using best case alignment * :github:`33207` - twister: Add option to load list with quarantined tests * :github:`33203` - Bluetooth: host: ISO: Missing terminate reason in ISO disconnected callback * :github:`33200` - USB CDC ACM sample application fails to compile * :github:`33196` - I2C doesn't work on STM32F103RE * :github:`33185` - TCP traffic with IPSP sample not working on 96Boards Nitrogen * :github:`33176` - tests: kernel: Multiple test cases from tests/kernel/workq/work_queue are failing * :github:`33173` - tests/kernel/workq/work_queue fails on sam_e70_xplained * :github:`33171` - Create Renesas HAL * :github:`33169` - STM32 SPI Driver - Transmit (MOSI) Only - Infinite Loop on Tranceive * :github:`33168` - CONFIG_HEAP_MEM_POOL_SIZE=64 doesn't work * :github:`33164` - Newlib has no synchronization * :github:`33153` - west flash cannot find OpenOCD * :github:`33149` - subsys: canbus: canopen EDSEditor / libedssharp version that works with Zephyr's CANopenNode * :github:`33147` - Not able to build blinky or set toolchain to zephyr * :github:`33142` - fs_mount for FAT FS does not distingush between no file system and other errors * :github:`33140` - STM32H7: Bus fault when reading corrupt flash sectors * :github:`33138` - invalid west cmake diagnostics when using board alias * :github:`33137` - Enabling DHCP without NET_MGMT shouldn't be allowed * :github:`33127` - Improve documentation user experience * :github:`33122` - Device-level Cache API * :github:`33120` - iotdk: running testcase tests/kernel/mbox/mbox_api/ failed * :github:`33114` - tests: mbox_api: testcase test_mbox_data_get_null has some bugs. * :github:`33104` - Updating Zephyr to fix Work Queue Problems * :github:`33101` - DNS resolver misbehaves if receiving response too late * :github:`33100` - tcp2 not working with ppp * :github:`33097` - Coverity ID links in associated GitHub issues are broken * :github:`33096` - [Coverity CID :215373] Unchecked return value in subsys/net/lib/lwm2m/lwm2m_rd_client.c * :github:`33095` - [Coverity CID :215379] Out-of-bounds write in subsys/mgmt/osdp/src/osdp_cp.c * :github:`33094` - [Coverity CID :215381] Resource leak in samples/net/mdns_responder/src/service.c * :github:`33093` - [Coverity CID :215391] Unchecked return value from library in samples/net/mdns_responder/src/service.c * :github:`33092` - [Coverity CID :215392] Logically dead code in subsys/mgmt/osdp/src/osdp_cp.c * :github:`33091` - [Coverity CID :219474] Logically dead code in subsys/bluetooth/controller/ll_sw/ull_scan.c * :github:`33090` - [Coverity CID :219476] Dereference after null check in subsys/bluetooth/controller/ll_sw/ull_conn.c * :github:`33089` - [Coverity CID :219556] Self assignment in drivers/espi/host_subs_npcx.c * :github:`33088` - [Coverity CID :219558] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33087` - [Coverity CID :219559] Out-of-bounds access in tests/arch/arm/arm_interrupt/src/arm_interrupt.c * :github:`33086` - [Coverity CID :219561] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33085` - [Coverity CID :219562] Out-of-bounds access in tests/bluetooth/tester/src/gatt.c * :github:`33084` - [Coverity CID :219563] Dereference after null check in arch/x86/core/multiboot.c * :github:`33083` - [Coverity CID :219564] Untrusted value as argument in subsys/net/lib/lwm2m/lwm2m_engine.c * :github:`33082` - [Coverity CID :219566] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33081` - [Coverity CID :219572] Untrusted value as argument in tests/net/lib/coap/src/main.c * :github:`33080` - [Coverity CID :219573] Untrusted value as argument in samples/net/sockets/coap_client/src/coap-client.c * :github:`33079` - [Coverity CID :219574] Side effect in assertion in tests/subsys/edac/ibecc/src/ibecc.c * :github:`33078` - [Coverity CID :219576] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33077` - [Coverity CID :219579] Out-of-bounds read in drivers/ipm/ipm_nrfx_ipc.c * :github:`33076` - [Coverity CID :219583] Operands don't affect result in drivers/clock_control/clock_control_npcx.c * :github:`33075` - [Coverity CID :219588] Out-of-bounds access in tests/bluetooth/tester/src/gatt.c * :github:`33074` - [Coverity CID :219590] Unchecked return value in subsys/bluetooth/mesh/proxy.c * :github:`33073` - [Coverity CID :219591] Untrusted divisor in drivers/sensor/bme680/bme680.c * :github:`33072` - [Coverity CID :219593] Logically dead code in tests/arch/x86/pagetables/src/main.c * :github:`33071` - [Coverity CID :219595] Dereference before null check in subsys/net/ip/net_context.c * :github:`33070` - [Coverity CID :219596] Out-of-bounds read in tests/kernel/interrupt/src/dynamic_isr.c * :github:`33069` - [Coverity CID :219597] Untrusted value as argument in tests/net/lib/coap/src/main.c * :github:`33068` - [Coverity CID :219598] Out-of-bounds access in tests/bluetooth/tester/src/gatt.c * :github:`33067` - [Coverity CID :219600] Unchecked return value in drivers/watchdog/wdt_wwdg_stm32.c * :github:`33066` - [Coverity CID :219601] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33065` - [Coverity CID :219603] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33064` - [Coverity CID :219608] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33063` - [Coverity CID :219609] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33062` - [Coverity CID :219610] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33061` - [Coverity CID :219611] Dereference after null check in subsys/net/ip/tcp2.c * :github:`33060` - [Coverity CID :219613] Uninitialized scalar variable in lib/cmsis_rtos_v1/cmsis_signal.c * :github:`33059` - [Coverity CID :219615] Out-of-bounds access in tests/arch/arm/arm_irq_advanced_features/src/arm_zero_latency_irqs.c * :github:`33058` - [Coverity CID :219616] Untrusted value as argument in subsys/net/lib/coap/coap_link_format.c * :github:`33057` - [Coverity CID :219619] Untrusted divisor in subsys/bluetooth/controller/hci/hci.c * :github:`33056` - [Coverity CID :219620] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33055` - [Coverity CID :219621] Uninitialized scalar variable in tests/net/socket/getaddrinfo/src/main.c * :github:`33054` - [Coverity CID :219622] Untrusted value as argument in subsys/net/lib/coap/coap.c * :github:`33053` - [Coverity CID :219623] Out-of-bounds read in drivers/ipm/ipm_nrfx_ipc.c * :github:`33051` - [Coverity CID :219625] Unchecked return value in subsys/bluetooth/mesh/proxy.c * :github:`33050` - [Coverity CID :219628] Untrusted value as argument in subsys/net/lib/lwm2m/lwm2m_engine.c * :github:`33049` - [Coverity CID :219629] Operands don't affect result in drivers/clock_control/clock_control_npcx.c * :github:`33048` - [Coverity CID :219631] Out-of-bounds read in drivers/espi/espi_npcx.c * :github:`33047` - [Coverity CID :219634] Out-of-bounds access in tests/net/lib/dns_addremove/src/main.c * :github:`33046` - [Coverity CID :219636] Untrusted value as argument in subsys/net/lib/lwm2m/lwm2m_engine.c * :github:`33045` - [Coverity CID :219637] Untrusted value as argument in tests/net/lib/coap/src/main.c * :github:`33044` - [Coverity CID :219638] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33043` - [Coverity CID :219641] Out-of-bounds access in tests/bluetooth/tester/src/gatt.c * :github:`33042` - [Coverity CID :219644] Side effect in assertion in tests/subsys/edac/ibecc/src/ibecc.c * :github:`33040` - [Coverity CID :219646] Untrusted value as argument in subsys/net/lib/coap/coap.c * :github:`33039` - [Coverity CID :219647] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33038` - [Coverity CID :219649] Operands don't affect result in kernel/sem.c * :github:`33037` - [Coverity CID :219650] Out-of-bounds access in samples/bluetooth/central_ht/src/main.c * :github:`33036` - [Coverity CID :219651] Logically dead code in subsys/bluetooth/mesh/net.c * :github:`33035` - [Coverity CID :219652] Unchecked return value in drivers/gpio/gpio_stm32.c * :github:`33034` - [Coverity CID :219653] Unchecked return value in drivers/modem/hl7800.c * :github:`33033` - [Coverity CID :219654] Out-of-bounds access in tests/net/lib/dns_addremove/src/main.c * :github:`33032` - [Coverity CID :219656] Uninitialized scalar variable in tests/kernel/threads/thread_stack/src/main.c * :github:`33031` - [Coverity CID :219658] Untrusted value as argument in samples/net/sockets/coap_client/src/coap-client.c * :github:`33030` - [Coverity CID :219659] Side effect in assertion in tests/subsys/edac/ibecc/src/ibecc.c * :github:`33029` - [Coverity CID :219660] Untrusted divisor in drivers/sensor/bme680/bme680.c * :github:`33028` - [Coverity CID :219661] Unchecked return value in subsys/bluetooth/host/gatt.c * :github:`33027` - [Coverity CID :219662] Inequality comparison against NULL in lib/os/cbprintf_packaged.c * :github:`33026` - [Coverity CID :219666] Out-of-bounds access in tests/bluetooth/tester/src/gatt.c * :github:`33025` - [Coverity CID :219667] Untrusted value as argument in tests/net/lib/coap/src/main.c * :github:`33024` - [Coverity CID :219668] Dereference after null check in drivers/espi/host_subs_npcx.c * :github:`33023` - [Coverity CID :219669] Untrusted value as argument in subsys/mgmt/updatehub/updatehub.c * :github:`33022` - [Coverity CID :219672] Untrusted value as argument in samples/net/sockets/coap_server/src/coap-server.c * :github:`33021` - [Coverity CID :219673] Untrusted value as argument in samples/net/sockets/coap_client/src/coap-client.c * :github:`33020` - [Coverity CID :219675] Macro compares unsigned to 0 in kernel/include/mmu.h * :github:`33019` - [Coverity CID :219676] Unchecked return value in drivers/modem/wncm14a2a.c * :github:`33018` - [Coverity CID :219677] Logically dead code in drivers/timer/npcx_itim_timer.c * :github:`33009` - kernel: k_heap failures on small heaps * :github:`33001` - stm32: window watchdog (wwdg): setup of prescaler not valid for newer series * :github:`33000` - stm32: window watchdog (wwdg): invalid interrupts priority for CM0 Series Socs * :github:`32996` - SPI speed when using SDHC via SPI in Zephyr * :github:`32994` - Question: Possible simplification in mutex.h? * :github:`32975` - Where should a few include/ headers live * :github:`32969` - Wrong board target in microbit v2 documentation * :github:`32966` - frdm_k64f: Run some testcases timeout failed by using twister * :github:`32963` - USB device is not supported by qemu_x86 platform * :github:`32961` - [Coverity CID :219478] Unchecked return value in subsys/bluetooth/controller/ll_sw/ull_filter.c * :github:`32960` - [Coverity CID :219479] Out-of-bounds access in subsys/net/l2/bluetooth/bluetooth.c * :github:`32959` - [Coverity CID :219480] Out-of-bounds read in lib/os/cbprintf_nano.c * :github:`32958` - [Coverity CID :219481] Out-of-bounds access in subsys/bluetooth/controller/ll_sw/nordic/lll/lll_adv_aux.c * :github:`32957` - [Coverity CID :219483] Improper use of negative value in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32956` - [Coverity CID :219484] Out-of-bounds access in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32955` - [Coverity CID :219485] Logically dead code in subsys/bluetooth/controller/ll_sw/ull.c * :github:`32954` - [Coverity CID :219486] Unrecoverable parse warning in tests/kernel/mem_protect/mem_protect/src/mem_domain.c * :github:`32953` - [Coverity CID :219487] Resource leak in tests/net/socket/getaddrinfo/src/main.c * :github:`32952` - [Coverity CID :219488] Unrecoverable parse warning in tests/kernel/mem_protect/mem_protect/src/mem_domain.c * :github:`32951` - [Coverity CID :219489] Structurally dead code in tests/drivers/dma/loop_transfer/src/test_dma_loop.c * :github:`32950` - [Coverity CID :219490] Unsigned compared against 0 in drivers/wifi/esp/esp.c * :github:`32949` - [Coverity CID :219491] Resource leak in tests/net/socket/af_packet/src/main.c * :github:`32948` - [Coverity CID :219492] Out-of-bounds access in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32947` - [Coverity CID :219493] Unchecked return value in tests/kernel/workq/work/src/main.c * :github:`32946` - [Coverity CID :219494] Logically dead code in boards/xtensa/intel_s1000_crb/pinmux.c * :github:`32945` - [Coverity CID :219495] Pointless string comparison in tests/lib/devicetree/api/src/main.c * :github:`32944` - [Coverity CID :219497] Logically dead code in subsys/bluetooth/host/gatt.c * :github:`32943` - [Coverity CID :219498] Out-of-bounds access in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32942` - [Coverity CID :219499] Argument cannot be negative in tests/net/socket/af_packet/src/main.c * :github:`32941` - [Coverity CID :219501] Unchecked return value in subsys/net/l2/bluetooth/bluetooth.c * :github:`32940` - [Coverity CID :219502] Improper use of negative value in tests/net/socket/af_packet/src/main.c * :github:`32939` - [Coverity CID :219504] Logically dead code in subsys/net/lib/lwm2m/lwm2m_engine.c * :github:`32938` - [Coverity CID :219508] Unchecked return value in lib/libc/minimal/source/stdlib/malloc.c * :github:`32937` - [Coverity CID :219508] Unchecked return value in lib/libc/minimal/source/stdlib/malloc.c * :github:`32936` - [Coverity CID :219509] Side effect in assertion in tests/net/socket/tcp/src/main.c * :github:`32935` - [Coverity CID :219510] Improper use of negative value in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32934` - [Coverity CID :219511] Uninitialized scalar variable in tests/kernel/mbox/mbox_api/src/test_mbox_api.c * :github:`32933` - [Coverity CID :219512] Unrecoverable parse warning in tests/kernel/mem_protect/mem_protect/src/mem_domain.c * :github:`32932` - [Coverity CID :219513] Logically dead code in drivers/wifi/esp/esp.c * :github:`32931` - [Coverity CID :219514] Out-of-bounds access in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32930` - [Coverity CID :219515] Side effect in assertion in subsys/bluetooth/controller/ll_sw/ull_sched.c * :github:`32929` - [Coverity CID :219516] Improper use of negative value in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32928` - [Coverity CID :219518] Macro compares unsigned to 0 in subsys/bluetooth/mesh/transport.c * :github:`32927` - [Coverity CID :219519] Unchecked return value in drivers/ethernet/eth_sam_gmac.c * :github:`32926` - [Coverity CID :219520] Unsigned compared against 0 in drivers/wifi/esp/esp.c * :github:`32925` - [Coverity CID :219521] Unchecked return value in tests/kernel/workq/work/src/main.c * :github:`32924` - [Coverity CID :219522] Unchecked return value in tests/subsys/dfu/mcuboot/src/main.c * :github:`32923` - [Coverity CID :219523] Side effect in assertion in subsys/bluetooth/controller/ll_sw/ull_adv_sync.c * :github:`32922` - [Coverity CID :219524] Logically dead code in drivers/wifi/esp/esp.c * :github:`32921` - [Coverity CID :219525] Unchecked return value in tests/subsys/settings/functional/src/settings_basic_test.c * :github:`32920` - [Coverity CID :219526] Operands don't affect result in tests/boards/mec15xxevb_assy6853/qspi/src/main.c * :github:`32919` - [Coverity CID :219527] Resource leak in tests/net/socket/getaddrinfo/src/main.c * :github:`32918` - [Coverity CID :219528] Arguments in wrong order in tests/drivers/pwm/pwm_loopback/src/main.c * :github:`32917` - [Coverity CID :219529] Unchecked return value in subsys/bluetooth/controller/ll_sw/ull_filter.c * :github:`32916` - [Coverity CID :219530] Dereference before null check in drivers/modem/ublox-sara-r4.c * :github:`32915` - [Coverity CID :219531] Improper use of negative value in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32914` - [Coverity CID :219532] Out-of-bounds access in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32913` - [Coverity CID :219535] Dereference after null check in drivers/sensor/icm42605/icm42605.c * :github:`32912` - [Coverity CID :219536] Dereference before null check in drivers/ieee802154/ieee802154_nrf5.c * :github:`32911` - [Coverity CID :219537] Out-of-bounds access in samples/boards/nrf/system_off/src/retained.c * :github:`32910` - [Coverity CID :219538] Illegal address computation in subsys/bluetooth/controller/ll_sw/nordic/lll/lll_adv_aux.c * :github:`32909` - [Coverity CID :219540] Side effect in assertion in subsys/bluetooth/controller/ll_sw/ull_sched.c * :github:`32908` - [Coverity CID :219541] Unused value in subsys/bluetooth/controller/ticker/ticker.c * :github:`32907` - [Coverity CID :219542] Dereference null return value in subsys/bluetooth/mesh/heartbeat.c * :github:`32906` - [Coverity CID :219543] Out-of-bounds access in samples/boards/nrf/mesh/onoff_level_lighting_vnd_app/src/smp_svr.c * :github:`32905` - [Coverity CID :219544] Logically dead code in drivers/wifi/esp/esp.c * :github:`32904` - [Coverity CID :219545] Side effect in assertion in subsys/bluetooth/controller/ll_sw/ull_adv_aux.c * :github:`32903` - [Coverity CID :219546] Unchecked return value in tests/kernel/workq/work/src/main.c * :github:`32902` - [Coverity CID :219547] Improper use of negative value in tests/drivers/timer/nrf_rtc_timer/src/main.c * :github:`32898` - Bluetooth: controller: Control PDU buffer leak into Data PDU buffer pool * :github:`32877` - acrn: test case of kernel.timer and kernel.timer.tickless failed * :github:`32875` - Benchmarking Zephyr vs. RIOT-OS * :github:`32867` - tests/kernel/sched/schedule_api does not start with stm32wb55 on nucleo * :github:`32866` - bt_le_ext_adv_create returns -5 with 0x2036 opcode status 1 * :github:`32862` - MCUboot, use default UART_0 value for RECOVERY_UART_DEV_NAME * :github:`32860` - Periodic advertising/synchronization on nRF52810 * :github:`32853` - lwm2m: uninitialized variable in this function * :github:`32839` - tests/kernel/timer/timer_api/test_timeout_abs still fails on multiple platforms * :github:`32835` - twister: integration_platforms stopped working as it should * :github:`32828` - tests: posix: Test case portability.posix.common.tls.newlib.posix_realtime fails on nrf9160dk_nrf9160 * :github:`32827` - question: Specify size of malloc arena * :github:`32818` - Function z_swap_next_thread() missing coverage in sched.c * :github:`32817` - Supporting fedora in the getting started docs * :github:`32816` - ehl_crb: tests/kernel/timer/timer_api/timer_api/test_sleep_abs (kernel.timer.tickless) failed. * :github:`32809` - Fail to build ARC zephyr with MetaWare toolchain * :github:`32800` - Race conditions with setting thread attributes after ``z_ready_thread``? * :github:`32798` - west flash fails for reel board * :github:`32778` - Cannot support both HID boot report keyboard and mouse on a USB HID device * :github:`32774` - Sensor BMI160: set of undersampling mode is not working * :github:`32771` - STM32 with Ethernet crashes when receiving packets early * :github:`32757` - Need openthread merge * :github:`32755` - mcumgr: shell output gets truncated * :github:`32745` - Bluetooth PAST shell command * :github:`32742` - Bluetooth: GAP: LE connection complete event handling priority * :github:`32741` - ARM32 / ARM64 separation * :github:`32735` - Subsys: Logging: Functions purely to avoid compiling error affects test coverage * :github:`32724` - qemu timer change introducing new CI failures * :github:`32723` - kernel/sched: Only send IPI to abort a thread if the hardware supports it * :github:`32721` - samples/bluetooth/periodic_adv/, print random address after every reset * :github:`32720` - ./samples/microbit/central_eatt builds failed at v2.5.0 release * :github:`32718` - NUCLEO-F446RE: Enable CAN Module * :github:`32715` - async uart api not working on stm32 with dmamux * :github:`32705` - KERNEL_COHERENCE on xtensa doesn't quite work yet * :github:`32702` - RAM overflow with bbc:microbit for samples/bluetooth/peripheral... * :github:`32699` - Setting custom BOARD_ROOT raises FileNotFoundError * :github:`32697` - sam_e70b_xplained: running tests/kernel/timer/timer_api failed * :github:`32696` - intel_adsp_cavs15: run testcases failed of tests/kernel/common * :github:`32695` - intel_adsp_cavs15: cannot get output of some testcases * :github:`32691` - Function z_find_first_thread_to_unpend() missing coverage in sched.c * :github:`32688` - up_squared: tests/kernel/timer/timer_api failed. * :github:`32679` - twister with --device-testing sometimes overlaps tests * :github:`32677` - z_user_string_nlen() might lead to non-recoverable errors, despite suggesting the opposite * :github:`32657` - canopen sample wont respond on pdo mapping with CO_ODs from objdict.eds * :github:`32656` - reel_board: tests/lib/devicetree/devices/ build failure * :github:`32655` - reel_board: tests/kernel/timer/timer_api/ failure * :github:`32644` - Cannot build any project with system-wide DTC * :github:`32619` - samples: usb: audio: Samples for usb audio fail building * :github:`32599` - bbc_microbit build failure is blocking CI * :github:`32589` - ehl_crb: tests/kernel/context fails sporadically * :github:`32581` - shell/usb cdc_acm: shell does not work on CDC_ACM * :github:`32579` - Corrupt CBOR payloads in MCUMGR when sending multiple commands together * :github:`32572` - tests/kernel/timer/timer_api/test_timeout_abs fails on stm32 boards * :github:`32566` - lwm2m: Long endpoint names are truncated due to short buffer * :github:`32537` - Fatal error syscall_list.h * :github:`32536` - Codec phy connection ASSERTION FAIL [event.curr.abort_cb] * :github:`32515` - zephyr/kernel/thread.c:382 failed * :github:`32514` - frdm_k64f:running testcase tests/subsys/debug/coredump/ and tests/subsys/debug/coredump_backends/ failed * :github:`32513` - intel_adsp_cavs15: run testcases of fifo failed * :github:`32512` - intel_adsp_cavs15: run testcases of queue failed * :github:`32511` - Zephyr build fail with LLVM on Ubuntu for target ARC * :github:`32509` - west build -p auto -b nrf52840dk_nrf52840 samples/bluetooth/hci_uart FAILED with zephyr-v2.5.0 * :github:`32506` - k_sleep: Invalid return value when using absolute timeout. * :github:`32499` - k_sleep duration is off by 1 tick * :github:`32497` - No checks of buffer size in l2cap_chan_le_recv * :github:`32492` - AArch64: Rework secure states (NS vs S) discussion * :github:`32485` - CONFIG_NFCT_PINS_AS_GPIOS not in Kconfig.soc for nRF53 * :github:`32478` - twister: Twister cannot properly handle runners errors (flashing) * :github:`32475` - twister error building mcux acmp driver * :github:`32474` - pm: review post sleep wake up application notification scheduling * :github:`32469` - Twister: potential race conditions. * :github:`32468` - up_squared: tests/kernel/smp failed. * :github:`32467` - x86_64: page fault with access violation error complaining supervisor thread not allowed to rwx * :github:`32459` - the cbprintf unit tests don't actually test all variations * :github:`32457` - samples: drivers: espi: Need to handle failures in temperature retrieval * :github:`32448` - C++ exceptions do not work on multiple platforms * :github:`32445` - 2021 GSoC Project Idea: Transplantation for embarc_mli * :github:`32444` - z_cstart bug * :github:`32433` - pwm_stm32: warning: non-portable use of "defined" * :github:`32431` - RTC driver support on STM32F1 series * :github:`32429` - Only one PWM Channel supported in STM32L4 ? * :github:`32420` - bbc_microbit_v2 build error for lis2dh * :github:`32414` - [Coverity CID :218733] Explicit null dereferenced in tests/ztest/error_hook/src/main.c * :github:`32413` - [Coverity CID :216799] Out-of-bounds access in tests/net/lib/dns_addremove/src/main.c * :github:`32412` - [Coverity CID :216797] Dereference null return value in tests/net/6lo/src/main.c * :github:`32411` - [Coverity CID :218744] Out-of-bounds access in subsys/bluetooth/host/gatt.c * :github:`32410` - [Coverity CID :218743] Out-of-bounds access in subsys/bluetooth/host/gatt.c * :github:`32409` - [Coverity CID :218742] Out-of-bounds access in subsys/bluetooth/host/gatt.c * :github:`32408` - [Coverity CID :218741] Out-of-bounds access in subsys/bluetooth/host/att.c * :github:`32407` - [Coverity CID :218740] Out-of-bounds access in subsys/bluetooth/host/gatt.c * :github:`32406` - [Coverity CID :218737] Out-of-bounds write in subsys/bluetooth/host/gatt.c * :github:`32405` - [Coverity CID :218735] Out-of-bounds access in subsys/bluetooth/host/att.c * :github:`32404` - [Coverity CID :218734] Out-of-bounds access in subsys/bluetooth/host/smp.c * :github:`32403` - [Coverity CID :218732] Out-of-bounds access in subsys/bluetooth/host/att.c * :github:`32402` - [Coverity CID :218731] Out-of-bounds access in subsys/bluetooth/shell/gatt.c * :github:`32401` - [Coverity CID :218730] Operands don't affect result in subsys/bluetooth/host/conn.c * :github:`32400` - [Coverity CID :218729] Out-of-bounds access in subsys/bluetooth/host/gatt.c * :github:`32399` - [Coverity CID :218728] Out-of-bounds access in subsys/bluetooth/host/gatt.c * :github:`32398` - [Coverity CID :218727] Out-of-bounds access in subsys/bluetooth/host/gatt.c * :github:`32397` - [Coverity CID :218726] Out-of-bounds access in subsys/bluetooth/host/att.c * :github:`32385` - clock_control: int is returned on enum return value * :github:`32382` - Clock issues for STM32F103RE custom board * :github:`32376` - samples: driver: watchdog: Sample fails on disco_l475_iot1 * :github:`32375` - Networking stack crashes when run in cooperative scheduling mode only * :github:`32365` - samples: hci_rpmsg build fail for nrf5340 * :github:`32344` - sporadic failure in tests/kernel/mem_protect/userspace/kernel.memory_protection.userspace * :github:`32343` - openthread manual joiner hangs * :github:`32342` - review use of cpsid in aarch32 / CONFIG_PM * :github:`32331` - Use of unitialized variables in can_set_bitrate() * :github:`32321` - /tmp/ccTlcyeD.s:242: Error: Unrecognized Symbol type " " * :github:`32320` - drivers: flash: stm32: Flush ART Flash cache after erase operation * :github:`32314` - 2021 GSoC Project Idea: Enable Interactive Zephyr Test Suite * :github:`32291` - Zephyr don't build sample hello world for Particle Xenon * :github:`32289` - USDHC: Fails after reset * :github:`32279` - Question about flasing Adafruit Feather Sense with Zephyr * :github:`32270` - TCP connection stalls * :github:`32269` - shield: cmake: Shield conf is not loaded during build * :github:`32265` - STM32F4 stuck handling I2C interrupt * :github:`32261` - problem with CONFIG_STACK_SENTINEL * :github:`32260` - STM32 counter driver error in estimating alarm time * :github:`32258` - power mgmt: pm_devices: Get rid of z_pm_core_devices array * :github:`32257` - Common DFU partition enumeration API * :github:`32256` - Bluetooth mesh : Long friendship establishment after reset * :github:`32252` - Building anything for nrf5340pdk_nrf5340_cpuappns/mps2_an521_ns(any non-secure platforms) pulls external git trees * :github:`32237` - twister failing locally - fails to link native_posix w/lld * :github:`32234` - Documentation: How to update Zephyr itself (with west) * :github:`32233` - Often disconnect timeouts when running the BLE peripheral HR sample on Nitrogen96 * :github:`32224` - Treat devicetree binding deprecation usage as build error when running w/twister * :github:`32212` - Tx power levels are not similar on ADV and CONN modes when set manually (nRF52) * :github:`32206` - CMSIS-DSP support seems broken on link * :github:`32205` - [misc] AArch64 improvements and fixes * :github:`32203` - Cannot set static address when using hci_usb or hci_uart on nRF5340 attached to Linux Host * :github:`32201` - arch_switch() on ARM64 isn't quite right * :github:`32197` - arch_switch() on SPARC isn't quite right * :github:`32195` - ARMv8-nofp support * :github:`32193` - Plan to support raspberry pi Pico? * :github:`32158` - twister: inconsistent total testcases number with same configuration * :github:`32145` - ``kernel threads`` and ``kernel stacks`` deadlock in many scenarios * :github:`32137` - Provide test execution times per ztest testcase * :github:`32118` - drivers/flash/soc_flash_nrf: nRF anomaly 242 workaround is not implemented * :github:`32098` - Implement a driver for the Microphone / audio sensor (MP23ABS1) in Sensotile.Box * :github:`32084` - Custom Log Backend breaks performance * :github:`32075` - net: lwm2m: Testing Strategy for LWM2M Engine * :github:`32072` - tests/kernel/common seems to fail on nrf52833dk_nrf52833 * :github:`32071` - devicetree: ``bus:`` does not work in ``child-binding`` * :github:`32052` - p4wq has a race with work item re-use * :github:`32023` - samples: bluetooth: peripheral_hids: Unable to communicate with paired device after board reset * :github:`32000` - 2021 GSoC Call for Project Ideas - deadline Feb.19, 2021 12:00PM PST * :github:`31985` - riscv: Long execution time when TICKLESS_KERNEL=y * :github:`31982` - tests: kernel: queue: regression introduced by FPU sharing PR #31772 * :github:`31980` - Communicating with BMI160 chip over SPI * :github:`31969` - test_tcp_fn:net2 mximxrt1060/1064/1050 fails on test_client_invalid_rst with semaphore timed out * :github:`31964` - up_squared: tests/kernel/timer/timer_api failed. * :github:`31922` - hci_usb: HCI ACL packet with size divisible by 64 not sent * :github:`31856` - power: ``device_pm_get_sync`` not thread-safe * :github:`31854` - undefined reference to ``sys_arch_reboot`` * :github:`31829` - net: lwm2m: Update IPSO objects to version 1.1 * :github:`31799` - uart_configure does not return -ENOTSUP for stm32 uart with 9 bit data length. * :github:`31774` - Add an application power management sample (PM_POLICY_APP) * :github:`31762` - ivshmem application in acrn * :github:`31761` - logging:buffer_write with len=0 causes kernel panic * :github:`31757` - GCC compiler option should include '-mcpu=hs38' for HSDK * :github:`31742` - Bluetooth: BLE 5 data throughput to Linux host * :github:`31721` - tests: nrf: posix: portability.posix.common.tls.newlib fails on nrf9160dk_nrf9160 * :github:`31711` - UART failure with CONFIG_UART_ASYNC_API * :github:`31613` - Undefined reference errors when using External Library with k_msgq_* calls * :github:`31588` - Bluetooth: Support for multiple connectable advertising sets with different identities. * :github:`31585` - BMD345: Extended BLE range with PA/LNA * :github:`31503` - drivers: i2c: i2c_nrfx_twim Power Consumption rises after I2C data transfer * :github:`31416` - ARC MPU version number misuse ver3, should be ver4 * :github:`31348` - twister: CI: Run twister daily builds with "--overflow-as-errors" * :github:`31323` - Compilation warning regards the SNTP subsys * :github:`31299` - tests/kernel/mbox/mbox_usage failed on hsdk board * :github:`31284` - [stm32] PM restore console after sleep mode * :github:`31280` - devicetree: Add a macro to easily get optionnal devicetree GPIO properties * :github:`31254` - Bluetooth: Extended advertising with one advertising set fails after the first time * :github:`31248` - i2c shell functions non-functional on nRF53 * :github:`31217` - Multi-threading flash access is not supported by flash_write_protection_set() * :github:`31191` - Samples: TF-M: Enable NS test app(s) * :github:`31179` - ``iso bind`` for slave not working as intended * :github:`31169` - kconfig configuration (prj.conf) based on zephyr version * :github:`31164` - Problem to build lorawan from samples * :github:`31150` - tests/subsys/canbus/isotp/conformance: failing on nucleo_f746zg * :github:`31149` - tests/subsys/canbus/isotp/implementation: failing on nucleo_f746zg * :github:`31103` - CMSIS RTOS v2 API implementation bugs in osEventFlagsWait * :github:`31058` - SWO log backend clock frequency is off on some CPUs * :github:`31036` - BMI 160 i2c version not working. I modified to i2c in kconfig to make it use i2c. * :github:`31031` - samples/bluetooth/mesh is not helpful * :github:`30991` - Unable to add new i2c sensor to nrf/samples * :github:`30943` - MPU fault with STM32L452 * :github:`30936` - tests: sockets: tcp: add a tls test * :github:`30929` - PDM Driver for nrf52840dk * :github:`30841` - How to disable reception of socket CAN frames * :github:`30771` - Logging: Fault instruction address in the logging thread * :github:`30770` - mps2_an521: no input to shell from Windows qemu host * :github:`30618` - Add arduino header/spi support for HSDK board * :github:`30544` - nrf5340 pwm "Unsupported board: pwm-led0 devicetree alias is not defined" * :github:`30540` - CONFIG_TRACING not working after updating from v2.1.0 to 2.2.0 * :github:`30520` - recv() call to Ublox Sara R4 cant return 0 * :github:`30465` - Spurious interrupts not handled in ARMv7-R code with GICv2. * :github:`30441` - hci_uart uses wrong BT_BUF_ACL_SIZE on dual chip solutions + multicore * :github:`30429` - Thread Border Router with NRC/RCP sample and nrf52840dk not starting * :github:`30416` - No restore possible with mesh shell app from /tests using qemu_x86 on RaspberryPi3 * :github:`30395` - Add possibility to use alternative list of platforms default for CI runs. * :github:`30355` - Multiple vlan interfaces on same interface not working * :github:`30353` - RFC: Logging subsystem overhaul * :github:`30325` - Stack overflow with http post when using civetweb * :github:`30204` - Support for Teensy 4.0 and 4.1 * :github:`30195` - Missing error check of device_get_binding() and flash_area_open() * :github:`30192` - mec15xxevb_assy6853: running tests/subsys/power/power_mgmt_soc failed * :github:`30162` - Build zephyr with Metaware toolchain for HSDK fails * :github:`30121` - Make log subsystem power aware * :github:`30101` - tests should not be silently skipped due to insufficient RAM * :github:`30074` - Occasional Spinlocks on zephyr 2.4.0 (ASSERTION FAIL [z_spin_lock_valid(l)] @ WEST_TOPDIR/zephyr/include/spinlock.h:92) * :github:`30055` - Memory corruption for newlib-nano with float printf and disabled heap * :github:`29946` - SD card initialization is wrong * :github:`29915` - eth: stm32h747i_disco: sem timeout and hang on debug build * :github:`29798` - test spi loopback with dma fails on nucleo_f746zg * :github:`29733` - SAM0 will wake up with interrupted execution after deep sleep * :github:`29722` - West flash is not able to flash with openocd * :github:`29689` - tests: drivers: gpio: gpio_basic_api: correct dts binding * :github:`29610` - documentation says giving a semaphore can release IRQ lock * :github:`29599` - gPTP: frdm_k64f : can not converge time * :github:`29581` - LoRaWAN sample for 96b_wistrio - Tx timeout * :github:`29545` - samples: tfm_integration: tfm_ipc: No module named 'cryptography.hazmat.primitives.asymmetric.ed25519' * :github:`29526` - generic page pool for MMU-based systems * :github:`29476` - Samples: TF-M: Add PSA FF API Sample * :github:`29349` - Using float when driver init in RISC-V arch might cause system to get stuck. * :github:`29224` - PTS: Test framework: Bluetooth: GATT/SR/GAC/BI-01-C - FAIL * :github:`29107` - Bluetooth: hci-usb uses non-standard interfaces * :github:`29038` - drivers/usb/device/usb_dc_native_posix_adapt.c sees weird commands and aborts * :github:`28901` - implement searchable bitfields * :github:`28900` - add support for memory un-mapping * :github:`28873` - z_device_ready() lies * :github:`28803` - Use generic config option for early platfrom init (AKA "warm boot") * :github:`28722` - Bluetooth: provide ``struct bt_conn`` to ccc_changed callback * :github:`28597` - Bluetooth: controller: Redesign the implementation/use of NODE_RX_TYPE_DC_PDU_RELEASE * :github:`28551` - up_squared: samples/boards/up_squared/gpio_counter failed. * :github:`28535` - RFC: Add lz4 Data Compresssion library Support * :github:`28438` - Example downstream manifest+module repo in zephyrproject-rtos * :github:`28249` - driver: espi: mchp: eSPI OOB driver does not support callbacks for incoming OOB messages from eSPI master. * :github:`28105` - sporadic "Attempt to resume un-suspended thread object" faults on x86-64 * :github:`28096` - fatfs update to latest upstream version * :github:`27855` - i2c bitbanging on nrf52840 * :github:`27697` - Add support for passing -nogui 1 to J-Link Commander on MS Windows * :github:`27692` - Allow to select between advertising packet/scan response for BT LE device name * :github:`27525` - Including STM32Cube's USB PD support to Zephyr * :github:`27484` - sanitycheck: Ease error interception from calling script * :github:`27415` - Decide if we keep a single thread support (CONFIG_MULTITHREADING=n) in Zephyr * :github:`27356` - deep review and redesign of API for work queue functionality * :github:`27203` - tests/subsys/storage/flash_map failure on twr_ke18f * :github:`27048` - Improve out-of-tree driver experience * :github:`27033` - Update terminology related to I2C * :github:`27032` - zephyr network stack socket APIs are not thread safe * :github:`27000` - Avoid oppressive language in code base * :github:`26952` - SMP support on ARM64 platform * :github:`26889` - subsys: power: Need syscall that allows to force sleep state * :github:`26760` - Improve caching configuration and move it to be cross architecture * :github:`26728` - Allow k_poll for multiple message queues * :github:`26495` - Make k_poll work with KERNEL_COHERENCE * :github:`26491` - PCIe: add API to get BAR region size * :github:`26363` - samples: subsys: canbus: canopen: objdict: CO_OD.h is not normally made. * :github:`26246` - Printing 64-bit values in LOG_DBG * :github:`26172` - Zephyr Master/Slave not conforming with Core Spec. 5.2 connection policies * :github:`26170` - HEXDUMP log gives warning when logging function name. * :github:`26118` - Bluetooth: controller: nRF5x: refactor radio_nrf5_ppi.h * :github:`25956` - Including header files from modules into app * :github:`25865` - Device Tree Memory Layout * :github:`25775` - [Coverity CID :210075] Negative array index write in samples/net/cloud/mqtt_azure/src/main.c * :github:`25719` - sanitycheck log mixing between tests * :github:`25601` - UART input does not work on mps2_an{385,521} * :github:`25440` - Bluetooth: controller: ensure deferred PDU populations complete on time * :github:`25389` - driver MMIO address range management * :github:`25313` - samples:mimxrt1010_evk:samples/subsys/usb/audio: build error no usbd found * :github:`25187` - Generic ethernet packet filtering based on link (MAC) address * :github:`24986` - Convert dma_nios2_msgdma to DTS * :github:`24731` - Bluetooth: controller: Network privacy not respected when address resolution is disabled * :github:`24625` - lib: drivers: clock: rtc: rtc api to maintain calendar time through reboot * :github:`24228` - system power states * :github:`24142` - NRF5340 PA/LNA support * :github:`24119` - STM32: SPI: Extend power saving SPI pin config to all stm32 series * :github:`24113` - STM32 Flash: Device tree updates * :github:`23727` - RFC: clarification and standardization of ENOTSUP/ENOSYS error returns * :github:`23520` - JLink Thread-Aware Debugging (RTOS Plugin) * :github:`23465` - Zephyr Authentication - ZAUTH * :github:`23449` - "make clean" doesn't clean a lot of generated files * :github:`23225` - Bluetooth: Quality of service: Adaptive channel map * :github:`23165` - macOS setup fails to build for lack of "elftools" Python package * :github:`22965` - 4 byte addressing in spi_nor driver for memory larger than 128Mb. * :github:`22956` - nios2: k_busy_wait() never returns if called with interrupts locked * :github:`22731` - Improve docker CI documentation * :github:`22620` - adapt cpu stats tracing to tracing infrastructure * :github:`22078` - stm32: Shell module sample doesn't work on nucleo_l152re * :github:`22061` - Ethernet switch support * :github:`22060` - Build fails with gcc-arm-none-eabi-9-2019-q4-major * :github:`22027` - i2c_scanner does not work on olimexino_stm32 * :github:`21993` - Bluetooth: controller: split: Move the LLL event prepare/resume queue handling into LLL * :github:`21840` - need test case for CONFIG_MULTIBOOT on x86 * :github:`21811` - Investigate using Doxygen-generated API docs vs. Sphinx/Breath API docs * :github:`21809` - Update document generating tools to newer versions * :github:`21783` - rename zassert functions * :github:`21489` - Allow to read any types during discovery * :github:`21484` - Option for safe k_thread_abort * :github:`21342` - z_arch_cpu_halt() should enter deep power-down where supported * :github:`21293` - adding timeout the I2C read/write functions for the stm32 port * :github:`21136` - ARC: Add support for reduced register file * :github:`21061` - Document where APIs can be called from using doxygen * :github:`21033` - Read out heap space used and unallocated * :github:`20707` - Define GATT service at run-time * :github:`20576` - DTS overlay files must include full path name * :github:`20366` - Make babbelsim testing more easily available outside of CI * :github:`19655` - Milestones toward generalized representation of timeouts * :github:`19582` - zephyr_library: missing 'kernel-mode' vs 'app-mode' documentation * :github:`19340` - ARM: Cortex-M: Stack Overflows when building with NO_OPTIMIZATIONS * :github:`19244` - BLE throughput of DFU by Mcumgr is too slow * :github:`19224` - deprecate spi_flash_w25qxxdv * :github:`18934` - Update Documentation To Reflect No Concurrent Multi-Protocol * :github:`18554` - Tracking Issue for C++ Support as of release 2.1 * :github:`18509` - Bluetooth:Mesh:Memory allocation is too large * :github:`18351` - logging: 32 bit float values don't work. * :github:`17991` - Cannot generate coverage reports on qemu_x86_64 * :github:`17748` - stm32: clock-control: Remove usage of SystemCoreClock * :github:`17745` - stm32: Move clock configuration to device tree * :github:`17571` - mempool is expensive for cyclic use * :github:`17486` - nRF52: SPIM: Errata work-around status? * :github:`17375` - Add VREF, TEMPSENSOR, VBAT internal channels to the stm32 adc driver * :github:`17353` - Configuring with POSIX_API disables NET_SOCKETS_POSIX_NAMES * :github:`17314` - doc: add tutorial for using mbed TLS * :github:`16539` - include/ directory and header cleanup * :github:`16150` - Make more LWM2M parameters configurable at runtime * :github:`15855` - Create a reliable footprint tracking benchmark * :github:`15854` - Footprint Enhancements * :github:`15738` - Networking with QEMU for mac * :github:`15497` - USB DFU: STM32: usb dfu mode doesn't work * :github:`15134` - samples/boards/reel_board/mesh_badge/README.rst : No compilation or flash instructions * :github:`14996` - enhance mutex tests * :github:`14973` - samples: Specify the board target required for the sample * :github:`14806` - Assorted pylint warnings in Python scripts * :github:`14591` - Infineon Tricore architecture support * :github:`14581` - Network interfaces should be able to declare if they work with IPv4 and IPv6 dynamically * :github:`14442` - x86 SOC/CPU definitions need clean up. * :github:`14309` - Automatic device dependency tracking * :github:`19760` - Provide command to check board supported features * :github:`13553` - Ways to reduce Bluetooth Mesh message loss * :github:`13469` - Shell does not show ISR stack usage * :github:`13436` - Enabling cooperative scheduling via menuconfig may result in an invalid configuration * :github:`13091` - sockets: Implement MSG_WAITALL flag * :github:`12718` - Generic MbedTLS setup doesn't use MBEDTLS_ENTROPY_C * :github:`12098` - Not possible to print 64 bit decimal values with minimal libc * :github:`12028` - Enable 16550 UART driver on x86_64 * :github:`11820` - sockets: Implement (POSIX-compatible) timeout support * :github:`11529` - Get configuration of a running kernel in console * :github:`11449` - checkpatch warns on .dtsi files about line length * :github:`11207` - ENOSYS has ambiguous meaning. * :github:`10621` - RFC: Enable device by using dts, not Kconfig * :github:`10499` - docs: References to "user threads" are confusing * :github:`10494` - sockets: Implement MSG_TRUNC flag for recv() * :github:`10436` - Mess with ssize_t, off_t definitions * :github:`10268` - Clean up remaining SPI_DW defines in soc.h * :github:`10042` - MISRA C - Do not cast an arithimetic type to void pointer * :github:`10041` - MISRA C - types that indicate size and signedness should be used instead of basic numerical types * :github:`10030` - MISRA C - Document Zephyr's code guideline based on MISRA C 2012 * :github:`9954` - samples/hello_world build failed on Windows/MSYS * :github:`9895` - MISRA C Add 'u' or 'U' suffix for all unsigned integer constants * :github:`9894` - MISRA C Make external identifiers distinct according with C99 * :github:`9889` - MISRA C Avoid implicit conversion between integers and boolean expressions * :github:`9886` - MISRA C Do not mix signed and unsigned types * :github:`9885` - MISRA C Do not have dead code * :github:`9884` - MISRA-C Check return value of a non-void function * :github:`9882` - MISRA-C - Do not use reserved names * :github:`9778` - Implement zephyr specific SEGGER_RTT_LOCK and SEGGER_RTT_UNLOCK macros * :github:`9626` - Add support for the FRDM-KL28Z board * :github:`9507` - pwm: No clear semantics to stop a PWM leads to diverse implementations * :github:`9284` - Issues/experience trying to use TI ARM code gen tools in Zephyr * :github:`8958` - Bluetooth: Proprietary vendor specific opcode discovery * :github:`8400` - test kernel XIP case seems not well defined * :github:`8393` - ``CONFIG_MULTITHREADING=n`` builds call ``main()`` with interrupts locked * :github:`7317` - Add generation of SPDX TagValue documents to each build * :github:`7297` - STM32: Drivers: Document series support for each driver * :github:`7246` - esp32 fails to build with xtensa-esp32-elf-gcc: error: unrecognized command line option '-no-pie' * :github:`7216` - Stop using gcc's "-include" flag * :github:`7214` - Defines from DTS and Kconfig should be available simultaneously * :github:`7151` - boards: Move existing boards to "default configuration guidelines" * :github:`6925` - Provide Reviewer Guidelines as part of the documentation * :github:`6291` - userspace: support MMU-based memory virtualization * :github:`6066` - LwM2M: support object versioning in register / discover operations * :github:`5517` - Expand toolchain/SDK support * :github:`5325` - Support interaction with console in twister * :github:`5116` - [Coverity CID: 179986] Null pointer dereferences in /subsys/bluetooth/host/mesh/access.c * :github:`4911` - Filesystem support for qemu * :github:`4569` - LoRa: support LoRa * :github:`1418` - kconfig options need some cleanup and reorganisation * :github:`1415` - Problem with forcing new line in generated documentation. * :github:`1392` - No module named 'elftools' * :github:`3933` - LWM2M: Create application/link-format writer object to handle discovery formatting * :github:`3931` - LWM2M: Data Validation Callback * :github:`3723` - WiFi support for ESP32 * :github:`3675` - LE Adv. Ext.: Extended Scan with PHY selection for non-conn non-scan un-directed without aux packets * :github:`3674` - LE Adv. Ext.: Non-Connectable and Non-Scannable Undirected without auxiliary packet * :github:`3634` - ARM: implement NULL pointer protection * :github:`3514` - Bluetooth: controller: LE Advertising Extensions * :github:`3487` - Keep Zephyr Device tree Linux compatible * :github:`3420` - Percepio Tracealyzer Support * :github:`3280` - Paging Support * :github:`2854` - Modbus RTU Support * :github:`2542` - battery: Add standard APIs for Battery Charging and Fuel Gauge Handling (Energy Management) * :github:`2470` - Supervisory and Monitoring Task * :github:`2381` - SQL Database * :github:`2336` - IPv4 - Multicast Join/Leave Support ```	/content/code_sandbox/doc/releases/release-notes-2.6.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	39,889
```restructuredtext :orphan: .. _zephyr_4.0: Zephyr 4.0.0 (Working Draft) ############################ We are pleased to announce the release of Zephyr version 4.0.0. Major enhancements with this release include: An overview of the changes required or recommended when migrating your application from Zephyr v3.7.0 to Zephyr v4.0.0 can be found in the separate :ref:`migration guide<migration_4.0>`. 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: path_to_url API Changes ********* * Removed deprecated arch-level CMSIS header files ``include/zephyr/arch/arm/cortex_a_r/cmsis.h`` and ``include/zephyr/arch/arm/cortex_m/cmsis.h``. ``cmsis_core.h`` needs to be included now. * Removed deprecated ``ceiling_fraction`` macro. :c:macro:`DIV_ROUND_UP` needs to be used now. * Deprecated ``EARLY``, ``APPLICATION`` and ``SMP`` init levels can no longer be used for devices. Removed APIs in this release ============================ Deprecated in this release ========================== * Deprecated the :c:func:`net_buf_put` and :c:func:`net_buf_get` API functions in favor of :c:func:`k_fifo_put` and :c:func:`k_fifo_get`. Architectures ************* * ARC * ARM * ARM64 * RISC-V * Xtensa Kernel **** Bluetooth ******* * Audio * Host * Added API :c:func:`bt_gatt_get_uatt_mtu` to get current Unenhanced ATT MTU of a given connection (experimental). * HCI Drivers Boards & SoC Support ******************** * Added support for these SoC series: * Made these changes in other SoC series: * NXP S32Z270: Added support for the new silicon cut version 2.0. Note that the previous versions (1.0 and 1.1) are no longer supported. * Added support for these boards: * Made these board changes: * :ref:`native_posix<native_posix>` has been deprecated in favour of :ref:`native_sim<native_sim>`. * Added support for the following shields: Build system and Infrastructure ***************************** Drivers and Sensors ***************** * ADC * Battery * CAN * Charger * Clock control * Counter * DAC * Disk * Display * Ethernet * LiteX: Renamed the ``compatible`` from ``litex,eth0`` to :dtcompatible:`litex,liteeth`. * Flash * GNSS * GPIO * Hardware info * I2C * I2S * I3C * Input * LED * LED Strip * LoRa * Mailbox * MDIO * MFD * Modem * MIPI-DBI * MSPI * Pin control * PWM * Regulators * Reset * RTC * RTIO * SDHC * Sensors * Serial * LiteX: Renamed the ``compatible`` from ``litex,uart0`` to :dtcompatible:`litex,uart`. * SPI * USB * Video * Watchdog * Wi-Fi Networking ********** * ARP: * CoAP: * Connection manager: * DHCPv4: * DHCPv6: * DNS/mDNS/LLMNR: * gPTP/PTP: * HTTP: * IPSP: * IPv4: * IPv6: * LwM2M: * Location object: optional resources altitude, radius, and speed can now be used optionally as per the location object's specification. Users of these resources will now need to provide a read buffer. * Misc: * MQTT: * Network Interface: * OpenThread * PPP * Shell: * Sockets: * Syslog: * TCP: * Websocket: * Wi-Fi: * zperf: USB * Devicetree ****** Kconfig *** Libraries / Subsystems ******************** * Debug * Demand Paging * Formatted output * Management * Logging * Modem modules * Power management * Crypto * CMSIS-NN * FPGA * Random * SD * State Machine Framework * Storage * LittleFS: The module has been updated with changes committed upstream from version 2.8.1, the last module update, up to and including the released version 2.9.3. * Task Watchdog * POSIX API * LoRa/LoRaWAN * ZBus HALs **** * Nordic * STM32 * ADI * Espressif MCUboot ***** OSDP Trusted Firmware-M ************** LVGL Tests and Samples ************* Issue Related Items ***************** Known Issues ============ ```	/content/code_sandbox/doc/releases/release-notes-4.0.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,107
```restructuredtext :orphan: .. _zephyr_1.9: Zephyr Kernel 1.9.2 ################### This is a maintenance release with fixes. Kernel ****** * Generic queue item acquisition fixed to always return a valid item when using K_FOREVER Bluetooth ********* * Multiple stability fixes for BLE Mesh * Multiple stability fixes for the BLE Controller Zephyr Kernel 1.9.1 ################### This is a maintenance release with fixes and a two new features in the BLE Controller. Drivers and Sensors ******************* * mcux ethernet driver buffer overflow fixed * STM32 PWM prescaler issue fixed Networking ********** * Support for IPv6 in DNS fixed Bluetooth ********* * Multiple stability fixes for the BLE Controller * Support for PA/LNA amplifiers in the BLE Controller * Support for additional VS commands in the BLE Controller Zephyr Kernel 1.9.0 ################### We are pleased to announce the release of Zephyr kernel version 1.9.0 Major enhancements planned with this release include: * Bluetooth 5.0 Support (all features except Advertising Extensions) * Bluetooth Qualification-ready BLE Controller * BLE Mesh * Lightweight Machine to Machine (LwM2M) support * Pthreads compatible API * BSD Sockets compatible API * MMU/MPU (Cont.): Thread Isolation, Paging * Expand Device Tree support to more architectures * Revamp Testsuite, Increase Coverage * Stack Sentinel support (See details below) The following sections provide detailed lists of changes by component. Kernel ****** * Added POSIX thread IPC support for Kernel * kernel: introduce opaque data type for stacks * Timeslicing and tickless kernel improvements Architectures ************* * arm: Added STM32F405, STM32F417, STM32F103x8 SoCs * arm: Added TI CC2650 SoC * arm: Removed TI CC3200 SoC * arm: Added MPU support to nRF52, STM32L4, and STM32F3 * xtensa: Added ESP32 support * Stack sentinel: This places a sentinel value at the lowest 4 bytes of a stack memory region and checks it at various intervals, including when servicing interrupts or context switching. * x86: Enable MMU for application memory * ARC: Added initial MPU support, including stack sentinel checking for ARC configurations not featuring hardware stack bounds checking * ARC: Nested interrupt support for normal, non-FIRQ interrupts Boards ****** * Added device tree support for Intel Quark based microcontroller boards such as Arduino_101, tinytile, and Quark_d2000_crb. * arm: Added Atmel SAM4S Xplained board * arm: Added Olimex STM32-E407 and STM32-P405 boards * arm: Added STM32F412 Nucleo and STM32F429I-DISC1 boards * arm: Added TI SensorTag board * arm: Removed TI CC3200 LaunchXL board * arm: Added VBLUno51 and VBLUno52 boards * xtensa: Added ESP32 board support * ARC: Added support for EMSK EM7D v2.2 version (incl. MPU) * ARC: Board configuration restructuring, peripheral configs moved from soc to board level Drivers and Sensors ******************* * KW40Z IEEE 802.15.4 radio driver support added * APDS9960 sensor driver added * Added TICKLESS KERNEL support for nrf RTC Timer * Added Kinetis adc and pwm drivers * Removed deprecated PWM driver APIs * Added ESP32 drivers for GPIO, pin mux, watchdog, random number generator, and UART * sensor: Add BMM150 Geomagnetic sensor driver Networking ********** * LWM2M support added * net-app API support added. This is higher level API that can be used by applications to create client/server applications with transparent TLS (for TCP) or DTLS (for UDP) support. * MQTT TLS support added * Add support to automatically setup IEEE 802.15.4 and Bluetooth IPSP networks * TCP receive window support added * Network sample application configuration file unification, where most of the similar configuration files were merged together * Added Bluetooth support to HTTP(S) server sample application * BSD Socket compatible API layer, allowing to write and/or port simple networking applications using a well-known, cross-platform API * Networking API documentation fixes * Network shell enhancements * Trickle algorithm fixes * Improvements to HTTP server and client libraries * CoAP API fixes * IPv6 fixes * RPL fixes Bluetooth ********* * Bluetooth Mesh support (all mandatory features and most optional ones) * GATT Service Changed Characteristic support * IPSP net-app support: a simplified networking API reducing duplication of common tasks an application writer has to go through to connect to the network. * BLE controller qualification-ready, with all required tests passing * Controller-based privacy (including all optional features) * Extended Scanner Filter Policies support in the controller * Controller roles (Advertiser, Scanner, Master and Slave) separation in source code, conditionally includable * Flash access cooperation with BLE radio activity * Bluetooth Kconfig options have been renamed have the same (consistent) prefix as the Bluetooth APIs, namely BT_* instead of BLUETOOTH_. Controller Kconfig options have been shortened to use CTLR instead of CONTROLLER. Removed deprecated NBLE support Build and Infrastructure ************************ * change description Libraries ********* * mbedTLS updated to 2.6.0 * TinyCrypt updated to 0.2.7 HALs **** * Added support for stm32f417 SOC * Added support for stm32f405 SOC * pinmux: stm32: 96b_carbon: Add support for SPI * Added rcc node on stm32 socs * Added pin config for USART1 on PB6/PB7 for stm32l4 * Removed TI cc3200 SOC and LaunchXL board support Documentation ************* * CONTRIBUTING.rst and Contribution Guide material added * Configuration options doc reorganized for easier access * Navigation sidebar issues fixed for supported boards section * Fixed link targets hidden behind header * Completed migration of wiki.zephyrproject.org content into docs and GitHub wiki. All links to old wiki updated. * Broken link and spelling check scans through .rst, Kconfig (used for auto-generated configuration docs), and source code doxygen comments (used for API documentation). * API documentation added for new interfaces and improved for existing ones. * Documentation added for new boards supported with this release. * Python packages needed for document generation added to new python pip requirements.txt Build System and Tools ********************** * Convert post-processing host tools to python, this includes the following tools: gen_offset_header.py gen_idt.py gen_gdt.py gen_mmu.py Tests and Samples ***************** * Added test Case to stress test round robin scheduling in schedule_api test. * Added test case to stress test priority scheduling in scheduling_api_test. JIRA Related Items ****************** * ``ZEP-230`` - Define I2S driver APIs * ``ZEP-601`` - enable CONFIG_DEBUG_INFO * ``ZEP-702`` - Integrate Nordic's Phoenix Link Layer into Zephyr * ``ZEP-749`` - TinyCrypt uses an old, unoptimized version of micro-ecc * ``ZEP-896`` - nRF5x Series: Add support for power and clock peripheral * ``ZEP-1067`` - Driver for BMM150 * ``ZEP-1396`` - Add ksdk adc shim driver * ``ZEP-1426`` - CONFIG_BOOT_TIME_MEASUREMENT on all targets? * ``ZEP-1552`` - Provide apds9960 sensor driver * ``ZEP-1647`` - Figure out new combo for breathe/doxygen/sphinx versions that are supported * ``ZEP-1744`` - UPF 56 BLE Controller Issues * ``ZEP-1751`` - Add template YAML file * ``ZEP-1819`` - Add tickless kernel support in nrf_rtc_timer timer * ``ZEP-1843`` - provide mechanism to filter test cases based on available hardware * ``ZEP-1892`` - Fix issues with Fix Release * ``ZEP-1902`` - Missing board documentation for arm/nucleo_f334r8 * ``ZEP-1911`` - Missing board documentation for arm/stm3210c_eval * ``ZEP-1917`` - Missing board documentation for arm/stm32373c_eval * ``ZEP-1918`` - Fix connection parameter request procedure * ``ZEP-2018`` - Remove deprecated PWM APIs * ``ZEP-2020`` - tests/crypto/test_ecc_dsa intermittently fails on riscv32 * ``ZEP-2025`` - Add mcux pwm shim driver for k64 * ``ZEP-2031`` - ESP32 Architecture Configuration * ``ZEP-2032`` - Espressif Open-source Toolchain Support * ``ZEP-2039`` - Implement stm32cube LL based clock control driver * ``ZEP-2054`` - Convert all helper script to use python3 * ``ZEP-2062`` - Convert gen_offset_header to a python script * ``ZEP-2063`` - Convert gen_idt to python * ``ZEP-2068`` - Need Tasks to Be Tracked in QRC too * ``ZEP-2071`` - samples: warning: (SPI_CS_GPIO && SPI_SS_CS_GPIO && I2C_NRF5) selects GPIO which has unmet direct dependencies * ``ZEP-2085`` - Add CONTRIBUTING.rst to root folder w/contributing guidelines * ``ZEP-2089`` - UART support for ESP32 * ``ZEP-2115`` - Common API for networked applications for setting up network * ``ZEP-2116`` - Common API for networked apps to create client/server applications * ``ZEP-2141`` - Coverity CID 169303 in tests/net/ipv6/src/main.c * ``ZEP-2150`` - Move Arduino 101 to Device Tree * ``ZEP-2151`` - Move Quark D2000 to device tree * ``ZEP-2156`` - Build warnings [-Wformat] with LLVM/icx (tests/kernel/sprintf) * ``ZEP-2168`` - Timers seem to be broken with TICKLESS_KERNEL on nRF51 (Cortex M0) * ``ZEP-2171`` - Move all board pinmux code from drivers/pinmux/stm32 to the corresponding board/soc locations * ``ZEP-2184`` - Split data, bss, noinit sections into application and kernel areas * ``ZEP-2188`` - x86: Implement simple stack memory protection * ``ZEP-2217`` - schedule_api test fails on ARM with tickless kernel enabled * ``ZEP-2218`` - unexpected short timeslice when running schedule_api with tickless kernel enabled * ``ZEP-2220`` - Extend MPU to stm32 family * ``ZEP-2225`` - Ability to unregister GATT services * ``ZEP-2226`` - BSD Sockets API: Basic blocking API * ``ZEP-2227`` - BSD Sockets API: Non-blocking API * ``ZEP-2229`` - test_time_slicing_preemptible fails on bbc_microbit and other NRF boards * ``ZEP-2250`` - sanitycheck not filtering defconfigs properly * ``ZEP-2258`` - Coverity static scan issues seen * ``ZEP-2265`` - stack declaration macros for ARM MPU * ``ZEP-2267`` - Create Release Notes * ``ZEP-2270`` - Convert mpu_stack_guard_test from using k_thread_spawn to k_thread_create * ``ZEP-2274`` - Build warnings [-Wpointer-sign] with LLVM/icx (tests/net/ipv6_fragment) * ``ZEP-2278`` - KW41-Z 802.15.4 driver hangs if full debug is disabled * ``ZEP-2279`` - echo_server TCP handler corrupt by SYN flood * ``ZEP-2280`` - add test case for KBUILD_ZEPHYR_APP * ``ZEP-2285`` - non-boards shows up in board list for docs * ``ZEP-2286`` - Write a GPIO driver for ESP32 * ``ZEP-2289`` - [DoS] Memory leak from large TCP packets * ``ZEP-2296`` - ESP32: watchdog driver * ``ZEP-2297`` - ESP32: Pin mux driver * ``ZEP-2303`` - Concurrent incoming TCP connections * ``ZEP-2305`` - linker: implement MMU alignment constraints * ``ZEP-2306`` - echo server hangs from IPv6 hop-by-hop option anomaly * ``ZEP-2308`` - (New) Networking API details documentation is missing * ``ZEP-2310`` - Improve configuration documentation index organization * ``ZEP-2314`` - Testcase failure :tests/benchmarks/timing_info/testcase.ini#test * ``ZEP-2316`` - Testcase failure :tests/bluetooth/shell/testcase.ini#test_br * ``ZEP-2318`` - some kernel objects sections are misaligned * ``ZEP-2319`` - tests/net/ieee802154/l2 uses semaphore before initialization * ``ZEP-2321`` - [PTS] All TC's of SM/GATT/GAP failed due to BTP_TIMEOUT error. * ``ZEP-2326`` - x86: API to validate user buffer * ``ZEP-2328`` - gen_mmu.py appears to generate incorrect tables in some situations * ``ZEP-2329`` - bad memory access tests/net/route * ``ZEP-2330`` - bad memory access tests/net/rpl * ``ZEP-2331`` - bad memory access tests/net/ieee802154/l2 * ``ZEP-2332`` - bad memory access tests/net/ip-addr * ``ZEP-2334`` - bluetooth shell build warning when CONFIG_DEBUG=y * ``ZEP-2335`` - Ensure the Licensing page is up-to-date for the release * ``ZEP-2340`` - Disabling advertising gets stuck * ``ZEP-2341`` - Build warnings:override: reassigning to symbol MAIN_STACK_SIZE with LLVM/icx (/tests/net/6lo) * ``ZEP-2343`` - Coverity static scan issues seen * ``ZEP-2344`` - Coverity static scan issues seen * ``ZEP-2345`` - Coverity static scan issues seen * ``ZEP-2352`` - network API docs don't mention when callbacks are called from a different thread * ``ZEP-2354`` - ESP32: Random number generator * ``ZEP-2355`` - Coverity static scan issues seen * ``ZEP-2358`` - samples:net:echo_server: Failed to send UDP packets * ``ZEP-2359`` - samples:net:coaps_server: unable to bind with IPv6 * ``ZEP-2360`` - Initial implementation of Bluetooth Mesh * ``ZEP-2361`` - Provide a POSIX compatibility Layer on top of native APIs * ``ZEP-2365`` - samples/net/wpanusb/test_15_4 fail on nrf52840_pca10056 and frdm_kw41z * ``ZEP-2366`` - implement \__kernel attribute * ``ZEP-2367`` - NULL pointer read in udp, tcp, context net tests * ``ZEP-2368`` - x86: QEMU: enable MMU at boot by default * ``ZEP-2370`` - [test] Create a stress test to test preemptive scheduling on zephyr * ``ZEP-2371`` - [test] Create a stress test to test round robin scheduling with equal priority tasks on zephyr * ``ZEP-2374`` - Build warnings:override: reassigning to symbol NET_IPV4 with LLVM/icx (/tests/net/dhcpv4) * ``ZEP-2375`` - Build warnings [-Wpointer-sign] with LLVM/icx (tests/net/udp) * ``ZEP-2378`` - sample/bluetooth/ipsp: When build the app 'ROM' overflowed * ``ZEP-2379`` - samples/bluetooth: Bluetooth init failed (err -19) * ``ZEP-2380`` - TCP is broken by Zephyr commit 3604c391e * ``ZEP-2382`` - Convert test to use ztest framework * ``ZEP-2383`` - Net-app API needs to support DTLS * ``ZEP-2384`` - "Common" bluetooth sample code does not build out of tree * ``ZEP-2385`` - Update TinyCrypt to 0.2.7 * ``ZEP-2395`` - Assert in http_server example when run over bluetooth on nrf52840 * ``ZEP-2397`` - net_if_ipv6_addr_rm calls k_delayed_work_cancel() on uninitialized k_delayed_work object * ``ZEP-2398`` - network stack test cases are only tested on x86 * ``ZEP-2403`` - Enabling MMU for qemu_x86 broke active connect support * ``ZEP-2407`` - [Cortex m series ] Getting a crash on Cortex m3 series when more than 8 preemptive threads with equal priority are scheduled * ``ZEP-2408`` - design mechanism for kernel object sharing policy * ``ZEP-2412`` - Bluetooth tester app not working from commit c1e5cb * ``ZEP-2423`` - samples/bluetooth/ipsp's builtin TCP echo crashes on TCP closure * ``ZEP-2432`` - ieee802154_shell.c, net_mgmt call leads to a BUS FAULT * ``ZEP-2433`` - x86: do forensic analysis to determine stack overflow context in supervisor mode * ``ZEP-2436`` - Unable to see console output in Quark_D200_CRB * ``ZEP-2437`` - warnings when building applications for quark d2000 * ``ZEP-2444`` - [nrf] Scheduling test API is getting failed in case of nrf51/nrf52 platforms * ``ZEP-2445`` - nrf52: CPU lock-up when using Bluetooth + Flash driver + CONFIG_ASSERT * ``ZEP-2447`` - 'make debugserver' fails for qemu_x86_iamcu * ``ZEP-2451`` - Move Bluetooth IPSP support functions from samples/bluetooth to a separate library * ``ZEP-2452`` - https server does not build for olimex_stm32_e407 * ``ZEP-2457`` - generated/offsets.h is being regenerated unnecessarily * ``ZEP-2459`` - Sample application not working with Quark SE C1000 * ``ZEP-2460`` - tests/crypto/ecc_dh fails on qemu_nios2 * ``ZEP-2464`` - "allow IPv6 interface init to work with late IP assignment" patch broke non-late IPv6 assignment * ``ZEP-2465`` - Static code scan (coverity) issues seen * ``ZEP-2467`` - Static code scan (coverity) issues seen * ``ZEP-2468`` - Static code scan (coverity) issues seen * ``ZEP-2469`` - Static code scan (coverity) issues seen * ``ZEP-2474`` - Static code scan (coverity) issues seen * ``ZEP-2480`` - Build warnings [-Wpointer-sign] with LLVM/icx (samples/net/coaps_server) * ``ZEP-2482`` - Build warnings [-Wpointer-sign] with LLVM/icx (samples/net/telnet) * ``ZEP-2483`` - samples:net:http_client: Failed to get http requests in IPv6 * ``ZEP-2484`` - samples:net:http_server: Failed to work in IPv6 * ``ZEP-2485`` - Build warnings [-Wpointer-sign] with LLVM/icx (samples/net/coaps_client) * ``ZEP-2486`` - Build warnings [-Wpointer-sign] with LLVM/icx (samples/net/mbedtls_dtlsserver) * ``ZEP-2488`` - Build warnings [-Wpointer-sign] and [-Warray-bounds] with LLVM/icx (samples/net/irc_bot) * ``ZEP-2489`` - bug in _x86_mmu_buffer_validate API * ``ZEP-2496`` - Build failure on tests/benchmarks/object_footprint * ``ZEP-2497`` - [TIMER] k_timer_start should take 0 value for duration parameter * ``ZEP-2498`` - [Display] Minimum Duration argument to k_timer_start should be non Zero positive value * ``ZEP-2508`` - esp32 linkage doesn't unify ELF sections correctly * ``ZEP-2510`` - BT: CONFIG_BT_HCI_TX_STACK_SIZE appears to be too low for BT_SPI * ``ZEP-2514`` - XCC sanitycheck build compile wrong targets * ``ZEP-2523`` - Static code scan (Coverity) issue seen in file: /samples/net/zoap_server/src/zoap-server.c * ``ZEP-2525`` - Static code scan (Coverity) issue seen in file: /samples/net/zoap_server/src/zoap-server.c * ``ZEP-2531`` - Static code scan (Coverity) issue seen in file: /tests/net/lib/dns_resolve/src/main.c * ``ZEP-2528`` - Static code scan (Coverity) issue seen in file: /samples/net/nats/src/nats.c * ``ZEP-2534`` - Static code scan (Coverity) issue seen in file: /tests/kernel/irq_offload/src/irq_offload.c * ``ZEP-2535`` - Static code scan (Coverity) issue seen in file: /tests/net/lib/zoap/src/main.c * ``ZEP-2537`` - Static code scan (Coverity) issue seen in file: /tests/crypto/ecc_dh/src/ecc_dh.c * ``ZEP-2538`` - Static code scan (Coverity) issue seen in file: /arch/arm/soc/st_stm32/stm32f1/soc_gpio.c * ``ZEP-2539`` - Static code scan (Coverity) issue seen in file: /tests/net/ieee802154/l2/src/ieee802154_test.c * ``ZEP-2540`` - Static code scan (Coverity) issue seen in file: /ext/lib/crypto/tinycrypt/source/ecc_dh.c * ``ZEP-2541`` - Static code scan (Coverity) issue seen in file: /subsys/bluetooth/host/mesh/cfg.c * ``ZEP-2549`` - Static code scan (Coverity) issue seen in file: /samples/net/leds_demo/src/leds-demo.c * ``ZEP-2552`` - ESP32 uart poll_out always return 0 * ``ZEP-2553`` - k_queue_poll not handling -EADDRINUSE (another thread already polling) properly * ``ZEP-2556`` - ESP32 watchdog WDT_MODE_INTERRUPT_RESET mode fails * ``ZEP-2557`` - ESP32 : Some GPIO tests are getting failed (tests/drivers/gpio/gpio_basic_api) * ``ZEP-2558`` - CONFIG_BLUETOOTH_* Kconfig options silently ignored * ``ZEP-2560`` - samples/net: the sample of zoap_server fails to add multicast address * ``ZEP-2561`` - samples/net: The HTTP client failed to send the POST request * ``ZEP-2568`` - [PTS] All TC's of L2CAP/SM/GATT/GAP failed due to BTP_ERROR. * ``ZEP-2575`` - error:[ '-O: command not found'] with LLVM/icx (samples/hello_world) * ``ZEP-2576`` - samples/net/sockets/echo, echo_async : fails to send the TCP packets * ``ZEP-2581`` - CC3220 executable binary format support * ``ZEP-2584`` - Update mbedTLS to 2.6.0 * ``ZEP-713`` - Implement preemptible regular IRQs on ARC ```	/content/code_sandbox/doc/releases/release-notes-1.9.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	5,392
```restructuredtext :orphan: .. _zephyr_2.4: Zephyr 2.4.0 ############ We are pleased to announce the release of Zephyr RTOS version 2.4.0. Major enhancements with this release include: * Introduced initial support for virtual memory management. * Added Bluetooth host support for periodic advertisement and isochronous channels. * Enabled the new TCP stack, TCP2, by default. This stack was introduced in Zephyr v2.1.0 to improve network protocol testability with open source tools. * Introduced a new toolchain abstraction with initial implementations for GCC and LLVM/Clang, and groundwork for future support of commercial toolchains. * Moved to using C99 integer types and deprecate Zephyr integer types. The Zephyr types can be enabled by Kconfig DEPRECATED_ZEPHYR_INT_TYPES option. The following sections provide detailed lists of changes by component. Security Vulnerability Related ****************************** The following CVEs are addressed by this release: * CVE-2020-10060: UpdateHub Might Dereference An Uninitialized Pointer * CVE-2020-10064: Improper Input Frame Validation in ieee802154 Processing * CVE-2020-10066: Incorrect Error Handling in Bluetooth HCI core * CVE-2020-10072: all threads can access all socket file descriptors * CVE-2020-13598: FS: Buffer Overflow when enabling Long File Names in FAT_FS and calling fs_stat * CVE-2020-13599: Security problem with settings and littlefs * CVE-2020-13601: Under embargo until 2020/11/18 * CVE-2020-13602: Remote Denial of Service in LwM2M do_write_op_tlv More detailed information can be found in: path_to_url Known issues ********** You can check all currently known issues by listing them using the GitHub interface and listing all issues with the `bug label <path_to_url`_. API Changes ********* * Moved to using C99 integer types and deprecate Zephyr integer types. The Zephyr types can be enabled by Kconfig DEPRECATED_ZEPHYR_INT_TYPES option. * The ``<sys/util.h>`` header has been promoted to a documented API with :ref:`experimental stability <api_lifecycle>`. See :ref:`util_api` for an API reference. * The :c:func:`wdt_feed` function will now return ``-EAGAIN`` if issuing a feed would stall the caller. Application code may need to ignore this diagnostic result or initiate another feed operation later. * ``<drivers/uart.h>`` has seen its callbacks normalized. :c:type:`uart_callback_t` and :c:type:`uart_irq_callback_user_data_t` had their signature changed to add a struct device pointer as first parameter. :c:type:`uart_irq_callback_t` has been removed. :c:func:`uart_callback_set`, :c:func:`uart_irq_callback_user_data_set` and :c:func:`uart_irq_callback_set` user code have been modified accordingly. * ``<drivers/dma.h>`` has seen its callback normalized. It had its signature changed to add a struct device pointer as first parameter. Such callback signature has been generalized through the addition of dma_callback_t. 'callback_arg' argument has been renamed to 'user_data. All user code have been modified accordingly. * ``<drivers/ipm.h>`` has seen its callback normalized. :c:type:`ipm_callback_t` had its signature changed to add a struct device pointer as first parameter. :c:func:`ipm_register_callback` user code have been modified accordingly. The context argument has been renamed to user_data and all drivers have been modified against it as well. * The :c:func:`fs_open` function now accepts open flags that are passed as a third parameter. All custom file system front-ends require change to the implementation of ``open`` callback to accept the new parameter. To maintain original behaviour within user code, two argument invocations should be converted to pass a third argument ``FS_O_CREATE \| FS_O_RDWR``. * The struct device got 3 attributes renamed: ``config_info`` to ``config``, ``driver_api`` to ``api`` and finally ``driver_data`` to ``data``. This renaming was done to get rid of legacy names, for which the reasons do no longer apply. * All device instances got a const qualifier. So this applies to all APIs manipulating ``struct device `` (ADC, GPIO, I2C, ...). In order to avoid const qualifier loss on ISRs, all ISRs now take a ``const void`` as a parameter as well. * The ``_gatt_`` and ``_GATT_`` infixes have been removed for the HRS, DIS and BAS APIs and the Kconfig options. * ``<include/bluetooth/gatt.h>`` callback :c:func:`bt_gatt_attr_func_t` used by :c:func:`bt_gatt_foreach_attr` and :c:func:`bt_gatt_foreach_attr_type` has been changed to always pass the original pointer of attributes along with its resolved handle. * Established the unrestricted alignment of flash reads for all drivers. Deprecated in this release ========================== * The full set of ``k_mem_pool`` and ``sys_mem_pool`` APIs are considered deprecated as of this release. The replacements are the ``k_heap`` and ``sys_heap`` APIs. These APIs are not tagged with ``__deprecated`` in the 2.4 release, but will be in 2.5. They will be removed completely in Zephyr 2.6 LTS. The set of APIs now deprecated is as follows: * ``k_mbox_data_block_get()`` * ``k_pipe_block_put()`` * ``K_MEM_POOL_DEFINE()`` * ``k_mem_pool_alloc()`` * ``k_mem_pool_free()`` * ``k_mem_pool_free_id()`` * ``SYS_MEM_POOL_DEFINE()`` * ``sys_mem_pool_init()`` * ``sys_mem_pool_alloc()`` * ``sys_mem_pool_free()`` * ``sys_mem_pool_try_expand_inplace()`` * The Kconfig option ``CONFIG_MULTITHREADING`` to disable multi-threading was deprecated due to lack of maintainership. This means that single-threaded mode with the scheduler disabled is deprecated; normal multi-threaded mode is still fully supported. Removed APIs in this release ============================ * Other * The deprecated ``MACRO_MAP`` macro has been removed from the :ref:`util_api`. Use ``FOR_EACH`` instead. * The CONFIG_NET_IF_USERSPACE_ACCESS is removed as it is no longer needed. * Build system * The set of ``_if_kconfig()`` CMake functions have been removed. Use ``_ifdef(CONFIG_ ...)`` instead. Stable API changes in this release ================================== USB * HID class callbacks now takes a parameter ``const struct device`` which is the HID device for which callback was called. Bluetooth * The ``_gatt_`` infix has been removed from all GATT service APIs. * Bluetooth HCI Driver * bt_hci_evt_is_prio() removed, use bt_hci_evt_get_flags() instead when CONFIG_BT_RECV_IS_RX_THREAD is defined and call bt_recv and bt_recv_prio when their flag is set, otherwise always call bt_recv(). Kernel ****** * Initial support for virtual memory management * API definitions in ``include/sys/mem_manage.h``. * Supporting architectures will implement ``arch_mem_map()`` and enable ``CONFIG_MMU``. * The kernel is linked at its physical memory location in RAM. * The size of the address space is controlled via ``CONFIG_KERNEL_VM_SIZE`` with memory mapping calls allocating virtual memory growing downward from the address space limit towards the system RAM mappings. * This infrastructure is still under heavy development. * Device memory mapped I/O APIs * Namedspaced as DEVICE_MMIO and specified in a new ``include/sys/device_mmio.h`` header. * This is added to facilitate the specification and the storage location of device driver memory-mapped I/O regions based on system configuration. * Maintained entirely in ROM for most systems. * Maintained in RAM with hooks to memory-mapping APIs for MMU or PCI-E systems. * Updates for Memory Domain APIs * All threads now are always a member of a memory domain. A new memory domain ``k_mem_domain_default`` introduced for initial threads like the main thread. * The ``k_mem_domain_destroy()`` and ``k_mem_domain_remove_thread()`` APIs are now deprecated and will be removed in a future release. * Header definitions moved to ``include/app_memory/mem_domain.h``. * Thread stack specification improvements * Introduced a parallel set of ``K_KERNEL_STACK_`` APIs for specifying thread stacks that will never host user threads. This will conserve memory as ancillary data structures (such as privilege mode elevation stacks) will not need to be created, and certain alignment requirements are less strict. Internal interfaces to the architecture code have been simplified. All thread stack macros are now centrally defined, with arches declaring support macros to indicate the alignment of the stack pointer, the stack buffer base address, and the stack buffer size. Architectures ************* * ARC * Added ARC MetaWare toolchain support * General arch improvements for stacks & memory domains * API improvements for cache flush and cache invalidate * Debugging help: show all registers on exception * Fix for fast irq (one register bank configuration) * Fix for undefined shift behavior (CID 211523) * ARM * AARCH32 * Added support for ARM Cortex-M1 architecture. * Implemented the timing API in Cortex-M architecture using the Data Watchpoint and Trace (DWT) unit. * The interrupt vector relaying feature support was extended to Cortex-M Mainline architecture variants. * Cortex-M fault handling implementation was enhanced by adding an option to generate and supply the full register state to the kernel fatal error handling mechanism. * Fixed Cortex-M boot sequence for single-threaded applications (CONFIG_MULTITHREADING=n). * Added thread safety to Non-Secure entry function calls in ARMv8-M architecture. * Fixed stack randomization for main thread. * Fixed exception vector table alignment in Cortex-M architecture * Increased test coverage in QEMU for ARMv6-M architecture variant. * Removed the implementation of arch_mem_domain_* APIs for Cortex-M * AARCH64 * Re-implemented thread context-switch to use the _arch_switch() API * POSIX * RISC-V * x86 * x86 MMU paging support has been overhauled to meet CONFIG_MMU requirements. * ``arch_mem_map()`` is implemented. * Restored support for 32-bit non-PAE paging. PAE use is now controlled via the ``CONFIG_X86_PAE`` option * Initial kernel page tables are now created at build time. * Page tables are no longer strictly identity-mapped * Added ``zefi`` infrastructure for packaging the 64-bit Zephyr kernel into an EFI application. * Added a GDB stub implementation that works over serial for x86 32-bit. Boards & SoC Support ******************** * Added support for these SoC series: * ARM Cortex-M1/M3 DesignStart FPGA * Atmel SAM4L * Nordic nRF52805 * NXP i.MX RT685, i.MX8M Mini, and LPC11U6x * ARC QEMU support for EM and HS family * Made these changes in other SoC series: * STM32L4/STM32WB: Added support for Low Power Mode. * STM32H7/STM32WB/STM32MP1: Added Dual Core concurrent register access protection using HSEM. * Increased cpu frequency for ARC nsim_hs_smp. * Changes for ARC boards: * ARC QEMU boards for ARC EM and HS * ARC MetaWare toolchain support, including mdb runner for various ARC boards * gcov coverage support for ARC QEMU * New nSIM configuration, corresponding to em7d_v22 EMSK board * Enabled SMP on HSDK board, including dual core and quad core configurations. * Switched from legacy ARC-nSIM UART to ns16550 UART model and driver. * Fixed EMSDP secure config for emsdp_em7d_esp. * Added support for these ARM boards: * Adafruit ItsyBitsy M4 Express * Arduino Nano 33 IOT * ARM Cortex-M1/M3 DesignStart FPGA reference designs running on the Digilent Arty A7 development board * Atmel SAM4L-EK board * Circuit Dojo nRF9160 Feather * EOS S3 Quick Feather * Laird Connectivity Pinnacle 100 Modem Development board (pinnacle_100_dvk) * nRF21540 DK (nrf21540dk_nrf52840) * nRF52805 emulation on nRF52 DK (nrf52dk_nrf52805) * nRF5340 DK * Nuvoton npcx7m6fb and pfm m487 boards * NXP i.MX RT685 EVK, i.MX8M Mini EVK, LPCXpresso LPC11U68 * OLIMEX-STM32-H103 * Ruuvitag board * Seagate FaZe board * Seeeduino XIAO * Serpente board * Silicon Labs BRD4180A (a.k.a. SLWRB4180A) Mighty Gecko Radio Board * ST B_L4S5I_IOT01A Discovery kit * ST NUCLEO-H745ZI-Q * Waveshare Open103Z * WeAct Studio Black Pill V2.0 * Made these changes in other boards: * b_l072z_lrwan1: Added flash, LoRa, USB, EEPROM, RNG * nRF boards: enabled HW Stack Protection by default on boards maintained by Nordic * nucleo_l552ze_q: Added non secure target and TFM support * STM32 boards: Enabled MPU on all boards with at least 64K flash * lpcxpresso55s69: Added TFM support * Added support for these following shields: * Adafruit WINC1500 Wifi * ARM Ltd. V2C-DAPLink for DesignStart FPGA * Atmel AT86RF2XX Transceivers * Buydisplay 2.8" TFT Touch Shield with Arduino adapter * DAC80508 Evaluation Module Drivers and Sensors ******************* * ADC * Added chip select flags to SPI ADC drivers. * Audio * N/A * Bluetooth * L2CAP RX MTU is now controlled by CONFIG_BT_L2CAP_RX_MTU when CONFIG_BT_ACL_FLOW_CONTROL is disabled, previously this was controlled by CONFIG_BT_RX_BUF_LEN. If CONFIG_BT_RX_BUF_LEN has been changed from its default value then CONFIG_BT_L2CAP_RX_MTU should be set to CONFIG_BT_RX_BUF_LEN - 8. * CAN * Added chip select flags to SPI CAN drivers. * Fixed MCP2515 driver to wait to reset. * Clock Control * STM32: Various changes including Flash latency wait states computation, configuration option additions for H7 series, and fixes on F0/F3 PREDIV1 support * Added LPC11U6X driver. * Console * Added IPM driver. * Counter * STM32: Added support on F0/F2 series. * Added MCUX PIT counter driver for Kinetis K6x and K8x SoCs. * Crypto * N/A * DAC * STM32: Added support for F0/F2/G4/L1 series. * Debug * N/A * Display * Enhanced SSD16XX driver to support loading WS from OTP. * Added chip select flags to SPI display drivers. * DMA * STM32: Number of changes including k_malloc removal, driver priority init increase, get_status API addition and various cleanups. * Added MCUX EDMA driver for i.MX RT and Kinetis K6x SoCs. * Added MCUX LPC driver for LPC and i.MX RT6xx SoCs. * EEPROM * Added driver supporting the on-chip EEPROM found on NXP LPC11U6X MCUs. * Fixed at2x cs gpio flags extraction from DT. * Entropy * STM32: Added support for ISR mode. Added support on F7/H7/L0 series. * ESPI * Enhanced XEC driver to support KBC status operations, ACPI_EC1 interface, and slaves with long initializations. * Fixed XEC driver frequency override during IO selection. * Ethernet * Added VLAN support to Intel e1000 driver. * Added Ethernet support to stm32h7 based boards (with IT based TX). * Moved stm32 driver to device tree configuration. * Added support for setting fixed configuration and read from device tree for ENET ETH interface and PHY in mcux driver. * Added support for device that do not use SMI for PHY setup in mcux driver. * Added support for multiport gPTP in native_posix driver. This allows gPTP bridging testing. * Fixed MAC registers in enc28j60 driver to the latest Microchip reference manual. * Flash * The driver selected by ``CONFIG_SPI_FLASH_W25QXXDV`` has been removed as it is unmaintained and all its functionality is available through ``CONFIG_SPI_NOR``. Out of tree uses should convert to the supported driver using the ``jedec,spi-nor`` compatible. * Enhanced nRF QSPI NOR flash driver (nrf_qspi_nor) so it supports unaligned read offset, read length and buffer offset. * Added SFDP support in spi_nor driver. * Fixed regression in nRF flash driver (soc_flash_nrf) with :kconfig:option:`CONFIG_BT_CTLR_LOW_LAT` option. * Introduced NRF radio scheduler interface in nRF flash driver (soc_flash_nrf). * STM32: Factorized support for F0/F1/F3. Added L0 support. Various fixes. * GPIO * Added driver for the Xilinx AXI GPIO IP. * Added LPC11U6X driver. * Hardware Info * Added Atmel SAM4L driver. * I2C * Introduced new driver for NXP LPC11U6x SoCs. See :kconfig:option:`CONFIG_I2C_LPC11U6X`. * Introduced new driver for emulated I2C devices, where I2C operations are forwarded to a module that emulates responses from hardware. This enables testing without hardware and allows unusual conditions to be synthesized to test driver behavior. See :kconfig:option:`CONFIG_I2C_EMUL`. * STM32: V1: Reset i2c device on read/write error. * STM32: V2: Added dts configurable Timing option. * Fixed MCUX LPI2C driver transfer status after NACK. * I2S * Added LiteX controller driver. * IEEE 802.15.4 * Allow user to disable auto-start of IEEE 802.15.4 network interface. By default the IEEE 802.15.4 network interface is automatically started. * Added support for setting TX power in rf2xx driver. * Added Nordic 802.15.4 multiprotocol support, see :kconfig:option:`CONFIG_NRF_802154_MULTIPROTOCOL_SUPPORT`. * Added Kconfig :kconfig:option:`CONFIG_IEEE802154_VENDOR_OUI_ENABLE` option for defining OUI. * Interrupt Controller * Enhanced GICV3 driver to support SGI API. * Added NPCX MIWU driver. * IPM * Added Intel ADSP driver. * Keyboard Scan * Enhanced FT5336 driver to support additional part number variants. * LED * Added TI LP503X controller driver. * Introduced led_set_color, let_get_info, and channel-dedicated syscalls * Added shell support. * LED Strip * Enhanced APA102 driver to support SPI chip select. * LoRa * Made various enhancements and fixes in SX1276 driver. * Modem * Added option to query the IMSI and ICCID from the SIM. * Added support for offloaded Sierra Wireless HL7800 modem. * PECI * N/A * Pinmux * Added LPC11U6X driver. * Added NPCX driver. * PS/2 * N/A * PWM * STM32: Refactored using Cube LL API. * Added SAM9 TCC based driver. * Sensor * Added API function ``sensor_attr_get()`` for getting a sensor's attribute. * Added support for wsen-itds accelerometer sensor. * Added chip select flags to SPI sensor drivers. * Added IIS2DH accelerometer driver. * Added MAX17055 fuel-gauge sensor driver. * Added SI7055 temperature sensor driver. * Enhanced FXOS8700 driver to support magnetic vector magnitude function. * Added SM351LT magnetoresistive sensor driver. * Added VCNL4040 proximity and light sensor driver. * Refactored LIS2DH and LSM6DSL drivers to support multiple instances. * Serial * Added driver for the Xilinx UART Lite IP. * Added NXP IUART driver for i.MX8M Mini. * Implemented uart_config_get API in MCUX UART driver. * Added LPC11U6X driver. * SPI * The SPI driver subsystem has been updated to use the flags specified in the cs-gpios devicetree properties rather than the SPI_CS_ACTIVE_LOW/HIGH configuration options. Devicetree files that specify 0 for this field will probably need to be updated to specify GPIO_ACTIVE_LOW. SPI_CS_ACTIVE_LOW/HIGH are still used for chip selects that are not specified by a cs-gpios property. * Added driver for the Xilinx AXI Quad SPI IP. * STM32: Various fixes around DMA mode. * Extended MCUX Flexcomm driver to support slave mode. * Added optional delays to MCUX DSPI and LPSPI drivers. * Timer * N/A * USB * The usb_enable() function, which, for some samples, was invoked automatically on system boot up, now needs to be explicitly called by the application in order to enable the USB subsystem. If your application relies on any of the following Kconfig options, then it shall also enable the USB subsystem: * :kconfig:option:`CONFIG_USB_DEVICE_NETWORK_ECM` * :kconfig:option:`CONFIG_USB_DEVICE_NETWORK_EEM` * :kconfig:option:`CONFIG_USB_DEVICE_NETWORK_RNDIS` * :kconfig:option:`CONFIG_TRACING_BACKEND_USB` * ``CONFIG_USB_UART_CONSOLE`` * USB device support has got its own work queue which is used by CDC ACM class by default. * CDC ACM Class was slightly reworked. * Suspend and resume support in CDC ACM and HID classes has been corrected. * Atmel SAM0 USB device driver (usb_dc_sam0) was revised. All drivers now use common macros for getting indexes and direction from an endpoint. * Video * N/A * Watchdog * Added MCUX WWDT driver for LPC SoCs. * Enhanced Gecko driver to support Gecko Series 2 SoC. * WiFi * Added IPv6 support to Simplelink driver. * Added DNS offloading support to eswifi driver. * Fixed esp driver offload protocol parsing. * Fixed esp driver GPIO reset control logic. * Fixed eswifi driver offloading packet parsing. Networking ********** * The new TCP stack is enabled by default. The legacy TCP stack is not yet removed and can be used if needed. * The network interface is made a kernel object. This allows better access control handling when usermode is enabled. * The kernel stacks are used in network related threads to save memory when usermode is enabled. * Network statistics collection can be enabled in key points of the network stack. This can be used to get information where time is spent in RX or TX. * The BSD socket sendmsg() can now be used with AF_PACKET type sockets. * Added support for enabling OpenThread reference device. * Added support for enabling MQTT persistent sessions. * Added "net tcp recv" command to net shell to enable TCP RX in manual testing. * Added ObjLnk resource type support to LWM2M. * Added userspace support to MQTT publisher, echo-server and echo-client sample applications. * Added support to rejecting received and unsupported PPP options. * Added support for select() when using socket offloading. * Added support for IPv6 multicast packet routing. * Added support to SOCK_DGRAM type sockets for AF_PACKET family. * Added support for using TLS sockets when using socket offloading. * Added additional checks in IPv6 to ensure that multicasts are only passed to the upper layer if the originating interface actually joined the destination multicast group. * Allow user to specify TCP port number in HTTP request. * Allow application to initialize the network config library instead of network stack calling initialization at startup. This enables better control of network resources but requires application to call net_config_init_app() manually. * Allow using wildcards in CoAP resource path description. * Allow user to specify used network interface in net-shell ping command. * Allow user to select a custom mbedtls library in OpenThread. * Removed dependency to :kconfig:option:`CONFIG_NET_SOCKETS_POSIX_NAMES` from offloaded WiFi device drivers. * Print more gPTP status information in gptp net shell. * Fixed the network traffic class statistics collection. * Fixed WiFi shell when doing a scan. * Fixed IPv6 routes when nexthop is link local address of the connected peer. * Fixed IPv6 Router Solicitation message handling. * Fixed BSD socket lib and set errno to EBADF if socket descriptor is invalid. * Fixed received DNS packet parsing. * Fixed DNS resolving by ignoring incoming queries while we are resolving a name. * Fixed CoAP zero length option parsing. * Fixed gPTP port numbering to start from 1. * Fixed gPTP BMCA priority vector calculation. * Fixed multiple interface bound socket recv() for AF_PACKET sockets. * Fixed PPP Term-Req and Term-Ack packet length when sending them. * Fixed PPP ipv6cp and ipcp Configure-Rej handling. * Fixed PPP option parsing and negotiation handling. * Fixed PPP ipcp option handling when the protocol goes down. * Fixed PPP ipv6cp and ipcp network address removal when connection goes down. * Added support to rejecting received and unsupported PPP options. * Added initial support for PAP authentication in PPP. * Fixed a race PPP when ppp_fsm_open() was called in CLOSED state. * Fixed LWM2M FOTA socket closing. * Fixed LWM2M block transfer retransmissions. * Fixed LWM2M opaque data transfer in block mode. * Fixed LWM2M Security and Server object instance matching. * Fixed LWM2M updating lifetime on Register Update event. * Fixed MQTT double CONNACK event notification on server reject. Bluetooth ********* * Host * Added basic support for Isochronous Channels (also known as LE Audio). * Added support for Periodic Advertising (both Advertising and Scanning procedures). * The application can now specify preferences for the PHY update procedure PHY choices. * A new "bond_deleted" callback has been introduced. * Added a new callback for GATT (un)subscription. * Added support for the application to provide subscription information to the stack prior to reconnection (``bt_gatt_resubscribe``). * The application can now request for the CCC descriptor to be discovered automatically by the stack when subscribing to a characteristic. * Fixed a regression introduced in 2.3 along the EATT feature, where the ATT throughput could not reach the expected values. * Fixed a deadlock in the RX thread that was observed multiple times in scenarios involving high throughput and a sudden disconnection. * Fixed a race condition upon advertising resume. * The GATT notify multiple feature is now disabled by default. * The advertiser can now be requested to restart even when a connection object is not available. * The L2CAP security level will now be elevated automatically when a connection is rejected for security reasons. * When LE Secure Connections are the only option enabled, the security level will now be elevated to Level 4 automatically. * Fixed CCC restoring when using settings lazy loading. * Fixed recombination of ACL L2CAP PDUs when the header itself is split across multiple HCI ACL packets. * GATT no longer assumes the position of the CCC descriptor and instead discovers it. * Multiple additional fixes. * Mesh * Added support for storage of model data in a key-value fashion. * Added support for a network loopback. * Multiple qualification-related fixes. * BLE split software Controller * The advanced scheduling algorithms that were supported in the legacy Controller have been ported to the split one. * Preliminary support for Advertising Extensions, restricted to non-connectable advertising for now. * Very early support for Periodic Advertising. This should be considered an early experimental draft at this stage. * Added full support for the Nordic nRF5340 IC, not just the engineering sample. * Added support for the Nordic nRF52805 IC. * Several fixes to scheduling and window calculation, some of which had an impact in the cooperation between the flash driver and the Controller. * Fixed an null pointer dereference in the ticker code. * HCI Driver * A new BT_QUIRK_NO_AUTO_DLE has been added for Controllers that do not follow the recommendation of auto-initating the data length update procedure. This is in fact the case of the split software Controller. Build and Infrastructure ************************ * Improved support for additional toolchains: * Better toolchain abstractions. * Support for the ARC MetaWare toolchain. * Devicetree * Added new devicetree macros that provide a default value if the property or cell accessor doesn't contain the requested data. * Added support for inferring bindings for ``/zephyr,user`` devicetree node to allow applications an easy way to specify application specific devicetree properties without having a binding. * Support for multiple SOC and ARCH roots. The :ref:`SOC_ROOT <application>` and ``ARCH_ROOT`` variables used to specify support files for out of tree SoCs and architectures now accept multiple paths, separated by semicolons. As a result, the ``SOC_DIR`` Kconfig variable is no longer supported. Uses like ``source $(SOC_DIR)/<path>`` must be changed to ``rsource <relative>/<path>`` or similar. * BOARD, SOC, DTS, and ARCH roots can now be specified in each module's :file:`zephyr/module.yml` file; see :ref:`modules_build_settings`. Libraries / Subsystems ********************** * Disk * Management * MCUmgr * Moved mcumgr into its own directory. * UDP port switched to using kernel stack. * smp: added missing socket close in error path. * Added support for Open Supervised Device Protocol (OSDP), see :kconfig:option:`CONFIG_OSDP`. * updatehub * Added download block check. * Added support to flash integrity check using SHA-256 algorithm. * Moved updatehub from lib to subsys/mgmt directory. * Fixed out-of-bounds access and add flash_img_init return value check. * Fixed getaddrinfo resource leak. * Settings * If a setting read is attempted from a channel that doesn't support reading return an error rather than faulting. * Disallow modifying the content of a static subtree name. * Random * POSIX subsystem * Power management * Logging * Fixed immediate logging with multiple backends. * Switched logging thread to use kernel stack. * Allow users to disable all shell backends at one using :kconfig:option:`CONFIG_SHELL_LOG_BACKEND`. * Added Spinel protocol logging backend. * Fixed timestamp calculation when using NEWLIB. * LVGL * Library has been updated to the new major release v7.0.2. * It is important to note that v7 introduces multiple API changes and new configuration settings, so applications developed on v6 or previous versions will likely require some porting work. Refer to `LVGL 7 Release notes <path_to_url`_ for more information. * LVGL Kconfig option names have been aligned with LVGL. All LVGL configuration options ``LV_[A-Z0-9_]`` have a matching Zephyr Kconfig option named as ``CONFIG_LVGL_[A-Z0-9_]``. * LVGL Kconfig constants have been aligned with upstream suggested defaults. If your application relies on any of the following Kconfig defaults consider checking if the new values are good or they need to be adjusted: * :kconfig:option:`CONFIG_LVGL_HOR_RES_MAX` * :kconfig:option:`CONFIG_LVGL_VER_RES_MAX` * :kconfig:option:`CONFIG_LVGL_DPI` * :kconfig:option:`CONFIG_LVGL_DISP_DEF_REFR_PERIOD` * :kconfig:option:`CONFIG_LVGL_INDEV_DEF_READ_PERIOD` * :kconfig:option:`CONFIG_LVGL_INDEV_DEF_DRAG_THROW` * :kconfig:option:`CONFIG_LVGL_TXT_LINE_BREAK_LONG_LEN` * :kconfig:option:`CONFIG_LVGL_CHART_AXIS_TICK_LABEL_MAX_LEN` * Note that ROM usage is significantly higher on v7 for minimal configurations. This is in part due to new features such as the new drawing system. LVGL maintainers are currently investigating ways for reducing the library footprint when some options are not enabled, so you should wait for future releases if higher ROM usage is a concern for your application. * Shell * Switched to use kernel stacks. * Fixed select command. * Fixed prompting dynamic commands. * Change behavior when more than ``CONFIG_SHELL_ARGC_MAX`` arguments are passed. Before 2.3 extra arguments were joined to the last argument. In 2.3 extra arguments caused a fault. Now the shell will report that the command cannot be processed. * Storage * Added flash SHA-256 integrity check. * Tracing * Tracing backed API now checks if init function exists prio to calling it. * Debug * Core Dump * Added the ability to do core dump when fatal error is encountered. This allows dumping the CPU registers and memory content for offline debugging. * Cortex-M, x86, and x86-64 are supported in this release. * A data output backend utilizing the logging subsystem is introduced in this release. HALs **** * HALs are now moved out of the main tree as external modules and reside in their own standalone repositories. Documentation *********** Tests and Samples *************** * nvs: Do full chip erase when flashing. * nrf: onoff_level_lighting_vnd_app: Fixed build with mcumgr. * drivers: flash_shell: new commands write_unaligned and write_pattern. * bluetooth: hci_spi: Fixed cmd_hdr and acl_hdr usage. * Removed zephyr nfc sample. * drivers: Fixed uninitialized spi_cfg in spi_fujitsu_fram sample. * Updated configuration for extended advertising in Bluetooth hci_uart and hci_rpmsg examples. Issue Related Items ******************* These GitHub issues were addressed since the previous 2.3.0 tagged release: * :github:`28665` - boards b_l4s5i_iot01a: invertion of user LEDS polarity * :github:`28659` - [Coverity CID :214346] Out-of-bounds access in subsys/net/ip/tcp2.c * :github:`28654` - [lwm2m stm32F429] No registration with server possible * :github:`28653` - Bluetooth: Mesh: TX Power Dynamic Control * :github:`28639` - tests: kernel: sleep: is failing for nRF51 * :github:`28638` - bq274xx sample unable to build * :github:`28635` - nrf: qspi: devicetree opcode properties are ignored * :github:`28628` - samples/tfm_integration/tfm_ipc: regression on nucleo_l552_ze * :github:`28627` - tests: kernel: fatal: exception: stack_sentinel test is failing for nRF platforms * :github:`28625` - tests: net: tcp2: llegal use of the EPSR * :github:`28621` - tests: kernel: mem_protect: syscalls: wrong FAULTY_ADDRESS for nucleo_l073rz * :github:`28605` - Build failure - (64-bit platforms) acrn/bcm958402m2_a72/native_posix_64/... on a number of sanitycheck tests w/TCP2 * :github:`28604` - mcumgr smp_svr sample not working over shell or serial transport * :github:`28603` - tests: kernel: timer: timer_api: Failed on nucleo_l073rz * :github:`28602` - TCP2:frdm_k64f/mimxrt1064_evk tests/net/tcp2 regression failure in RC2 * :github:`28577` - possible bug / regression in new TCP stack * :github:`28571` - Erroneous call to ull_disable_mark in ull_adv::disable() * :github:`28565` - sensor: lsm6dsl: incompatible pointer type (warning) * :github:`28559` - Unable to extend the flash sync API part of the BLE Controller * :github:`28552` - up_squared: samples/portability/cmsis_rtos_v1/philosophers/ failed. * :github:`28549` - up_squared: tests/kernel/threads/thread_apis/ failed * :github:`28548` - up_squared: tests/arch/x86/pagetables/ failed. * :github:`28547` - up_squared: tests/subsys/debug/coredump failed. * :github:`28540` - littlefs: MPU FAULT and failed to run * :github:`28538` - Atmel SAM4L have two pinctrl with wrong map * :github:`28492` - Could not build Zephyr application for swervolf_nexys board in simulation * :github:`28480` - ``tests/lib/devicetree/legacy_api/libraries.devicetree.legacy`` fails to build on pinnacle_100_dvk * :github:`28471` - Central not working properly on nRF5340-DK * :github:`28465` - Building OpenThread NCP: build system has concurrency issue * :github:`28460` - Generated ExternalProject include directories * :github:`28453` - qemu 5.1 hangs on a number tests on x86_64 * :github:`28443` - drivers: sensor: hts221 compilation issue linked to DT property drdy_gpios * :github:`28434` - Shell Tab Completion Candidates results in segmentation fault * :github:`28414` - kernel/timeout: next_timeout() is returning negative number of ticks * :github:`28413` - [Coverity CID :214280] Unintentional integer overflow in tests/posix/common/src/nanosleep.c * :github:`28412` - [Coverity CID :214279] 'Constant' variable guards dead code in tests/drivers/clock_control/nrf_lf_clock_start/src/main.c * :github:`28411` - [Coverity CID :214281] Unchecked return value in subsys/mgmt/osdp/src/osdp.c * :github:`28397` - gcc 10.x compile warning/error for array subscript is outside the bounds in cmsis_rtos_v2/thread.c * :github:`28394` - nanosleep test failed on ARC series targets * :github:`28390` - drivers: sensor: lsm6dsl compilation issue when sensor defined in board (I2C) and in test (SPI) * :github:`28385` - drivers.clock.nrf_lf_clock_start_xtal_no_wait.wait_in_thread fails on nrf9160dk_nrf9160 * :github:`28384` - Bluetooth: L2CAP: Bad CoC SDU segment handling * :github:`28380` - drivers: peci: xec: Cannot recover PECI bus after PECI transfer fails * :github:`28375` - gcc 10.x compile warning/error for array subscript 0 is outside the bounds in tests/bluetooth/tester/src/gap.c * :github:`28371` - gcc 10.x compile warning/error for array subscript 0 is outside the bounds in subsys/bluetooth/mesh/prov.c * :github:`28361` - USB audio samples fails if ASSERT=y * :github:`28360` - drivers: nrf_802154: SWI IRQ priority is not read correctly * :github:`28347` - Possible use-after-free of rx_msg->tx_block in kernel/mailbox.c * :github:`28344` - cdc_acm sample with CONFIG_NO_OPTIMIZATIONS=y crashes on nrf52840 dev board * :github:`28343` - Bluetooth peripheral sample auto disconnects "ST B_L4S5I_IOT01A Discovery kit" * :github:`28341` - No SRAM available to link echo_server for atsamr21 with ieee802154.overlay * :github:`28337` - Cannot flash Atmel boards using west * :github:`28332` - What is the airspeed velocity of an unladen swallow running Zephyr? * :github:`28331` - Shell on CDC ACM UART stopped working after PR #24873 * :github:`28326` - Sample boards nrf mesh onoff not working * :github:`28325` - bluetooth: null pointer dereference for non-connectable extended advertising * :github:`28324` - GATT notifications aren't working for CUD characteristics * :github:`28319` - tests: kernel: context: fails because timer expiration is shorter than excepted * :github:`28317` - Asymmetric nrfx spi_transceive tx/rx lengths outputs error * :github:`28307` - Can't build bootloader/mcuboot while ``CONF_FILE`` contains multiple files. * :github:`28305` - Device not found (SX1276 with nRF52840) * :github:`28303` - nucleo_l4r5zi uses wrong pinmux setting * :github:`28295` - kernel.common: lpcxpresso55s16_ns test failure * :github:`28294` - arch.interrupt.gen_isr_table.arm_mainline: lpcxpresso55s16_ns failed * :github:`28289` - tests: arch: arm: arm_sw_vector_relay: fails on nucleo_f091rc * :github:`28283` - LWM2M: Invalid ACK when server is using message ID 0 * :github:`28282` - Slave host auto-initiate stalls if master does not support extended reject indications, and procedure collision occurs * :github:`28280` - tests/kernel/tickless/tickless_concept: disco_l475_iot1 build issue * :github:`28275` - drivers: bluetooth: hci_spi: hci driver is init before spi causing an error on device_get_binding * :github:`28270` - Errors in the HL7800.c file * :github:`28267` - up_squared(acrn):running tests/kernel/workq/work_queue_api/ failed * :github:`28266` - up_squared(acrn):running tests/kernel/sched/schedule_api/ failed * :github:`28265` - up_squared(acrn):running tests/kernel/timer/timer_api/ failed * :github:`28264` - up_squared(acrn):running tests/kernel/timer/timer_monotonic/ failed * :github:`28262` - up_squared(acrn):running tests/kernel/tickless/tickless_concept/ failed * :github:`28261` - up_squared(acrn):running tests/kernel/common/ failed * :github:`28260` - up_squared(acrn):running tests/portability/cmsis_rtos_v2/ failed * :github:`28259` - up_squared(acrn):running tests/subsys/debug/coredump/ failed * :github:`28258` - up_squared(acrn):running tests/drivers/counter/counter_cmos/ failed * :github:`28256` - mimxrt1050_evk: running samples/subsys/fs/fat_fs/ failed * :github:`28255` - mimxrt1050_evk:running samples/drivers/display/ failed * :github:`28251` - Tests of the cmsis_dsp library fails on nrf52840dk_nrf52840 platform * :github:`28248` - bt_gatt_notify() causes "unable to alllocate TX buffer" * :github:`28240` - nordic spim: does not work with SPI-SDHC infrastructure * :github:`28234` - ipv6: multicast group: wrong filtering * :github:`28230` - "make zephyr_generated_headers" produces incorrect result (SHELL:") after recent cmake refactor * :github:`28229` - Possible NULL dereference in subsys/net/ip/net_context.c. * :github:`28223` - LEDs in the board nRF52840dk_nRF52840 dont work with Lora * :github:`28218` - Possible NULL dereference in subsys/logging/log_msg.c. * :github:`28216` - socket: send fails instead of blocking when there are no more net buffers * :github:`28211` - "High" current drawn when ussing RTT log back-end with CONFIG_LOG_IMMEDIATE and CONFIG_LOG_BACKEND_RTT_MODE_DROP * :github:`28206` - mimxrt685_cm33: many cases has no console output seems hangs in kernel init. * :github:`28205` - kernel.timer.tickless: frdmk64f failure * :github:`28203` - Cannot flash TI boards using west * :github:`28202` - Adafruit TFT touch shield cap touch flipped sides left-to-right * :github:`28197` - samples/net/sockets/echo_client/sample.net.sockets.echo_client.nrf_openthread fails to build * :github:`28196` - samples/boards/intel_s1000_crb/audio/sample.board.intel_s1000_crb.audio Fails to build * :github:`28193` - include/drivers/flash: API stands mistakenly unrestricted alignment of writes. * :github:`28185` - Problem using SX1276 with nRF52840dk * :github:`28184` - tests: drivers: spi: spi_loopback: fails on board nucleo_wb55rg * :github:`28181` - MQTT not working with MOSQUITTO broker: * :github:`28174` - [Coverity CID :214213] Improper use of negative value in tests/net/socket/af_packet/src/main.c * :github:`28173` - [Coverity CID :214210] Side effect in assertion in tests/arch/arm/arm_interrupt/src/arm_interrupt.c * :github:`28172` - [Coverity CID :214227] Resource leak in subsys/mgmt/hawkbit/hawkbit.c * :github:`28171` - [Coverity CID :214224] Unsigned compared against 0 in subsys/storage/flash_map/flash_map.c * :github:`28169` - [Coverity CID :214220] Explicit null dereferenced in subsys/mgmt/hawkbit/hawkbit.c * :github:`28167` - [Coverity CID :214209] Dereference after null check in subsys/mgmt/osdp/src/osdp.c * :github:`28166` - [Coverity CID :214211] Unused value in drivers/entropy/entropy_stm32.c * :github:`28165` - [Coverity CID :214215] Out-of-bounds access in subsys/mgmt/mcumgr/smp_shell.c * :github:`28164` - [Coverity CID :214225] Buffer not null terminated in subsys/net/lib/lwm2m/ipso_generic_sensor.c * :github:`28163` - [Coverity CID :214223] Untrusted value as argument in subsys/net/lib/sockets/sockets_tls.c * :github:`28162` - [Coverity CID :214221] Untrusted value as argument in subsys/net/lib/sockets/sockets_tls.c * :github:`28161` - [Coverity CID :214219] Uninitialized scalar variable in subsys/net/lib/sockets/sockets_tls.c * :github:`28160` - [Coverity CID :214212] Negative array index read in subsys/net/lib/dns/resolve.c * :github:`28157` - benchmark.data_structures fails(bus error) on mimxrt1020/60/64/frdmk64f platform * :github:`28156` - twr_kv58f220m: libraries.cmsis_dsp.transform.cf64 test fails * :github:`28154` - reel_board:running samples/subsys/usb/console/ failed * :github:`28153` - reel_board: running samples/subsys/shell/fs/ failed * :github:`28152` - frdm_k64f: running samples/subsys/canbus/canopen/ failed * :github:`28151` - gPTP should allow user setting of priority1 and priority2 fields used in BMCA * :github:`28150` - mec15xxevb_assy6853:running samples/boards/mec15xxevb_assy6853/power_management/ failed * :github:`28149` - mec15xxevb_assy6853:running samples/drivers/ps2/ failed * :github:`28148` - mec15xxevb_assy6853:running samples/drivers/espi/ failed * :github:`28146` - mec15xxevb_assy6853:running samples/drivers/kscan/ failed * :github:`28145` - nRF52840 Dongle cannot scan LE Coded PHY devices * :github:`28139` - tests: benchmarks: data_structure_perf: rbtree_perf: uninitialized root struct * :github:`28138` - No more able to flash board on windows * :github:`28134` - mcuboot: specifying -DCONF_FILE results in failure * :github:`28133` - using nrf52dk_nrf52832 with serial disabled * :github:`28131` - Crash while serving large files via HTTP with TCP2 * :github:`28118` - timers strange rounding errors * :github:`28114` - subsys: OSDP forces SERIAL=y * :github:`28112` - timer/scheduler problem (STM32F407) * :github:`28108` - EEPROM shell MPU Fault when performing a write command with more than 9 bytes * :github:`28104` - sanitycheck overloaded by tests/subsys/logging/log_immediate with large -j values * :github:`28099` - subsys: power: device implicit depends on CONFIG_SYS_POWER_MANAGEMENT * :github:`28097` - cmake: fails to filter options for target language * :github:`28095` - Doc: Getting Started Guide: reel board blinky gif is outdated * :github:`28092` - Make SPI speed of SDHC card configurable * :github:`28090` - bluetooth: build error with extended advertising * :github:`28083` - Align MWDT and LD linker scripts * :github:`28069` - eswifi: build failure * :github:`28068` - Crash in USB device when turning HFXO off * :github:`28061` - nrf52840 can't boot up after power plug in,unless it was connected to JLINKRTTVIEWER with a JTAG * :github:`28059` - sample for sensor lps22hh is not filtered out for bare nrf52dk_nrf52832 * :github:`28057` - TCP2: client side receives EOF before all pending data is fed into it * :github:`28053` - Eclipse broken build ability * :github:`28052` - metairq_dispatch sample fails on nrf platforms * :github:`28049` - nucleo_wb55rg: test/spi/spi_loopback build failure * :github:`28045` - [mimxrt1050_evk] uart_fifo_fill only send 1 byte * :github:`28040` - sanitycheck reports test timeouts as "exited with 2" * :github:`28036` - samples/drivers/flash_shell/sample.drivers.flash.shell fails to build on nucleo_wb55rg * :github:`28033` - rand32_ctr_drbg.c fails to build * :github:`28032` - eth_enc424j600 fails to build * :github:`28031` - samples/subsys/mgmt/mcumgr/smp_svr/sample.mcumg.smp_svr.bt fails to build * :github:`28020` - call k_malloc or k_mem_slab_alloc allowed or not * :github:`28017` - tests/bluetooth/init/bluetooth.init.test_controller_dbg_ll_sw_split fails to build on a few boards * :github:`28016` - tests/boards/intel_s1000_crb/main/boards.s1000_crb.main fails to build * :github:`28013` - tests/misc/test_build/buildsystem.kconfig.utf8_in_values fails on faze * :github:`28012` - tests/net/lib/mqtt_subscriber/net.mqtt.subscriber fails to build on cc3220sf_launchxl * :github:`28006` - Module: mbedtls broken following driver instances const-ification * :github:`28003` - Module: segger broken following driver instances const-ification * :github:`28000` - sam_e70_xplained:Test cases run failed at tests/net/lib/dns_packet/. * :github:`27985` - change in device initialization behavior * :github:`27982` - TCP2: Apparent issues with client-side connections (hangs when server (apparently) closes connection). * :github:`27964` - usb: Standard requests are not filtered. * :github:`27963` - tests: net: socket: af_packet: failed on nucleo_f746zg * :github:`27958` - USB: GET_STATUS(Device) is improperly handled * :github:`27943` - tests/kernel/sched/schedule_api fails on nsim_hs_smp * :github:`27935` - hci_uart not acknowledging data correctly / losing packets * :github:`27934` - Tests ignore custom board config overlays * :github:`27931` - Address resolving when eswifi is used causes MPU FAULT * :github:`27929` - Address resolving when eswifi is used causes MPU FAULT * :github:`27928` - Settings api hangs * :github:`27921` - Bluetooth: Dynamic TX power is overwritten every procedure * :github:`27915` - Samples:LoRa send;sx126x with NRF52840dk ,no data from SPI miso * :github:`27887` - Event counter may get out of sync when multiple events collide in ticker * :github:`27880` - build errors for some samples/ on lpcxpresso55s69_cpu1 * :github:`27876` - TCP2: Apparent issues with server-side connections (>1 connection doesn't work properly) * :github:`27874` - Nordic timer failures with synchronized periodic timers * :github:`27867` - up_squared: couldn't get test result from serial of each test. * :github:`27855` - i2c bitbanging on nrf52840 * :github:`27849` - tests: lib: cmsis_dsp: transform: malloc out of memory * :github:`27847` - tests/lib/sprintf fails on native_posix_64 * :github:`27843` - spi_nor.c: Wrong buffers for rx_set * :github:`27838` - [Coverity CID :212961] Side effect in assertion in tests/kernel/threads/thread_apis/src/test_threads_cancel_abort.c * :github:`27837` - [Coverity CID :212956] Out-of-bounds access in tests/kernel/mem_protect/mem_map/src/main.c * :github:`27836` - [Coverity CID :212960] Logically dead code in samples/net/sockets/echo_client/src/echo-client.c * :github:`27835` - [Coverity CID :212962] Macro compares unsigned to 0 in include/sys/mem_manage.h * :github:`27834` - [Coverity CID :212959] Macro compares unsigned to 0 in include/sys/mem_manage.h * :github:`27833` - [Coverity CID :212958] Out-of-bounds access in arch/x86/core/x86_mmu.c * :github:`27832` - [Coverity CID :212957] Out-of-bounds access in arch/x86/core/x86_mmu.c * :github:`27821` - frdm_k64f:running test cases /tests/subsys/power/power_mgmt/ error * :github:`27820` - reel_board:running failed in tests/drivers/gpio/gpio_api_1pin/ * :github:`27813` - samples without sample.yaml * :github:`27811` - intermittent failure of tests/net/socket/select on qemu_x86 * :github:`27803` - samples: update to support new devicetree flag defaults * :github:`27792` - Default clock settings for STM32F7 violates operating conditions * :github:`27791` - DT_DRV_COMPAT in spi_flash_w25qxxdv.c named incorrectly * :github:`27785` - memory domain arch implementation not correct with respect to SMP on ARC * :github:`27783` - Add support for mbedTLS Server Name Indication (SNI) at configuration * :github:`27771` - iotdk: cpu_stats function doesn't work as expected * :github:`27768` - Usage fault when running with CONFIG_NO_OPTIMIZATIONS=y * :github:`27765` - Sanitycheck: non-existing test case shows up in .xml file. * :github:`27753` - drivers: sensor: lis2dh: compilation issue struct lis2dh_config' has no member named 'spi_conf' * :github:`27745` - Zephyr with host stack and hci driver only ? * :github:`27738` - em_starterkit_7d sanitycheck test failure on tests\kernel\mem_protect\syscalls test * :github:`27734` - vl53l0x driver gives wrong offset calibration value * :github:`27727` - mcumgr serial interface does not work with CDC_ACM UART * :github:`27721` - Concurrent file descriptor allocations may return the same descriptor * :github:`27718` - Updatehub might dereference an uninitialized pointer * :github:`27712` - warnings when compiling smp_svr with newlibc on 2.3.0 * :github:`27706` - Cannot debug specific files * :github:`27693` - Crash on ARM when BT LE scan response packet too big * :github:`27648` - [Coverity CID :212430] Unchecked return value in tests/kernel/msgq/msgq_api/src/test_msgq_contexts.c * :github:`27647` - [Coverity CID :212429] Negative array index write in tests/subsys/fs/fs_api/src/test_fs_dir_file.c * :github:`27646` - [Coverity CID :212428] Unchecked return value in tests/kernel/msgq/msgq_api/src/test_msgq_contexts.c * :github:`27645` - [Coverity CID :212424] Unchecked return value in tests/kernel/msgq/msgq_api/src/test_msgq_contexts.c * :github:`27644` - [Coverity CID :212141] Improper use of negative value in tests/lib/fdtable/src/main.c * :github:`27643` - [Coverity CID :212427] Invalid type in argument to printf format specifier in samples/drivers/jesd216/src/main.c * :github:`27642` - [Coverity CID :212143] Unused value in samples/drivers/flash_shell/src/main.c * :github:`27641` - [Coverity CID :212142] Unused value in samples/drivers/flash_shell/src/main.c * :github:`27640` - [Coverity CID :212426] Unrecoverable parse warning in drivers/wifi/eswifi/eswifi_socket_offload.c * :github:`27639` - [Coverity CID :212425] Out-of-bounds access in drivers/ethernet/eth_mcux.c * :github:`27637` - Bluetooth: controller: Possible corruption in AD data * :github:`27636` - sensor: shell float output broken w/ CONFIG_NEWLIB_LIBC=y * :github:`27634` - wifi simple_link driver build error * :github:`27613` - CONFIG_ASSERT not working on nrf5340dk_nrf5340_cpunet in hci_rpmsg sample * :github:`27612` - RFC: API Change: usb: Device argument to USB HID ops * :github:`27610` - UART_ERROR_FRAMING * :github:`27600` - JSON Api refuse to decode null value * :github:`27599` - bluetooth shell deadlock on USB shell UART * :github:`27597` - build system fails to propagate devicetree change to Kconfig * :github:`27592` - threads without name show up as junk names in SystemView * :github:`27587` - New socket close() implementation broke build of platforms using socket offloading * :github:`27582` - BT Identity address is overwritten when using extended advertising * :github:`27580` - west install error * :github:`27576` - sample.drivers.sample.drivers.peci failed to run * :github:`27574` - mec15xxevb_assy6853:arch.arm.arch.arm.no.multithreading failed to run * :github:`27572` - mec15xxevb_assy6853:crypto.tinycrypt.hmac_prng.hmac_prng failed to build, * :github:`27571` - up_squared:tests/portability/cmsis_rtos_v2/thread_api failed * :github:`27569` - mimxrt1050_evk:samples.usb.cdc-acm-composite failed * :github:`27566` - nRF52832: MCUBoot cannot read signed SMP Server Sample binary * :github:`27560` - APIs for dynamically creating thread stacks * :github:`27558` - "west update" only certain vendor * :github:`27548` - CMake and west doesn't accept multiple overlay files during build * :github:`27547` - samples/boards/reel_board/mesh_badge fails booting with error in i2c_nrfx_twim * :github:`27544` - TrustZone: NSC_ALIGN gets redefined * :github:`27533` - kernel crashes with small CONFIG_TIMESLICE_SIZE * :github:`27531` - Zephyr testing via emulators * :github:`27529` - sanitycheck: incorrect correct calculation of total_skipped when --subset is set: * :github:`27526` - poll(2) returning -1 errno ENOMEM * :github:`27523` - [RFC] drivers: display: Implementing driver for sharp memory display * :github:`27522` - shell: Output can get corrupted when printing from thread before command completes * :github:`27511` - coverage: qemu platforms: sanitycheck generates many ``unexpected eof`` failures when enable coverage * :github:`27505` - spi: mchp: Unintended data is transmitted when tx and rx operations are performed simultaneously * :github:`27503` - testcases under zephyr/tests/application_development take a very long time to dump coverage data * :github:`27495` - Include full register state in ARM Cortex M Exception Stack Frame (ESF) * :github:`27488` - Bluetooth Mesh samples don't build * :github:`27482` - Bluetooth stops responding when calling k_delayed_work_submit. v2.3.0 * :github:`27473` - RT1050/60/64-evk board user LED does not work * :github:`27465` - How recursively build boards on Zephyr? * :github:`27464` - LOG_BACKEND_NET does not work for certain application/ip configurations * :github:`27463` - Cannot build samples/net/sockets/echo for cc3220sf_launchxl * :github:`27448` - fatal error: device_imx.h: No such file or directory * :github:`27446` - Unable to flash cc1352r (no xds) with openocd in Zephyr SDK * :github:`27444` - spi sdhc CS signal not working * :github:`27434` - Bluetooth: L2CAP: buffer use after free * :github:`27428` - Cannot compile network logging backend with IPv6-only * :github:`27421` - libraries.cmsis_dsp.matrix.binary_q15: buffer allocation failure on twr_kv58f220m * :github:`27420` - drivers.uart: config test failure on uart_mcux.c (was twr_kv58f220m platform) * :github:`27414` - Bluetooth: Controller: First advertisement does not preempt continuous scanner * :github:`27404` - IS_ENABLED not working with C++ (was: Is DT_INST_FOREACH_STATUS_OKAY broken on v2.3?) * :github:`27403` - uart_fifo_read can only read one character * :github:`27399` - [RFC] API change - Switch all struct device to constant * :github:`27397` - [RFC] API change - Device structure attribute renaming * :github:`27396` - samples/subsys/logging/logger timeout when sanitycheck enable coverage, it needs a filter * :github:`27392` - tests/kernel/device/kernel.device.pm fails to build on cc1352r1_launchxl * :github:`27380` - Cannot use mcuboot with i.MXRT1060 due to a problem with the vector table address * :github:`27379` - Macro Z_ARC_MPU_SIZE_ALIGN seems to be missing * :github:`27377` - up_squared(acrn):samples/philosophers/ caused the acrn platform crashed. * :github:`27375` - "west zephyr-export" dumps stack if cmake is not installed * :github:`27373` - CivetWeb Support for STM32H7 Series * :github:`27370` - Constant asserts from nrf5 clock calibration * :github:`27366` - tests: net: regression on many tests * :github:`27363` - mec15xxevb_assy6853:kernel.device.pm failed * :github:`27362` - cannot move to 1M baud rate in bt_shell * :github:`27353` - west flash ignores --bin-file parameter and uses hex file when nrfjprog is used internally * :github:`27348` - When using CONFIG_NVS it triggers BUS FAULT during startup on "nucleo_wb55rg" board * :github:`27340` - <wrn> bt_driver: Discarding event 0x3e * :github:`27339` - up_squared: Zephyr does not boot via grub anymore * :github:`27338` - Bluetooth: host: GATT service request is not able to trigger the authentication procedure while in SC only mode * :github:`27331` - Fails to upload over BLE using Zephyr with SMP Server Sample * :github:`27330` - include in prj.conf * :github:`27329` - [Coverity CID :211587] Unchecked return value in tests/drivers/clock_control/clock_control_api/src/test_clock_control.c * :github:`27328` - [Coverity CID :211586] Resource leak in tests/posix/fs/src/test_fs_open_flags.c * :github:`27327` - [Coverity CID :211585] Argument cannot be negative in tests/posix/fs/src/test_fs_open_flags.c * :github:`27326` - [Coverity CID :211584] Logically dead code in drivers/wifi/eswifi/eswifi_core.c * :github:`27325` - [Coverity CID :211583] Unchecked return value in drivers/wifi/eswifi/eswifi_socket.c * :github:`27324` - [Coverity CID :211572] Out-of-bounds read in soc/xtensa/sample_controller/include/_soc_inthandlers.h * :github:`27323` - [Coverity CID :211551] Out-of-bounds read in soc/xtensa/sample_controller/include/_soc_inthandlers.h * :github:`27322` - [Coverity CID :211546] Out-of-bounds read in soc/xtensa/sample_controller/include/_soc_inthandlers.h * :github:`27321` - [Coverity CID :211539] Out-of-bounds read in soc/xtensa/sample_controller/include/_soc_inthandlers.h * :github:`27320` - [Coverity CID :211537] Out-of-bounds read in soc/xtensa/sample_controller/include/_soc_inthandlers.h * :github:`27319` - [Coverity CID :211523] Bad bit shift operation in arch/arc/core/mpu/arc_mpu_v2_internal.h * :github:`27318` - Decouple TLS socket from net_context * :github:`27303` - RFC: downgrade i2c eeprom_slave driver to test * :github:`27293` - Test nrf52840dk_nrf52840 tests/net/socket/net_mgmt/net.socket.mgmt build failure * :github:`27288` - linker relocation feature fails for out of tree projects * :github:`27282` - Drivers in app folder * :github:`27280` - drivers: bluetooth: hci: spi: CS DT config not working because CS gpio_dt_flags are not set in the spi_cs_config struct * :github:`27268` - usb: mcux RT1060 EVK - when using on-chip memory, USB fails * :github:`27266` - samples: bluetooth: hci_spi: Invalid cmd_hdr and acl_hdr usage * :github:`27249` - Is there any development plan for supporting RPL stack * :github:`27239` - samples/subsys/canbus/isotp/sample.subsys.canbus.isotp fails on FRDM-K64F * :github:`27238` - tests/net/socket/af_packet fails on FRDM-K64F * :github:`27237` - Out_of_tree example broken * :github:`27227` - shell crashes on qemu_x86 board upon the Tab button press * :github:`27220` - Bluetooth: L2CAP: l2cap_change_security() not considering bt_conn::sec_level when handling BT_L2CAP_LE_ERR_AUTHENTICATION * :github:`27219` - thousands of lines of log spam in buildkite output * :github:`27212` - drivers: clock_control: stm32h7 cannot choose system frequency higher than 400MHz * :github:`27211` - sanitycheck: add option to only build/run on emulated targets * :github:`27205` - tests/kernel/timer/timer_api test fails on twr_ke18f * :github:`27202` - tests/kernel/threads/thread_apis failure on lpcxpresso55s16_ns * :github:`27181` - New drivers out of device tree * :github:`27177` - Unable to build samples/bluetooth/st_ble_sensor for steval_fcu001v1 board * :github:`27173` - [v2.1] Unable to build Zephyr 2.1 for Upsquared board running ACRN * :github:`27172` - shell: logging: CONFIG_SHELL_LOG_BACKEND is forced if CONFIG_LOG is chosen * :github:`27166` - tests/kernel/sched/schedule_api need add ram limitaion as some platform not support * :github:`27164` - tests/lib/mem_alloc failed on up_squared board. * :github:`27162` - reel_board:tests/net/ieee802154/l2 failed. * :github:`27161` - shell: shell_start() and shell_stop() can cause deadlock * :github:`27154` - bt_conn_le_param_update doesn't return an error when setting the timeout >30sec, stops device from sleeping on nrf52840 * :github:`27151` - sanitycheck: samples: net: echo_server: Doesn't run all configurations from atmel_rf2xx shield * :github:`27150` - [Coverity CID :211513] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`27149` - [Coverity CID :211508] Unchecked return value in tests/kernel/mem_protect/futex/src/main.c * :github:`27148` - [Coverity CID :211506] Operands don't affect result in tests/drivers/clock_control/nrf_onoff_and_bt/src/main.c * :github:`27147` - [Coverity CID :211505] Operands don't affect result in tests/drivers/clock_control/nrf_onoff_and_bt/src/main.c * :github:`27145` - [Coverity CID :211511] Dereference after null check in subsys/net/ip/net_if.c * :github:`27144` - [Coverity CID :211501] Explicit null dereferenced in subsys/net/ip/tcp2.c * :github:`27143` - [Coverity CID :211512] Out-of-bounds read in drivers/wifi/eswifi/eswifi_socket_offload.c * :github:`27142` - [Coverity CID :211509] Out-of-bounds read in drivers/wifi/eswifi/eswifi_socket_offload.c * :github:`27141` - [Coverity CID :211507] Out-of-bounds read in drivers/wifi/eswifi/eswifi_socket_offload.c * :github:`27140` - [Coverity CID :211504] Out-of-bounds read in drivers/wifi/eswifi/eswifi_socket_offload.c * :github:`27139` - [Coverity CID :211503] Out-of-bounds read in drivers/wifi/eswifi/eswifi_socket_offload.c * :github:`27138` - [Coverity CID :211502] Out-of-bounds read in drivers/wifi/eswifi/eswifi_socket_offload.c * :github:`27130` - samples/drivers/spi_flash has no README * :github:`27120` - exception happened when running CI * :github:`27118` - Bluetooth: HCI: Missing implementation of hci_driver.h functions * :github:`27112` - [v2.3.0] mcumgr fs download crashes * :github:`27090` - LE Coded PHY scanning on nRF9160DK fails * :github:`27081` - missing ``python3-devel`` dependency (was python3-psutil) * :github:`27080` - uarte_instance_init() in NRF UARTE driver does not disable UART prior to setting PSEL pin values * :github:`27079` - espi: driver: mchp: eSPI driver indicates flash channel is ready to eSPI host even before the channel negotiation takes place * :github:`27078` - drivers: espi: mchp: Cannot perform multiple transactions over eSPI OOB channel * :github:`27074` - doc: coding_guidelines: broken links to MISRA-C example suite * :github:`27071` - USB: CDC-ACM uart console hijacks usb_enable call preventing user applications from registering callbacks * :github:`27057` - NUCLEO-H745ZI-Q add cortex-m4 ethernet support * :github:`27056` - Local header found before system header of same name * :github:`27055` - BlueZ with ESP32 boards supported or not? * :github:`27037` - No network interface found when running wifi sample * :github:`27010` - net: ieee802154: wrong header generation * :github:`27003` - CMakeLists.txt newline check is too strict * :github:`27002` - checkpatch.pl incorrect ERROR:POINTER_LOCATION * :github:`26998` - [Coverity CID :211479] Unchecked return value in tests/kernel/mutex/mutex_api/src/test_mutex_apis.c * :github:`26997` - [Coverity CID :211474] Unchecked return value in tests/kernel/mutex/mutex_api/src/test_mutex_apis.c * :github:`26996` - [Coverity CID :211340] Side effect in assertion in tests/kernel/smp/src/main.c * :github:`26995` - [Coverity CID :211478] Logically dead code in samples/net/sockets/big_http_download/src/big_http_download.c * :github:`26994` - [Coverity CID :210616] Resource leak in lib/updatehub/updatehub.c * :github:`26993` - [Coverity CID :210593] Out-of-bounds access in lib/updatehub/updatehub.c * :github:`26992` - [Coverity CID :210547] Unchecked return value in lib/updatehub/updatehub.c * :github:`26991` - [Coverity CID :210072] Resource leak in subsys/mgmt/smp_udp.c * :github:`26990` - i2c transfers are timing out with SSD1306 display * :github:`26989` - [Coverity CID :211477] Unchecked return value in subsys/net/lib/lwm2m/lwm2m_engine.c * :github:`26988` - [Coverity CID :211473] Unchecked return value in subsys/net/lib/lwm2m/lwm2m_engine.c * :github:`26986` - [Coverity CID :211480] Printf arg count mismatch in arch/x86/zefi/zefi.c * :github:`26985` - [Coverity CID :211476] Extra argument to printf format specifier in arch/x86/zefi/zefi.c * :github:`26984` - sys/device_mmio.h API design should accept generic DT node identifiers * :github:`26983` - MPU FAULT in nRF52840-DK * :github:`26981` - Problem with PPP + GSM MUX with SIMCOM7600E * :github:`26970` - usb: overflow of USB transfers leads to clogging * :github:`26966` - Example OTA-DFU for Android/IOS app * :github:`26961` - occasional sanitycheck failures in samples/subsys/settings * :github:`26954` - devicetree: warning: braces around scalar initializer * :github:`26953` - settings: ISO C++ forbids converting a string constant to 'char' :github:`26948` - cmake failure when using ZEPHYR_MODULES without west * :github:`26941` - Meta-IRQ documentation references * :github:`26939` - MCUMGR - smp shell server sends responses to wrong port * :github:`26937` - Kconfig choice Warning * :github:`26924` - Bluetooth: Mesh: no space to store ccc cfg * :github:`26923` - [RFC] API change - Normalize DMA, IPM and UART callbacks signatures including the caller's device pointer. * :github:`26919` - ipv6: promiscuous mode: packet flood over 802.15.4 adapter * :github:`26914` - gen_kobject_list.py dosn't generate correct gperf info for ARC MetaWare toolchain * :github:`26910` - sanitycheck always treats warnings as errors * :github:`26900` - Bluetooth: host: bt_conn_recv() assumes ACL data is >= 2 bytes * :github:`26896` - STM32: mcu goes to sleep inadvertently when using PM. * :github:`26868` - qemu_x86_64 icount support with SMP * :github:`26862` - Bluetooth: GATT: CCC is not properly stored * :github:`26848` - kernel: undefined reference with --no-gc-sections * :github:`26833` - RFC: subsys: fs: Support file open flags to fs and POSIX API * :github:`26832` - [mcux_counter_rtc][frdm_k82f] counter_basic_api hangs * :github:`26828` - Build Error - Network communication between Zephyr app on QEMU and Host OS * :github:`26826` - i2c_nrfx_twi_transfer hangs when SDA/SCL are set to pins 0,1 * :github:`26818` - drivers: uart_console.c: usb_enable() broken * :github:`26814` - net_ipv6_send_rs behaviour doesn't comply with RFC4291 * :github:`26812` - NXP: tests/drivers/dma/loop_transfer fails on FRDM-K64F * :github:`26807` - Bluetooth HCI USB sample is not working * :github:`26805` - test: drivers: i2c: i2c_slave_api: * :github:`26804` - Bluetooth mesh repeated provision/gatt bearer connection crash * :github:`26803` - Cortex-M7 Thumb-2 Instructions Alignment * :github:`26801` - UART API has ifdefs around API functions * :github:`26796` - Interrupts on Cortex-M do not work with CONFIG_MULTITHREADING=n * :github:`26793` - kernel: work: triggers immediately with longer timeouts * :github:`26788` - cmake build system works wrong with cmake version 3.15.5 * :github:`26782` - boards: mchp: mec15xxevb_assy6853: Cannot set gpios as alternate function when enabling multiple instances of a driver * :github:`26769` - "west flash -r openocd --serial <serial_num>" ignores serial_num and flashes wrong board * :github:`26766` - Build failure on nucleo_wb55rg for tests/kernel/profiling/profiling_api/kernel.common.profiling * :github:`26764` - Build failure on intel_s1000_crb for samples/drivers/flash_shell/sample.drivers.flash.shell * :github:`26759` - Build error - Nothing found at GNUARMEMB_TOOLCHAIN_PATH * :github:`26758` - Missing documentation of report targets (ram/rom report, puncover) * :github:`26746` - Change sanitycheck to used pickled EDT * :github:`26731` - Single channel selection - Bluetooth - Zephyr * :github:`26729` - FCB flash_area_write fails on nRF52840DK when using mx25r64 storage * :github:`26725` - USB suspend-resume process is not properly handled * :github:`26723` - NULL handler in work queue entry can be called resulting in silent reboot * :github:`26720` - lib: sockets: getaddrinfo don't work without newlib C on ARM * :github:`26717` - Big HTTP Download - Upgrade * :github:`26708` - RFC: API Change: watchdog: wdt_feed error codes * :github:`26701` - Invalid handling of large cycle count in rtc timer * :github:`26700` - waveshare_open103z board can't build tests/mem_protect * :github:`26695` - net: TCP2: connect() returns 0 without waiting for handshake completion * :github:`26689` - Couldn't get test result from serial on up_squared board. * :github:`26685` - sanitycheck "--only-failed" is broken * :github:`26683` - Transition from non-secure to kernel causes "Stacking error" * :github:`26679` - sanitycheck passes tests if the emulator exits unexpectedly * :github:`26676` - MDB runner is not capturing real board's output * :github:`26665` - Implement reset for ARC development boards * :github:`26664` - frdm_kw41z: tests/drivers/pwm/pwm_api fails in test_pwm_cycle() * :github:`26663` - sanitycheck reports failing tests with em_starterkit_em7d_v22 board * :github:`26651` - Updatehub: frdm_k64f resets in a loop * :github:`26647` - build generates unaligned function reference in v2.3 * :github:`26643` - Nucleo board Slow Code execution at power up - need to always reset * :github:`26628` - Couldn't find Definition for CTE transmit and enable command for Connectionless AoA/AoD implementation in Zephyr * :github:`26627` - tests/benchmarks/sys_kernel failed on up_squared. * :github:`26626` - tests/portability/cmsis_rtos_v1 failed on reel_board. * :github:`26625` - tests/net/utils failed on multiple arm platforms. * :github:`26624` - Noridc52840 hci_usb bug on linux when " discoverable on " by bluetoothctl * :github:`26621` - System can't recover after assertion failed in kernel/mem_domain.c * :github:`26619` - tests/unit/rbtree fails * :github:`26617` - devicetree: sam0 gclk * :github:`26607` - STM32F0 nucleo PWM output not working * :github:`26602` - GH Action: Automate removal of tag "Waiting for response" * :github:`26600` - net.util test is broken on MPU-enabled ARM platforms * :github:`26596` - west: rimage support in ``west sign`` poorly documented * :github:`26595` - tests/kernel/obj_tracing thread counting issue with 1.14 branch. * :github:`26587` - DT_CALL_WITH_ARG macro missing * :github:`26586` - K_TIMER_DEFINE macro causing build error * :github:`26582` - What happened to DT_HAS_NODE macro? * :github:`26575` - devicetree: need save/restore support for devicetree data * :github:`26568` - tests: net: socket: af_packet: is ethernet cable now mandatory to run this test ? * :github:`26555` - uart: uart_nrfx_uarte: async init does not cleanup previous sync rx * :github:`26551` - sam0 devicetree failing to compile * :github:`26536` - The CONFIG_BT_L2CAP_RX_MTU setting is not reflected correctly in the build * :github:`26529` - How to support Nordic ble5.0 on Android 7.0 * :github:`26527` - mimxrt1050_evk:Couldn't flash image by using west flash command. * :github:`26524` - Problem with hci_uart and L2CAP CoC connections * :github:`26519` - samples: net: sockets: dumb_http_server: instabllity on nucleo_f767zi * :github:`26518` - NRF temperature sensor driver race condition * :github:`26509` - net_l2_ppp.ppp_link_terminated: SARA U201 modem * :github:`26508` - CI: simulated BT tests not run if BT tests are changed * :github:`26506` - how does hci_usb (hci_usb fw : \ncs\v1.3.0\zephyr\samples\bluetooth\hci_usb) set mac and send/receive files ? * :github:`26505` - An example of using the microphone in Thingy 52 * :github:`26499` - usermode: random: backport random syscall * :github:`26476` - ARM Cortex-A: architecture timer continuously firing in tick-less mode * :github:`26467` - Bluetooth: Race-condition on persistent connectable advertiser * :github:`26466` - Bluetooth: host: Do auto-postponement of advertising also when application requests advertising * :github:`26455` - bme280 connect to rt1020_evk * :github:`26450` - Bad disconnect reason when client connects with wrong address type * :github:`26438` - Bluetooth: Reconnection to paired/bonded peripheral fails * :github:`26435` - Suspicious source code with subsys/random/random32_entropy_device: seg fault risk * :github:`26434` - nrf9160 uart_tx can return -ENOTSUP, which is not documented behavior * :github:`26428` - LPSPI support for i.MX RT106x * :github:`26427` - Linker problems with zephyr-sdk-0.11.2: undefined reference to 'gettimeofday' * :github:`26424` - master west.yml references pull in hal_stm32 * :github:`26419` - Cannot request update when writing to external flash * :github:`26415` - CONFIG_FS_LOG_LEVEL_OFF option doesn't work with LittleFS * :github:`26413` - disco_l475_iot1: flash storage corruption caused by partition overlap * :github:`26410` - RFC: soc: Initial Nuvoton NPCX port * :github:`26407` - fs: nvs: Incorrect handling of corrupt ate's in nvs_gc * :github:`26406` - On x86, the main stack overflows when CONFIG_NET_IPV6 and CONFIG_DEBUG are enabled * :github:`26403` - Compile Error when trying to build samples/synchronization * :github:`26397` - storage: flash_map: Only works on limited compatibles * :github:`26391` - stm32f746g: sample subsys/usb/hid-cdc does not work * :github:`26377` - Problems getting I2C to work on NXP i.MX RT1020 EVK * :github:`26372` - qspi driver does not work if multithreading is disabled * :github:`26369` - C++ compilation warning for Z_TIMEOUT_TICKS * :github:`26363` - samples: subsys: canbus: canopen: objdict: CO_OD.h is not normally made. * :github:`26362` - arc gdb failed to load core dump file * :github:`26361` - [Coverity CID :211051] Explicit null dereferenced in tests/lib/ringbuffer/src/main.c * :github:`26360` - [Coverity CID :211048] Side effect in assertion in tests/drivers/uart/uart_async_api/src/test_uart_async.c * :github:`26359` - [Coverity CID :211047] Dereference null return value in tests/net/ipv6/src/main.c * :github:`26358` - [Coverity CID :211044] Unchecked return value in tests/subsys/settings/fcb_init/src/settings_test_fcb_init.c * :github:`26357` - [Coverity CID :211046] Unchecked return value in boards/posix/native_posix/timer_model.c * :github:`26356` - [Coverity CID :211043] Logical vs. bitwise operator in subsys/net/lib/lwm2m/lwm2m_rw_oma_tlv.c * :github:`26355` - [Coverity CID :211045] Macro compares unsigned to 0 in kernel/timeout.c * :github:`26354` - [Coverity CID :211040] Macro compares unsigned to 0 in kernel/timeout.c * :github:`26353` - [Coverity CID :211039] Out-of-bounds access in drivers/gpio/gpio_nrfx.c * :github:`26352` - [Coverity CID :211049] Macro compares unsigned to 0 in arch/x86/core/x86_mmu.c * :github:`26343` - Gatt Bearer Issue * :github:`26337` - BT scan: filter duplicates yields duplicates * :github:`26333` - Bluetooth: Split LL: Cannot store Bluetooth keys * :github:`26313` - nucleo_h745zi_q_m7 pwm device tree bug * :github:`26303` - Bluetooth: Windows 10 cannot reconnect on direct advertising from Zephyr * :github:`26302` - Test gen_isr_tables from ./tests/kernel/gen_isr_table/ fails on nrf9160dk_nrf9160 * :github:`26296` - Store logs in persistent storage (ext. flash, SD card) * :github:`26295` - Enable persistent storage (ext flash/SD card) as logger backend * :github:`26294` - Test suite output is hard to read * :github:`26291` - canopen: error when CAN_MCP2515_MAX_FILTER > 8 * :github:`26290` - gfhgf * :github:`26284` - device.h doxygen * :github:`26281` - Question: Does NRF52840-DK support both OpenThread and BLE at the same time * :github:`26280` - test_kernel_systicks from tests/portability/cmsis_rtos_v1 fails on nrf platforms * :github:`26279` - littlefs: Unable to erase external flash. * :github:`26278` - [v2.2] bt_att: Unhandled ATT code 0x1d * :github:`26271` - k_sleep/k_msleep ends too early on UP_squared board * :github:`26267` - drivers: SPI: CS output type not honored * :github:`26266` - Cast and shift operator priority issue may lead to wrong memory size result in fat_fs example * :github:`26265` - Zephyr os bluetooth peripheral example indication. When i flash code to my board custom configuration for indication will shown and after i click button for indication it device will disconnect from phone. My board is nrf52832. * :github:`26264` - tests/benchmarks/latency_measure failed on up_squared board. * :github:`26263` - reel_board:tests/posix/common failed. * :github:`26259` - Add AT86RF233 REB Xplained Pro Extension shield * :github:`26256` - NRF51822 BLE Micro module: hangs on k_msleep() (RTC counter not working) * :github:`26255` - k_uptime_ticks() returns pointer instead of value * :github:`26252` - bluetooth: controller: Cannot receive long packets * :github:`26248` - A timer with 24-hour timeout fires immediately * :github:`26242` - qemu_x86 and qemu_cortex_m3 time handling broken with CONFIG_QEMU_ICOUNT * :github:`26235` - multi vlan support networking * :github:`26234` - Question: how can a NRF52840-DK's clock be set to 64MHz * :github:`26232` - Segger Embedded Studio doesn't find the right python * :github:`26220` - OpenThread L2 does not implement ``enable`` API function * :github:`26209` - sanitycheck tries to run random samples, without being asked for * :github:`26200` - BT_LE_ADV_OPT_EXT_ADV causes bt_le_adv_start to return -22 * :github:`26197` - tracking provenance of utility code * :github:`26185` - Sample posix:eventfd fails on all platforms * :github:`26177` - Bluetooth: Mesh: Friend node unexpected un-reference buffer * :github:`26174` - Add STM32H7 Series Ethernet Driver Support * :github:`26172` - Zephyr Master/Slave not conforming with Core Spec. 5.2 connection policies * :github:`26169` - Enable -O0 for only one \.c file :github:`26168` - arch-level memory-mapping interface * :github:`26167` - Extend the sensor API with function for getting the value of a sensor attribute * :github:`26165` - Clock not initialized in LPC Flexcomm UART driver * :github:`26150` - storage/stream: flash_img_bytes_written() might returns more than number of payload bytes written. * :github:`26149` - building native_posix against musl-libc * :github:`26139` - west: nrfjprog and jlink runner leave SW-DP registers in enabled state * :github:`26136` - CMake Error in Windows Environment * :github:`26131` - nrf52840_mdk: add support for nrf stock bootloader * :github:`26119` - Compilation error when enabling MPU on STM32 L0 boards * :github:`26112` - bug: cmake loops when passing overlay file with left slashes in file path * :github:`26107` - driver MMIO virtual address space mapping * :github:`26106` - mcumgr: smp_bt: wrong notify MTU calculation with CONFIG_BT_GATT_NOTIFY_MULTIPLE * :github:`26105` - Test kernel.memory_protection.stack_random fails on nrf52dk_nrf52832 * :github:`26104` - Asynchronous input via UART * :github:`26096` - cmake finds a DTC from Zephyr-SDK version, it tries to execute it, and it fails * :github:`26095` - Requirements.txt pip version conflict * :github:`26080` - gPTP time sync fails if having more than one port * :github:`26076` - bug: cortex-m0: vector table base address is set to zero when soc has control over where to put vector table. * :github:`26071` - Bluetooth: host: ATT sent callback lost * :github:`26070` - Bluetooth: ATT request not processed * :github:`26065` - sanitycheck reports failing tests with timeout as passing * :github:`26064` - tests/kernel/timer/timer_api failed on mec15xxevb_assy6853 board. * :github:`26059` - Potentially incorrect interrupt handling in nRF SoC .dtsi for GPIO * :github:`26049` - False multiple define of irq with IRQ_CONNECT * :github:`26039` - tests: kernel: timer: timer_api: regression on STM32 boards * :github:`26038` - build zephyr with llvm fail * :github:`26037` - RFC: API Change: Bluetooth Mesh * :github:`26034` - menuconfig target aborts when Kconfig warnings are present * :github:`26033` - NET_SOCKETS_OFFLOAD conflicts with POSIX_API * :github:`26030` - RV32M1_RI5CY: tests/kernel/threads/thread_apis and thread_init fails * :github:`26021` - Problems compiling for Measuring Time * :github:`26017` - Build error in shell with gcc 10.1 (tests/drivers/uart/uart_basic_api) * :github:`25991` - [net][net.socket.select][imx-rt series] test fails (k_uptime_get_32() - tstamp <= FUZZ is false) * :github:`25990` - tests/net/socket/select failed on sam_e70_xplained board. * :github:`25989` - STM32_LPTIM_TIMER wrongly depends on DEVICE_POWER_MANAGEMENT * :github:`25988` - [Coverity CID :210687] Argument cannot be negative in tests/net/socket/socketpair/src/test_socketpair_happy_path.c * :github:`25987` - [Coverity CID :210685] Pointless string comparison in tests/lib/devicetree/legacy_api/src/main.c * :github:`25986` - [Coverity CID :210684] Explicit null dereferenced in tests/kernel/mbox/mbox_api/src/test_mbox_api.c * :github:`25985` - [Coverity CID :210683] Pointless string comparison in tests/lib/devicetree/legacy_api/src/main.c * :github:`25984` - [Coverity CID :210686] Unchecked return value in lib/os/mempool.c * :github:`25983` - [Coverity CID :210682] Unchecked return value in lib/os/mempool.c * :github:`25982` - [Coverity CID :210020] Explicit null dereferenced in drivers/usb/device/usb_dc_mcux_ehci.c * :github:`25981` - Support storing mcuboot images on serial flash accessed through Nordic QSPI * :github:`25979` - Need root LICENSE files in hal_stm32 module * :github:`25965` - hci_uart not responding at higher baudrates on NRF52810 * :github:`25964` - Bluetooth: <err> bt_att: ATT Timeout * :github:`25958` - Concept Overview for improving support for serial flash devices via SPI and QSPI * :github:`25956` - Including header files from modules into app * :github:`25952` - STM32 LPTIM driver doesn't restart counter after sleeping K_TICKS_FOREVER * :github:`25945` - devicetree: support generating symbols for -gpios properties w/o compatible * :github:`25942` - Bluetooth: Scanning + Non-connectable advertising broken on nRF5340 * :github:`25926` - k_cycle_get_32() returns 0 in native_posix * :github:`25920` - Compilation error when CONFIG_BOOTLOADER_MCUBOOT=y specified * :github:`25919` - dhcpv4 or rx ethernet packets not working on nucleo_f429zi * :github:`25892` - arc emsdp board work wrong with emsdp_em7d_esp config * :github:`25869` - 2.3: Missing release notes * :github:`25865` - Device Tree Memory Layout * :github:`25859` - mesh example not working with switched off dcdc? * :github:`25853` - modem_ublox_sara_r4: Cannot connect to UDP remote * :github:`25833` - [lpcxpresso55s69_cpu1] no applications and build guide, hello world can not build * :github:`25827` - Devicetree: add accessors with defaults * :github:`25794` - [Coverity CID :210554] Uninitialized scalar variable in tests/net/iface/src/main.c * :github:`25792` - [Coverity CID :210552] Resource leak in tests/net/pm/src/main.c * :github:`25790` - [Coverity CID :210594] Dereference after null check in subsys/testsuite/ztest/src/ztest_mock.c * :github:`25786` - [Coverity CID :210558] Dereference before null check in drivers/sensor/sensor_shell.c * :github:`25784` - [Coverity CID :210546] Dereference after null check in tests/net/promiscuous/src/main.c * :github:`25783` - [Coverity CID :210051] Dereference after null check in subsys/net/ip/tcp2.c * :github:`25782` - [Coverity CID :210035] Dereference before null check in drivers/sensor/bq274xx/bq274xx.c * :github:`25781` - [Coverity CID :210031] Dereference before null check in drivers/modem/gsm_ppp.c * :github:`25778` - [Coverity CID :210604] Out-of-bounds access in tests/kernel/mem_protect/protection/src/main.c * :github:`25777` - [Coverity CID :210589] Out-of-bounds access in tests/kernel/mem_protect/protection/src/main.c * :github:`25776` - [Coverity CID :210573] Out-of-bounds access in tests/kernel/mem_protect/userspace/src/main.c * :github:`25750` - [Coverity CID :210066] Unintentional integer overflow in include/sys/time_units.h * :github:`25749` - [Coverity CID :210033] Unintentional integer overflow in drivers/sensor/mpr/mpr.c * :github:`25748` - [Coverity CID :210606] Pointless string comparison in tests/lib/devicetree/src/main.c * :github:`25747` - [Coverity CID :210596] Assign instead of compare in subsys/logging/log_output_syst.c * :github:`25746` - [Coverity CID :210584] Assign instead of compare in subsys/logging/log_output_syst.c * :github:`25745` - [Coverity CID :210052] Side effect in assertion in tests/kernel/fpu_sharing/generic/src/pi.c * :github:`25744` - [Coverity CID :210045] Side effect in assertion in tests/kernel/fpu_sharing/generic/src/pi.c * :github:`25743` - [Coverity CID :209944] Pointless string comparison in tests/lib/devicetree/src/main.c * :github:`25742` - [Coverity CID :209943] Pointless string comparison in tests/lib/devicetree/src/main.c * :github:`25741` - [Coverity CID :210618] Unchecked return value in drivers/wifi/esp/esp.c * :github:`25740` - [Coverity CID :210617] Argument cannot be negative in tests/net/pm/src/main.c * :github:`25739` - [Coverity CID :210610] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`25738` - [Coverity CID :210602] Unchecked return value in tests/drivers/uart/uart_basic_api/src/test_uart_fifo.c * :github:`25735` - [Coverity CID :210582] Unchecked return value in tests/net/socket/getaddrinfo/src/main.c * :github:`25734` - [Coverity CID :210580] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`25733` - [Coverity CID :210575] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`25732` - [Coverity CID :210570] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`25729` - [Coverity CID :210056] Unchecked return value in subsys/net/ip/tcp2.c * :github:`25728` - [Coverity CID :210050] Unchecked return value in tests/subsys/settings/littlefs/src/settings_setup_littlefs.c * :github:`25726` - [Coverity CID :210598] Missing break in switch in subsys/net/l2/ieee802154/ieee802154_frame.c * :github:`25725` - [Coverity CID :210578] Structurally dead code in kernel/mem_domain.c * :github:`25724` - [Coverity CID :210566] Missing break in switch in subsys/net/l2/ieee802154/ieee802154_frame.c * :github:`25723` - [Coverity CID :210559] Unsigned compared against 0 in subsys/net/ip/tcp2.c * :github:`25722` - [Coverity CID :210058] Logically dead code in samples/net/sockets/big_http_download/src/big_http_download.c * :github:`25721` - [Coverity CID :209945] Logically dead code in tests/net/tcp2/src/main.c * :github:`25720` - [Coverity CID :210073] Arguments in wrong order in drivers/modem/wncm14a2a.c * :github:`25713` - Miss shift i2c slave address in i2c_sifive * :github:`25710` - FS: Buffer Overflow when enabling Long File Names in FAT_FS and calling fs_stat * :github:`25704` - lib: updatehub: Corrupted updated when receiving CoAP duplicate packages * :github:`25693` - ESP WiFi MPU Fault causes zephyr fatal error * :github:`25682` - [v2.2] Shell freezes with cout printf, prink on float * :github:`25678` - enhance k_mutex to be ISR safe * :github:`25672` - Bluetooth: Mesh: scan_start fails with synchronous bt_enable * :github:`25664` - nRF Boards: unify static partition size for Bootloader * :github:`25658` - Issue to run sample on nucleo_g474re * :github:`25652` - smp_svr fails for nrf5340 * :github:`25645` - USB RNDIS driver can't work with Windows 10 (10.0.18363) * :github:`25601` - UART input does not work on mps2_an{385,521} * :github:`25599` - scanf() not functional with newlib out of the box * :github:`25566` - LSPI of NXP i.MX RT Other interrupts treated as transfer completion * :github:`25554` - lib: posix: nanosleep * :github:`25501` - shields: mikroe_eth_click config should be made conditional * :github:`25499` - Out of tree board: No sources given to target * :github:`25474` - ipv6 client-server between ble's failed * :github:`25458` - Multiple issues with timing benchmark * :github:`25453` - tests/posix/common fails on nucleo_wb55rg * :github:`25444` - No IPv6 routes from BLE IPSP node (NRF52840DK) * :github:`25398` - UpSquared Grub build docs don't work on Ubuntu 20.04 * :github:`25358` - net: config: application starts with 3s delay when CONFIG_NET_CONFIG_SETTINGS=y * :github:`25328` - mesh_demo is failing * :github:`25327` - Move to C99 integer types and deprecate zephyr specific types * :github:`25317` - RFC: Unstable API Change: uart_async: Call UART_RX_RDY event after rx_disable() * :github:`25312` - samples:mimxrt1010_evk:samples/net/openthread/ncp: build error * :github:`25311` - samples:frdmkw64f:bluetooth/peripheral_hr\| peripheral_ht: could not get ADC device * :github:`25308` - I2C simulation in native_posix * :github:`25299` - SYSTICK: Inconsistency between dts status and Kconfig * :github:`25295` - sanitycheck: race when running sanitycheck on native_posix producing false negatives. * :github:`25294` - Nordic mcuboot + smp_svr + QSPI smp_shell incompatibility * :github:`25293` - Add USB Device Support to STM32411E-DISCO * :github:`25283` - sam0: watchdog: Times out twice as fast as expected * :github:`25268` - sanitycheck doesn't report native_posix failures properly * :github:`25258` - drivers: i2c_nios2: device config_info content mutated * :github:`25257` - drivers: audio: dma_nios2_msgdma: device config_info content mutated * :github:`25256` - drivers: audio: tlv320dac310x: device config_info content mutated * :github:`25255` - drivers: i2c: gecko: device config_info content mutated * :github:`25231` - net.offload test fails on atsame54_xpro * :github:`25229` - net.neighbour test fails on atsame54_xpro * :github:`25228` - net.util test fails on atsame54_xpro * :github:`25227` - net.icmpv6 test fails on atsame54_xpro * :github:`25226` - net.vlan test fails on atsame54_xpro * :github:`25215` - enable modules to append to $DTS_ROOT * :github:`25189` - Wrong flash size set in the XIP boot header for NXP imxrt SoCs * :github:`25171` - Can only run the flash_simulator test once on native_posix * :github:`25165` - LE Coded Phy code rate switch [s2/s8] * :github:`25156` - Unable to use --use-elf option in 'west flash' to correctly flash the .elf file * :github:`25148` - tests: gpio: Add check to validate initial values of gpio output * :github:`25140` - Unable to obtain dhcp lease * :github:`25104` - whitelist in {sample,testcase}.yaml precludes a test from being run with sanitycheck * :github:`25101` - driver: gpio: mchp: GPIO initialization value doesn't get reflected when using new flags * :github:`25098` - MCUX I2C bus errors leave state machine in busy state * :github:`25076` - Remove potential I2C deadlock on NRFX implementation * :github:`25063` - USB Console + USB CDC_ACM co-existing * :github:`25051` - tests/drivers/gpio/gpio_api_1pin failed on reel_board. * :github:`25022` - hsdk:There is no cases information in serial log for ARC(R) HS Development Kit after one case was been flashed into the board. * :github:`25021` - Problems getting open62541 to run on Zephyr * :github:`24960` - The example "blinky" didn't work on MIMXRT1050-EVK * :github:`24939` - LSPI of NXP i.MX RT timing delay issue * :github:`24918` - Segger RTT using j-link doesn't work on NXP i.MX RT * :github:`24916` - echo_client sample return: Cannot connect to TCP remote (IPv6): 60 (frdm_k64f <--> native_posix) * :github:`24910` - kernel: stack sentinel crashes * :github:`24859` - os: Add memory partition overlap assert check is not made for x86 boards * :github:`24844` - Setting esp-idf path to match Espressif's documentation * :github:`24770` - Low throughput with the zperf sample using stm32f746g_disco * :github:`24767` - Ethernet support for STM32H747 * :github:`24750` - need API to get list of succeed initialization device or add initialization status flag in struct device * :github:`24747` - tests/lib/heap fails on ARC nsim_sem nsim_em * :github:`24745` - Mitigate changes in peripheral enable state after Kconfig replaced by DT status * :github:`24730` - C standard library <time.h> functions and structures not available when using POSIX API * :github:`24703` - hal_nuvoton: Add new module for Nuvoton numicro M480 HAL layer * :github:`24700` - mimxrt1050_evk:tests/drivers/kscan/kscan_api failed. * :github:`24632` - Devices vs. drivers * :github:`24627` - tests/subsys/usb/device fails on SAM E54 * :github:`24625` - lib: drivers: clock: rtc: rtc api to maintain calendar time through reboot * :github:`24619` - CONFIG_USERSPACE=y CONFIG_XIP=n causes .bin space to be wasted * :github:`24546` - Implement MDB runner for ARC * :github:`24499` - devicetree: node name for SPI buses should be 'spi' warning * :github:`24429` - LPC55S69 flash faults when reading unwritten areas * :github:`24372` - Json: array of objects is not properly handled * :github:`24318` - Postpone driver initialization * :github:`24301` - Support for multi core STM32 H75/H77 boards * :github:`24300` - tests/net/trickle failed on frdm_k64f and sam_e70_xplained with v1.14 branch. * :github:`24293` - subsys: shell: bug: shell_fprintf() before shell_enable() causes shell deadlock * :github:`24233` - adxl362_trigger.c adxl362_init_interrupt function :const struct adxl362_config \cfg not found gpio_cs_port :github:`24224` - Possible uninitialized variable in zephyr\subsys\logging\log_msg.c * :github:`24221` - Do not run cron workflow on forks * :github:`24217` - Shell: provide mechanism to call any command while in select command * :github:`24191` - obj_tracing: Local IPC variables are not removed from obj tracing list after function return * :github:`24147` - nrf5340 pdk: BOARDS_ENABLE_CPUNET does not allow proper NET MCU configuration * :github:`24134` - [NXP i.MX RT Flash]: evkmimxrt1020 does not boot with a new flash chip * :github:`24133` - Question: Context save/restore after deep sleep using device driver * :github:`24111` - drivers: flash: littlefs: add sync to flash API & update LittleFS to use it * :github:`24092` - Unable to change recv() buffer size in frdm_k64f board. * :github:`24076` - [v1.14] UARTE high current consumption on NRF * :github:`24030` - [Coverity CID :209379] Unchecked return value in tests/kernel/mem_protect/sys_sem/src/main.c * :github:`24029` - [Coverity CID :209380] Unchecked return value in tests/kernel/poll/src/test_poll.c * :github:`24028` - [Coverity CID :209381] Unrecoverable parse warning in include/bluetooth/bluetooth.h * :github:`23961` - CCC does not get cleared when CONFIG_BT_KEYS_OVERWRITE_OLDEST is enabled * :github:`23949` - Question: Is there any example for BR/EDR profile/protocols (like A2DP, AVDTP, RFCOMM)? * :github:`23887` - drivers: modem: question: Should modem stack include headers to put into zephyr/include? * :github:`23886` - drivers: modem_socket: Question: socket ID appears to be the same for all sockets * :github:`23873` - GNA subsystem does not provide any system calls * :github:`23825` - edtlib.py fails to find bindings when DTS_ROOT is a relative path * :github:`23808` - ARM bus fault with code coverage * :github:`23802` - up_squared(acrn):tests/kernel/timer/timer_api/ failed. * :github:`23801` - up_squared(acrn):tests/kernel/sched/schedule_api failed. * :github:`23800` - tests/drivers/counter/counter_cmos failed on up_squared platform * :github:`23775` - k_poll() documentation is wrong or unclear * :github:`23713` - CMake integration with libmetal errors-out with the bleeding edge CMake release * :github:`23702` - STACK_POINTER_RANDOM is not working on ARM for the main thread * :github:`23672` - dts: sam0: question: Is it possible to clean up samd.dtsi devicetree warning? * :github:`23629` - support inverted PWM on STM32 * :github:`23599` - zephyr/samples/application_development/code_relocation execution stop at z_arm_bus_fault * :github:`23578` - [Coverity CID :208922] Uninitialized pointer read in tests/posix/common/src/pthread.c * :github:`23574` - [Coverity CID :208926] Side effect in assertion in tests/kernel/interrupt/src/nested_irq.c * :github:`23546` - Kconfig: default value not assigned when inheriting Kconfig values in range * :github:`23514` - Allocate executable memory for ESP32 * :github:`23474` - tests/subsys/usb/device failed on reel_board. * :github:`23443` - esp32 needs i2c_transfer call to turn on the display * :github:`23423` - Mitigation in case system [created] threads hang/non-responsive * :github:`23419` - posix: clock: No thread safety clock_[get/set]time * :github:`23366` - ARM: Core Stack Improvements/Bug fixes for 2.3 release * :github:`23364` - Bluetooth: bt_recv deadlock on supervision timeout with pending GATT Write Commands * :github:`23349` - Question: How to add external soc, board, DTS, drivers and libs? * :github:`23322` - flash, spi-nor: Configuration of jedec spi nor flash device driver * :github:`23319` - hci interface stopped working after few hours/days * :github:`23248` - Add secure version of strcpy * :github:`23246` - net: tx_bufs are not freed when NET_TCP_BACKLOG_SIZE is too high * :github:`23243` - test/kernel/gen_isr_table fails in v2.2.0-rc3 on lpcxpresso54114_m4 board * :github:`23215` - fujitsu FRAM read error on stm32_olimexino * :github:`23211` - need a proper arch_system_halt() for x86_64 * :github:`23178` - usb: endpoint buffer leak upon SET_CONFIGURATION, SET_INTERFACE * :github:`23177` - Bluetooth: Mesh: Access structure member with a possible NULL pointer * :github:`23149` - [v1.14] sam_e70_xplained:tests/drivers/watchdog/wdt_basic_api failed with v1.14 branch. * :github:`23139` - USB Mass storage - Unexpected USB restart from host * :github:`23138` - Codegen for an C structure that stores pinmux definitions * :github:`23134` - BT: Host: Notification dropped instead of truncated if bigger than ATT_MTU-3 * :github:`23111` - drivers:usb:device:sam0: Descriptor tables are filled with zeros in attach() * :github:`23052` - nrf52840_pca10056: Spurious RTS pulse and incorrect line level with hardware flow control disabled * :github:`23040` - samples: net/wifi: net ping shell causes USAGE FAULT once wifi is connected * :github:`23039` - SystemView does not work with C++ enabled * :github:`22996` - scripts/footprint/size_report doesn't work on qemu_x86_64 * :github:`22980` - bluetooth: logging: Build assertion prevents immediate logging when using legacy LL * :github:`22975` - tests/kernel/gen_isr_table: filtered in CI only for Cortex-M Mainline * :github:`22974` - Add cancel function to onoff service * :github:`22955` - tests/kernel/interrupt fails intermittently on qemu_cortex_m0 * :github:`22906` - Slow read/write speed of microSD card via SPI and FatFS * :github:`22892` - Kconfig warning when serial disable on PCA10059 * :github:`22873` - Bluetooth: RSSI Read command can be configured out even when mandatory * :github:`22872` - Hello world application for mps2_an521 board when build as a secure/non-secure with Trusted Firmware is crashing on qemu * :github:`22865` - drivers: enc28j60: sample: dumb_http_server: TX failed errors * :github:`22758` - RFC: Require system clock stability on startup * :github:`22751` - STM32F407 I2C driver hangs * :github:`22722` - posix: redefinition of symbols while porting zeromq to zephyr * :github:`22704` - Implement watchdog driver for lpcxpresso55s69 * :github:`22637` - 2.3 Release Checklist * :github:`22594` - NXP S32K144 MCU support * :github:`22562` - West: Allow configuring ``west sign`` similar to west runners * :github:`22466` - Add hx711 sensor * :github:`22391` - Resuming from suspend should check device usage count in device idle PM * :github:`22344` - convert espi sample to devicetree * :github:`22340` - Security problem with settings and littlefs * :github:`22322` - Clang linking error * :github:`22301` - k_msgq_put() semantics definition * :github:`22151` - hal_nordic: nrfx: doxygen: Reference to missing nrfx/templates * :github:`22145` - RISCV arch_irq_connect_dynamic() broken with PLIC interrupts * :github:`22144` - arch: arm64: interrupt test is failing * :github:`22140` - Exiting deep sleep without button help; nrf52832 * :github:`22091` - Blink-Led example doesn't build on Nucleo_L476RG, STM32F4_DISCOVERY, Nucleo_F302R8, Nucleo_F401RE * :github:`22077` - W25Q32fv supported in spi_flash examples ? * :github:`22063` - fs/NVS: NVS is not compatible with flash memories which have 0x00 as erased * :github:`22060` - Build fails with gcc-arm-none-eabi-9-2019-q4-major * :github:`21994` - Bluetooth: controller: split: Fix procedure complete event generation * :github:`21848` - sanitycheck duplicate tests Testing/Ztest * :github:`21843` - CONFIG_INIT_STACKS issue on x86_64 * :github:`21819` - Shell fails when dynamic command has empty subcommand * :github:`21801` - Logger sample's performance estimates are incorrect * :github:`21798` - Bluetooth: host: Allow GATT client to restore subscription info without resubscribing * :github:`21772` - Adding I2C devices to device tree with the same address on different busses generates excessive warnings. * :github:`21762` - [v1.14] stm32: k_sleep() actual sleep times are different than its input * :github:`21754` - Arduino Due shell does not accept input (UART0) * :github:`21725` - device power management by device * :github:`21711` - sam0 i2c slave * :github:`21708` - Multiple partitions for LittleFS * :github:`21707` - Timing violation for all sensor drivers * :github:`21670` - Keep device structures in ROM * :github:`21635` - sht3xd error -5 on olimexino_stm32 * :github:`21616` - LWM2M: unable to get plain text from incoming message * :github:`21611` - IS25LP032D-JNLE Flash support * :github:`21554` - ldscript:datas section is not properly aligned in ROM * :github:`21549` - i2c_sam0 interrupt latency is excessive * :github:`21511` - re-visit k_thread_abort wrt SMP * :github:`21498` - Zephyr Peripheral not responding to Terminate command from central * :github:`21455` - driver: subsys: sdhc: USAGE FAULT trace and no cs control * :github:`21452` - drivers: ethernet: unify the initiaization * :github:`21445` - drivers/i2c: add I2C slave support for nrfx * :github:`21436` - refactor and augment CPU cache management APIs * :github:`21399` - NUCLEO-H745ZI-Q Support * :github:`21378` - The program cannot be downloaded to nrf52840, only to pca10056 * :github:`21240` - Error west flash * :github:`21234` - drivers: usb_dc_sam0: usb detach and reattach does not work * :github:`21233` - i2c_sam0 driver does not execute a STOP condition * :github:`21232` - i2c_sam0 LOWTOUT is not functional * :github:`21229` - cc1plus: warning: '-Werror=' argument '-Werror=implicit-int' is not valid for C++ * :github:`21187` - Can not ping or run http server via ethernet when gPTP is enabled * :github:`21114` - Invalid interaction between the RTC and the I2C drivers for the sam0 * :github:`21111` - Reschedule points are currently undocumented * :github:`21092` - i2c-sam0 sleeps waiting for interrupt * :github:`21053` - net: 6lo: Use context 0 as default when CID-bit is not set * :github:`21016` - Unexpected ethernet network traffic after power up * :github:`20987` - Console showing frequent usb warnings: <wrn> usb_device: Failed to write endpoint buffer 0x82 * :github:`20978` - Add bond_deleted callback * :github:`20870` - [Coverity CID :205816] Control flow issues in subsys/settings/src/settings_file.c * :github:`20844` - [Coverity CID :205781] Integer handling issues in lib/os/printk.c * :github:`20806` - nrf: clock control: clock control on/off routines are refcounted * :github:`20780` - Feature Request: Half-duplex UART shell backend * :github:`20750` - shell: shell_execute_cmd introduce new line * :github:`20734` - Are cooperative threads cooperative in SMP? * :github:`20729` - Coverage reporting hangs for C++ tests on X86 qemu * :github:`20712` - nRF clock_control_on() is nonblocking * :github:`20693` - tests: watchdog: test_wdt_callback_1() implementation vs API specification * :github:`20687` - Clarification: How to enable on-board nor-flash following the board porting guide? * :github:`20671` - ARC: remove scheduler code from arch layer * :github:`20663` - kernel objects are being included always, regardless of usage * :github:`20595` - tests/arch/arm/arm_thread_swap failed on frdm_k64f board. * :github:`20589` - RV32M1 SPI loopback needs DEBUG_OPTIMIZATIONS * :github:`20541` - [Coverity CID :205639]Security best practices violations in /tests/subsys/settings/functional/src/settings_basic_test.c * :github:`20520` - [Coverity CID :205652]Memory - corruptions in /tests/crypto/tinycrypt/src/ecc_dsa.c * :github:`20519` - [Coverity CID :205616]Memory - corruptions in /tests/crypto/tinycrypt/src/ecc_dsa.c * :github:`20517` - [Coverity CID :205640]Control flow issues in /subsys/testsuite/ztest/src/ztest.c * :github:`20516` - [Coverity CID :205609]Control flow issues in /subsys/testsuite/ztest/src/ztest.c * :github:`20500` - [Coverity CID :205629]Control flow issues in /drivers/timer/cc13x2_cc26x2_rtc_timer.c * :github:`20418` - CONFIG_HEAP_MEM_POOL_SIZE should not be limited * :github:`20297` - Bluetooth: can't close bt_driver log output * :github:`20012` - Support peripheral deallocation at runtime * :github:`19824` - Build sample net app for ACRN (nuc i7dnhe) * :github:`19739` - stty: standard input: Inappropriate ioctl for device * :github:`19701` - mem_pool_threadsafe sporadic failures impacting CI * :github:`19684` - doc: [message_queues.rst] unclear about data_item structure type * :github:`19670` - samples/drivers/spi_fujitsu_fram crashs due to uninitialized variables * :github:`19661` - missing files in xtensa/xt-sim doc * :github:`19550` - drivers/pcie: ``pcie_get_mbar()`` should return a ``void `` not ``u32_t`` :github:`19483` - Add support for Open Supervised Device Protocol (OSDP) * :github:`19414` - UART and prf not working * :github:`19376` - Build on a ARM host * :github:`19348` - net: TCP/IPv6 set of fragmented packets causes Zephyr QEMU to double free * :github:`19063` - can we increase qemu_riscv32/64 RAM sizes * :github:`18960` - [Coverity CID :203908]Error handling issues in /lib/libc/newlib/libc-hooks.c * :github:`18843` - Usage Fault with CONFIG_NO_OPTIMIZATIONS even on samples/hello_world * :github:`18815` - UART API documentation * :github:`18629` - Some tests fail to reach test_main() on cc1352r1_launchxl * :github:`18570` - Dynamic interrupt does not work with multi-level interrupts * :github:`18345` - Is there a way to get the bytes that shell receives? * :github:`18157` - adding an offset to the zephyr code via dts overlay breaks linking + the image size changes * :github:`18045` - BT Host: Advertising Extensions - Periodic Advertisement * :github:`17814` - Zephyr support for NXP i.MX8M SoC * :github:`17688` - Unable to Read data from SCC811 * :github:`17624` - SRAM size configurations aren't always consistent * :github:`17372` - sanitycheck does not parse extra_args with spaces correctly * :github:`16968` - silabs/gecko/emlib/src/em_gpio.c:111:35: warning: ?: using integer constants in boolean context [-Werror=int-in-bool-context] * :github:`16886` - Bluetooth Mesh: Receive segmented message multiple times * :github:`16809` - TCP2 integration * :github:`16790` - adxl362 sample isn't build by sanitycheck * :github:`16661` - Symmetric multiprocessing (SMP) for ARC HS cores * :github:`16638` - Filesystem API is missing fs_open() flags * :github:`16439` - flash: unify read alignment requirements * :github:`16387` - STM32wb55 bluetooth samples fail * :github:`16363` - Error building x_nucleo_iks01a1 sample on nucleo_wb55rg after activating I2C Bus * :github:`16210` - ARM: initialization sequence might be not using all of interrupt stack * :github:`16031` - Toolchain abstraction * :github:`15968` - rom_report very imprecise * :github:`15845` - _RESET_VECTOR different from 0x00 gives invalid .elf size on nios2 * :github:`15286` - HF clock's m16src_grd and BLE stack * :github:`15246` - doc: confusion about dtc version * :github:`14591` - Infineon Tricore architecture support * :github:`14587` - IPv6 support in cc3220sf_launchxl * :github:`14520` - invalid locking in shell * :github:`14302` - USB MSC fails USB3CV tests * :github:`14269` - Enforce usage of K_THREAD_STACK_SIZEOF macro in k_thread_create() * :github:`14173` - Configure QEMU to run independent of the host clock * :github:`13819` - mimxrt10xx: Wrong I2C transfer status * :github:`13813` - Test suite mslab_threadsafe fails randomly * :github:`13737` - Where can I find tutorial to make my own device driver for a device under I2C bus? * :github:`13651` - ARC does not set thread->stack_info correctly * :github:`13637` - Introduce supervisor-only stack declaration macros * :github:`13276` - Do we need to update fatfs * :github:`12987` - Fix workaround of using 'mmio-sram' compat for system memory (DRAM) in DTS * :github:`12935` - Zephyr usurps "STRINGIFY" define * :github:`12705` - Implement select() call for socket offloading and SimpleLink driver * :github:`12025` - OS Pwr Manager doesn't put nrf52 into LPS_1 * :github:`11976` - APIs that support a callback should provide both the device pointer and a generic pointer * :github:`11974` - rework eeprom driver to clearly indicate it is a test stub * :github:`11908` - Power Manager does not handle K_FOREVER properly * :github:`11890` - Reimplement getaddrinfo() to call SlNetUtil_getaddrinfo() in new SimpleLink SDK v 2.30+ * :github:`10628` - tests/kernel/common and tests/posix/fs crash on ESP32 * :github:`10436` - Mess with ssize_t, off_t definitions * :github:`9893` - MISRA C Review switch statement usage * :github:`9808` - remove single thread support * :github:`9596` - tests/subsys/logging/log_core fails on ESP32 with no console output * :github:`8469` - Zephyr types incompatibilities (e.g. u32_t vs uint32_t) * :github:`8364` - mcumgr: unable to properly read big files * :github:`8360` - CI should enforce that extract_dts_includes.py does not trigger warnings * :github:`8262` - [Bluetooth] MPU FAULT on sdu_recv * :github:`8257` - Unify TICKLESS_IDLE & TICKLESS_KERNEL * :github:`7951` - doc: naming convention for requirements ids * :github:`7385` - i2c_esp32 can write past checked buffer length * :github:`6783` - Clean up wiki.zephyrproject.org content * :github:`6184` - drivers: ISR-friendly driver APIs * :github:`5934` - esp32: Output frequency is different from that configured on I2C and PWM drivers * :github:`5443` - Deprecate # CONFIG`_ is not set * :github:`4404` - Align k_poll with waiters * :github:`3423` - Optimize MCUX shim drivers to reduce memory footprint * :github:`3180` - implement direct interrupts on ARC * :github:`3165` - xtensa: switch to clang-based frontend * :github:`3066` - Improve Multi Core support * :github:`2955` - Use interrupt-driven TX in hci_uart sample ```	/content/code_sandbox/doc/releases/release-notes-2.4.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	30,795
```restructuredtext :orphan: .. _migration_4.0: Migration guide to Zephyr v4.0.0 (Working Draft) ################################################ This document describes the changes required when migrating your application from Zephyr v3.7.0 to Zephyr v4.0.0. Any other changes (not directly related to migrating applications) can be found in the :ref:`release notes<zephyr_4.0>`. .. contents:: :local: :depth: 2 Build System ********** Kernel ** Boards **** * :ref:`native_posix<native_posix>` has been deprecated in favour of :ref:`native_sim<native_sim>` (:github:`76898`). Modules ******* Mbed TLS ======== * The Kconfig options ``CONFIG_MBEDTLS_TLS_VERSION_1_0`` and ``CONFIG_MBEDTLS_TLS_VERSION_1_1`` have been removed because Mbed TLS doesn't support TLS 1.0 and 1.1 anymore since v3.0. (:github:`76833`) Trusted Firmware-M ================== LVGL ==== Device Drivers and Devicetree ***************************** * The ``compatible`` of the LiteX ethernet controller has been renamed from ``litex,eth0`` to :dtcompatible:`litex,liteeth`. (:github:`75433`) * The ``compatible`` of the LiteX uart controller has been renamed from ``litex,uart0`` to :dtcompatible:`litex,uart`. (:github:`74522`) * The devicetree bindings for the Microchip ``mcp23xxx`` series have been split up. Users of ``microchip,mcp230xx`` and ``microchip,mcp23sxx`` should change their devicetree ``compatible`` values to the specific chip variant, e.g. :dtcompatible:`microchip,mcp23017`. The ``ngpios`` devicetree property has been removed, since it is implied by the model name. Chip variants with open-drain outputs (``mcp23x09``, ``mcp23x18``) now correctly reflect this in their driver API, users of these devices should ensure they pass appropriate values to :c:func:`gpio_pin_set`. (:github:`65797`) Controller Area Network (CAN) ============================= Display ======= Enhanced Serial Peripheral Interface (eSPI) =========================================== GNSS ==== Input ===== * :c:macro:`INPUT_CALLBACK_DEFINE` has now an extra ``user_data`` void pointer argument that can be used to reference any user data structure. To restore the current behavior it can be set to ``NULL``. A ``void user_data`` argument has to be added to the callback function arguments. The :dtcompatible:`analog-axis` ``invert`` property has been renamed to ``invert-input`` (there's now an ``invert-output`` available as well). Interrupt Controller ==================== LED Strip ========= Sensors ======= Serial ====== Regulator ========= * Internal regulators present in nRF52/53 series can now be configured using devicetree. The Kconfig options :kconfig:option:`CONFIG_SOC_DCDC_NRF52X`, :kconfig:option:`CONFIG_SOC_DCDC_NRF52X_HV`, :kconfig:option:`CONFIG_SOC_DCDC_NRF53X_APP`, :kconfig:option:`CONFIG_SOC_DCDC_NRF53X_NET` and :kconfig:option:`CONFIG_SOC_DCDC_NRF53X_HV` selected by board-level Kconfig options have been deprecated. Example for nRF52 series: .. code-block:: devicetree /* configure REG/REG1 in DC/DC mode / &reg/reg1 { regulator-initial-mode = <NRF5X_REG_MODE_DCDC>; }; / enable REG0 (HV mode) / &reg0 { status = "okay"; }; Example for nRF53 series: .. code-block:: devicetree / configure VREGMAIN in DC/DC mode / &vregmain { regulator-initial-mode = <NRF5X_REG_MODE_DCDC>; }; / configure VREGRADIO in DC/DC mode / &vregradio { regulator-initial-mode = <NRF5X_REG_MODE_DCDC>; }; / enable VREGH (HV mode) / &vregh { status = "okay"; }; Bluetooth ******** Bluetooth HCI ============= Bluetooth Mesh ============== Bluetooth Audio =============== * The Volume Renderer callback functions :code:`bt_vcp_vol_rend_cb.state` and :code:`bt_vcp_vol_rend_cb.flags` for VCP now contain an additional parameter for the connection. This needs to be added to all instances of VCP Volume Renderer callback functions defined. (:github:`76992`) Bluetooth Classic ================= Bluetooth Host ============== Bluetooth Crypto ================ Networking ********** * The CoAP public API functions :c:func:`coap_get_block1_option` and :c:func:`coap_get_block2_option` have changed. The ``block_number`` pointer type has changed from ``uint8_t `` to ``uint32_t ``. Additionally, :c:func:`coap_get_block2_option` now accepts an additional ``bool has_more`` parameter, to store the value of the more flag. (:github:`76052`) Other Subsystems ************* Flash map ========= hawkBit ======= MCUmgr ====== Modem ===== Architectures *********** ```	/content/code_sandbox/doc/releases/migration-guide-4.0.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,236
```restructuredtext :orphan: .. _migration_3.7: Migration guide to Zephyr v3.7.0 ################################ This document describes the changes required when migrating your application from Zephyr v3.6.0 to Zephyr v3.7.0. Any other changes (not directly related to migrating applications) can be found in the :ref:`release notes<zephyr_3.7>`. .. contents:: :local: :depth: 2 Build System ************ * Completely overhauled the way SoCs and boards are defined. This requires all out-of-tree SoCs and boards to be ported to the new model. See the :ref:`hw_model_v2` for more detailed information. (:github:`69607`) * The following build-time generated headers: .. list-table:: :header-rows: 1 * - Affected header files * - ``app_version.h`` * - ``autoconf.h`` * - ``cmake_intdef.h`` * - ``core-isa-dM.h`` * - ``devicetree_generated.h`` * - ``driver-validation.h`` * - ``kobj-types-enum.h`` * - ``linker-kobject-prebuilt-data.h`` * - ``linker-kobject-prebuilt-priv-stacks.h`` * - ``linker-kobject-prebuilt-rodata.h`` * - ``mcuboot_version.h`` * - ``offsets.h`` * - ``otype-to-size.h`` * - ``otype-to-str.h`` * - ``strerror_table.h`` * - ``strsignal_table.h`` * - ``syscall_list.h`` * - ``version.h`` * - ``zsr.h`` as well as syscall headers & sources are now namespaced into the ``zephyr/`` folder. The change is largely automated, and the script can be found in :github:`63973`. For the time being, the compatibility Kconfig (:kconfig:option:`CONFIG_LEGACY_GENERATED_INCLUDE_PATH`) is enabled by default so that downstream applications will continue to compile, a warning message will be generated during CMake configuration time. This Kconfig will be deprecated and eventually removed in the future, developers are advised to update the include paths of these affected headers as soon as possible. Kernel ****** * All architectures are now required to define the new ``struct arch_esf``, which describes the members of a stack frame. This new struct replaces the named struct ``z_arch_esf_t``. (:github:`73593`) * The named struct ``z_arch_esf_t`` is now deprecated. Use ``struct arch_esf`` instead. (:github:`73593`) * The header file :zephyr_file:`include/zephyr/arch/arch_interface.h` has been moved from ``include/zephyr/sys/`` into ``include/zephyr/arch/``. Out-of-tree source files will need to update the include path. (:github:`64987`) Boards ****** * Reordered D1 and D0 in the ``pro_micro`` connector gpio-map for SparkFun Pro Micro RP2040 to match original Pro Micro definition. Out-of-tree shields must be updated to reflect this change. (:github:`69994`) * ITE: Rename all SoC variant Kconfig options, e.g., ``CONFIG_SOC_IT82202_AX`` is renamed to :kconfig:option:`CONFIG_SOC_IT82202AX`. All symbols are renamed as follows: ``SOC_IT81202BX``, ``SOC_IT81202CX``, ``SOC_IT81302BX``, ``SOC_IT81302CX``, ``SOC_IT82002AW``, ``SOC_IT82202AX``, ``SOC_IT82302AX``. And, rename the ``SOC_SERIES_ITE_IT8XXX2`` to ``SOC_SERIES_IT8XXX2``. (:github:`71680`) * For native_sim/posix: :kconfig:option:`CONFIG_EMUL` is no longer enabled by default when :kconfig:option:`CONFIG_I2C` is set. Users who need this setting enabled should set it in their project config file. (:github:`73067`) * LiteX: Renamed the ``compatible`` of the LiteX VexRiscV interrupt controller node from ``vexriscv-intc0`` to :dtcompatible:`litex,vexriscv-intc0`. (:github:`73211`) * ``lairdconnect`` boards are now ``ezurio`` boards. Laird Connectivity has rebranded to `Ezurio <path_to_url`_. Modules ******* Mbed TLS ======== * TLS 1.2, RSA, AES, DES, and all the hash algorithms except SHA-256 (SHA-224, SHA-384, SHA-512, MD5 and SHA-1) are not enabled by default anymore. Their respective Kconfig options now need to be explicitly enabled to be able to use them. (:github:`72078`) * The Kconfig options previously named ``CONFIG_MBEDTLS_MAC__ENABLED`` have been renamed. The ``_MAC`` and ``_ENABLED`` parts have been removed from their names. (:github:`73267`) The :kconfig:option:`CONFIG_MBEDTLS_HASH_ALL_ENABLED` Kconfig option has been fixed to actually enable all the available hash algorithms. Previously, it used to only enable the SHA-2 ones. (:github:`73267`) * The ``CONFIG_MBEDTLS_HASH_SHA_ENABLED`` Kconfig options have been removed. They were duplicates of other Kconfig options which are now named ``CONFIG_MBEDTLS_SHA``. (:github:`73267`) * The ``CONFIG_MBEDTLS_MAC_ALL_ENABLED`` Kconfig option has been removed. Its equivalent is the combination of :kconfig:option:`CONFIG_MBEDTLS_HASH_ALL_ENABLED` and :kconfig:option:`CONFIG_MBEDTLS_CMAC`. (:github:`73267`) * The Kconfig options ``CONFIG_MBEDTLS_MAC_MD4_ENABLED``, ``CONFIG_MBEDTLS_CIPHER_ARC4_ENABLED`` and ``CONFIG_MBEDTLS_CIPHER_BLOWFISH_ENABLED`` were removed because they are no more supported in Mbed TLS. (:github:`73222`) * When there is any PSA crypto provider available in the system (i.e. :kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_CLIENT` is set), desired PSA crypto features must be explicitly enabled using proper ``CONFIG_PSA_WANT_``. (:github:`72243`) TLS/X509/PK/MD modules will use PSA crypto APIs instead of legacy ones as soon as there is any PSA crypto provider available in the system (i.e. :kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_CLIENT` is set). (:github:`72243`) Trusted Firmware-M ================== * The default MCUboot signature type has been changed from RSA-3072 to EC-P256. This affects builds that have MCUboot enabled in TF-M (:kconfig:option:`CONFIG_TFM_BL2`). If you wish to keep using RSA-3072, you need to set :kconfig:option:`CONFIG_TFM_MCUBOOT_SIGNATURE_TYPE` to ``"RSA-3072"``. Otherwise, make sure to have your own signing keys of the signature type in use. LVGL ==== * :kconfig:option:`CONFIG_LV_Z_POINTER_KSCAN` was removed, you need to convert your kscan based driver to the input subsystem and use a :dtcompatible:`zephyr,lvgl-pointer-input` in your devicetree instead. (:github:`73800`) Device Drivers and Devicetree ***************************** * The :dtcompatible:`nxp,kinetis-pit` pit driver has changed its compatible to :dtcompatible:`nxp,pit` and has been updated to support multiple channels. To configure the individual channels, you must add a child node with the compatible :dtcompatible:`nxp,pit-channel` and configure as below. The :kconfig:option:`CONFIG_COUNTER_MCUX_PIT` has also been renamed to :kconfig:option:`CONFIG_COUNTER_NXP_PIT` with regards to the renaming of the binding for the pit. (:github:`66336`) example: .. code-block:: devicetree / { pit0: pit@40037000 { /* Other Pit DT Attributes / compatible = "nxp,pit"; status = "disabled"; num-channels = <1>; #address-cells = <1>; #size-cells = <0>; pit0_channel0: pit0_channel@0 { compatible = "nxp,pit-channel"; reg = <0>; status = "disabled"; }; }; The :dtcompatible:`nxp,kinetis-ethernet` has been deprecated in favor of :dtcompatible:`nxp,enet`. All in tree SOCs were converted to use this new schema. Thus, all boards using NXP's ENET peripheral will need to align to this binding in DT, which also comes with a different version driver. Alternatively, the Ethernet node can be deleted and redefined as the old binding to use the deprecated legacy driver. The primary advantage of the new binding is to be able to abstract an arbitrary phy through the mdio API. (:github:`70400`) Example of a basic board level ENET DT definition: .. code-block:: devicetree &enet_mac { status = "okay"; pinctrl-0 = <&pinmux_enet>; pinctrl-names = "default"; phy-handle = <&phy>; zephyr,random-mac-address; phy-connection-type = "rmii"; }; &enet_mdio { status = "okay"; pinctrl-0 = <&pinmux_enet_mdio>; pinctrl-names = "default"; phy: phy@3 { compatible = "ethernet-phy"; reg = <3>; status = "okay"; }; }; * The :dtcompatible:`nxp,kinetis-lptmr` compatible string has been changed to :dtcompatible:`nxp,lptmr`. The old string will be usable for a short time, but should be replaced for it will be removed in the future. * Some of the driver API structs have been rename to have the required ``_driver_api`` suffix. (:github:`72182`) The following types have been renamed: * ``emul_sensor_backend_api`` to :c:struct:`emul_sensor_driver_api` * ``emul_bbram_backend_api`` to :c:struct:`emul_bbram_driver_api` * ``usbc_ppc_drv`` to :c:struct:`usbc_ppc_driver_api` * The driver for :dtcompatible:`maxim,max31790` got split up into a MFD and an actual PWM driver. (:github:`68433`) Previously, an instance of this device could have been defined like this: .. code-block:: devicetree max31790_max31790: max31790@20 { compatible = "maxim,max31790"; status = "okay"; reg = <0x20>; pwm-controller; #pwm-cells = <2>; }; This can be converted to: .. code-block:: devicetree max31790_max31790: max31790@20 { compatible = "maxim,max31790"; status = "okay"; reg = <0x20>; max31790_max31790_pwm: max31790_max31790_pwm { compatible = "maxim,max31790-pwm"; status = "okay"; pwm-controller; #pwm-cells = <2>; }; }; * The driver for :dtcompatible:`invensense,icm42688` now correctly supports device tree configuration(:github:`74267`). Prior devicetrees may have tried to use the bindings to set sample rate and scale for the accel/gyro without any effect. The devicetree usage should now use the provided defines and include file along with new bindings which take these values. For example: .. code-block:: devicetree #include <zephyr/dt-bindings/sensor/icm42688.h> icm42688: icm42688@0 { accel-pwr-mode = <ICM42688_ACCEL_LN>; accel-fs = <ICM42688_ACCEL_FS_16G>; accel-odr = <ICM42688_ACCEL_ODR_2000>; gyro-pwr-mode= <ICM42688_GYRO_LN>; gyro-fs = <ICM42688_GYRO_FS_2000>; gyro-odr = <ICM42688_GYRO_ODR_2000>; }; * :dtcompatible:`st,lis2mdl` property ``spi-full-duplex`` changed to ``duplex = SPI_FULL_DUPLEX``. Full duplex is now the default. * The DT property ``nxp,reference-supply`` of :dtcompatible:`nxp,lpc-lpadc` driver has been removed, users should remove this property from their devicetree if it is present. Added new phandle-array type DT property ``nxp,references``, the user can use this property to specify the reference voltage and reference voltage value to be used by the lpadc. (:github:`75005`) * The DT properties ``mc,interface-type``, ``mc,reset-gpio``, and ``mc,interrupt-gpio`` of the :dtcompatible:`microchip,ksz8081` phy binding have changed to ``microchip,interface-type``, ``reset-gpios``, and ``int-gpios``, respectively (:github:`73725`) Charger ======= * Dropped ``constant-charge-current-max-microamp`` property in ``charger_max20335`` driver because it did not reflect real chip functionality. (:github:`69910`) * Added enum key to ``constant-charge-voltage-max-microvolt`` property in ``maxim,max20335-charger`` binding to indicate invalid devicetree values at build time. (:github:`69910`) Controller Area Network (CAN) ============================= * Removed the following deprecated CAN controller devicetree properties. Out-of-tree boards using these properties can switch to using the ``bitrate``, ``sample-point``, ``bitrate-data``, and ``sample-point-data`` devicetree properties (or rely on :kconfig:option:`CONFIG_CAN_DEFAULT_BITRATE` and :kconfig:option:`CONFIG_CAN_DEFAULT_BITRATE_DATA`) for specifying the initial CAN bitrate: * ``sjw`` * ``prop-seg`` * ``phase-seg1`` * ``phase-seg2`` * ``sjw-data`` * ``prop-seg-data`` * ``phase-seg1-data`` * ``phase-seg2-data`` The ``bus-speed`` and ``bus-speed-data`` CAN controller devicetree properties have been deprecated. (:github:`68714`) * Support for manual bus-off recovery was reworked (:github:`69460`): * Automatic bus recovery will always be enabled upon driver initialization regardless of Kconfig options. Since CAN controllers are initialized in "stopped" state, no unwanted bus-off recovery will be started at this point. * The Kconfig ``CONFIG_CAN_AUTO_BUS_OFF_RECOVERY`` was renamed (and inverted) to :kconfig:option:`CONFIG_CAN_MANUAL_RECOVERY_MODE`, which is disabled by default. This Kconfig option enables support for the :c:func:`can_recover()` API function and a new manual recovery mode (see the next bullet). * A new CAN controller operational mode :c:macro:`CAN_MODE_MANUAL_RECOVERY` was added. Support for this is only enabled if :kconfig:option:`CONFIG_CAN_MANUAL_RECOVERY_MODE` is enabled. Having this as a mode allows applications to inquire whether the CAN controller supports manual recovery mode via the :c:func:`can_get_capabilities` API function. The application can then either fail initialization or rely on automatic bus-off recovery. Having this as a mode furthermore allows CAN controller drivers not supporting manual recovery mode to fail early in :c:func:`can_set_mode` during application startup instead of failing when :c:func:`can_recover` is called at a later point in time. Crypto ====== * The CSS driver has been deprecated on NXP lpc55s36 (:github:`71173`). Display ======= * GC9X01 based displays now use the MIPI DBI driver class. These displays must now be declared within a MIPI DBI driver wrapper device, which will manage interfacing with the display. (:github:`73686`) For an example, see below: .. code-block:: devicetree /* Legacy GC9X01 display definition / &spi0 { gc9a01: gc9a01@0 { status = "okay"; compatible = "galaxycore,gc9x01x"; reg = <0>; spi-max-frequency = <100000000>; cmd-data-gpios = <&gpio0 8 GPIO_ACTIVE_HIGH>; reset-gpios = <&gpio0 14 GPIO_ACTIVE_LOW>; ... }; }; / New display definition with MIPI DBI device / #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h> ... mipi_dbi { compatible = "zephyr,mipi-dbi-spi"; dc-gpios = <&gpio0 8 GPIO_ACTIVE_HIGH>; reset-gpios = <&gpio0 14 GPIO_ACTIVE_LOW>; spi-dev = <&spi0>; #address-cells = <1>; #size-cells = <0>; gc9a01: gc9a01@0 { status = "okay"; compatible = "galaxycore,gc9x01x"; reg = <0>; mipi-max-frequency = <100000000>; ... }; }; ST7735R based displays now use the MIPI DBI driver class. These displays must now be declared within a MIPI DBI driver wrapper device, which will manage interfacing with the display. Note that the ``cmd-data-gpios`` pin has changed polarity with this update, to align better with the new ``dc-gpios`` name. For an example, see below: .. code-block:: devicetree /* Legacy ST7735R display definition / &spi0 { st7735r: st7735r@0 { compatible = "sitronix,st7735r"; reg = <0>; spi-max-frequency = <32000000>; reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>; cmd-data-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>; ... }; }; / New display definition with MIPI DBI device / #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h> ... mipi_dbi { compatible = "zephyr,mipi-dbi-spi"; reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>; dc-gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>; spi-dev = <&spi0>; #address-cells = <1>; #size-cells = <0>; st7735r: st7735r@0 { compatible = "sitronix,st7735r"; reg = <0>; mipi-max-frequency = <32000000>; mipi-mode = <MIPI_DBI_MODE_SPI_4WIRE>; ... }; }; UC81XX based displays now use the MIPI DBI driver class. These displays must now be declared within a MIPI DBI driver wrapper device, which will manage interfacing with the display. (:github:`73812`) Note that the ``dc-gpios`` pin has changed polarity with this update, for an example, see below: .. code-block:: devicetree /* Legacy UC81XX display definition / &spi0 { uc8179: uc8179@0 { compatible = "ultrachip,uc8179"; reg = <0>; spi-max-frequency = <4000000>; reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>; dc-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>; ... }; }; / New display definition with MIPI DBI device / #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h> ... mipi_dbi { compatible = "zephyr,mipi-dbi-spi"; reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>; dc-gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>; spi-dev = <&spi0>; #address-cells = <1>; #size-cells = <0>; uc8179: uc8179@0 { compatible = "ultrachip,uc8179"; reg = <0>; mipi-max-frequency = <4000000>; ... }; }; ST7789V based displays now use the MIPI DBI driver class. These displays must now be declared within a MIPI DBI driver wrapper device, which will manage interfacing with the display. (:github:`73750`) Note that the ``cmd-data-gpios`` pin has changed polarity with this update, to align better with the new ``dc-gpios`` name. For an example, see below: .. code-block:: devicetree /* Legacy ST7789V display definition / &spi0 { st7789: st7789@0 { compatible = "sitronix,st7789v"; reg = <0>; spi-max-frequency = <32000000>; reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>; cmd-data-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>; ... }; }; / New display definition with MIPI DBI device / #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h> ... mipi_dbi { compatible = "zephyr,mipi-dbi-spi"; reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>; dc-gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>; spi-dev = <&spi0>; #address-cells = <1>; #size-cells = <0>; st7789: st7789@0 { compatible = "sitronix,st7789v"; reg = <0>; mipi-max-frequency = <32000000>; mipi-mode = <MIPI_DBI_MODE_SPI_4WIRE>; ... }; }; SSD16XX based displays now use the MIPI DBI driver class (:github:`73946`). These displays must now be declared within a MIPI DBI driver wrapper device, which will manage interfacing with the display. Note that the ``dc-gpios`` pin has changed polarity with this update. For an example, see below: .. code-block:: devicetree /* Legacy SSD16XX display definition / &spi0 { ssd1680: ssd1680@0 { compatible = "solomon,ssd1680"; reg = <0>; spi-max-frequency = <4000000>; reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>; dc-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>; ... }; }; / New display definition with MIPI DBI device / #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h> ... mipi_dbi { compatible = "zephyr,mipi-dbi-spi"; reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>; dc-gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>; spi-dev = <&spi0>; #address-cells = <1>; #size-cells = <0>; ssd1680: ssd1680@0 { compatible = "solomon,ssd1680"; reg = <0>; mipi-max-frequency = <4000000>; ... }; }; The ``orientation-flipped`` property has been removed from the SSD16XX display driver, as the driver now supports display rotation. Users should drop this property from their devicetree, and set orientation at runtime via :c:func:`display_set_orientation` (:github:`73360`) Enhanced Serial Peripheral Interface (eSPI) =========================================== * The macros ``ESPI_SLAVE_TO_MASTER`` and ``ESPI_MASTER_TO_SLAVE`` were renamed to ``ESPI_TARGET_TO_CONTROLLER`` and ``ESPI_CONTROLLER_TO_TARGET`` respectively to reflect the new terminology in eSPI 1.5 specification. The enum values ``ESPI_VWIRE_SIGNAL_SLV_BOOT_STS``, ``ESPI_VWIRE_SIGNAL_SLV_BOOT_DONE`` and all ``ESPI_VWIRE_SIGNAL_SLV_GPIO_<NUMBER>`` signals were renamed to ``ESPI_VWIRE_SIGNAL_TARGET_BOOT_STS``, ``ESPI_VWIRE_SIGNAL_TARGET_BOOT_DONE`` and ``ESPI_VWIRE_SIGNAL_TARGET_GPIO_<NUMBER>`` respectively to reflect the new terminology in eSPI 1.5 specification. (:github:`68492`) The Kconfig ``CONFIG_ESPI_SLAVE`` was renamed to :kconfig:option:`CONFIG_ESPI_TARGET`, similarly ``CONFIG_ESPI_SAF`` was renamed as :kconfig:option:`CONFIG_ESPI_TAF` (:github:`73887`) GNSS ==== * Basic power management support has been added to the ``gnss-nmea-generic`` driver. If ``CONFIG_PM_DEVICE=y`` the driver is now initialized in suspended mode and the application needs to call :c:func:`pm_device_action_run` with :c:macro:`PM_DEVICE_ACTION_RESUME` to start up the driver. (:github:`71774`) Input ===== * The ``analog-axis`` deadzone calibration value has been changed to be relative to the raw ADC values, similarly to min and max. The data structures and properties have been renamed to reflect that (from ``out-deadzone`` to ``in-deadzone``) and when migrating to the new definition the value should be scaled accordingly. (:github:`70377`) * The ``holtek,ht16k33-keyscan`` driver has been converted to use the :ref:`input` subsystem, callbacks have to be migrated to use the input APIs, :dtcompatible:`zephyr,kscan-input` can be used for backward compatibility. (:github:`69875`) Interrupt Controller ==================== * The static auto-generation of the multilevel interrupt controller lookup table has been deprecated, and will be compiled only when the new compatibility Kconfig: :kconfig:option:`CONFIG_LEGACY_MULTI_LEVEL_TABLE_GENERATION` is enabled, which will eventually be removed in the coming releases. Multi-level interrupt controller drivers should be updated to use the newly created ``IRQ_PARENT_ENTRY_DEFINE`` macro to register itself with the new multi-level interrupt architecture. To make the macro easier to use, ``INTC_INST_ISR_TBL_OFFSET`` macro is made to deduce the software ISR table offset for a given driver instance, for pseudo interrupt controller child, use the ``INTC_CHILD_ISR_TBL_OFFSET`` macro instead. New devicetree macros (``DT_INTC_GET_AGGREGATOR_LEVEL`` & ``DT_INST_INTC_GET_AGGREGATOR_LEVEL``) have been added for an interrupt controller driver instance to pass its aggregator level into the ``IRQ_PARENT_ENTRY_DEFINE`` macro. LED Strip ========= * The property ``in-gpios`` defined in :dtcompatible:`worldsemi,ws2812-gpio` has been renamed to ``gpios``. (:github:`68514`) * The ``chain-length`` and ``color-mapping`` properties have been added to all LED strip bindings and are now mandatory. * Added a new mandatory ``length`` function which returns the length (number of pixels) of an LED strip device. * Made ``update_channels`` function optional and removed unimplemented functions. * The ``CONFIG_WS2812_STRIP_DRIVER`` kconfig option has been removed. Previously, when using :kconfig:option:`CONFIG_WS2812_STRIP_SPI`, :kconfig:option:`CONFIG_WS2812_STRIP_I2S`, :kconfig:option:`CONFIG_WS2812_STRIP_GPIO`, or :kconfig:option:`CONFIG_WS2812_STRIP_RPI_PICO_PIO`, one of them had to be selected with ``CONFIG_WS2812_STRIP_DRIVER``, but this is no longer necessary. Please set each option directly. MDIO ==== * :kconfig:option:`CONFIG_MDIO_NXP_ENET_TIMEOUT` is now in units of microseconds instead of milliseconds. (:github:`75625`) Sensors ======= * The ``chip`` devicetree property from the :dtcompatible:`sensirion,shtcx` sensor driver has been removed. Chip variants are now selected using the matching compatible property (:github:`74033`). For an example of the new shtc3 configuration, see below: .. code-block:: devicetree &i2c0 { status = "okay"; shtc3: shtc3@70 { compatible = "sensirion,shtc3", "sensirion,shtcx"; reg = <0x70>; measure-mode = "normal"; clock-stretching; }; }; Serial ====== * The Raspberry Pi UART driver ``uart_rpi_pico`` has been removed. Use ``uart_pl011`` (:dtcompatible:`arm,pl011`) instead. (:github:`71074`) Regulator ========= * The :dtcompatible:`nxp,vref` driver no longer supports the ground selection function, as this setting should not be modified by the user. The DT property ``nxp,ground-select`` has been removed, users should remove this property from their devicetree if it is present. (:github:`70642`) W1 == * The :dtcompatible:`zephyr,w1-gpio` 1-Wire master driver no longer defaults to enabling the internal pull-up resistor of the GPIO pin. The configuration is now taken from the pin's configuration flags specified in devicetree. (:github:`71789`) Watchdog ======== * The ``nuvoton,npcx-watchdog`` driver has been changed to extend the max timeout period. The time of one watchdog count varies with the different pre-scalar settings. Removed :kconfig:option:`CONFIG_WDT_NPCX_DELAY_CYCLES` because it is no longer suitable to set the leading warning time. Instead, added the :kconfig:option:`CONFIG_WDT_NPCX_WARNING_LEADING_TIME_MS` to set the leading warning time in milliseconds. Bluetooth ********* Bluetooth HCI ============= * A new HCI driver API was introduced (:github:`72323`) and the old one deprecated. The new API follows the normal Zephyr driver model, with devicetree nodes, etc. The host now selects which driver instance to use as the controller by looking for a ``zephyr,bt-hci`` chosen property. The devicetree bindings for all HCI drivers derive from a common ``bt-hci.yaml`` base binding. * As part of the new HCI driver API, the ``zephyr,bt-uart`` chosen property is no longer used, rather the UART HCI drivers select their UART by looking for the parent devicetree node of the HCI driver instance node. * As part of the new HCI driver API, the ``zephyr,bt-hci-ipc`` chosen property is only used for the controller side, whereas the HCI driver now relies on nodes with the compatible string ``zephyr,bt-hci-ipc``. * The ``BT_NO_DRIVER`` Kconfig option was removed. HCI drivers are no-longer behind a Kconfig choice, rather they can now be enabled and disabled independently, mostly based on their respective devicetree node being enabled or not. * The ``BT_HCI_VS_EXT`` Kconfig option was deleted and the feature is now included in the :kconfig:option:`CONFIG_BT_HCI_VS` Kconfig option. * The ``BT_HCI_VS_EVT`` Kconfig option was removed, since vendor event support is implicit if the :kconfig:option:`CONFIG_BT_HCI_VS` option is enabled. * The bt_read_static_addr() API was removed. This wasn't really a completely public API, but since it was exposed by the public hci_driver.h header file the removal is mentioned here. Enable the :kconfig:option:`CONFIG_BT_HCI_VS` Kconfig option instead, and use vendor specific HCI commands API to get the Controller's Bluetooth static address when available. Bluetooth Mesh ============== * The model metadata pointer declaration of :c:struct:`bt_mesh_model` has been changed to add ``const`` qualifiers. The data pointer of :c:struct:`bt_mesh_models_metadata_entry` got ``const`` qualifier too. The model's metadata structure and metadata raw value can be declared as permanent constants in the non-volatile memory. (:github:`69679`) * The model metadata pointer declaration of :c:struct:`bt_mesh_model` has been changed to a single ``const `` and redundant metadata pointer from :c:struct:`bt_mesh_health_srv` is removed. Consequently, :code:`BT_MESH_MODEL_HEALTH_SRV` definition is changed to use variable argument notation. Now, when your implementation supports :kconfig:option:`CONFIG_BT_MESH_LARGE_COMP_DATA_SRV` and when you need to specify metadata for Health Server model, simply pass metadata as the last argument to the :code:`BT_MESH_MODEL_HEALTH_SRV` macro, otherwise omit the last argument. (:github:`71281`) Bluetooth Audio =============== :kconfig:option:`CONFIG_BT_ASCS`, :kconfig:option:`CONFIG_BT_PERIPHERAL` and :kconfig:option:`CONFIG_BT_ISO_PERIPHERAL` are no longer enabled automatically when enabling :kconfig:option:`CONFIG_BT_BAP_UNICAST_SERVER`, and these must now be set explicitly in the project configuration file. (:github:`71993`) * The discover callback functions :code:`bt_cap_initiator_cb.unicast_discovery_complete` and :code:`bt_cap_commander_cb.discovery_complete` for CAP now contain an additional parameter for the set member. This needs to be added to all instances of CAP discovery callback functions defined. (:github:`72797`) * :c:func:`bt_bap_stream_start` no longer connects the CIS. To connect the CIS, the :c:func:`bt_bap_stream_connect` shall now be called before :c:func:`bt_bap_stream_start`. (:github:`73032`) * Renamed ``stream_lang`` to just ``lang`` to better fit with the assigned numbers document. This affects the ``BT_AUDIO_METADATA_TYPE_LANG`` macro and the following functions: * :c:func:`bt_audio_codec_cap_meta_set_lang` * :c:func:`bt_audio_codec_cap_meta_get_lang` * :c:func:`bt_audio_codec_cfg_meta_set_lang` * :c:func:`bt_audio_codec_cfg_meta_get_lang` (:github:`72584`) * Changed ``lang`` from ``uint32_t`` to ``uint8_t [3]``. This modifies the following functions: * :c:func:`bt_audio_codec_cap_meta_set_lang` * :c:func:`bt_audio_codec_cap_meta_get_lang` * :c:func:`bt_audio_codec_cfg_meta_set_lang` * :c:func:`bt_audio_codec_cfg_meta_get_lang` The result of this is that string values such as ``"eng"`` and ``"deu"`` can now be used to set new values, and to prevent unnecessary copies of data when getting the values. (:github:`72584`) * All occurrences of ``set_sirk`` have been changed to just ``sirk`` as the ``s`` in ``sirk`` stands for set. (:github:`73413`) * Added ``fallback_to_default`` parameter to :c:func:`bt_audio_codec_cfg_get_chan_allocation`. To maintain existing behavior set the parameter to ``false``. (:github:`72090`) * Added ``fallback_to_default`` parameter to :c:func:`bt_audio_codec_cap_get_supported_audio_chan_counts`. To maintain existing behavior set the parameter to ``false``. (:github:`72090`) * Added ``fallback_to_default`` parameter to :c:func:`bt_audio_codec_cap_get_max_codec_frames_per_sdu`. To maintain existing behavior set the parameter to ``false``. (:github:`72090`) * Added ``fallback_to_default`` parameter to :c:func:`bt_audio_codec_cfg_meta_get_pref_context`. To maintain existing behavior set the parameter to ``false``. (:github:`72090`) Bluetooth Classic ================= * The source files of Host BR/EDR have been moved to ``subsys/bluetooth/host/classic``. The Header files of Host BR/EDR have been moved to ``include/zephyr/bluetooth/classic``. Removed the :kconfig:option:`CONFIG_BT_BREDR`. It is replaced by new option :kconfig:option:`CONFIG_BT_CLASSIC`. (:github:`69651`) Bluetooth Host ============== * The advertiser options :code:`BT_LE_ADV_OPT_USE_NAME` and :code:`BT_LE_ADV_OPT_FORCE_NAME_IN_AD` are deprecated in this release. The application need to include the device name explicitly. One way to do it is by adding the following to the advertising data or scan response data passed to the host: .. code-block:: c BT_DATA(BT_DATA_NAME_COMPLETE, CONFIG_BT_DEVICE_NAME, sizeof(CONFIG_BT_DEVICE_NAME) - 1) (:github:`71686`) * The field :code:`init_credits` in :c:type:`bt_l2cap_le_endpoint` has been removed as it was no longer used in Zephyr 3.4.0 and later. Any references to this field should be removed. No further action is needed. * :c:macro:`BT_LE_ADV_PARAM` now returns a :code:`const` pointer. Any place where the result is stored in a local variable such as :code:`struct bt_le_adv_param param = BT_LE_ADV_CONN;` will need to be updated to :code:`const struct bt_le_adv_param param = BT_LE_ADV_CONN;` or use it for initialization like :code:`struct bt_le_adv_param param = BT_LE_ADV_CONN;` The change to :c:macro:`BT_LE_ADV_PARAM` also affects all of its derivatives, including but not limited to: :c:macro:`BT_LE_ADV_CONN` * :c:macro:`BT_LE_ADV_NCONN` * :c:macro:`BT_LE_EXT_ADV_SCAN` * :c:macro:`BT_LE_EXT_ADV_CODED_NCONN_NAME` (:github:`75065`) * :kconfig:option:`CONFIG_BT_BUF_ACL_RX_COUNT` now needs to be larger than :kconfig:option:`CONFIG_BT_MAX_CONN`. This was always the case due to the design of the HCI interface. It is now being enforced through a build-time assertion. (:github:`75592`) Bluetooth Crypto ================ * :kconfig:option:`CONFIG_BT_USE_PSA_API` was added to explicitly request use of PSA APIs instead of TinyCrypt for crypto operations. Of course, this is possible only a PSA crypto provider available in the system, i.e. :kconfig:option:`CONFIG_PSA_CRYPTO_CLIENT` is set. (:github:`73378`) Networking ********** * Deprecate the :kconfig:option:`CONFIG_NET_SOCKETS_POSIX_NAMES` option. It is a legacy option and was used to allow user to call BSD socket API while not enabling POSIX API. This could cause complications when building applications that wanted to enable the :kconfig:option:`CONFIG_POSIX_API` option. This means that if the application wants to use normal BSD socket interface, then it needs to enable :kconfig:option:`CONFIG_POSIX_API`. If the application does not want or is not able to enable that option, then the socket API calls need to be prefixed by a ``zsock_`` string. All the sample applications that use BSD socket interface are changed to enable :kconfig:option:`CONFIG_POSIX_API`. Internally the network stack will not enable POSIX API option which means that various network libraries that use sockets, are converted to use the ``zsock_`` API calls. (:github:`69950`) The zperf zperf_results struct is changed to support 64 bits transferred bytes (total_len) and test duration (time_in_us and client_time_in_us), instead of 32 bits. This will make the long-duration zperf test show with correct throughput result. (:github:`69500`) * Each IPv4 address assigned to a network interface has an IPv4 netmask tied to it instead of being set for the whole interface. If there is only one IPv4 address specified for a network interface, nothing changes from the user point of view. But, if there is more than one IPv4 address / network interface, the netmask must be specified for each IPv4 address separately. (:github:`68419`) * Virtual network interface API no longer has the ``input`` callback. The input callback was used to read the inner IPv4/IPv6 packets in an IP tunnel. This incoming tunnel read is now implemented in the ``recv`` callback. (:github:`70549`) * Virtual LAN (VLAN) implementation is changed to use the Virtual network interfaces. There are no API changes, but the type of a VLAN network interface is changed from ``ETHERNET`` to ``VIRTUAL``. This could require changes to the code that sets the VLAN tags to a network interface. For example in the :c:func:`net_eth_is_vlan_enabled()` API, the 2nd interface parameter must point to the main Ethernet interface, and not to the VLAN interface. (:github:`70345`) * Modified the ``wifi connect`` command to use key-value format for the arguments. In the previous implementation, we were identifying an option using its position in the argument string. This made it difficult to deal with optional arguments or extending the support for other options. Having this key-value format makes it easier to extend the options that can be passed to the connect command. ``wifi -h`` will give more information about the usage of connect command. (:github:`70024`) * The Kconfig :kconfig:option:`CONFIG_NET_TCP_ACK_TIMEOUT` has been deprecated. Its usage was limited to TCP handshake only, and in such case the total timeout should depend on the total retransmission timeout (as in other cases) making the config redundant and confusing. Use :kconfig:option:`CONFIG_NET_TCP_INIT_RETRANSMISSION_TIMEOUT` and :kconfig:option:`CONFIG_NET_TCP_RETRY_COUNT` instead to control the total timeout at the TCP level. (:github:`70731`) * In LwM2M API, the callback type :c:type:`lwm2m_engine_set_data_cb_t` has now an additional parameter ``offset``. This parameter is used to indicate the offset of the data during a Coap Block-wise transfer. Any post write, validate or some firmware callbacks should be updated to include this parameter. (:github:`72590`) * The DNS resolver and mDNS/LLMNR responders are converted to use socket service API. This means that the number of pollable sockets in the system might need to be increased. Please check that the values of :kconfig:option:`CONFIG_NET_SOCKETS_POLL_MAX` and :kconfig:option:`CONFIG_POSIX_MAX_FDS` are high enough. Unfortunately no exact values for these can be given as it depends on application needs and usage. (:github:`72834`) * The packet socket (type ``AF_PACKET``) protocol field in ``socket`` API call has changed. The protocol field should be in network byte order so that we are compatible with Linux socket calls. Linux expects the protocol field to be ``htons(ETH_P_ALL)`` if it is desired to receive all the network packets. See details in path_to_url documentation. (:github:`73338`) * TCP now uses SHA-256 instead of MD5 for ISN generation. The crypto support for this hash computation was also changed from Mbed TLS to PSA APIs. This was achieved by making :kconfig:option:`CONFIG_NET_TCP_ISN_RFC6528` depend on :kconfig:option:`PSA_WANT_ALG_SHA_256` instead of legacy ``CONFIG_MBEDTLS_`` features. (:github:`71827`) Other Subsystems *************** Flash map ========= * The crypto backend for the flash check functions (:kconfig:option:`CONFIG_FLASH_AREA_CHECK_INTEGRITY_BACKEND`), previously provided through either TinyCrypt or Mbed TLS, is now provided through either PSA or Mbed TLS. The updated Mbed TLS implementation has a slightly smaller footprint than the previous TinyCrypt one, and the PSA implementation offers an even greater footprint reduction for devices built with TF-M. PSA is the supported way forward, however as of now you may still use Mbed TLS if you cannot afford the one-time cost of enabling the PSA API (:kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_C` for devices without TF-M). :github:`73511` hawkBit ======= * :kconfig:option:`CONFIG_HAWKBIT_PORT` is now an int instead of a string. :kconfig:option:`CONFIG_SETTINGS` needs to be enabled to use hawkBit, as it now uses the settings subsystem to store the hawkBit configuration. (:github:`68806`) MCUmgr ====== * The support for SHA-256 (when using checksum/hash functions), previously provided by either TinyCrypt or Mbed TLS, is now provided by either PSA or Mbed TLS. PSA is the recommended API going forward, however, if it is not already enabled (:kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_CLIENT`) and you have tight code size constraints, you may be able to save 1.3 KB by using Mbed TLS instead. Modem ===== * The ``CONFIG_MODEM_CHAT_LOG_BUFFER`` Kconfig option was renamed to :kconfig:option:`CONFIG_MODEM_CHAT_LOG_BUFFER_SIZE`. (:github:`70405`) .. _zephyr_3.7_posix_api_migration: POSIX API ========= * The :ref:`POSIX API Kconfig deprecations <zephyr_3.7_posix_api_deprecations>` may require changes to Kconfig files (``prj.conf``, etc), as outlined in the release notes. A more automated approach is available via the provided migration script. Simply run the following: .. code-block:: bash $ python ${ZEPHYR_BASE}/scripts/utils/migrate_posix_kconfigs.py -r root_path State Machine Framework ======================= * The :c:macro:`SMF_CREATE_STATE` macro now always takes 5 arguments. The amount of arguments is now independent of the values of :kconfig:option:`CONFIG_SMF_ANCESTOR_SUPPORT` and :kconfig:option:`CONFIG_SMF_INITIAL_TRANSITION`. If the additional arguments are not used, they have to be set to ``NULL``. (:github:`71250`) * SMF now follows a more UML-like transition flow when the transition source is a parent of the state called by :c:func:`smf_run_state`. Exit actions up to (but not including) the Least Common Ancestor of the transition source and target state will be executed, as will entry actions from (but not including) the LCA down to the target state. (:github:`71675`) * Previously, calling :c:func:`smf_set_state` with a ``new_state`` set to NULL would execute all exit actions from the current state to the topmost parent, with the expectation the topmost exit action would terminate the state machine. Passing ``NULL`` is now not allowed. Instead create a 'terminate' state at the top level, and call :c:func:`smf_set_terminate` from its entry action. UpdateHub ========= * The SHA-256 implementation used to perform integrity checks is not chosen with :kconfig:option:`CONFIG_FLASH_AREA_CHECK_INTEGRITY_BACKEND` anymore. Instead, the implementation used (now either Mbed TLS or PSA) is chosen based on :kconfig:option:`CONFIG_PSA_CRYPTO_CLIENT`. It still defaults to using Mbed TLS (with a smaller footprint than previously) unless the board is built with TF-M or :kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_C` is enabled. (:github:`73511`) Architectures ************* * Function :c:func:`arch_start_cpu` has been renamed to :c:func:`arch_cpu_start`. (:github:`64987`) * ``CONFIG_ARM64_ENABLE_FRAME_POINTER`` is deprecated. Use :kconfig:option:`CONFIG_FRAME_POINTER` instead. (:github:`72646`) * x86 * Kconfigs ``CONFIG_DISABLE_SSBD`` and ``CONFIG_ENABLE_EXTENDED_IBRS`` are deprecated. Use :kconfig:option:`CONFIG_X86_DISABLE_SSBD` and :kconfig:option:`CONFIG_X86_ENABLE_EXTENDED_IBRS` instead. (:github:`69690`) * POSIX arch: * LLVM fuzzing support has been refactored. A test application now needs to provide its own ``LLVMFuzzerTestOneInput()`` hook instead of relying on a board provided one. Check ``samples/subsys/debug/fuzz/`` for an example. (:github:`71378`) ```	/content/code_sandbox/doc/releases/migration-guide-3.7.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	11,163
```restructuredtext :orphan: .. _zephyr_3.7: Zephyr 3.7.0 ############ We are pleased to announce the release of Zephyr version 3.7.0. This release is the last non-maintenance 3.x release and, as such, will be the next :ref:`Long Term Support (LTS) release <release_process_lts>`. Major enhancements with this release include: * A new, completely :ref:`overhauled hardware model <hw_model_v2>` has been introduced. It 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`. * A long-awaited :ref:`HTTP Server <http_server_interface>` library, and associated service API, allow to easily implement HTTP/1.1 and HTTP/2 servers in Zephyr. Resources can be registered statically or dynamically, and WebSocket support is included. * :ref:`POSIX support <posix_support>` has been extended, with most Options of the IEEE 1003-2017 :ref:`System Interfaces <posix_system_interfaces_required>` receiving support, as well as most Options and Option groups required for :ref:`PSE51 <posix_aep_pse51>`, :ref:`PSE52 <posix_aep_pse52>`, and :ref:`PSE53 <posix_aep_pse53>`. * Bluetooth Host has been extended with support for the Nordic UART Service (NUS), Hands-free Audio Gateway (AG), Advanced Audio Distribution Profile (A2DP), and Audio/Video Distribution Transport Protocol (AVDTP). * Sensor abstraction model has been overhauled to adopt a :ref:`read-then-decode approach <sensor-read-and-decode>` that enables more types of sensors and data flows than the previous fetch/get APIs. * A new :ref:`LLEXT Extension Developer Kit (EDK) <llext_build_edk>` makes it easier to develop and integrate custom extensions into Zephyr, including outside of the Zephyr tree. * :ref:`Native simulator <native_sim>` now supports leveraging the native host networking stack without having to rely on a complex setup of the host environment. * Trusted Firmware-M (TF-M) 2.1.0 and Mbed TLS 3.6.0 have been integrated into Zephyr. Both of these versions are LTS releases. What's more, :ref:`psa_crypto` has been adopted as a replacement for TinyCrypt and provides enhanced security and performance. * A new experimental implementation of the :ref:`Precision Time Protocol <ptp_interface>` (PTP, IEEE 1588) allows to synchronize time across devices with sub-microsecond accuracy. * New documentation pages have been introduced to help developers setup their local development environment for :ref:`vscode_ide` and :ref:`clion_ide`. 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>`. While you may refer to release notes from previous 3.x releases for a full change log, other major enhancements and changes since previous LTS release, Zephyr 2.7.0, include: * Added support for Picolibc as the new default C library. * Added support for the following types of hardware peripherals: * 1-Wire * Battery Charger * Cellular Modem * Fuel Gauge * GNSS * Hardware Spinlock * I3C * RTC (Real Time Clock) * SMBus * Added support for snippets. Snippets are common configuration settings that can be used across platforms. * Added support for Linkable Loadable Extensions (LLEXT). * Summary of breaking changes (refer to release notes and migration guides from previous release notes for more details): * All Zephyr public headers have been moved to :file:`include/zephyr`, meaning they need to be prefixed with ``<zephyr/...>`` when included. * Pinmux API has been removed. Pin control needs to be used as its replacement, refer to :ref:`pinctrl-guide` for more details. * The following deprecated or experimental features have been removed: * 6LoCAN * civetweb module. See Zephyr 3.7's new :ref:`http_server_interface` as a replacement. * tinycbor module. You may use zcbor as a replacement. 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: path_to_url * CVE-2024-3077 `Zephyr project bug tracker GHSA-gmfv-4vfh-2mh8 <path_to_url`_ * CVE-2024-3332 `Zephyr project bug tracker GHSA-jmr9-xw2v-5vf4 <path_to_url`_ * CVE-2024-4785: Under embargo until 2024-08-07 * CVE-2024-5754: Under embargo until 2024-09-04 * CVE-2024-5931: Under embargo until 2024-09-10 * CVE-2024-6135: Under embargo until 2024-09-11 * CVE-2024-6137: Under embargo until 2024-09-11 * CVE-2024-6258: Under embargo until 2024-09-05 * CVE-2024-6259: Under embargo until 2024-09-12 * CVE-2024-6442: Under embargo until 2024-09-22 * CVE-2024-6443: Under embargo until 2024-09-22 * CVE-2024-6444: Under embargo until 2024-09-22 API Changes *********** Removed APIs in this release ============================ * The Bluetooth subsystem specific debug symbols are removed. They have been replaced with the Zephyr logging ones. * Removed deprecated ``pcie_probe`` and ``pcie_bdf_lookup`` functions from the PCIe APIs. * Removed deprecated ``CONFIG_EMUL_EEPROM_AT2X`` Kconfig option. * Removed ``pm_device_state_lock``, ``pm_device_state_is_locked`` and ``pm_device_state_unlock`` functions from the Device PM APIs. * Removed deprecated MCUmgr transport API functions: ``zephyr_smp_rx_req``, ``zephyr_smp_alloc_rsp`` and ``zephyr_smp_free_buf``. Deprecated in this release ========================== * Bluetooth advertiser options :code:`BT_LE_ADV_OPT_USE_NAME` and :code:`BT_LE_ADV_OPT_FORCE_NAME_IN_AD` are now deprecated. That means the following macro are deprecated: * :c:macro:`BT_LE_ADV_CONN_NAME` * :c:macro:`BT_LE_ADV_CONN_NAME_AD` * :c:macro:`BT_LE_ADV_NCONN_NAME` * :c:macro:`BT_LE_EXT_ADV_CONN_NAME` * :c:macro:`BT_LE_EXT_ADV_SCAN_NAME` * :c:macro:`BT_LE_EXT_ADV_NCONN_NAME` * :c:macro:`BT_LE_EXT_ADV_CODED_NCONN_NAME` Application developers will now need to set the advertised name themselves by updating the advertising data or the scan response data. * 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. * Deprecated the :c:func:`can_get_min_bitrate` and :c:func:`can_get_max_bitrate` API functions in favor of :c:func:`can_get_bitrate_min` and :c:func:`can_get_bitrate_max`. * Deprecated the :c:macro:`CAN_MAX_STD_ID` and :c:macro:`CAN_MAX_EXT_ID` macros in favor of :c:macro:`CAN_STD_ID_MASK` and :c:macro:`CAN_EXT_ID_MASK`. * PM * Deprecated :kconfig:option:`CONFIG_PM_DEVICE_RUNTIME_EXCLUSIVE`. Similar behavior can be achieved using :kconfig:option:`CONFIG_PM_DEVICE_SYSTEM_MANAGED`. .. _zephyr_3.7_posix_api_deprecations: * POSIX API * Deprecated :c:macro:`PTHREAD_BARRIER_DEFINE` has been removed. * Deprecated :c:macro:`EFD_IN_USE` and :c:macro:`EFD_FLAGS_SET` have been removed. * In efforts to use Kconfig options that map directly to the Options and Option Groups in IEEE 1003.1-2017, the following Kconfig options have been deprecated (replaced by): * :kconfig:option:`CONFIG_EVENTFD_MAX` (:kconfig:option:`CONFIG_ZVFS_EVENTFD_MAX`) * :kconfig:option:`CONFIG_FNMATCH` (:kconfig:option:`CONFIG_POSIX_C_LIB_EXT`) * :kconfig:option:`CONFIG_GETOPT` (:kconfig:option:`CONFIG_POSIX_C_LIB_EXT`) * :kconfig:option:`CONFIG_MAX_PTHREAD_COUNT` (:kconfig:option:`CONFIG_POSIX_THREAD_THREADS_MAX`) * :kconfig:option:`CONFIG_MAX_PTHREAD_KEY_COUNT` (:kconfig:option:`CONFIG_POSIX_THREAD_KEYS_MAX`) * :kconfig:option:`CONFIG_MAX_TIMER_COUNT` (:kconfig:option:`CONFIG_POSIX_TIMER_MAX`) * :kconfig:option:`CONFIG_POSIX_LIMITS_RTSIG_MAX` (:kconfig:option:`CONFIG_POSIX_RTSIG_MAX`) * :kconfig:option:`CONFIG_POSIX_CLOCK` (:kconfig:option:`CONFIG_POSIX_CLOCK_SELECTION`, :kconfig:option:`CONFIG_POSIX_CPUTIME`, :kconfig:option:`CONFIG_POSIX_MONOTONIC_CLOCK`, :kconfig:option:`CONFIG_POSIX_TIMERS`, and :kconfig:option:`CONFIG_POSIX_TIMEOUTS`) * :kconfig:option:`CONFIG_POSIX_FS` (:kconfig:option:`CONFIG_POSIX_FILE_SYSTEM`) * :kconfig:option:`CONFIG_POSIX_MAX_FDS` (:kconfig:option:`CONFIG_POSIX_OPEN_MAX` and :kconfig:option:`CONFIG_ZVFS_OPEN_MAX`) * :kconfig:option:`CONFIG_POSIX_MAX_OPEN_FILES` (:kconfig:option:`CONFIG_POSIX_OPEN_MAX` and :kconfig:option:`CONFIG_ZVFS_OPEN_MAX`) * :kconfig:option:`CONFIG_POSIX_MQUEUE` (:kconfig:option:`CONFIG_POSIX_MESSAGE_PASSING`) * :kconfig:option:`CONFIG_POSIX_PUTMSG` (:kconfig:option:`CONFIG_XOPEN_STREAMS`) * :kconfig:option:`CONFIG_POSIX_SIGNAL` (:kconfig:option:`CONFIG_POSIX_SIGNALS`) * :kconfig:option:`CONFIG_POSIX_SYSCONF` (:kconfig:option:`CONFIG_POSIX_SINGLE_PROCESS`) * :kconfig:option:`CONFIG_POSIX_UNAME` (:kconfig:option:`CONFIG_POSIX_SINGLE_PROCESS`) * :kconfig:option:`CONFIG_PTHREAD` (:kconfig:option:`CONFIG_POSIX_THREADS`) * :kconfig:option:`CONFIG_PTHREAD_BARRIER` (:kconfig:option:`CONFIG_POSIX_BARRIERS`) * :kconfig:option:`CONFIG_PTHREAD_COND` (:kconfig:option:`CONFIG_POSIX_THREADS`) * :kconfig:option:`CONFIG_PTHREAD_IPC` (:kconfig:option:`CONFIG_POSIX_THREADS`) * :kconfig:option:`CONFIG_PTHREAD_KEY` (:kconfig:option:`CONFIG_POSIX_THREADS`) * :kconfig:option:`CONFIG_PTHREAD_MUTEX` (:kconfig:option:`CONFIG_POSIX_THREADS`) * :kconfig:option:`CONFIG_PTHREAD_RWLOCK` (:kconfig:option:`CONFIG_POSIX_READER_WRITER_LOCKS`) * :kconfig:option:`CONFIG_PTHREAD_SPINLOCK` (:kconfig:option:`CONFIG_POSIX_SPIN_LOCKS`) * :kconfig:option:`CONFIG_SEM_NAMELEN_MAX` (:kconfig:option:`CONFIG_POSIX_SEM_NAMELEN_MAX`) * :kconfig:option:`CONFIG_SEM_VALUE_MAX` (:kconfig:option:`CONFIG_POSIX_SEM_VALUE_MAX`) * :kconfig:option:`CONFIG_TIMER` (:kconfig:option:`CONFIG_POSIX_TIMERS`) * :kconfig:option:`CONFIG_TIMER_DELAYTIMER_MAX` (:kconfig:option:`CONFIG_POSIX_DELAYTIMER_MAX`) Please see the :ref:`POSIX API migration guide <zephyr_3.7_posix_api_migration>`. * SPI * Deprecated :c:func:`spi_is_ready` API function has been removed. * Deprecated :c:func:`spi_transceive_async` API function has been removed. * Deprecated :c:func:`spi_read_async` API function has been removed. * Deprecated :c:func:`spi_write_async` API function has been removed. Architectures ************* * ARC * Added ARC MWDT toolchain support for ARC-V targets * Added HW memory barrier API support for multicore targets * Enabled TLS by default if C++ is used in case of ARC MWDT toolchain * Fixed the issue when mbedtls failed to build with ARC MWDT toolchain & minimal LibC due to incorrect define which mark support of bounds-checking interfaces C library extension * Fixed device deferred initialization in case of ARC MWDT toolchain * ARM * Added initial support for Cortex-M85 Core * ARM64 * Implemented symbol names in the backtraces, enable by selecting :kconfig:option:`CONFIG_SYMTAB` * Add compiler tuning for Cortex-R82 * RISC-V * The fatal error message triggered from a fault now contains the callee-saved-registers states. * Implemented stack unwinding * Frame-pointer can be selected to enable precise stack traces at the expense of slightly increased size and decreased speed. * Symbol names can be enabled by selecting :kconfig:option:`CONFIG_EXCEPTION_STACK_TRACE_SYMTAB` * Xtensa * Added support to save/restore HiFi AudioEngine registers. * Added support to utilize MPU. * Added support to automatically generate interrupt handlers. * Added support to generate vector table at build time to be included in the linker script. * Added kconfig :kconfig:option:`CONFIG_XTENSA_BREAK_ON_UNRECOVERABLE_EXCEPTIONS` to guard using break instruction for unrecoverable exceptions. Enabling the break instruction via this kconfig may result in an infinite interrupt storm which may hinder debugging efforts. * Fixed an issue where passing the 7th argument via syscall was handled incorrectly. * Fixed an issue where :c:func:`arch_user_string_nlen` accessing unmapped memory resulted in an unrecoverable exception. Kernel ****** * Added :c:func:`k_uptime_seconds` function to simplify ``k_uptime_get() / 1000`` usage. * Added :c:func:`k_realloc`, that uses kernel heap to implement traditional :c:func:`realloc` semantics. * Devices can now store devicetree metadata such as nodelabels by turning on :kconfig:option:`CONFIG_DEVICE_DT_METADATA`. This option may be useful in e.g. shells as devices can be obtained using human-friendly names thanks to APIs like :c:func:`device_get_by_dt_nodelabel`. * Any device initialization can be deferred if its associated devicetree node has the special ``zephyr,deferred-init`` property set. The device can be initialized later in time by using :c:func:`device_init`. * The declaration of statically allocated thread stacks has been updated to utilize :c:macro:`K_THREAD_STACK_LEN` for both single thread stack declaration and array thread stack declarations. This ensures correct alignment for all thread stacks. For user threads, this may increase the size of the statically allocated stack objects depending on architecture alignment requirements. * Fix an edge case deadlock in :c:func:`k_thread_abort` (and join) where racing ISRs on SMP systems could become stuck spinning to signal each other's interrupted threads. * Fix a bug where :kconfig:option:`CONFIG_SCHED_SCALABLE` and :kconfig:option:`CONFIG_SCHED_DEADLINE` would corrupt the scheduling queue when used together. Bluetooth ********* * Audio * Removed ``err`` from :c:struct:`bt_bap_broadcast_assistant_cb.recv_state_removed` as it was redundant. * The broadcast_audio_assistant sample has been renamed to bap_broadcast_assistant. The broadcast_audio_sink sample has been renamed to bap_broadcast_sink. The broadcast_audio_source sample has been renamed to bap_broadcast_source. The unicast_audio_client sample has been renamed to bap_unicast_client. The unicast_audio_server sample has been renamed to bap_unicast_server. The public_broadcast_sink sample has been renamed to pbp_public_broadcast_sink. The public_broadcast_source sample has been renamed to pbp_public_broadcast_source. * The CAP Commander and CAP Initiator now no longer require CAS to be discovered for :code:`BT_CAP_SET_TYPE_AD_HOC` sets. This allows applications to use these APIs on e.g. BAP Unicast Servers that do not implement the CAP Acceptor role. * Host * Added Nordic UART Service (NUS), enabled by the :kconfig:option:`CONFIG_BT_ZEPHYR_NUS`. This Service exposes the ability to declare multiple instances of the GATT service, allowing multiple serial endpoints to be used for different purposes. * Implemented Hands-free Audio Gateway (AG), enabled by the :kconfig:option:`CONFIG_BT_HFP_AG`. It works as a device that is the gateway of the audio. The typical device acting as Audio Gateway is a cellular phone. It controls the device (Hands-free Unit), that is the remote audio input and output mechanism. * Implemented Advanced Audio Distribution Profile (A2DP) and Audio/Video Distribution Transport Protocol (AVDTP), A2DP is enabled by :kconfig:option:`CONFIG_BT_A2DP`, AVDTP is enabled by :kconfig:option:`CONFIG_BT_AVDTP`. They implement the protocols and procedures that realize distribution of audio content of high quality in mono, stereo, or multi-channel modes. A typical use case is the streaming of music content from a stereo music player to headphones or speakers. The audio data is compressed in a proper format for efficient use of the limited bandwidth. * Reworked the transmission path for data and commands. The "BT TX" thread has been removed, along with the buffer pools for HCI fragments and L2CAP segments. All communication with the Controller is now exclusively done in the system workqueue context. * :kconfig:option:`CONFIG_BT_PER_ADV_SYNC_TRANSFER_RECEIVER` and :kconfig:option:`CONFIG_BT_PER_ADV_SYNC_TRANSFER_SENDER` now depend on :kconfig:option:`CONFIG_BT_CONN` as they do not work without connections. * Improve :c:func:`bt_foreach_bond` to support Bluetooth Classic key traversal. * HCI Drivers * Completely redesigned HCI driver interface. See the Bluetooth HCI section in :ref:`migration_3.7` for more information. * Added support for Ambiq Apollo3 Blue series. * Added support for NXP RW61x. * Added support for Infineon CYW208XX. * Added support for Renesas SmartBond DA1469x. * Removed unmaintained B91 driver. * Added support for NXP IW612 on boards mimxrt1170_evkb and mimxrt1040_evk. It can be enabled by :kconfig:option:`CONFIG_BT_NXP_NW612`. Boards & SoC Support ******************** * Added support for these SoC series: * Added support for Ambiq Apollo3 Blue and Apollo3 Blue Plus SoC series. * Added support for Synopsys ARC-V RMX1xx simulation platform. * Added support for STM32H7R/S SoC series. * Added support for NXP mke15z7, mke17z7, mke17z9, MCXNx4x, RW61x * Added support for Analog Devices MAX32 SoC series. * Added support for Infineon Technologies AIROC \|trade\| CYW20829 Bluetooth LE SoC series. * Added support for MediaTek MT8195 Audio DSPs * Added support for Nuvoton Numaker M2L31X SoC series. * Added support for the Microchip PolarFire ICICLE Kit SMP variant. * Added support for Renesas RA8 series SoC. * Made these changes in other SoC series: * Intel ACE Audio DSP: Use dedicated registers to report boot status instead of arbitrary memory. * ITE: Rename the Kconfig symbol for all ITE SoC variants. * STM32: Enabled ART Accelerator, I-cache, D-cache and prefetch on compatible series. * STM32H5: Added support for Stop mode and :kconfig:option:`CONFIG_PM`. * STM32WL: Decreased Sub-GHz SPI frequency from 12 to 8MHz. * STM32C0: Added support for :kconfig:option:`CONFIG_POWEROFF`. * STM32U5: Added support for Stop3 mode. * Synopsys: * nsim: split nsim platform for arc_classic (ARCv2 and ARCv3 ISA based) and arc_v (RISC-V ISA based) * nsim/nsim_hs5x/smp: align sys clock frequency with other SMP nSIM configs * NXP IMX8M: added resource domain controller support * NXP s32k146: set RTC clock source to internal oscillator * GD32F4XX: Fixed an incorrect uart4 irq number. * Nordic nRF54L: Added support for the FLPR (fast lightweight processor) RISC-V CPU. * Espressif: Removed idf-bootloader dependency from all ESP32 SoC variants. * Espressif: Added Simple boot support for ESP32 SoC variants, which allows loading application using a single binary image without a 2nd stage bootloader. * Espressif: Re-worked and optimized all SoCs memory map. * LiteX: * Added support for :c:func:`sys_arch_reboot()`. * :kconfig:option:`CONFIG_RISCV_ISA_EXT_A` is no longer erroneously y-selected. * rp2040: The proprietary UART driver has been discontinued and replaced with PL011. * Renesas RZ/T2M: Added default values for System Clock Control register. * Added support for these boards: * Added support for :ref:`Ambiq Apollo3 Blue board <apollo3_evb>`: ``apollo3_evb``. * Added support for :ref:`Ambiq Apollo3 Blue Plus board <apollo3p_evb>`: ``apollo3p_evb``. * Added support for :ref:`Raspberry Pi 5 board <rpi_5>`: ``rpi_5``. * Added support for :ref:`Seeed Studio XIAO RP2040 board <xiao_rp2040>`: ``xiao_rp2040``. * Added support for :ref:`Mikroe RA4M1 Clicker board <mikroe_clicker_ra4m1>`: ``mikroe_clicker_ra4m1``. * Added support for :ref:`Arduino UNO R4 WiFi board <arduino_uno_r4>`: ``arduino_uno_r4_wifi``. * Added support for :ref:`Renesas EK-RA8M1 board <ek_ra8m1>`: ``ek_ra8m1``. * Added support for :ref:`ST Nucleo H533RE <nucleo_h533re_board>`: ``nucleo_h533re``. * Added support for :ref:`ST STM32C0116-DK Discovery Kit <stm32c0116_dk_board>`: ``stm32c0116_dk``. * Added support for :ref:`ST STM32H745I Discovery <stm32h745i_disco_board>`: ``stm32h745i_disco``. * Added support for :ref:`ST STM32H7S78-DK Discovery <stm32h7s78_dk_board>`: ``stm32h7s78_dk``. * Added support for :ref:`ST STM32L152CDISCOVERY board <stm32l1_disco_board>`: ``stm32l152c_disco``. * Added support for :ref:`ST STEVAL STWINBX1 Development kit <steval_stwinbx1_board>`: ``steval_stwinbx1``. * Added support for NXP boards: ``frdm_mcxn947``, ``ke17z512``, ``rd_rw612_bga``, ``frdm_rw612``, ``frdm_ke15z``, ``frdm_ke17z`` * Added support for :ref:`Synopsys ARC-V RMX1xx nSIM-based simulation platform <nsim_arc_v>`: ``nsim_arc_v/rmx100``. * Added support for :ref:`Analog Devices MAX32690EVKIT <max32690_evkit>`: ``max32690evkit``. * Added support for :ref:`Analog Devices MAX32680EVKIT <max32680_evkit>`: ``max32680evkit``. * Added support for :ref:`Analog Devices MAX32672EVKIT <max32672_evkit>`: ``max32672evkit``. * Added support for :ref:`Analog Devices MAX32672FTHR <max32672_fthr>`: ``max32672fthr``. * Added support for :ref:`Analog Devices MAX32670EVKIT <max32670_evkit>`: ``max32670evkit``. * Added support for :ref:`Analog Devices MAX32655EVKIT <max32655_evkit>`: ``max32655evkit``. * Added support for :ref:`Analog Devices MAX32655FTHR <max32655_fthr>`: ``max32655fthr``. * Added support for :ref:`Analog Devices AD-APARD32690-SL <ad_apard32690_sl>`: ``ad_apard32690_sl``. * Added support for :ref:`Infineon Technologies CYW920829M2EVK-02 <cyw920829m2evk_02>`: ``cyw920829m2evk_02``. * Added support for :ref:`Nuvoton Numaker M2L31KI board <nuvoton_m2l31ki>`: ``numaker_m2l31ki``. * Added support for :ref:`Espressif ESP32-S2 DevKit-C <esp32s2_devkitc>`: ``esp32s2_devkitc``. * Added support for :ref:`Espressif ESP32-S3 DevKit-C <esp32s3_devkitc>`: ``esp32s3_devkitc``. * Added support for :ref:`Espressif ESP32-C6 DevKit-C <esp32c6_devkitc>`: ``esp32c6_devkitc``. * Added support for :ref:`Waveshare ESP32-S3-Touch-LCD-1.28 <esp32s3_touch_lcd_1_28>`: ``esp32s3_touch_lcd_1_28``. * Added support for :ref:`M5Stack ATOM Lite <m5stack_atom_lite>`: ``m5stack_atom_lite``. * Added support for :ref:`CTHINGS.CO Connectivity Card nRF52840 <ctcc_nrf52840>`: ``ctcc_nrf52840``. * Made these board changes: * On :ref:`ST STM32H7B3I Discovery Kit <stm32h7b3i_dk_board>`: ``stm32h7b3i_dk_board``, enabled full cache management, Chrom-ART, double frame buffer and full refresh for optimal LVGL performance. * On ST STM32 boards, stm32cubeprogrammer runner can now be used to program external flash using ``--extload`` option. * Add HEX file support for Linkserver to all NXP boards * Updated the Linkserver west runner to reflect changes to the CLI of LinkServer v1.5.xx * Add LinkServer support to NXP ``mimxrt1010_evk``, ``mimxrt1160_evk``, ``frdm_rw612``, ``rd_rw612_bga``, ``frdm_mcxn947`` * Introduced the simulated :ref:`nrf54l15bsim<nrf54l15bsim>` target. * The nrf5x bsim targets now support BT LE Coded PHY. * LLVM fuzzing support has been refactored while adding support for it in native_sim. * nRF54H20 PDK (pre-release) converted to :ref:`nrf54h20dk_nrf54h20` * PPR core target in :ref:`nrf54h20dk_nrf54h20` runs from RAM by default. A new ``xip`` variant has been introduced which runs from MRAM (XIP). * Refactored :ref:`beagleconnect_freedom` external antenna switch handling. * Added Arduino dts node labels for the nRF5340 Audio DK. * Changed the default revision of the nRF54L15 PDK from 0.2.1 to 0.3.0. * In boards based on the nRF5340 SoC, replaced direct accesses to the register that controls the network core Force-OFF signal with a module that uses an on-off manager to keep track of the network core use and exposes its API in ``<nrf53_cpunet_mgmt.h>``. * Laird Connectivity boards are rebranded to Ezurio. * Added support for the following shields: * :ref:`adafruit_2_8_tft_touch_v2` (``adafruit_2_8_tft_touch_v2``) * :ref:`adafruit_neopixel_grid_bff` (``adafruit_neopixel_grid_bff``) * :ref:`arduino_uno_click` (``arduino_uno_click``) * :ref:`dvp_fpc24_mt9m114` (``dvp_fpc24_mt9m114``) * :ref:`lcd_par_s035` (``lcd_par_s035``) * :ref:`mikroe_weather_click` (``mikroe_weather_click``) * :ref:`nxp_btb44_ov5640` (``nxp_btb44_ov5640``) * :ref:`reyax_lora` (``reyax_lora``) * :ref:`rk043fn02h_ct` (``rk043fn02h_ct``) * :ref:`rk043fn66hs_ctg` (``rk043fn66hs_ctg``) * :ref:`rpi_pico_uno_flexypin` (``rpi_pico_uno_flexypin``) * :ref:`seeed_xiao_expansion_board` (``seeed_xiao_expansion_board``) * :ref:`seeed_xiao_round_display` (``seeed_xiao_round_display``) * :ref:`sparkfun_carrier_asset_tracker` (``sparkfun_carrier_asset_tracker``) * :ref:`st_b_lcd40_dsi1_mb1166` (``st_b_lcd40_dsi1_mb1166``) * :ref:`waveshare_epaper` (``waveshare_epaper``) * :ref:`x_nucleo_bnrg2a1` (``x_nucleo_bnrg2a1``) Build system and Infrastructure ******************************* * CI-enabled blackbox tests were added to verify the correctness of most Twister flags. * A ``socs`` folder for applications has been introduced that allows for Kconfig fragments and devicetree overlays that should apply to any board target using a particular SoC and board qualifier (:github:`70418`). Support has also been added to sysbuild (:github:`71320`). * :ref:`Board/SoC flashing configuration<flashing-soc-board-config>` settings have been added (:github:`69748`). * Deprecated the global CSTD cmake property in favor of the :kconfig:option:`CONFIG_STD_C` choice to select the C Standard version. Additionally, subsystems can select a minimum required C Standard version, with, for example, :kconfig:option:`CONFIG_REQUIRES_STD_C11`. * Fixed issue with passing UTF-8 configs to applications using sysbuild (:github:`74152`). * Fixed issue whereby domain file in sysbuild projects would be loaded and used with outdated information if sysbuild configuration was changed, and ``west flash`` was ran directly after (:github:`73864`). * Fixed issue with Zephyr modules not being listed in sysbuild if they did not have a Kconfig file set (:github:`72070`). * Added sysbuild ``SB_CONFIG_COMPILER_WARNINGS_AS_ERRORS`` Kconfig option to turn on "warning as error" toolchain flags for all images, if set (:github:`70217`). * Fixed issue whereby files used in a project (e.g. devicetree overlays or Kconfig fragments) were not correctly watched and CMake would not reconfigure if they were changed (:github:`74655`). * Added flash support for Intel Hex files for the LinkServer runner. * Added sysbuild ``sysbuild/CMakeLists.txt`` entry point and added support for ``APPLICATION_CONFIG_DIR`` which allows for adjusting how sysbuild functions (:github:`72923`). * Fixed issue with armfvp find path if it contained a colon-separated list (:github:`74868`). * Fixed issue with version.cmake field sizes not being enforced (:github:`74357`). * Fixed issue with sysbuild not clearing ``EXTRA_CONF_FILE`` before processing images which prevented this option being passed on to the image (:github:`74082`). * Added sysbuild root support which works similarly to the existing root module, adjusting paths relative to ``APP_DIR`` (:github:`73390`). * Added warning/error message for blobs that are missing (:github:`73051`). * Fixed issue with correct python executable detection on some systems (:github:`72232`). * Added support for enabling LTO for whole application (:github:`69519`). * Fixed ``FILE_SUFFIX`` issues relating to double application of suffixes, non-application in sysbuild and variable name clashes in CMake functions (:github:`70124`, :github:`71280`). * Added support for new aggressive size optimisation flag (for GCC and Clang) using :kconfig:option:`CONFIG_SIZE_OPTIMIZATIONS_AGGRESSIVE` (:github:`70511`). * Fixed issue with printing out ``BUILD_VERSION`` if it was empty (:github:`70970`). * Fixed sysbuild issue of ``sysbuild_cache_set()`` cmake function wrongly detecting partial matches for de-duplication (:github:`71381`). * Fixed issue with detecting wrong ``VERSION`` file (:github:`71385`). * Added support for disabling output disassembly having the source code in using :kconfig:option:`CONFIG_OUTPUT_DISASSEMBLY_WITH_SOURCE` (:github:`71535`). * Twister now supports ``--flash-before`` parameter that allows flashing DUT before opening serial port (:github:`47037`). Drivers and Sensors ******************* * ADC * Added ``ADC_DT_SPEC_BY_NAME()`` macros to get ADC IO-channel information from DT by name. Added support for voltage biasing: * Added a :kconfig:option:`CONFIG_ADC_CONFIGURABLE_VBIAS_PIN` selected by drivers that support voltage biasing. * Added a ``zephyr,vbias-pins`` property to the adc-controller base binding to describe voltage bias pins. * Implemented for the TI ADC114s08 ADC driver. * Sample changes * Renamed existing ADC sample to adc_dt. * Added a new sample called adc_sequence that shows more of the runtime :c:struct:`adc_sequence` features. * New ADC Drivers * Added driver for the ENE KB1200. * Added driver for the NXP GAU ADC. * ADI AD559x changes * Added support for ADI's ad5593. * Added I2C bus support for ADI ad559x. * Added configuration of internal reference voltage value to ad559x to support calls of :c:func:`adc_raw_to_millivolts()`. * Fixed issue with driver initialization causing improper operation in the ad559x driver regarding the availability of :kconfig:option:`CONFIG_THREAD_NAME`. * Improved the ADC read efficiency and validation in ad559x driver. * ESP32 changes * Updated ESP32 ADC driver to work with version 5.1 of hal_espressif. * Added support for DMA mode operation for ESP32S3 and ESP32C3. * nRF changes * Added support for nRF54L15 and nRF54H20 in the nrfx_saadc driver. * Improved the nRF SAADC driver by disabling burst mode on unused channels, avoiding freezes. * Fixed issue which allowed negative ADC readings in single-ended mode using the ``adc_nrfx_saadc.c`` device driver. Note that this fix prevents the nRF54H and nRF54L series from performing 8-bit resolution single-ended readings due to hardware limitations. * NXP LPADC changes * Enabled acquisition time feature in the NXP LPADC driver. * Added support for regulator output as reference to NXP LPADC. * Changed phandle type DT property ``nxp,reference-supply`` to phandle-array type DT property ``nxp,references`` in ``nxp,lpc-lpadc`` binding. The NXP LPADC driver now supports passing the reference voltage value by using ``nxp,references``. * Smartbond changes * Added support for power management to the Smartbond SDADC and GPADC drivers. * Fixed support for :kconfig:option:`CONFIG_PM_DEVICE_RUNTIME` in the Smartbond ADC driver. * STM32 changes * Fixed various issues with DMA support in the STM32 ADC driver. * Added support for STM32H7R/S series. * Other driver changes * Added support for Nuvoton m2l31x in the numaker ADC driver. * Fixed issue with configuration register access in the ads1119 driver. * Fixed uninitialized value in kb1200 driver found in static analysis. * Fixed issue with :c:func:`adc_raw_to_millivolts` returning half the actual voltage with the tla2021 driver by correcting the reference voltage value. * Added support for Nuvoton Numaker M2L31X series. * Battery * Added ``re-charge-voltage-microvolt`` property to the ``battery`` binding. This allows to set limit to automatically start charging again. * Battery backed up RAM * Added support for STM32G0 and STM32H5 series. * CAN * 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 :c:func:`can_get_bitrate_min` and :c:func:`can_get_bitrate_max` for retrieving the minimum and maximum supported bitrate for a given CAN controller/CAN transceiver combination, reflecting that retrieving the bitrate limits can no longer fail. Deprecated the existing :c:func:`can_get_max_bitrate` API function. * Updated the CAN timing functions to take the minimum supported bitrate into consideration when validating the bitrate. * Made the ``sample-point`` and ``sample-point-data`` devicetree properties optional. * Renamed the ``bus_speed`` and ``bus_speed_data`` fields of :c:struct:`can_driver_config` to ``bitrate`` and ``bitrate_data``. * Added driver for :dtcompatible:`nordic,nrf-can`. * Added driver support for Numaker M2L31X to the :dtcompatible:`nuvoton,numaker-canfd` driver. * Added host communication test suite. * Charger * Added ``chgin-to-sys-current-limit-microamp`` property to ``maxim,max20335-charger``. * Added ``system-voltage-min-threshold-microvolt`` property to ``maxim,max20335-charger``. * Added ``re-charge-threshold-microvolt`` property to ``maxim,max20335-charger``. * Added ``thermistor-monitoring-mode`` property to ``maxim,max20335-charger``. * Clock control * Added support for Microcontroller Clock Output (MCO) on STM32H5 series. * Added support for MSI clock on STM32WL series. * Added driver for Analog Devices MAX32 SoC series. * Added support for Nuvoton Numaker M2L31X series. * Refactored ESP32 clock control driver to support ESP32-C6. * In LiteX (:file:`drivers/clock_control/clock_control_litex.c`) added return code checking for :c:func:`litex_clk_get_duty_cycle()` and :c:func:`litex_clk_get_clkout_divider`. * Counter * Added support for Ambiq Apollo3 series. * Added support for STM32H7R/S series. * Added driver for LPTMR to NXP MCXN947 * Added the ``resolution`` property in ``nxp,lptmr`` binding to represent the maximum width in bits the LPTMR peripheral uses for its counter. * DAC * Added support for NXP RW SOC series DAC (:dtcompatible:`nxp,gau-dac`). * Added support for Analog Devices AD5691 / AD5692 / AD5693 DACs (:dtcompatible:`adi,ad5691`, :dtcompatible:`adi,ad5692` and :dtcompatible:`adi,ad5693`). * Added support for Texas Instruments DACx0501 series DACs (:dtcompatible:`ti,dacx0501`). * Disk * Support for eMMC devices was added to the STM32 SD driver. This can be enabled with :kconfig:option:`CONFIG_SDMMC_STM32_EMMC`. * Added a loopback disk driver, to expose a disk device backed by a file. A file can be registered with the loopback disk driver using :c:func:`loopback_disk_access_register` * Added support for :c:macro:`DISK_IOCTL_CTRL_INIT` and :c:macro:`DISK_IOCTL_CTRL_DEINIT` macros, which allow for initializing and de-initializing a disk at runtime. This allows hotpluggable disk devices (like SD cards) to be removed and reinserted at runtime. * Added SDMMC support for STM32H5 series. * Display * All in tree displays capable of supporting the :ref:`mipi_dbi_api` have been converted to use it. GC9X01X, UC81XX, SSD16XX, ST7789V, ST7735R based displays have been converted to this API. Boards using these displays will need their devicetree updated, see the display section of :ref:`migration_3.7` for examples of this process. * Added driver for ST7796S display controller (:dtcompatible:`sitronix,st7796s`) * Added support for :c:func:`display_read` API to ILI9XXX display driver, which can be enabled with :kconfig:option:`CONFIG_ILI9XXX_READ` * Added support for :c:func:`display_set_orientation` API to SSD16XXX display driver * Added driver for NT35510 MIPI-DSI display controller (:dtcompatible:`frida,nt35510`) * Added driver to abstract LED strip devices as displays (:dtcompatible:`led-strip-matrix`) * Added support for :c:func:`display_set_pixel_format` API to NXP eLCDIF driver. ARGB8888, RGB888, and BGR565 formats are supported. * Added support for inverting color at runtime to the SSD1306 driver, via the :c:func:`display_set_pixel_format` API. * Inversion mode can now be disabled in the ST7789V driver (:dtcompatible:`sitronix,st7789v`) using the ``inversion-off`` property. * Added support for NXP MCXNx4x * DMA * Error callback configuration renamed to better signal enable/disable status * Add support to NXP MCXN947 * DMIC * Added support for NXP ``rd_rw612_bga`` * Entropy * Added support for STM32H7R/S series. * EEPROM * Added property for specifying ``address-width`` to :dtcompatible:`zephyr,i2c-target-eeprom`. * eSPI * Renamed eSPI virtual wire direction macros, enum values and Kconfig to match the new terminology in eSPI 1.5 specification. * Ethernet * Introduced :kconfig:option:`CONFIG_ETH_DRIVER_RAW_MODE`. This option allows building ethernet drivers without the zephyr L2 ethernet layer. * Removed the ethernet-fixed-link DT binding. * Removed VLAN handling from ethernet drivers since it is now handled by the generic ethernet L2 code. * Implemented/reworked HW MAC Address filtering in the eth_mcux, eth_nxp_enet, and eth_nxp_s32_gmac, eth_stm32, and eth_nxp_s32_netc drivers. * New Drivers * Added new eth_nxp_enet_qos driver for the ethernet controller present on NXP MCXN SOCs. * Added support for adin1100 phy. * Added support for the Realtek RTL8211F phy. * NXP ENET driver changes * eth_nxp_enet driver is no longer experimental. * Deprecated eth_mcux driver. * All boards and SOCs with :dtcompatible:`nxp,kinetis-ethernet` compatible nodes reworked to use the new :dtcompatible:`nxp,enet` binding. * Added support for network device power management with nxp_enet driver on Kinetis platforms. * Converted eth_nxp_enet driver to use a dedicated workqueue for RX managed by the kernel rather than a manual infinite loop. * Disabled hardware checksum acceleration when IPV6 is enabled with eth_nxp_enet, since the hardware does not support accelerating ICMPv6 checksums. * Added support for :dtcompatible:`nxp,enet1g`. * Added support to use a fused MAC address for nxp_enet MAC on some platforms. * Fixed issue with LAA bit not being set and a confusing description of the nxp,unique-mac property used with the nxp_enet driver. * Fixed cache maintain being enabled when using a noncache DMA buffer in nxp_enet driver. * Added MMIO mappings to nxp_enet driver. * Clarified DSA supported with eth_nxp_enet. * NXP S32 ethernet changes * The eth_nxp_s32_gmac driver now implies :kconfig:option:`CONFIG_MDIO`. * eth_nxp_s32_netc driver updated to use new MBOX API. * Adin2111 driver changes * Corrected the bitfield position of IAMSK1 TX_READY_MASK in adin2111 driver. * Changed adin2111 driver to always append crc32 to the end of the frame. * Adjusted eth_adin2111 driver to have the appropriate multicaster filter mask. * Fixed the "generic SPI without crc8" mode of adin2111 driver. * Added Open Alliance SPI protocol support to the adin2111 driver. * Added custom driver extension APIs for adin2111 driver. * Enabled support for promiscuous mode in the adin2111 driver. * Moved OA buffers out of device data of the adin2111 driver to save ~32KB of space when using the generic SPI protocol. * Fixed a build warning in eth_adin2111 driver on 64-bit platforms. * Various small changes to adin2111 driver. * STM32 ethernet driver changes * Added support for PTP on compatible STM32 series (STM32F7, STM32H5 and STM32H7). * Changed eth_stm32 to use phy APIs to access the phy to avoid collisions when multitasking. * Removed legacy STM32Cube HAL API support for STM32 F4, F7, and H7 series. * Added support for RX/TX timestamping to eth_stm32_hal driver. * ESP32 ethernet driver changes * Added support to esp32 ethernet driver to set the MAC address during runtime. * Updated esp32 ethernet driver to work with version 5.1 of hal_espressif. * Fixed build of esp32 ethernet driver when :kconfig:option:`CONFIG_NET_STATISTICS` is enabled. * Fixed ESP32 ethernet driver not clocking external PHY correctly over GPIO. * Other ethernet driver changes * Added link status detection to the w5500 ethernet driver, configurable via Kconfig. * Added ability to set MAC address at runtime with eth_liteeth driver. * Fixed issue in the eth_stellaris driver where it was previously not taken into account that the number of interrupts received by the driver may be less than the number of data packets received by the ethernet controller. * Added a devicetree property for the enc28j60 to set the RX filter. * Fixed ESTAT TXABRT bit not being cleared on error in the enc28j60 driver. * Added conditions to enable ptp_clock driver implementation for the native_posix ethernet driver when PTP subsystem is enabled. * Fixed DSA driver for KSZ8xxx to correctly initialize LAN devices. * Fixed the wrong register address being used for tail tag enable in ksz8863. * Phy driver changes * Fixed various control issues with the KSZ8081 phy driver regarding resets, autonegotiation, link detection, and missing/spamming logging messages. * Changed property names of the reset and interrupt gpios in the KSZ8081 DT binding. * Fixed bus fault in phy_mii driver when using fixed-link mode. * Flash * Added support for Ambiq Apollo3 series. * Added support for multiple instances of the SPI NOR driver (spi_nor.c). * Added preliminary support for non-erase devices with introduction of device capabilities to c:struct:`flash_parameters` and the utility function c:func:`flash_params_get_erase_cap` that allows to obtain the erase type provided by a device; added c:macro:`FLASH_ERASE_C_EXPLICIT`, which is currently the only supported erase type and is set by all flash devices. * Added the c:func:`flash_flatten` function that can be used on devices, with or without erase requirement, when erase has been used not for preparing a device for a random data write, but rather to remove/scramble data from that device. * Added the c:func:`flash_fill` utility function which allows to write a single value across a provided range in a selected device. * Added support for RRAM on nrf54l15 devices. * Added support of non busy wait polling in STM32 OSPI driver. * Added support for STM32 XSPI external NOR flash driver (:dtcompatible:`st,stm32-xspi-nor`). * Added support for XIP on external NOR flash in STM32 OSPI, QSPI and XSPI driver. * STM32 OSPI driver: clk, dqs, ncs ports can now be configured by device tree configurable (see :dtcompatible:`st,stm32-ospi`). * Added FlexSPI support to NXP MCXN947 * Added support for Nuvoton Numaker M2L31X series. * Fuel Gauge * max17048: Corrected voltage units from mV to uV. * GNSS * Added GNSS device driver API test suite. * Added support for the u-blox UBX protocol. * Added device driver for the u-blox M10 GNSS modem (:dtcompatible:`u-blox,m10`). * Added device driver for the Luatos Air530z GNSS modem (:dtcompatible:`luatos,air530z`). * GPIO * Added support for Ambiq Apollo3 series. * Added Broadcom Set-top box(brcmstb) SoC GPIO driver. * Added c:macro:`STM32_GPIO_WKUP` flag which allows to configure specific pins as wakeup source from Power Off state on STM32 L4, U5, WB, & WL SoC series. * Added driver for Analog Devices MAX32 SoC series. * Added support for Nuvoton Numaker M2L31X series. * Added interrupt support to the Renesas RZ/T2M GPIO driver (:dtcompatible:`renesas,rzt2m-gpio`). * Hardware info * Added device EUI64 ID support and implementation for STM32WB, STM32WBA and STM32WL series. * I2C * Added support for Ambiq Apollo3 series. * In STM32 V2 driver, added support for a new :kconfig:option:`CONFIG_I2C_STM32_V2_TIMING` which automatically computes bus timings which should be used to configure the hardware block depending on the clock configuration in use. To avoid embedding this heavy algorithm in a production application, a dedicated sample :zephyr:code-sample:`stm32_i2c_v2_timings` is provided to get the output of the algorithm. Once bus timings configuration is available, :kconfig:option:`CONFIG_I2C_STM32_V2_TIMING` could be disabled, bus timings configured using device tree. * Added support for STM32H5 series. * Added support to NXP MCXN947 * Added driver for Analog Devices MAX32 SoC series. * Added support for Nuvoton Numaker M2L31X series. * LiteX I2C driver (:file:`drivers/i2c/i2c_litex.c`): * Added support for bitrate setting from the devicetree. * Added :c:func:`i2c_litex_recover_bus()` and :c:func:`i2c_litex_get_config()` API implementations. * I2S * Added support for STM32H5 series. * Extended the MCUX Flexcomm driver to support additional channels and formats. * Added support for Nordic nRF54L Series. * Fixed divider calculations in the nRF I2S driver. * I3C * Added shell support for querying bus and CCC commands. * Added driver to support the I3C controller on NPCX. * Improvements and bug fixes on :dtcompatible:`nxp,mcux-i3c`, including handling the bus being busy more gracefully instead of simply returning errors. * Input * New drivers: :dtcompatible:`adc-keys`, :dtcompatible:`chipsemi,chsc6x`, :dtcompatible:`cirque,pinnacle`, :dtcompatible:`futaba,sbus`, :dtcompatible:`pixart,pat912x`, :dtcompatible:`pixart,paw32xx`, :dtcompatible:`pixart,pmw3610` and :dtcompatible:`sitronix,cf1133`. * Migrated :dtcompatible:`holtek,ht16k33` and :dtcompatible:`microchip,xec-kbd` from kscan to input subsystem. * LED * Added device completion to LED shell commands and made the ``get_info`` command display colors as strings. * Added driver for Lumissil Microsystems (a division of ISSI) IS31FL3194 controller (:dtcompatible:`issi,is31fl3194`). * LED Strip * The ``chain-length`` and ``color-mapping`` properties have been added to all LED strip bindings. * The length of a strip is now checked before updating it, an error is returned if the provided data is too long. * A length function has been added which returns the length of the LED strip (:c:func:`led_strip_length`). * The update channels function is now optional and can be left unimplemented. * The ``in-gpios`` and ``output-pin`` properties of the respective :dtcompatible:`worldsemi,ws2812-gpio` and :dtcompatible:`worldsemi,ws2812-rpi_pico-pio` devicetree bindings have been renamed to ``gpios``. * Removed ``CONFIG_WS2812_STRIP`` and ``CONFIG_WS2812_STRIP_DRIVER`` Kconfig options. They became useless after refactoring. * Added driver for Texas Instruments TLC59731 RGB controller. * LoRa * Added driver for Reyax LoRa module * Mailbox * Added support for HSEM based STM32 driver. * MDIO * Made the ``bus_enable`` and ``bus_disable`` functions optional for drivers to implement, and removed empty implementation from many drivers. * Added NXP ENET QOS MDIO controller driver. * Fixed but with NXP ENET MDIO driver blocking the system workqueue. * :kconfig:option:`CONFIG_MDIO_NXP_ENET_TIMEOUT` units change to microseconds. * Added support for STM32 MDIO controller driver. * MFD * New driver :dtcompatible:`nxp,lp-flexcomm`. * New driver :dtcompatible:`rohm,bd8lb600fs`. * New driver :dtcompatible:`maxim,max31790`. * New driver :dtcompatible:`infineon,tle9104` * New driver :dtcompatible:`adi,ad559x` * Added option to disable N_VBUSEN for :dtcompatible:`x-powers,axp192`. * Added GPIO input edge events for :dtcompatible:`nordic,npm1300`. * Added long press reset configuration for :dtcompatible:`nordic,npm1300`. * Fixed initialisation of hysteretic mode for :dtcompatible:`nordic,npm6001`. * Modem * Removed deprecated ``GSM_PPP`` driver along with its dts compatible ``zephyr,gsm-ppp``. * Removed deprecated ``UART_MUX`` and ``GSM_MUX`` previously used by ``GSM_PPP``. * Removed support for dts compatible ``zephyr,gsm-ppp`` from ``MODEM_CELLULAR`` driver. * Removed integration with ``UART_MUX`` from ``MODEM_IFACE_UART_INTERRUPT`` module. * Removed integration with ``UART_MUX`` from ``MODEM_SHELL`` module. * Implemented modem pipelinks in ``MODEM_CELLULAR`` driver for additional DLCI channels available by the different modems. This includes generic AT mode DLCI channels, named ``user_pipe_<index>`` and DLCI channels reserved for GNSS tunneling named ``gnss_pipe``. * Added new set of shell commands for sending AT commands directly to a modem using the newly implemented modem pipelinks. The implementation of the new shell commands is both functional and together with the ``MODEM_CELLULAR`` driver will provide an example of how to implement and use the modem pipelink module. * PCIE * ``pcie_bdf_lookup`` and ``pcie_probe`` have been removed since they have been deprecated since v3.3.0. * MIPI-DBI * Added release API * Added support for mode selection via the device tree * MSPI * Add the new experimental :ref:`MSPI(Multi-bit SPI) <mspi_api>` API, enabling support for advanced SPI controllers and peripherals that typically require command, address and data phases as well as variable latency for a transfer. The API now supports from single wire SDR up to hex wires DDR communication in sync/async ways. * Added MSPI bus emulator under bus emulators to showcase the implementation of the MSPI API. * Added MSPI flash device emulator to showcase the use of the MSPI API and interfacing with MSPI bus controllers. * Added APS6404L QPI pSRAM device driver. * Added ATXP032 OPI NOR flash device driver. * Added Ambiq Apollo3p MSPI controller driver. * Added :zephyr:code-sample:`mspi-async` and :zephyr:code-sample:`mspi-flash` samples to showcase the use of MSPI device drivers. * Added mspi/api and mspi/flash testcase for developers to check their implementations. * Pin control * Added driver for Renesas RA8 series * Added driver for Infineon PSoC6 (legacy) * Added driver for Analog Devices MAX32 SoC series. * Added driver for Ambiq Apollo3 * Added driver for ENE KB1200 * Added driver for NXP RW * Espressif driver now supports ESP32C6 * STM32 driver now supports remap functionality for STM32C0 * Added support for Nuvoton Numaker M2L31X series. * PWM * Added support for STM32H7R/S series. * Added a Add QTMR PWM driver for NXP imxrt11xx * Made the NXP MCUX PWM driver thread safe * Fix zephyr:code-sample:`pwm-blinky` code sample to demonstrate PWM support for :ref:`beagleconnect_freedom`. * Added driver for ENE KB1200. * Added support for Nordic nRF54H and nRF54L Series SoCs. * Added support for Nuvoton Numaker M2L31X series. * Regulators * New driver :dtcompatible:`cirrus,cp9314`. * Added ``regulator-boot-off`` property to common regulator driver. Updated :dtcompatible:`adi,adp5360-regulator`, :dtcompatible:`nordic,npm1300-regulator`, :dtcompatible:`nordic,npm6001-regulator` and :dtcompatible:`x-powers,axp192-regulator` to use this new property. * Added power management for :dtcompatible:`renesas,smartbond-regulator`. * Added ``is_enabled`` shell command. * Removed use of busy wait for single threaded systems. * Fixed control of DCDC2 output for :dtcompatible:`x-powers,axp192-regulator`. * Fixed current and voltage get functions for :dtcompatible:`renesas,smartbond-regulator`. * Fixed NXP VREF Kconfig leakage. * Fixed display of micro values in shell. * Fixed strcmp usage bug in ``adset`` shell command. * Reset * Added driver for reset controller on Nuvoton NPCX chips. * Added reset controller driver for NXP SYSCON. * Added reset controller driver for NXP RSTCTL. * Added support for Nuvoton Numaker M2L31X series. * RTC * Added Raspberry Pi Pico RTC driver. * Added support for :kconfig:option:`CONFIG_RTC_ALARM` on all STM32 MCU series (except STM32F1). * Added support for Nuvoton Numaker M2L31X series. * RTIO * Move lock-free queues out of RTIO into lib, dropping the ``rtio_`` prefix to SPSC and MPSC queues. * Added tests and fixed bugs related to chained callback requests. * Wrapper around p4wq (rtio workq) created to go from blocking to non-blocking behavior in cases where native asynchronous RTIO functionality is unavailable. * SDHC * Added ESP32 SDHC driver (:dtcompatible:`espressif,esp32-sdhc`). * Added SDHC driver for Renesas MMC controller (:dtcompatible:`renesas,rcar-mmc`). * Sensors * General * Added a channel specifier to the new read/decoder API. * Added a blocking sensor read call :c:func:`sensor_read`. * Decoupled RTIO requests using RTIO workqueues service to turn :c:func:`sensor_submit_callback` into an asynchronous request. * Moved most drivers to vendor subdirectories. * AMS * Added TSL2591 light sensor driver (:dtcompatible:`ams,tsl2591`). * Aosong * Added DHT20 digital-output humidity and temperature sensor driver (:dtcompatible:`aosong,dht20`). * Added :kconfig:option:`CONFIG_DHT_LOCK_IRQS` for the dht11 driver which allows for locking interrupts during sensor reading to prevent issues with reading the sensor. * Bosch * Updated BME280 to the new async API. * Infineon * Added TLE9104 power train switch diagnostics sensor driver (:dtcompatible:`infineon,tle9104-diagnostics`). * Maxim * Added DS18S20 1-Wire temperature sensor driver (:dtcompatible:`maxim,ds18s20`). * Added MAX31790 fan speed and fan fault sensor (:dtcompatible:`maxim,max31790-fan-fault` and :dtcompatible:`maxim,max31790-fan-speed`). * NXP * Added low power comparator driver (:dtcompatible:`nxp,lpcmp`). * Rohm * Added BD8LB600FS diagnostics sensor driver (:dtcompatible:`rohm,bd8lb600fs-diagnostics`). * Silabs * Made various fixes and enhancements to the SI7006 humidity/temperature sensor driver. * ST * QDEC driver now supports encoder mode configuration (see :dtcompatible:`st,stm32-qdec`). * Added support for STM32 Digital Temperature Sensor (:dtcompatible:`st,stm32-digi-temp`). * Added IIS328DQ I2C/SPI accelerometer sensor driver (:dtcompatible:`st,iis328dq`). * TDK * Added support for the MPU6500 3-axis accelerometer and 3-axis gyroscope sensor to the MPU6050 driver. * TI * Added TMP114 driver (:dtcompatible:`ti,tmp114`). * Added INA226 bidirectional current and power monitor driver (:dtcompatible:`ti,ina226`). * Added LM95234 quad remote diode and local temperature sensor driver (:dtcompatible:`national,lm95234`). * Other vendors * Added Angst+Pfister FCX-MLDX5 O2 sensor driver (:dtcompatible:`ap,fcx-mldx5`). * Added ENE KB1200 tachometer sensor driver (:dtcompatible:`ene,kb1200-tach`). * Added Festo VEAA-X-3 series proportional pressure regulator driver (:dtcompatible:`festo,veaa-x-3`). * Added Innovative Sensor Technology TSic xx6 temperature sensor driver (:dtcompatible:`ist,tsic-xx6`). * Added ON Semiconductor NCT75 temperature sensor driver (:dtcompatible:`onnn,nct75`). * Added ScioSense ENS160 digital metal oxide multi-gas sensor driver (:dtcompatible:`sciosense,ens160`). * Made various fixes and enhancements to the GROW_R502A fingerprint sensor driver. * Serial * Added driver to support UART over Bluetooth LE using NUS (Nordic UART Service). This driver enables using Bluetooth as a transport to all the subsystems that are currently supported by UART (e.g: Console, Shell, Logging). * Added :kconfig:option:`CONFIG_NOCACHE_MEMORY` support in async DMA mode in STM32 driver. It is now possible to use UART in DMA mode with :kconfig:option:`CONFIG_DCACHE` enabled on STM32 F7 & H7 SoC series, as long as DMA buffers are placed in an uncached memory section. * Added support for STM32H7R/S series. * Added support for HSCIF (High Speed Serial Communication Interface with FIFO) in the UART driver for Renesas RCar platforms. * Added driver for ENE KB1200 UART. * Added driver for UART on Analog Devices MAX32 series microcontrollers. * Added driver for UART on Renesas RA8 devices. * ``uart_emul`` (:dtcompatible:`zephyr,uart-emul`): * Added support for asynchronous API for the emulated UART driver. * ``uart_esp32`` (:dtcompatible:`espressif,esp32-uart`): * Added support to invert TX and RX pin signals. * Added support for ESP32C6 SoC. * ``uart_native_tty`` (:dtcompatible:`zephyr,native-tty-uart`): * Added support to emulate interrupt driven UART. * ``uart_mcux_lpuart`` (:dtcompatible:`nxp,kinetis-lpuart`): * Added support for single wire half-duplex communication. * Added support to invert TX and RX pin signals. * ``uart_npcx`` (:dtcompatible:`nuvoton,npcx-uart`): * Added support for asynchronous API. * Added support for baud rate of 3MHz. * ``uart_nrfx_uarte`` (:dtcompatible:`nordic,nrf-uarte`): * Added support to put TX and RX pins into low power mode when UART is not active. * ``uart_nrfx_uarte2`` (:dtcompatible:`nordic,nrf-uarte`): * Prevents UART from transmitting when device is suspended. * Fixed some events not being triggered. * ``uart_pl011`` (:dtcompatible:`arm,pl011`): * Added support for runtime configuration. * Added support for reset device. * Added support to use clock control to determine frequency. * Added support for hardware flow control. * Added support for UART on Ambiq Apollo3 SoC. * ``uart_smartbond`` (:dtcompatible:`renesas,smartbond-uart`): * Added support for power management. * Added support to wake up via DTR and RX lines. * ``uart_stm32`` (:dtcompatible:`st,stm32-uart`): * Added support to identify if DMA buffers are in data cache or non-cacheable memory. * Added support for Nuvoton Numaker M2L31X series. * SPI * Added support to NXP MCXN947 * Added support for Ambiq Apollo3 series general IOM based SPI. * Added support for Ambiq Apollo3 BLEIF based SPI, which is specific for internal HCI. * Added support for :kconfig:option:`CONFIG_PM` and :kconfig:option:`CONFIG_PM_DEVICE_RUNTIME` on STM32 SPI driver. * Added support for :kconfig:option:`CONFIG_NOCACHE_MEMORY` in DMA SPI mode for STM32F7x SoC series. * Added support for STM32H7R/S series. * Added driver for Analog Devices MAX32 SoC series. * Fixed an incorrect register assignment in gd32 spi. * USB * Added UDC shim driver for NXP EHCI and IP3511 USB controller. * Various fixes and improvements in IT82xx2, DWC2, STM32, RP2040, Smartbond USB controller drivers. * Video * Added support for STM32 Digital camera interface (DCMI) driver (:dtcompatible:`st,stm32-dcmi`). * Enabled NXP USB Device controllers * Added support for the ov7670 camera * Added support for the ov5640 camera * Added CSI-2 MIPI driver for NXP MCUX * Added support for DVP FPC 24-pins mt9m114 camera module shield * Watchdog * Added :kconfig:option:`CONFIG_WDT_NPCX_WARNING_LEADING_TIME_MS` to set the leading warning time in milliseconds. Removed no longer used :kconfig:option:`CONFIG_WDT_NPCX_DELAY_CYCLES`. * Added support for Ambiq Apollo3 series. * Added support for STM32H7R/S series. * Added support for Nuvoton Numaker M2L31X series. * Added watchdog for external 32kHz crystal in ESP32 SoC variants. * Wi-Fi * Fixed message parsing for esp-at. * Fixed esp-at connect failures. * Implement :c:func:`bind` and :c:func:`recvfrom` for UDP sockets for esp-at. * Added option for setting maximum data size for eswifi. * Fixed ESP32 Wi-Fi driver memory leak. Networking ********** * ARP: * Added support for gratuitous ARP transmission. * Fixed a possible deadlock between TX and RX threads within ARP module. * Fixed a possible ARP entry leak. * Improved ARP debug logs. * CoAP: * Fixed CoAP observe age overflows. * Increased upper limit for CoAP retransmissions (:kconfig:option:`CONFIG_COAP_MAX_RETRANSMIT`). * Fixed CoAP observations in CoAP client library. * Added new CoAP client :c:func:`coap_client_cancel_requests` API which allows to cancel active observations. * Fixed CoAP ID generation for responses in CoAP Server sample. * Connection manager: * Added support for new net_mgmt events, which allow to track IPv4 and IPv6 connectivity independently: * :c:macro:`NET_EVENT_L4_IPV4_CONNECTED` * :c:macro:`NET_EVENT_L4_IPV4_DISCONNECTED` * :c:macro:`NET_EVENT_L4_IPV6_CONNECTED` * :c:macro:`NET_EVENT_L4_IPV6_DISCONNECTED` * DHCPv4: * Added support for encapsulated vendor specific options. By enabling :kconfig:option:`CONFIG_NET_DHCPV4_OPTION_CALLBACKS_VENDOR_SPECIFIC` callbacks can be registered with :c:func:`net_dhcpv4_add_option_vendor_callback` to handle these options after being initialised with :c:func:`net_dhcpv4_init_option_vendor_callback`. * Added support for the "Vendor class identifier" option. Use the :kconfig:option:`CONFIG_NET_DHCPV4_VENDOR_CLASS_IDENTIFIER` to enable it and :kconfig:option:`CONFIG_NET_DHCPV4_VENDOR_CLASS_IDENTIFIER_STRING` to set it. * The NTP server from the DHCPv4 option can now be used to set the system time. This is done by default, if :kconfig:option:`CONFIG_NET_CONFIG_CLOCK_SNTP_INIT` is enabled. * The syslog server address can now be set with DHCPv4 option. This is done by default, if :kconfig:option:`CONFIG_LOG_BACKEND_NET_USE_DHCPV4_OPTION` is enabled. * Fixed a bug, where options with registered callbacks were not requested from the server. * Fixed a bug, where netmask received from the server was not applied correctly. * Reimplemented DHCPv4 client RENEW/REBIND logic to be compliant with RFC2131. * Improved declined addresses management in DHCPv4 server, which now can be reused after configured time. * Fixed including the client ID option in the DHCPv4 server response, according to RFC6842. * Added :kconfig:option:`CONFIG_NET_DHCPV4_SERVER_NAK_UNRECOGNIZED_REQUESTS` which allows to override RFC-defined behavior, and NAK requests from unrecognized clients. * Fixed client ID generation in DHCPv4 server. * Other minor fixes in DHCPv4 client and server implementations. * DHCPv6: * Fixed incorrect DHCPv6 events code base for net_mgmt events. * Added :kconfig:option:`CONFIG_NET_DHCPV6_DUID_MAX_LEN` which allows to configure maximum supported DUID length. * Added documentation page for DHCPv6. * DNS/mDNS/LLMNR: * Fixed an issue where the mDNS Responder did not work when the mDNS Resolver was also enabled. The mDNS Resolver and mDNS Responder can now be used simultaneously. * Reworked LLMNR and mDNS responders, and DNS resolver to use sockets and socket services API. * Added ANY query resource type. * Added support for mDNS to provide records in runtime. * Added support for caching DNS records. * Fixed error codes returned when socket creation fails, and when all results have been returned. * Fixed DNS retransmission timeout calculation. * gPTP/PTP: * Added support for IEEE 1588-2019 PTP. * Added support for SO_TIMESTAMPING socket option to get timestamping information in socket ancillary data. * Fixed race condition on timestamp callback. * Fixed clock master sync send SM if we are not the GM clock. * HTTP: * Added HTTP/2 server library and sample application with support for static, dynamic and Websocket resource types. * Added HTTP shell component. * Improved HTTP client error reporting. * Moved HTTP client library out of experimental. * Added POLLOUT monitoring when sending response in HTTP client. * IPSP: * Removed IPSP support. ``CONFIG_NET_L2_BT`` does not exist anymore. * IPv4: * Implemented IPv4 Address Conflict Detection, according to RFC 5227. * Added :c:func:`net_ipv4_is_private_addr` API function. * IPv4 netmask is now set individually for each address instead of being set for the whole interface. * Other minor fixes and improvements. * IPv6: * Implemented IPv6 Privacy Extensions according to RFC 8981. * Added :c:func:`net_ipv6_is_private_addr` API function. * Implemented reachability hint for IPv6. Upper layers can use c:func:`net_if_nbr_reachability_hint` to report Neighbor reachability and avoid unnecessary Neighbor Discovery solicitations. * Added :kconfig:option:`CONFIG_NET_IPV6_MTU` allowing to set custom IPv6 MTU. * Added :kconfig:option:`CONFIG_NET_MCAST_ROUTE_MAX_IFACES` which allows to set multiple interfaces for multicast forwarding entries. * Added :kconfig:option:`CONFIG_NET_MCAST_ROUTE_MLD_REPORTS` which allows to report multicast routes in MLDv2 reports. * Fixed IPv6 hop limit handling for multicast packets. * Improved IPv6 Neighbor Discovery test coverage. * Fixed a bug, where Neighbor Advertisement packets reporting Duplicate address detection conflicts were dropped. * Other minor fixes and improvements. * LwM2M: * Added new API functions: * :c:func:`lwm2m_set_bulk` * :c:func:`lwm2m_rd_client_set_ctx` * Added new ``offset`` parameter to :c:type:`lwm2m_engine_set_data_cb_t` callback type. This affects post write and validate callbacks as well as some firmware callbacks. * Fixed block context not being reset upon receiving block number 0 in block transfer. * Fixed block size negotiation with the server in block transfer. * Added :kconfig:option:`CONFIG_LWM2M_ENGINE_ALWAYS_REPORT_OBJ_VERSION` which allows to force the client to always report object version. * Block transfer is now possible with resource w/o registered callback. * Fixed a bug, where an empty ACK sent from the registered callback would not be sent immediately. * Removed deprecated API functions and definitions. * Other minor fixes and improvements. * Misc: * Improved overall networking API Doxygen documentation. * Converted TFTP library to use ``zsock_`` API. Added SNTP :c:func:`sntp_simple_addr` API function to perform SNTP query when the server IP address is already known. * Added :kconfig:option:`CONFIG_NET_TC_THREAD_PRIO_CUSTOM` allowing to override default traffic class threads priority. * Fixed the IPv6 event handler initialization order in net config library. * Reworked telnet shell backend to use sockets and socket services API. * Fixed double dereference of IGMP packets. * Moved from ``native_posix`` to ``native_sim`` support in various tests and samples. * Added support for copying user data in network buffers. * Fixed cloning of zero sized network buffers. * Added net_buf APIs to handle 40 bit data format. * Added receive callback for dummy L2, applicable in certain use cases (for example, packet capture). * Implemented pseudo interface, a.k.a "any" interface for packet capture use case. * Added cooked mode capture support. This allows non-IP based network data capture. * Generate network events when starting or stopping packet capture. * Removed obsolete and unused ``tcp_first_msg`` :c:struct:`net_pkt` flag. * Added new :zephyr:code-sample:`secure-mqtt-sensor-actuator` sample. * Added support for partial L3 and L4 checksum offloading. * Updated :zephyr:code-sample:`mqtt-azure` with new CA certificates, the current on expires soon. * Added new driver for Native Simulator offloaded sockets. * Overhauled VLAN support to use Virtual network interfaces. * Added statistics collection for Virtual network interfaces. * Fixed system workqueue block in :c:func:`mgmt_event_work_handler` when :kconfig:option:`CONFIG_NET_MGMT_EVENT_SYSTEM_WORKQUEUE` is enabled. * MQTT: * Added ALPN support for MQTT TLS backend. * Added user data field in :c:struct:`mqtt_client` context structure. * Fixed a potential socket leak in MQTT Websockets transport. * Network Interface: * Added new API functions: * :c:func:`net_if_ipv4_maddr_foreach` * :c:func:`net_if_ipv6_maddr_foreach` * Improved debug logging in the network interface code. * Added reference counter to the :c:struct:`net_if_addr` structure. * Fixed IPv6 DAD and MLDv2 operation when interface goes up. * Added unique default name for OpenThread interfaces. * Other minor fixes. * OpenThread * Removed deprecated ``openthread_set_state_changed_cb()`` function. * Added implementation of BLE TCAT advertisement API. * PPP * Removed deprecated ``gsm_modem`` driver and sample. * Optimized memory allocation in PPP driver. * Misc improvements in the :zephyr:code-sample:`cellular-modem` sample * Added PPP low level packet capture support. * Shell: * Added ``net ipv4 gateway`` command to set IPv4 gateway address. * Added argument validation in network shell macros. * Fixed net_mgmt sockets information printout. * Reworked VLAN information printout. * Added option to set random MAC address with ``net iface set_mac`` command. * Added multicast join status when printing multicast address information. * Sockets: * Implemented new networking POSIX APIs: * :c:func:`if_nameindex` * :c:func:`inet_ntoa` * :c:func:`inet_addr` * Added support for tracing socket API calls. * TLS sockets are no longer experimental API. * Fixed the protocol field endianness for ``AF_PACKET`` type sockets. * Fixed :c:func:`getsockname` for TCP. * Improve :c:func:`sendmsg` support when using DTLS sockets. * Fixed :c:func:`net_socket_service_register` function stall in case socket services thread stopped. * Fixed potential socket services thread stoppage when deregistering service. * Removed support for asynchronous timeouts in socket services library. * Fixed potential busy looping when using :c:func:`zsock_accept` in case of file descriptors shortage. * Syslog: * Added new API functions: * :c:func:`log_backend_net_set_ip` to initialize syslog net backend with IP address directly. * :c:func:`log_backend_net_start` to facilitate syslog net backend activation. * Added structured logging support to syslog net backend. * Added TCP support to syslog net backend. * TCP: * Fixed possible deadlock when accepting new TCP connection. * Fixed ACK number verification during connection teardown. * Fixed a bug, where data bytes included in FIN packet were ignored. * Fixed a possible TCP context leak in case initial SYN packet transmission failed. * Deprecated :kconfig:option:`CONFIG_NET_TCP_ACK_TIMEOUT` as it was redundant with other configs. * Improved debug logs, so that they're easier to follow under heavy load. * ISN generation now uses SHA-256 instead of MD5. Moreover, it now relies on PSA APIs instead of legacy Mbed TLS functions for hash computation. * Improved ACK reply logic in case no PSH flag is present to reduce redundant ACKs. * Websocket: * Added new Websocket APIs: * :c:func:`websocket_register` * :c:func:`websocket_unregister` * Converted Websocket library to use ``zsock_`` API. Added Object Core support to Websocket sockets. * Added POLLOUT monitoring when sending. * Wi-Fi: * Reduce memory usage of 5 GHz channel list. * Added channel validity check in AP mode. * Added support for BSSID configuration in connect call. * Wifi shell help text fixes. Option parsing fixes. * Support WPA auto personal security mode. * Collect unicast received/sent network packet statistics. * Added support for configuring RTS threshold. With this, users can set the RTS threshold value or disable the RTS mechanism. * Added support for configuring AP parameters. With this, users can set AP parameters at build and run time. * Added support to configure ``max_inactivity`` BSS parameter. Users can set this both build and runtime duration to control the maximum time duration after which AP may disconnect a STA due to inactivity from STA. * Added support to configure ``inactivity_poll`` BSS parameter. Users can set build only AP parameter to control whether AP may poll the STA before throwing away STA due to inactivity. * Added support to configure ``max_num_sta`` BSS parameter. Users can set this both build and run time parameter to control the maximum number of STA entries. * zperf: * Fixed ``IP_TOS`` and ``IPV6_TCLASS`` options handling in zperf. * Fixed throughput calculation during long zperf sessions. * Fixed error on TCP upload session end in case multicast IP address was used. * Fixed a bug, where IPv6 socket was bound with IPv4 address, giving error. * Added an option to specify the network interface to use during zperf sessions. * Added a new ``ZPERF_SESSION_PERIODIC_RESULT`` event for periodic updates during TCP upload sessions. * Fixed possible socket leak in case of errors during zperf session. * Improved performance in the default configuration for the zperf sample. USB *** * New USB device stack: * Added support for HID devices * Introduced speed-specific configurations and made high-speed support compliant with the USB2.0 specification * Added notification support and initial BOS support Devicetree ********** * Added :c:macro:`DT_INST_NODE_HAS_COMPAT` to check if a node has a compatible. This is useful for nodes that have multiple compatibles. * Added :c:macro:`DT_CHILD_NUM` and variants to count the number of children of a node. * Added :c:macro:`DT_FOREACH_NODELABEL` and variants, which can be used to iterate over the node labels of a devicetree node. * Added :c:macro:`DT_NODELABEL_STRING_ARRAY` and :c:macro:`DT_NUM_NODELABELS` and their variants. * Added :c:macro:`DT_REG_HAS_NAME` and variants. * Reworked :c:macro:`DT_ANY_INST_HAS_PROP_STATUS_OKAY` so that the result can be used with macros like :c:macro:`IS_ENABLED`, IF_ENABLED, or COND_CODE_x. * Reworked :c:macro:`DT_NODE_HAS_COMPAT_STATUS` so that it can be evaluated at preprocessor time. * Updated PyYaml version used in dts scripts to 6.0 to remove supply chain vulnerabilities. Kconfig ******* * Added a ``substring`` Kconfig preprocessor function. * Added a ``dt_node_ph_prop_path`` Kconfig preprocessor function. * Added a ``dt_compat_any_has_prop`` Kconfig preprocessor function. Libraries / Subsystems ********************** * Debug * symtab * By enabling :kconfig:option:`CONFIG_SYMTAB`, the symbol table will be generated with Zephyr link stage executable on supported architectures. * Demand Paging * NRU (Not Recently Used) eviction algorithm has updated its selection logic to avoid picking the same page to evict constantly. The updated login now searches for a new candidate linearly after the last evicted page. * Added LRU (Least Recently Used) eviction algorithm. * Formatted output * Fix warning when compiling cbprintf with ARCMWDT. * Management * hawkBit * The hawkBit subsystem has been reworked to use the settings subsystem to store the hawkBit configuration. * By enabling :kconfig:option:`CONFIG_HAWKBIT_SET_SETTINGS_RUNTIME`, the hawkBit settings can be configured at runtime. Use the :c:func:`hawkbit_set_config` function to set the hawkBit configuration. It can also be set via the hawkBit shell, by using the ``hawkbit set`` command. * When using the hawkBit autohandler and an update is installed, the device will now automatically reboot after the installation is complete. * By enabling :kconfig:option:`CONFIG_HAWKBIT_CUSTOM_DEVICE_ID`, a callback function can be registered to set the device ID. Use the :c:func:`hawkbit_set_device_identity_cb` function to register the callback. * By enabling :kconfig:option:`CONFIG_HAWKBIT_CUSTOM_ATTRIBUTES`, a callback function can be registered to set the device attributes that are sent to the hawkBit server. Use the :c:func:`hawkbit_set_custom_data_cb` function to register the callback. * MCUmgr * Instructions for the deprecated mcumgr go tool have been removed, a list of alternative, supported clients can be found on :ref:`mcumgr_tools_libraries`. * Fixed an issue with the SMP structure not being packed which would cause a fault on devices that do not support unaligned memory accesses. * Added :kconfig:option:`CONFIG_MCUMGR_TRANSPORT_BT_DYNAMIC_SVC_REGISTRATION` that allows users to select whether MCUmgr BT service is statically registered at compile time or dynamically at run time. * In FS group, TinyCrypt has been replaced with PSA calls for SHA calculation. * Logging * By enabling :kconfig:option:`CONFIG_LOG_BACKEND_NET_USE_DHCPV4_OPTION`, the IP address of the syslog server for the networking backend is set by the DHCPv4 Log Server Option (7). * Use real time clock as timestamp on POSIX. * Add support for syslog (POSIX). * Add :c:macro:`LOG_WRN_ONCE` for logging warning message where only the first occurrence is logged. * Add :c:func:`log_thread_trigger` for triggering processing of the log messages. * Fix case when deferred logging not compiling when :kconfig:option:`CONFIG_MULTITHREADING` was disabled. * Fix case when logging strings could be stripped from the binary when dictionary based logging was mixed with non-dictionary. * Fix dictionary database not being generated in certain situations. * Fix dictionary logging parser not handling long long arguments correctly. * Fix support for :kconfig:option:`CONFIG_LOG_MSG_APPEND_RO_STRING_LOC`. * Modem modules * Added modem pipelink module which shares modem pipes globally, allowing device drivers to create and set up pipes for the application to use. * Simplified the modem pipe module's synchronization mechanism to only protect the callback and user data. This matches the actual in-tree usage of the modem pipes. * Added ``modem_stats`` module which tracks the usage of buffers throughout the modem subsystem. * Power management * Devices can now declare which system power states cause power loss. This information can be used to set and release power state constraints when it is needed by the device. This feature is enabled with :kconfig:option:`CONFIG_PM_POLICY_DEVICE_CONSTRAINTS`. Use functions :c:func:`pm_policy_device_power_lock_get` and :c:func:`pm_policy_device_power_lock_put` to lock and unlock all power states that cause power loss in a device. * Added shell support for device power management. * Device power management was de-coupled from system power management. The new :kconfig:option:`CONFIG_PM_DEVICE_SYSTEM_MANAGED` option is used to enable whether devices must be suspended when the system sleeps. * Make it possible to disable system device power management individually per power state using ``zephyr,pm-device-disabled``. This allows targets tuning which states should (and which should not) trigger device power management. * Crypto * TinyCrypt remains available but is now being phased out in favor of PSA Crypto for enhanced security and performance. * Mbed TLS was updated to 3.6.0. Release notes can be found at: path_to_url * When any PSA crypto provider is available in the system (:kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_CLIENT` is enabled), desired PSA features must now be explicitly selected through ``CONFIG_PSA_WANT_xxx`` symbols. * Choice symbols :kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_LEGACY_RNG` and :kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG` were added in order to allow the user to specify how Mbed TLS PSA crypto core should generate random numbers. The former option, which is the default, relies on legacy entropy and CTR_DRBG/HMAC_DRBG modules, while the latter relies on CSPRNG drivers. * :kconfig:option:`CONFIG_MBEDTLS_PSA_P256M_DRIVER_ENABLED` enables support for the Mbed TLS's p256-m driver PSA crypto library. This is a Cortex-M SW optimized implementation of secp256r1 curve. * CMSIS-NN * CMSIS-NN was updated to v6.0.0 from v4.1.0: path_to_url * FPGA * Improve handling of drivers missing ``reset``, ``load``, ``get_status``, and ``get_info`` methods. * Add support for Agilex and Agilex 5. * Random * Besides the existing :c:func:`sys_rand32_get` function, :c:func:`sys_rand8_get`, :c:func:`sys_rand16_get` and :c:func:`sys_rand64_get` are now also available. These functions are all implemented on top of :c:func:`sys_rand_get`. * SD * SDMMC and SDIO frequency and timing selection logic have been reworked, to resolve an issue where a timing mode would not be selected if the SDHC device in use did not report support for the maximum frequency possible in that mode. Now, if the host controller and card both report support for a given timing mode but not the highest frequency that mode supports, the timing mode will be selected and configured at the reduced frequency (:github:`72705`). * State Machine Framework * The :c:macro:`SMF_CREATE_STATE` macro now always takes 5 arguments. * Transition sources that are parents of the state that was run now choose the correct Least Common Ancestor for executing Exit and Entry Actions. * Passing ``NULL`` to :c:func:`smf_set_state` is now not allowed. * Storage * FAT FS: It is now possible to expose file system formatting functionality for FAT without also enabling automatic formatting on mount failure by setting the :kconfig:option:`CONFIG_FS_FATFS_MKFS` Kconfig option. This option is enabled by default if :kconfig:option:`CONFIG_FILE_SYSTEM_MKFS` is set. * FS: It is now possible to truncate a file while opening using :c:func:`fs_open` and by passing ``FS_O_TRUNC`` flag. * Flash Map: TinyCrypt has been replaced with PSA Crypto in Flash Area integrity check. * Flash Map: :c:func:`flash_area_flatten` has been added to be used where an erase operation has been previously used for removing/scrambling data rather than to prepare a device for a random data write. * Flash Map: :c:macro:`FIXED_PARTITION_NODE_OFFSET`, :c:macro:`FIXED_PARTITION_NODE_SIZE` and :c:macro:`FIXED_PARTITION_NODE_DEVICE` have been added to allow obtaining fixed partition information from a devicetree node rather than a label. * Added :kconfig:option:`CONFIG_NVS_DATA_CRC`, to add CRC protection for data. Note that enabling this option makes NVS incompatible with existing storage that have not been previously using CRC on data. * Fixed NVS issue where :c:func:`nvs_calc_free_space` would return larger size than available, because space for reserved ate was not subtracted. * Fixed ext2 incorrectly calculating free space when attempting to format partition. * Fixed FAT driver leaving disk in initialized state after unmount. * Task Watchdog * Added shell (mainly for testing purposes during development). * POSIX API * Improved Kconfig options to reflect standard POSIX Options and Option Groups. * Added support for the following Option Groups * :ref:`POSIX_MAPPED_FILES <posix_option_group_mapped_files>` * :ref:`POSIX_MEMORY_PROTECTION <posix_option_group_memory_protection>` * :ref:`POSIX_NETWORKING <posix_option_group_networking>` * :ref:`POSIX_SINGLE_PROCESS <posix_option_group_single_process>` * :ref:`POSIX_TIMERS <posix_option_group_timers>` * :ref:`XSI_SYSTEM_LOGGING <posix_option_group_xsi_system_logging>` * Added support for the following Options * :ref:`_POSIX_ASYNCHRONOUS_IO <posix_option_asynchronous_io>` * :ref:`_POSIX_CPUTIME <posix_option_cputime>` * :ref:`_POSIX_FSYNC <posix_option_fsync>` * :ref:`_POSIX_MEMLOCK <posix_option_memlock>` * :ref:`_POSIX_MEMLOCK_RANGE <posix_option_memlock_range>` * :ref:`_POSIX_READER_WRITER_LOCKS <posix_option_reader_writer_locks>` * :ref:`_POSIX_SHARED_MEMORY_OBJECTS <posix_shared_memory_objects>` * :ref:`_POSIX_THREAD_CPUTIME <posix_option_thread_cputime>` * :ref:`_POSIX_THREAD_PRIO_PROTECT <posix_option_thread_prio_protect>` * :ref:`_POSIX_THREAD_PRIORITY_SCHEDULING <posix_option_thread_priority_scheduling>` * :ref:`_XOPEN_STREAMS <posix_option_xopen_streams>` * Fixed eventfd ``F_SETFL`` handling to avoid overwriting internal flags. * Fixed thread stack address printed in debug message. * Fixed macro parameter usage in signal code. * LoRa/LoRaWAN * Added the Fragmented Data Block Transport service, which can be enabled via :kconfig:option:`CONFIG_LORAWAN_FRAG_TRANSPORT`. In addition to the default fragment decoder implementation from Semtech, an in-tree implementation with reduced memory footprint is available. * Added a sample to demonstrate LoRaWAN firmware-upgrade over the air (FUOTA). * ZBus * Improved the VDED process by optimizing the channel reference copying for the clones delivered during the message subscriber delivery notification. * Improved the initialization phase by statically initiating the semaphores and runtime observer list. That decreased the duration of the zbus initialization. * Added a way of isolating a channel message subscribers pool. Some channels can now share an isolated pool to avoid delivery failures and shorten communication latency. It is only necessary to enable the :kconfig:option:`CONFIG_ZBUS_MSG_SUBSCRIBER_NET_BUF_POOL_ISOLATION` and use the function :c:func:`zbus_chan_set_msg_sub_pool` to change the msg pool used by the channel. Channels can share the same message pool. HALs **** * Nordic * Updated nrfx to version 3.5.0. * Added nRF Services (nrfs) library. * STM32 * Updated STM32F0 to cube version V1.11.5. * Updated STM32F3 to cube version V1.11.5. * Updated STM32F4 to cube version V1.28.0. * Updated STM32F7 to cube version V1.17.2. * Updated STM32G0 to cube version V1.6.2. * Updated STM32G4 to cube version V1.5.2. * Updated STM32H5 to cube version V1.2.0. * Updated STM32H7 to cube version V1.11.2. * Updated STM32L5 to cube version V1.5.1. * Updated STM32U5 to cube version V1.5.0. * Updated STM32WB to cube version V1.19.1. * Updated STM32WBA to cube version V1.3.1. * Added STM32H7R/S with cube version V1.0.0. * ADI * Introduced the ``hal_adi`` module, which is a subset of the Maxim Software Development Kit (MSDK) that contains device header files and bare metal peripheral drivers (:github:`72391`). * Espressif * Updated HAL to version v5.1, which has new SoCs low-level files. MCUboot ******* * Fixed memory leak in bootutil HKDF implementation * Fixed enforcing TLV entries to be protected * Fixed disabling instruction/data caches * Fixed estimated image overhead size calculation * Fixed issue with swap-move algorithm failing to validate multiple-images * Fixed align script error in imgtool * Fixed img verify for hex file format in imgtool * Fixed issue with reading the flash image reset vector * Fixed too-early ``check_config.h`` include in mbedtls * Refactored image dependency functions to reduce code size * Added MCUboot support for ``ESP32-C6`` * Added optional MCUboot boot banner * Added TLV querying for protected region * Added using builtin keys for verification in bootutil * Added builtin ECDSA key support for PSA Crypto backend * Added ``OVERWRITE_ONLY_KEEP_BACKUP`` option for secondary images * Added defines for ``SOC_FLASH_0_ID`` and ``SPI_FLASH_0_ID`` * Fixed ASN.1 support for mbedtls version >= 3.1 * Fixed bootutil signed/unsigned comparison in ``boot_read_enc_key`` * Updated imgtool version.py to take command line arguments * Added imgtool improvements to dumpinfo * Fixed various imgtool dumpinfo issues * Fixed imgtool verify command for edcsa-p384 signed images * Added support for NXP MCXN947 * The MCUboot version in this release is version ``2.1.0+0-dev``. OSDP **** * Fixed issue in CP secure channel handshake where R-MAC can be reverted to an old one by a rogue PD sending an out-of-order secure channel response resulting in a replay attack. Trusted Firmware-M ****************** * TF-M was updated to 2.1.0. Release notes can be found at: path_to_url * Support for MCUboot signature types other than RSA-3072 has been added. The type can be chosen with the :kconfig:option:`CONFIG_TFM_MCUBOOT_SIGNATURE_TYPE` Kconfig option. Using EC-P256, the new default, reduces flash usage by several KBs compared to RSA. LVGL **** LVGL was updated to 8.4.0. Release notes can be found at: path_to_url#v8-4-0-19-march-2024 Additionally, the following changes in Zephyr were done: * Added support to place memory pool buffers in ``.lvgl_heap`` section by enabling :kconfig:option:`CONFIG_LV_Z_MEMORY_POOL_CUSTOM_SECTION` * Removed kscan-based pointer input wrapper code. * Corrected encoder button behavior to emit ``LV_KEY_ENTER`` events correctly. * Improved handling for :samp:`invert-{x,y}` and ``swap-xy`` configurations. * Added ``LV_MEM_CUSTOM_FREE`` call on file closure. * Added missing Kconfig stubs for DMA2D symbols. * Integrated support for LVGL rounder callback function. Tests and Samples ***************** * Added snippet for easily enabling UART over Bluetooth LE by passing ``-S nus-console`` during ``west build``. This snippet sets the :kconfig:option:`CONFIG_BT_ZEPHYR_NUS_AUTO_START_BLUETOOTH` which allows non-Bluetooth samples that use the UART APIs to run without modifications (e.g.: Console and Logging examples). * Removed ``GSM_PPP`` specific configuration overlays from samples ``net/cloud/tagoio`` and ``net/mgmt/updatehub``. The ``GSM_PPP`` device driver has been deprecated and removed. The new ``MODEM_CELLULAR`` device driver which replaces it uses the native networking stack and ``PM`` subsystem, which like ethernet, requires no application specific actions to set up networking. * Removed ``net/gsm_modem`` sample as the ``GSM_PPP`` device driver it depended on has been deprecated and removed. The sample has been replaced by the sample ``net/cellular_modem`` based on the ``MODEM_CELLULAR`` device driver. * BT LE Coded PHY is now runtime tested in CI with the nrf5x bsim targets. * External ethernet network interfaces have been disabled in the ``tests/net`` tests, since these tests are meant to use simulated network interfaces. Issue Related Items ******************* Known Issues ============ - :github:`74345` - Bluetooth: Non functional on nRF51 with fault ```	/content/code_sandbox/doc/releases/release-notes-3.7.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	23,733
```restructuredtext :orphan: .. _zephyr_3.3: Zephyr 3.3.0 ############ We are pleased to announce the release of Zephyr version 3.3.0. Major enhancements with this release include: * Introduced :ref:`Fuel Gauge <fuel_gauge_api>` subsystem for battery level monitoring. * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery) support. * Introduced :ref:`DSP (digital signal processing) <zdsp_api>` subsystem with CMSIS-DSP as the default backend. * Added Picolibc support for all architectures when using Zephyr SDK. 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: path_to_url * CVE-2023-0359: Under embargo until 2023-04-20 * CVE-2023-0779: Under embargo until 2023-04-22 API Changes *********** * Emulator creation APIs have changed to better match :c:macro:`DEVICE_DT_DEFINE`. It also includes a new backend API pointer to allow sensors to share common APIs for more generic tests. Changes in this release ======================= * Newlib nano variant is no longer selected by default when :kconfig:option:`CONFIG_NEWLIB_LIBC` is selected. :kconfig:option:`CONFIG_NEWLIB_LIBC_NANO` must now be explicitly selected in order to use the nano variant. * Bluetooth: Added extra options to bt_le_per_adv_sync_transfer_subscribe to allow disabling sync reports, and enable sync report filtering. these two options are mutually exclusive. * Bluetooth: :kconfig:option:`CONFIG_BT_PER_ADV_SYNC_TRANSFER_RECEIVER` and :kconfig:option:`CONFIG_BT_PER_ADV_SYNC_TRANSFER_SENDER` have been added to enable the PAST implementation rather than :kconfig:option:`CONFIG_BT_CONN`. * Flashdisk: :kconfig:option:`CONFIG_DISK_FLASH_VOLUME_NAME`, :kconfig:option:`CONFIG_DISK_FLASH_DEV_NAME`, :kconfig:option:`CONFIG_DISK_FLASH_START`, :kconfig:option:`CONFIG_DISK_FLASH_MAX_RW_SIZE`, :kconfig:option:`CONFIG_DISK_ERASE_BLOCK_SIZE`, :kconfig:option:`CONFIG_DISK_FLASH_ERASE_ALIGNMENT`, :kconfig:option:`CONFIG_DISK_VOLUME_SIZE` and :kconfig:option:`CONFIG_DISK_FLASH_SECTOR_SIZE` Kconfig options have been removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding. * Regulator APIs previously located in ``<zephyr/drivers/regulator/consumer.h>`` are now part of ``<zephyr/drivers/regulator.h>``. * Starting from this release ``zephyr-`` prefixed tags won't be created anymore. The project will continue using ``v`` tags, for example ``v3.3.0``. * Bluetooth: Deprecated the Bluetooth logging subsystem in favor of the Zephyr standard logging system. To enable debugging for a particular module in the Bluetooth subsystem, enable `CONFIG_BT_(module name)_LOG_LEVEL_DBG` instead of `CONFIG_BT_DEBUG_(module name)`. * MCUmgr img_mgmt now requires that a full sha256 hash to be used when uploading an image to keep track of the progress, where the sha256 hash is of the whole file being uploaded (different to the hash used when getting image states). Use of a truncated hash or non-sha256 hash will still work but will cause issues and failures in client software with future updates to Zephyr/MCUmgr such as image verification. * MCUmgr handlers no longer need to be registered by the application code, handlers just need to use a define which will then call the supplied registration function at boot-up. If applications register this then those registrations should be removed to prevent registering the same handler multiple times. * MCUmgr Bluetooth and UDP transports no longer need to be registered by the application code, these will now automatically be registered at boot-up (this feature can be disabled for the UDP transport by setting :kconfig:option:`CONFIG_MCUMGR_TRANSPORT_UDP_AUTOMATIC_INIT`). If applications register transports then those registrations should be removed to prevent registering the same transport multiple times. * MCUmgr transport Kconfigs have changed from ``select`` to ``depends on`` which means that for applications using the Bluetooth transport, applications will now need to enable the following: * :kconfig:option:`CONFIG_BT` * :kconfig:option:`CONFIG_BT_PERIPHERAL` For CDC or serial transports: * :kconfig:option:`CONFIG_CONSOLE` For shell transport: * :kconfig:option:`CONFIG_SHELL` * :kconfig:option:`CONFIG_SHELL_BACKEND_SERIAL` For UDP transport: * :kconfig:option:`CONFIG_NETWORKING` * :kconfig:option:`CONFIG_NET_UDP` * MCUmgr fs_mgmt hash/checksum function, type and variable names have been changed to be prefixed with ``fs_mgmt_`` to retain alignment with other zephyr and MCUmgr APIs. * Python's argparse argument parser usage in Zephyr scripts has been updated to disable abbreviations, any future python scripts or python code updates must also disable allowing abbreviations by using ``allow_abbrev=False`` when setting up ``ArgumentParser()``. This may cause out-of-tree scripts or commands to fail if they have relied upon their behaviour previously, these will need to be updated in order for building to work. As an example, if a script argument had ``--reset-type`` and an out-of-tree script used this by passing ``--reset`` then it will need to be updated to use the full argument name, ``--reset-type``. * Rewrote the CAN API to utilize flag bitfields instead discrete of struct members for indicating standard/extended CAN ID, Remote Transmission Request (RTR), and added support for filtering of CAN-FD format frames. * New :ref:`Zephyr message bus (Zbus) <zbus>` subsystem added; a message-oriented bus that enables one-to-one, one-to-many and many-to-many communication between threads. * zTest now supports controlling test summary printouts via the :kconfig:option:`CONFIG_ZTEST_SUMMARY`. This Kconfig can be set to ``n`` for less verbose test output. * Emulators now support a backend API pointer which allows a single class of devices to provide similar emulated functionality. This can be used to write a single test for the class of devices and testing various boards using different chips. Removed APIs in this release ============================ * Removed :kconfig:option:`CONFIG_COUNTER_RTC_STM32_LSE_DRIVE` This should now be configured using the ``driving_capability`` property of LSE clock Removed :kconfig:option:`CONFIG_COUNTER_RTC_STM32_LSE_BYPASS` This should now be configured using the new ``lse_bypass`` property of LSE clock * Removed :kconfig:option:`CONFIG_COUNTER_RTC_STM32_BACKUP_DOMAIN_RESET`. Its purpose was to control the reset of the counter value at board reset. It is removed since it has too wide scope (full Backup RAM reset). Replaced by :kconfig:option:`CONFIG_COUNTER_RTC_STM32_SAVE_VALUE_BETWEEN_RESETS` which also allows to control the reset of counter value, with an opposite logic. * Removed deprecated tinycbor module, code that uses this module should be updated to use zcbor as a replacement. * Removed deprecated GPIO flags used for setting debounce, drive strength and voltage level. All drivers now use vendor-specific flags as needed. * Removed deprecated ``UTIL_LISTIFY`` helper macro. * Removed deprecated ``pwm_pin`` family of functions from the PWM API. Removed deprecated ``nvs_init`` function from the NVS filesystem API. * Removed deprecated ``DT_CHOSEN__LABEL`` helper macros. Removed deprecated property ``enable-pin-remap`` from :dtcompatible: `st,stm32-usb`:. ``remap-pa11-pa12`` from :dtcompatible: `st-stm32-pinctrl`: should now be used. Deprecated in this release ========================== * :ref:`xtools toolchain variant <toolchain_xtools>` is now deprecated. When using a custom toolchain built with Crosstool-NG, the :ref:`cross-compile toolchain variant <other_x_compilers>` should be used instead. * C++ library Kconfig options have been renamed to improve consistency. See below for the list of deprecated Kconfig options and their replacements: .. table:: :align: center +----------------------------------------+------------------------------------------------+ \| Deprecated \| Replacement \| +========================================+================================================+ \| :kconfig:option:`CONFIG_CPLUSPLUS` \| :kconfig:option:`CONFIG_CPP` \| +----------------------------------------+------------------------------------------------+ \| :kconfig:option:`CONFIG_EXCEPTIONS` \| :kconfig:option:`CONFIG_CPP_EXCEPTIONS` \| +----------------------------------------+------------------------------------------------+ \| :kconfig:option:`CONFIG_RTTI` \| :kconfig:option:`CONFIG_CPP_RTTI` \| +----------------------------------------+------------------------------------------------+ \| :kconfig:option:`CONFIG_LIB_CPLUSPLUS` \| :kconfig:option:`CONFIG_LIBCPP_IMPLEMENTATION` \| +----------------------------------------+------------------------------------------------+ * MCUmgr subsystem, specifically the SMP transport API, is dropping `zephyr_` prefix, deprecating prefixed functions and callback type definitions with the prefix and replacing them with prefix-less variants. The :c:struct:`zephyr_smp_transport` type, representing transport object, is now replaced with :c:struct:`smp_transport`, and the later one is used, instead of the former one, by all prefix-less functions. Deprecated functions and their replacements: .. table:: :align: center +-------------------------------------+---------------------------------------+ \| Deprecated \| Drop in replacement \| +=====================================+=======================================+ \| :c:func:`zephyr_smp_transport_init` \| :c:func:`smp_transport_init` \| +-------------------------------------+---------------------------------------+ \| :c:func:`zephyr_smp_rx_req` \| :c:func:`smp_rx_req` \| +-------------------------------------+---------------------------------------+ \| :c:func:`zephyr_smp_alloc_rsp` \| :c:func:`smp_alloc_rsp` \| +-------------------------------------+---------------------------------------+ \| :c:func:`zephyr_smp_free_buf` \| :c:func:`smp_free_buf` \| +-------------------------------------+---------------------------------------+ Deprecated callback types and their replacements: .. table:: :align: center +---------------------------------------------+---------------------------------------+ \| Deprecated \| Drop in replacement \| +=============================================+=======================================+ \| :c:func:`zephyr_smp_transport_out_fn` \| :c:func:`smp_transport_out_fn` \| +---------------------------------------------+---------------------------------------+ \| :c:func:`zephyr_smp_transport_get_mtu_fn` \| :c:func:`smp_transport_get_mtu_fn` \| +---------------------------------------------+---------------------------------------+ \| :c:func:`zephyr_smp_transport_ud_copy_fn` \| :c:func:`smp_transport_ud_copy_fn` \| +---------------------------------------------+---------------------------------------+ \| :c:func:`zephyr_smp_transport_ud_free_fn` \| :c:func:`smp_transport_ud_free_fn` \| +---------------------------------------------+---------------------------------------+ NOTE: Only functions are marked as ``__deprecated``, type definitions are not. * STM32 Ethernet Mac address Kconfig related symbols (:kconfig:option:`CONFIG_ETH_STM32_HAL_RANDOM_MAC`, :kconfig:option:`CONFIG_ETH_STM32_HAL_MAC4`, ...) have been deprecated in favor of the use of zephyr generic device tree ``local-mac-address`` and ``zephyr,random-mac-address`` properties. * STM32 RTC source clock should now be configured using devicetree. Related Kconfig :kconfig:option:`CONFIG_COUNTER_RTC_STM32_CLOCK_LSI` and :kconfig:option:`CONFIG_COUNTER_RTC_STM32_CLOCK_LSE` options are now deprecated. * STM32 Interrupt controller Kconfig symbols such as :kconfig:option:`CONFIG_EXTI_STM32_EXTI0_IRQ_PRI` are removed. Related IRQ priorities should now be configured in device tree. * `PWM_STM32_COMPLEMENTARY` deprecated in favor of `STM32_PWM_COMPLEMENTARY`. * File backend for settings APIs and Kconfig options were deprecated: :c:func:`settings_mount_fs_backend` in favor of :c:func:`settings_mount_file_backend` :kconfig:option:`CONFIG_SETTINGS_FS` in favor of :kconfig:option:`CONFIG_SETTINGS_FILE` :kconfig:option:`CONFIG_SETTINGS_FS_DIR` in favor of creating all parent directories from :kconfig:option:`CONFIG_SETTINGS_FILE_PATH` :kconfig:option:`CONFIG_SETTINGS_FS_FILE` in favor of :kconfig:option:`CONFIG_SETTINGS_FILE_PATH` :kconfig:option:`CONFIG_SETTINGS_FS_MAX_LINES` in favor of :kconfig:option:`CONFIG_SETTINGS_FILE_MAX_LINES` * PCIe APIs :c:func:`pcie_probe` and :c:func:`pcie_bdf_lookup` have been deprecated in favor of a centralized scan of available PCIe devices. * POSIX API * Deprecated :c:macro:`PTHREAD_COND_DEFINE`, :c:macro:`PTHREAD_MUTEX_DEFINE` in favour of the standard :c:macro:`PTHREAD_COND_INITIALIZER` and :c:macro:`PTHREAD_MUTEX_INITIALIZER`. * Deprecated ``<fcntl.h>``, ``<sys/stat.h>`` header files in the minimal libc in favour of ``<zephyr/posix/fcntl.h>`` and ``<zephyr/posix/sys/stat.h>``. * SPI DT :c:func:`spi_is_ready` function has been deprecated in favor of :c:func:`spi_is_ready_dt`. * LwM2M APIs using string references as LwM2M paths has been deprecated in favor of functions using :c:struct:`lwm2m_path_obj` instead. Stable API changes in this release ================================== * MCUmgr events have been reworked to use a single, unified callback system. This allows better customisation of the callbacks with a lower flash size. Applications using the existing callback system will need to be upgraded to use the new API by following the :ref:`migration guide <mcumgr_cb_migration>` * :c:func:`net_pkt_get_frag`, :c:func:`net_pkt_get_reserve_tx_data` and :c:func:`net_pkt_get_reserve_rx_data` functions are now requiring to specify the minimum fragment length to allocate, so that they work correctly also in case :kconfig:option:`CONFIG_NET_BUF_VARIABLE_DATA_SIZE` is enabled. Applications using this APIs will need to be updated to provide the expected fragment length. * Marked the Controller Area Network (CAN) controller driver API as stable. New APIs in this release ======================== Kernel ****** * Added an "EARLY" init level that runs immediately on entry to z_cstart() * Refactored the internal CPU count API to allow for runtime changes * Added support for defining application main() in C++ code * Fixed a race condition on SMP when pending threads where a second CPU could attempt to run a thread before the pending thread had finished the context switch. Architectures ************* * ARC * Fixed & reworked interrupt management (enabling / disabling) for the SMP systems * Added TLS (thread-local storage) for ARC MWDT toolchain * Fixed & rework irq_offload implementation * Fixed multiple logging & cbprintf issues for ARCv3 64bit * Added XIP support with MWDT toolchain * Improved DSP support, add DSP and AGU context save / restore * Added XY memory support for ARC DSP targets * Added architectures-specific DSP tests * Added additional compile-time checks for unsupported configuration: ARC_FIRQ + ARC_HAS_SECURE * Added support for using ``__auto_type`` type for ARC MWDT toolchain * Added support for using ``_Generic`` and ``__fallthrough`` keywords for ARC MWDT toolchain * Bumped minimal required ARC MWDT version to 2022.09 * Fixed & reworked inclusion of C/C++ headers for ARC MWDT toolchain which cased build issue with C++ * ARM * More precise 'reason' codes are now returned in the fault handler. * Cache functions now use proper ``sys_`` functions. Renamed default RAM region from ``SRAM`` to ``RAM``. * ARM64 * Implemented ASID support for ARM64 MMU * RISC-V * Converted :kconfig:option:`CONFIG_MP_NUM_CPUS` to :kconfig:option:`CONFIG_MP_MAX_NUM_CPUS`. * Added support for hardware register stacking/unstacking during ISRs and exceptions. * Added support for overriding :c:func:`arch_irq_lock`, :c:func:`arch_irq_unlock` and :c:func:`arch_irq_unlocked`. * Zephyr CPU number is now decoupled from the hart ID. * Secondary boot code is no longer included when :kconfig:option:`CONFIG_MP_MAX_NUM_CPUS` equals ``1``. * IPIs are no longer hardcoded to :c:func:`z_sched_ipi`. * Implemented an on-demand context switching algorithm for thread FPU accesses. * Enabled booting from non-zero indexed RISC-V harts with :kconfig:option:`CONFIG_RV_BOOT_HART`. * Hart IDs are now mapped to Zephyr CPUs with the devicetree. * Added a workaround for ``MTVAL`` not updating properly on QEMU-based platforms. Bluetooth ********* * Audio * Refactored the handling of extended and periodic advertising in the BAP broadcast source. * Implemented the Common Audio Profile initiator role. * Added support for Broadcast source subgroup and BIS codec configuration. * Renamed the CSI and VCP functionality to use the "P" postfix for profile instead of "S" for service. * Added a broadcast source metadata update function. * Added (un)binding of audio ISO structs to Audio Streams. * Added support for encrypted broadcast. * Added the ability to change the supported contexts in PACS. * Improved stream coupling for CIS as the unicast client * Added broadcast source metadata update function * Added packing to unicast group create * Added packing field to broadcast source * Renamed BASS and BASS client to BAP Scan Delegator and BPA Broadcast Assistant * Added support for multiple subgroups for BAP broadcast sink * Replaced capabilities API with PACS * Host * Added a new ``BT_CONN_INTERVAL_TO_US`` utility macro. * Made the HCI fragmentation logic asynchronous, thus fixing a long-standing potential deadlock between data and control procedures. * Added the local advertising address to :c:func:`bt_le_ext_adv_get_info`. * Improved the implementation of :c:func:`bt_disable` to handle additional edge cases. * Removed all Bluetooth-specific logging macros and functionality, switching instead to the OS-wide ones. * Added a new :c:func:`bt_le_per_adv_sync_lookup_index` function. * Fixed missing calls to bt_le_per_adv_sync_cb.term when deleting a periodic advertising sync object. * Added local advertising address to bt_le_ext_adv_info. * Added the printing of function names by default when logging. * Changed the policy for advertising restart after disconnection, which is now done only for connections in the peripheral role. * Added a guard to prevent bonding to the same device more than once. * Refactored crypto functionality from SMP into its own folder, and added the h8 crypto function. * Changed the behavior when receiving an L2CAP K-frame larger than the MPS, disconnecting instead of truncating it. * Added a new :kconfig:option:`BT_ID_ALLOW_UNAUTH_OVERWRITE` that allows unauthorized bond overrides with multiple identities. * Added support for the object calculate checksum feature in OTS. * Changed back the semantics of :kconfig:option:`BT_PRIVACY` to refer to local RPA address generation. * Modified the SMP behavior when outside a pairing procedure. The stack no longer sends unnecessary Pairing Failed PDUs in that state. * ISO: Changed ISO seq_num to 16-bit * Mesh * Changed the default advertiser to be extended advertiser. * Made the provisioning feature set dynamic. * Made the maximum number of simultaneous Bluetooth connections that the mesh stack can use configurable via :kconfig:option:`BT_MESH_MAX_CONN`. * Changed the advertising duration calculation to avoid imprecise estimations. * Added the :kconfig:option:`BT_MESH_FRIEND_ADV_LATENCY` Kconfig option. * Controller * Implemented the Read/Write Connection Accept Timeout HCI commands. * Implemented the Sleep Clock Accuracy Update procedure. * Implemented additional ISO-related HCI commands. * Implemented ISO-AL SDU buffering and PDU release timeout. * Added support for handling fragmented AD without chaining PDUs. * Added support for multiple memory pools for advertising PDUs * Added support for retrying the automatic peripheral connection parameter update. * Added support for deferring anchor points moves using an external hook. * Added a new ``LL_ASSERT_MSG`` macro for verbose assertions. * Added long control PDU support. * Added support for Broadcast ISO encryption. * Added support for central CIS/CIG, including ULL and Nordic LLL. * Added support for peripheral CIS/CIG in the Nordic LLL. * Added the :kconfig:option:`BT_CTLR_SLOT_RESERVATION_UPDATE` Kconfig option. * Integrated ISOAL for ISO broadcast. Boards & SoC Support ******************** * Added support for these SoC series: * Atmel SAMC20, SAMC21 * Atmel SAME70Q19 * GigaDevice GD32L23X * GigaDevice GD32A50X * NXP S32Z2/E2 * Made these changes in other SoC series: * STM32F1: USB Prescaler configuration is now expected to be done using :dtcompatible: `st,stm32f1-pll-clock`: ``usbpre`` or :dtcompatible: `st,stm32f105-pll-clock`: ``otgfspre`` properties. * STM32F7/L4: Now supports configuring MCO. * STM32G0: Now supports FDCAN * STM32G4: Now supports power management (STOP0 and STOP1 low power modes). * STM32H7: Now supports PLL2, USB OTG HS and ULPI PHY. * STM32L5: Now supports RTC based :ref:`counter_api`. * STM32U5: Now supports :ref:`crypto_api` through AES device. * STM32F7/L4: Now supports configuring MCO. * Changes for ARC boards: * Multiple fixes to ``mdb-hw`` and ``mdb-nsim`` west runners to improve usability * Added ``nsim_em11d`` board with DSP features (XY DSP with AGU and XY memory) * Fixed cy8c95xx I2C GPIO port init on HSDK board * Added SPI flash support on EM starter kit board * Multiple fixes for nSIM platform - configuration: adding of missing HW features or configurations sync * Improved creg_gpio platform driver - add pin_configure API * Added separate QEMU config ``qemu_arc_hs_xip`` for XIP testing * Added ``nsim_hs_sram``, ``nsim_hs_flash_xip`` nSIM platforms to verify various memory models * nSIM board documentation overhaul * Added support for these ARM boards: * Adafruit ItsyBitsy nRF52840 Express * Adafruit KB2040 * Atmel atsamc21n_xpro * GigaDevice GD32L233R-EVAL * GigaDevice GD32A503V-EVAL * nRF5340 Audio DK * Sparkfun pro micro RP2040 * Arduino Portenta H7 * SECO JUNO SBC-D23 (STM32F302) * ST Nucleo G070RB * ST Nucleo L4A6ZG * NXP X-S32Z27X-DC (DC2) * Added support for these ARM64 boards: * i.MX93 (Cortex-A) EVK board * Khadas Edge-V board * QEMU Virt KVM * Added support for these X86 boards: * Intel Raptor Lake CRB * Added support for these RISC-V boards: * Added LCD support for ``longan_nano`` board. * Made these changes in ARM boards: * sam4s_xplained: Enabled PWM * sam_e70_xplained: Added DMA devicetree entries for SPI * sam_v71_xult: Added DMA devicetree entries for SPI * tdk_robokit1: Added DMA devicetree entries for SPI * The scratch partition has been removed for the following Nordic boards and flash used by this area re-assigned to other partitions to free up space and rely upon the swap-using-move algorithm in MCUboot (which does not suffer from the same faults or stuck image issues as swap-using-scratch does): ``nrf21540dk_nrf52840`` ``nrf51dk_nrf51422`` ``nrf51dongle_nrf51422`` ``nrf52833dk_nrf52833`` ``nrf52840dk_nrf52811`` ``nrf52840dk_nrf52840`` ``nrf52840dongle_nrf52840`` ``nrf52dk_nrf52805`` ``nrf52dk_nrf52810`` ``nrf52dk_nrf52832`` ``nrf5340dk_nrf5340`` ``nrf9160dk_nrf52840`` ``nrf9160dk_nrf9160`` Note that MCUboot and MCUboot image updates from pre-Zephyr 3.3 might be incompatible with Zephyr 3.3 onwards and vice versa. * The default console for the ``nrf52840dongle_nrf52840`` board has been changed from physical UART (which is not connected to anything on the board) to use USB CDC instead. * Forced configuration of FPU was removed from following boards: ``stm32373c_eval`` ``stm32f3_disco`` * On STM32 boards, configuration of USB, SDMMC and entropy devices that generally expect a 48MHz clock is now done using device tree. When available, HSI48 is enabled and configured as domain clock for these devices, otherwise PLL_Q output or MSI is used. On some boards, previous PLL SAI configuration has been changed to above options, since PLL SAI cannot yet be configured using device tree. * Made these changes in other boards: * The nrf52_bsim (natively simulated nRF52 device with BabbleSim) now models a nRF52833 instead of a nRF52832 device * Added support for these following shields: * Adafruit PCA9685 * nPM6001 EK * nPM1100 EK * Semtech SX1262MB2DAS * Sparkfun MAX3421E Build system and infrastructure ******************************* * Code relocation * ``zephyr_code_relocate`` API has changed to accept a list of files to relocate and a location to place the files. * Sysbuild * Issue with duplicate sysbuild image name causing an infinite cmake loop has been fixed. * Issue with board revision not being passed to sysbuild images has been fixed. * Application specific configurations of sysbuild controlled images. * Userspace * Userspace option to disable using the ``relax`` linker option has been added. * Tools * Static code analyser (SCA) tool support has been added. Drivers and Sensors ******************* * ADC * STM32: Now Supports sequencing multiple channels into a single read. * Fixed a problem in :c:macro:`ADC_CHANNEL_CFG_DT` that forced users to add artificial ``input-positive`` property in nodes related to ADC drivers that do not use configurable analog inputs when such drivers were used together with an ADC driver that uses such input configuration. * Added driver for TI CC13xx/CC26xx family. * Added driver for Infineon XMC4xxx family. * Added driver for ESP32 SoCs. * Battery-backed RAM * STM32: Added driver to enable support for backup registers from RTC. * CAN * Added RX overflow counter statistics support (STM32 bxCAN, Renesas R-Car, and NXP FlexCAN). * Added support for TWAI on ESP32-C3. * Added support for multiple MCP2515 driver instances. * Added Kvaser PCIcan driver and support for using it under QEMU. * Made the fake CAN test driver generally available. * Added support for compiling the Native Posix Linux CAN driver against Linux kernel headers prior to v5.14. * Removed the CONFIG_CAN_HAS_RX_TIMESTAMP and CONFIG_CAN_HAS_CANFD Kconfig helper symbols. * Clock control * STM32: HSI48 can now be configured using device tree. * Counter * STM32 RTC based counter domain clock (LSE/SLI) should now be configured using device tree. * Added Timer based driver for GigaDevice GD32 SoCs. * Added NXP S32 System Timer Module driver. * DAC * Added support for GigaDevice GD32 SoCs. * Added support for Espressif ESP32 SoCs. * DFU * Removed :c:macro:`BOOT_TRAILER_IMG_STATUS_OFFS` in favor a two new functions; :c:func:`boot_get_area_trailer_status_offset` and :c:func:`boot_get_trailer_status_offset` * Disk * STM32 SD host controller clocks are now configured via devicetree. * Zephyr flash disks are now configured using the :dtcompatible:`zephyr,flash-disk` devicetree binding * Flash disks can be marked as read only by setting the ``read-only`` property on the linked flash device partition. * DMA * Adjusted incorrect dma1 clock source for GD32 gd32vf103 SoC. * Atmel SAM: Added support to select fixed or increment address mode when using peripherals to memory or memory to peripheral transfers. * STM32 DMA variable scope cleanups * Intel GPDMA linked list transfer descriptors appropriately aligned to 64 byte addresses * Intel GPDMA fixed bug in transfer configuration to initialize cfg_hi and cfg_lo * STM32 DMA Support for the STM32MP1 series * SAM XDMAC fixes to enable usage with SPI DMA transfers * Intel GPDMA fixed to return errors on dma stop * Intel GPDMA disabled interrupts when unneeded * Intel GPDMA fixed for register/ip ownership * STM32U5 GPDMA bug fix for busy flag * STM32U5 Suspend and resume features added * Intel GPDMA Report total bytes read/written (linear link position) in dma status * DMA API get attribute function added, added attributes for scatter/gather blocks available to Intel HDA and Intel GPDMA drivers. * Intel GPDMA Power management functionality added * Intel HDA Power management functionality added * GD32 Slot used for peripheral selection * GD32 memory to memory support added * ESP32C3 GDMA driver added * Intel HDA underrun/overrun (xrun) handling and reporting added * Intel GPDMA underrun/overrun (xrun) handling nad reporting added * DMA API start/stop are defined to be repeatable callable with test cases added. STM32 DMA, Intel HDA, and Intel GPDMA all comply with the contract after patches. * NXP EDMA Unused mutex removed * EEPROM * Added fake EEPROM driver for testing purposes. * Ethernet * STM32: Default Mac address configuration is now uid based. Optionally, user can configure it to be random or provide its own address using device tree. * STM32: Added support for STM32Cube HAL Ethernet API V2 on F4/F7/H7. By default disabled, it can be enabled with :kconfig:option:`CONFIG_ETH_STM32_HAL_API_V2`. * STM32: Added ethernet support on STM32F107 devices. * STM32: Now supports multicast hash filtering in the MAC. It can be enabled using :kconfig:option:`CONFIG_ETH_STM32_MULTICAST_FILTER`. * STM32: Now supports statistics logging through :kconfig:option:`CONFIG_NET_STATISTICS_ETHERNET`. Requires use of HAL Ethernet API V2. * Flash * Flash: Moved CONFIG_FLASH_FLEXSPI_XIP into the SOC level due to the flexspi clock initialization occurring in the SOC level. * NRF: Added CONFIG_SOC_FLASH_NRF_TIMEOUT_MULTIPLIER to allow tweaking the timeout of flash operations. * spi_nor: Added 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. * spi_nor: Added check if the flash is busy during init. This used to cause the flash device to be unavailable until the system was restarted. The fix waits for the flash to become ready before continuing. In cases where a full flash erase was started before a restart, this might result in several minutes of waiting time (depending on flash size and erase speed). * rpi_pico: Added a flash driver for the Raspberry Pi Pico platform. * STM32 OSPI: sfdp-bfp table and jedec-id can now be read from device tree and override the flash content if required. * STM32 OSPI: Now supports DMA transfer on STM32U5. * STM32: Flash driver was revisited to simplify reuse of driver for new series, taking advantage of device tree compatibles. * FPGA * Added preliminary support for the Lattice iCE40. * Added Qomu board sample. * GPIO * Atmel SAM: Added support to configure Open-Drain pins * Added driver for nPM6001 PMIC GPIOs * Added NXP S32 GPIO (SIUL2) driver * hwinfo * Added hwinfo_get_device_id for ESP32-C3 * Added reset cause for iwdg and wwdg for STM32H7 and MP1 * I2C * SAM0 Fixed spurious trailing data by moving stop condition from thread into ISR * I2C Shell command adds ability to configure bus speed through `i2c speed` * ITE usage of instruction local memory support * NPCX bus recovery on transaction timeout * ITE log status of registers on transfer failure * ESP32 enabled configuring a hardware timeout to account for longer durations of clock stretching * ITE fixed bug where an operation was done outside of the driver mutex * NRFX TWIM Made transfer timeout configurable * DW Bug fix for clearing FIFO on initialization * NPCX simplified smb bank register usage * NXP LPI2C enabled target mode * NXP FlexComm Added semaphore for shared usage of bus * I2C Added support for dumping messages in the log for all transactions, reads and writes * STM32: Slave configuration now supports 10-bit addressing. * STM32: Now support power management. 3 modes supported: :kconfig:option:`CONFIG_PM`, :kconfig:option:`CONFIG_PM_DEVICE`, :kconfig:option:`CONFIG_PM_DEVICE_RUNTIME`. * STM32: Domain clock can now be configured using device tree * I3C * Added a new target device API :c:func:`i3c_target_tx_write` to explicit write to TX FIFO. * GETMRL and GETMWL are both optional in :c:func:`i3c_device_basic_info_get` as MRL and MWL are optional according to I3C specification. * Added a new driver to support Cadence I3C controller. * Interrupt Controller * STM32: Driver configuration and initialization is now based on device tree * Added NXP S32 External Interrupt Controller (SIUL2) driver. * IPM * ipm_stm32_ipcc: fixed an issue where interrupt mask is not cleaned correctly, resulting in infinite TXF interrupts. * MBOX * Added NXP S32 Message Receive Unit (MRU) driver. * PCIE * Support for accessing I/O BARs, which was previously removed, is back. * Added new API :c:func:`pcie_scan` to scan for devices. * This iterates through the buses and devices which are expected to exist. The old method was to try all possible combination of buses and devices to determine if there is a device there. :c:func:`pci_init` and :c:func:`pcie_bdf_lookup` have been updated to use this new API. * :c:func:`pcie_scan` also introduces a callback mechanism for when a new device has been discovered. * Pin control * Common pin control properties are now defined at root level in a single file: :zephyr_file:`dts/bindings/pinctrl/pincfg-node.yaml`. Pin control bindings are expected to include it at the level they need. For example, drivers using the grouping representation approach need to include it at grandchild level, while drivers using the node approach need to include it at the child level. This change will only impact out-of-tree pin control drivers, since all in-tree drivers have been updated. * Added NXP S32 SIUL2 driver * Added Nuvoton NuMicro driver * Added Silabs Gecko driver * Added support for i.MX93 in the i.MX driver * Added support for GD32L23x/GD32A50x in the Gigadevice driver * PWM * Atmel SAM: Added support to select pin polarity * Added driver for NXP PCA9685 LED controller * Regulators * Completed an API overhaul so that devices like PMICs can be supported. The API now offers a clear and concise API that allows to perform the following operations: - Enable/disable regulator output (reference counted) - List supported voltages - Get/set operating voltage - Get/set maximum current - Get/set operating mode - Obtain errors, e.g. overcurrent. The devicetree part maintains compatibility with Linux bindings, for example, the following properties are well supported: - ``regulator-boot-on`` - ``regulator-always-on`` - ``regulator-min-microvolt`` - ``regulator-max-microvolt`` - ``regulator-min-microamp`` - ``regulator-max-microamp`` - ``regulator-allowed-modes`` - ``regulator-initial-mode`` A common driver class layer takes care of the common functionality so that driver implementations are kept simple. For example, allowed voltage ranges are verified before calling into the driver. An experimental parent API to configure DVS (Dynamic Voltage Scaling) has also been introduced. * Refactored NXP PCA9420 driver to align with the new API. * Added support for nPM6001 PMIC (LDO and BUCK converters). * Added support for nPM1100 PMIC (allows to dynamically change its mode). * Added a new test that allows to verify regulator output voltage using the ADC API. * Added a new test that checks API behavior provided we have a well-behaved driver. * Reset * STM32: STM32 reset driver is now available. Devices reset line configuration should be done using device tree. * SDHC * i.MX RT USDHC: - Support HS400 and HS200 mode. This mode is used with eMMC devices, and will enable high speed operation for those cards. - Support DMA operation on SOCs that do not support non-cacheable memory, such as the RT595. DMA will enable higher performance SD modes, such as HS400 and SDR104, to reliably transfer data using the SD host controller * Sensor * Refactored all drivers to use :c:macro:`SENSOR_DEVICE_DT_INST_DEFINE` to enable a new sensor info iterable section and shell command. See :kconfig:option:`CONFIG_SENSOR_INFO`. * Refactored all sensor devicetree bindings to inherit new base sensor device properties in :zephyr_file:`dts/bindings/sensor/sensor-device.yaml`. * Added sensor attribute support to the shell. * Added ESP32 and RaspberryPi Pico die temperature sensor drivers. * Added TDK InvenSense ICM42688 six axis IMU driver. * Added TDK InvenSense ICP10125 pressure and temperature sensor driver. * Added AMS AS5600 magnetic angle sensor driver. * Added AMS AS621x temperature sensor driver. * Added HZ-Grow R502A fingerprint sensor driver. * Enhanced FXOS8700, FXAS21002, and BMI270 drivers to support SPI in addition to I2C. * Enhanced ST LIS2DW12 driver to support free fall detection. * rpi_pico: Added die temperature sensor driver. * STM32 family Quadrature Decoder driver was added. Only enabled on STM32F4 for now. * Serial * Atmel SAM: UART/USART: Added support to configure driver at runtime * STM32: DMA now supported on STM32U5 series. * uart_altera_jtag: added support for Nios-V UART. * uart_esp32: added support asynchronous operation. * uart_gecko: added support for pinctrl. * uart_mchp_xec: now supports UART on MEC15xx SoC. * uart_mcux_flexcomm: added support for runtime configuration. * uart_mcux_lpuart: added support for RS-485. * uart_numicro: uses pinctrl to configure UART pins. * uart_pl011: added support for pinctrl. * uart_rpi_pico: added support for runtime configuration. * uart_xmc4xxx: added support for interrupt so it can now be interrupt driven. Also added support for FIFO. * New UART drivers are added: * Cadence IP6528 UART. * NXP S32 LINFlexD UART. * OpenTitan UART. * QuickLogic USBserialport_S3B. * SPI * Added dma support for GD32 driver. * Atmel SAM: * Added support to transfers using DMA. * Added support to loopback mode for testing purposes. * Added NXP S32 SPI driver. * Timer * Corrected CPU numbering on SMP RISC-V systems using the mtime device * Added support for OpenTitan's privileged timer device to riscv_machine_timer * Refactored SYS_CLOCK_EXISTS such that it always matches the existence of a timer device in kconfig * Significant rework to nrf_rtc_timer with multiple fixes * Fixed prescaler correction in stm32_lptim driver and fix race with auto-reload * USB * STM32F1: Clock bus configuration is not done automatically by driver anymore. It is user's responsibility to configure the proper bus prescaler using clock_control device tree node to achieve a 48MHz bus clock. Note that, in most cases, core clock is 72MHz and default prescaler configuration is set to achieve 48MHz USB bus clock. Prescaler only needs to be configured manually when core clock is already 48MHz. * STM32 (non F1): Clock bus configuration is now expected to be done in device tree using ``clocks`` node property. When a dedicated HSI 48MHz clock is available on target, is it configured by default as the USB bus clock, but user has the ability to select another 48MHz clock source. When no HSI48 is available, a specific 48MHz bus clock source should be configured by user. * STM32: Now supports :c:func:`usb_dc_detach` and :c:func:`usb_dc_wakeup_request`. * STM32: Vbus sensing is now supported and determined based on the presence of the hardware detection pin(s) in the device tree. E.g: pinctrl-0 = <&usb_otg_fs_vbus_pa9 ...>; * RPi Pico: fixed buffer status handling, fixed infinite unhandled irq retriggers, fixed DATA PID toggle and control transfer handling. * NXP: Enabled high speed support, fixed endpoint buffer write operation. * nRF USBD: Removed HAL driver uninit on detach, fixed endpoints disable on USB stack disable. * Added new experimental USB device controller (UDC) API and implementation for nRF USBD, Kinetis USBFSOTG, and virtual controllers. * Added new experimental USB host controller (UDC) API and implementation for MAX3421E and virtual controllers. * Watchdog * Added driver for nPM6001 PMIC Watchdog. * Added free watchdog driver for GigaDevice GD32 SoCs. * Added window watchdog driver for GigaDevice GD32 SoCs. * Added NXP S32 Software Watchdog Timer driver. Networking ********** * CoAP: * Implemented insertion of a CoAP option at arbitrary position. * Ethernet: * Fixed AF_PACKET/SOCK_RAW/IPPROTO_RAW sockets on top of Ethernet L2. * Added support for setting Ethernet MAC address with net shell. * Added check for return values of the driver start/stop routines when bringing Ethernet interface up. * Added ``unknown_protocol`` statistic for packets with unrecognized protocol field, instead of using ``error`` for this purpose. * Added NXP S32 NETC Ethernet driver. * HTTP: * Reworked HTTP headers: moved methods to a separate header, added status response codes header and grouped HTTP headers in a subdirectory. * Used :c:func:`zsock_poll` for HTTP timeout instead of a delayed work. * ICMPv4: * Added support to autogenerate Echo Request payload. * ICMPv6: * Added support to autogenerate Echo Request payload. * Fixed stats counting for ND packets. * IEEE802154: * Improved short address support. * Improved IEEE802154 context thread safety. * Decoupled IEEE802154 parameters from :c:struct:`net_pkt` into :c:struct:`net_pkt_cb_ieee802154`. * Multiple other minor fixes/improvements. * IPv4: * IPv4 packet fragmentation support has been added, this allows large packets to be split up before sending or reassembled during receive for packets that are larger than the network device MTU. This is disabled by default but can be enabled with :kconfig:option:`CONFIG_NET_IPV4_FRAGMENT`. * Added support for setting/reading DSCP/ECN fields. * Fixed packet leak in IPv4 address auto-configuration procedure. * Added support for configuring IPv4 addresses with ``net ipv4`` shell command. * Zephyr now adds IGMP all systems 224.0.0.1 address to all IPv4 network interfaces by default. * IPv6: * Made it possible to add route to router's link local address. * Added support for setting/reading DSCP/ECN fields. * Improved test coverage for IPv6 fragmentation. * Added support for configuring IPv6 addresses with ``net ipv6`` shell command. * Added support for configuring IPv6 routes with ``net route`` shell command. * LwM2M: * Renamed ``LWM2M_RD_CLIENT_EVENT_REG_UPDATE_FAILURE`` to :c:macro:`LWM2M_RD_CLIENT_EVENT_REG_TIMEOUT`. This event is now used in case of registration timeout. * Added new LwM2M APIs for historical data storage for LwM2M resource. * Updated LwM2M APIs to use ``const`` pointers when possible. * Added shell command to lock/unlock LwM2M registry. * Added shell command to enable historical data cache for a resource. * Switched to use ``zsock_`` functions internally. Added uCIFI LPWAN (ID 3412) object implementation. * Added BinaryAppDataContainer (ID 19) object implementation. * Deprecated :kconfig:option:`CONFIG_LWM2M_RD_CLIENT_SUPPORT`, as it's now considered as an integral part of the LwM2M library. * Added support for SenML Object Link data type. * Fixed a bug causing incorrect ordering of the observation paths. * Deprecated string based LwM2M APIs. LwM2M APIs now use :c:struct:`lwm2m_obj_path` to represent object/resource paths. * Refactored ``lwm2m_client`` sample by splitting specific functionalities into separate modules. * Multiple other minor fixes within the LwM2M library. * Misc: * Updated various networking test suites to use the new ztest API. * Added redirect support for ``big_http_download`` sample and updated the server URL for TLS variant. * Fixed memory leak in ``net udp`` shell command. * Fixed cloning of LL address for :c:struct:`net_pkt`. * Added support for QoS and payload size setting in ``net ping`` shell command. * Added support for aborting ``net ping`` shell command. * Introduced carrier and dormant management on network interfaces. Separated interface administrative state from operational state. * Improved DHCPv4 behavior with multiple DHCPv4 servers in the network. * Fixed net_mgmt event size calculation. * Added :kconfig:option:`CONFIG_NET_LOOPBACK_MTU` option to configure loopback interface MTU. * Reimplemented the IP/UDP/TCP checksum calculation to speed up the processing. * Removed :kconfig:option:`CONFIG_NET_CONFIG_SETTINGS` use from test cases to improve test execution on real platforms. * Added MQTT-SN library and sample. * Fixed variable buffer length configuration (:kconfig:option:`CONFIG_NET_BUF_VARIABLE_DATA_SIZE`). * Fixed IGMPv2 membership report destination address. * Added mutex protection for the connection list handling. * Separated user data pointer from FIFO reserved space in :c:struct:`net_context`. * Added input validation for ``net pkt`` shell command. * OpenThread: * Implemented PSA support for ECDSA API. * Fixed :c:func:`otPlatRadioSetMacKey` when asserts are disabled. * Deprecated :c:func:`openthread_set_state_changed_cb` in favour of more generic :c:func:`openthread_state_changed_cb_register`. * Implemented diagnostic GPIO commands. * SNTP: * Switched to use ``zsock_`` functions internally. Fixed the library operation with IPv4 disabled. * Sockets: * Fixed a possible memory leak on failed TLS socket creation. * TCP: * Extended the default TCP out-of-order receive queue timeout to 2 seconds. * Reimplemented TCP ref counting, to prevent situation, where TCP connection context could be released prematurely. * Websockets: * Reimplemented websocket receive routine to fix several issues. * Implemented proper websocket close procedure. * Fixed a bug where websocket would overwrite the mutex used by underlying TCP socket. * Wi-Fi: * Added support for power save configuration. * Added support for regulatory domain configuration. * Added support for power save timeout configuration. * zperf * Added option to set QoS for zperf. * Fixed out of order/lost packets statistics. * Defined a public API for the library to allow throughput measurement without shell enabled. * Added an option for asynchronous upload. USB *** * New experimental USB support: * Added new USB device stack (device_next), class implementation for CDC ACM and BT HCI USB transport layer. * Added initial support for USB host * USB device stack (device): * Removed transfer cancellation on bus suspend. * Reworked disabling all endpoints on stack disable to allow re-enabling USB device stack. * Revised endpoint enable/disable on alternate setting. * Improved USB DFU support with WinUSB on Windows. * Added check to prevent recursive logging loop and allowed to send more than one byte using poll out in CDC ACM class implementation. * Corrected IAD and interface descriptors, removed unnecessary CDC descriptors, and fixed packet reception in RNDIS ethernet implementation. * Implemented cache synchronization after write operations in USB MSC class. Devicetree ********** API === New general-purpose macros: - :c:macro:`DT_FOREACH_PROP_ELEM_SEP_VARGS` - :c:macro:`DT_FOREACH_PROP_ELEM_SEP` - :c:macro:`DT_INST_FOREACH_PROP_ELEM_SEP_VARGS` - :c:macro:`DT_INST_FOREACH_PROP_ELEM_SEP` - :c:macro:`DT_INST_GPARENT` - :c:macro:`DT_NODE_MODEL_BY_IDX_OR` - :c:macro:`DT_NODE_MODEL_BY_IDX` - :c:macro:`DT_NODE_MODEL_HAS_IDX` - :c:macro:`DT_NODE_MODEL_OR` New special-purpose macros introduced for the GPIO hogs feature (see :zephyr_file:`drivers/gpio/gpio_hogs.c`): - :c:macro:`DT_GPIO_HOG_FLAGS_BY_IDX` - :c:macro:`DT_GPIO_HOG_PIN_BY_IDX` - :c:macro:`DT_NUM_GPIO_HOGS` The following deprecated macros were removed: - ``DT_CHOSEN_ZEPHYR_ENTROPY_LABEL`` - ``DT_CHOSEN_ZEPHYR_FLASH_CONTROLLER_LABEL`` Bindings ======== New bindings: - Generic or vendor-independent: - :dtcompatible:`usb-c-connector` - :dtcompatible:`usb-ulpi-phy` - AMS AG (ams): - :dtcompatible:`ams,as5600` - :dtcompatible:`ams,as6212` - Synopsys, Inc. (formerly ARC International PLC) (arc): - :dtcompatible:`arc,xccm` - :dtcompatible:`arc,yccm` - ARM Ltd. (arm): - :dtcompatible:`arm,cortex-a55` - :dtcompatible:`arm,ethos-u` - ASPEED Technology Inc. (aspeed): - :dtcompatible:`aspeed,ast10x0-reset` - Atmel Corporation (atmel): - :dtcompatible:`atmel,samc2x-gclk` - :dtcompatible:`atmel,samc2x-mclk` - Bosch Sensortec GmbH (bosch): - :dtcompatible:`bosch,bmi270` - :dtcompatible:`bosch,bmi270` - Cadence Design Systems Inc. (cdns): - :dtcompatible:`cdns,i3c` - :dtcompatible:`cdns,uart` - Espressif Systems (espressif): - :dtcompatible:`espressif,esp32-adc` - :dtcompatible:`espressif,esp32-dac` - :dtcompatible:`espressif,esp32-eth` - :dtcompatible:`espressif,esp32-gdma` - :dtcompatible:`espressif,esp32-mdio` - :dtcompatible:`espressif,esp32-temp` - GigaDevice Semiconductor (gd): - :dtcompatible:`gd,gd322-dma` has new helper macros to easily setup the ``dma-cells`` property. - :dtcompatible:`gd,gd32-dma-v1` - :dtcompatible:`gd,gd32-fwdgt` - :dtcompatible:`gd,gd32-wwdgt` - Hangzhou Grow Technology Co., Ltd. (hzgrow): - :dtcompatible:`hzgrow,r502a` - Infineon Technologies (infineon): - :dtcompatible:`infineon,xmc4xxx-adc` - :dtcompatible:`infineon,xmc4xxx-flash-controller` - :dtcompatible:`infineon,xmc4xxx-intc` - :dtcompatible:`infineon,xmc4xxx-nv-flash` - Intel Corporation (intel): - :dtcompatible:`intel,adsp-communication-widget` - :dtcompatible:`intel,adsp-dfpmcch` - :dtcompatible:`intel,adsp-dfpmccu` - :dtcompatible:`intel,adsp-mem-window` - :dtcompatible:`intel,adsp-sha` - :dtcompatible:`intel,adsp-timer` - :dtcompatible:`intel,hda-dai` - :dtcompatible:`intel,raptor-lake` - InvenSense Inc. (invensense): - :dtcompatible:`invensense,icm42688` - :dtcompatible:`invensense,icp10125` - ITE Tech. Inc. (ite): - :dtcompatible:`ite,it8xxx2-espi` - :dtcompatible:`ite,it8xxx2-gpiokscan` - :dtcompatible:`ite,it8xxx2-ilm` - :dtcompatible:`ite,it8xxx2-shi` - :dtcompatible:`ite,it8xxx2-usbpd` - Kvaser (kvaser): - :dtcompatible:`kvaser,pcican` - Lattice Semiconductor (lattice): - :dtcompatible:`lattice,ice40-fpga` - lowRISC Community Interest Company (lowrisc): - :dtcompatible:`lowrisc,machine-timer` - :dtcompatible:`lowrisc,opentitan-uart` - Maxim Integrated Products (maxim): - :dtcompatible:`maxim,max3421e_spi` - Microchip Technology Inc. (microchip): - :dtcompatible:`microchip,xec-bbled` - :dtcompatible:`microchip,xec-ecs` - :dtcompatible:`microchip,xec-espi-saf-v2` - :dtcompatible:`microchip,xec-qmspi-full-duplex` - Nordic Semiconductor (nordic): - :dtcompatible:`nordic,npm1100` - :dtcompatible:`nordic,npm6001` - :dtcompatible:`nordic,npm6001-gpio` - :dtcompatible:`nordic,npm6001-regulator` - :dtcompatible:`nordic,npm6001-wdt` - Nuvoton Technology Corporation (nuvoton): - :dtcompatible:`nuvoton,npcx-kscan` - :dtcompatible:`nuvoton,npcx-sha` - :dtcompatible:`nuvoton,npcx-shi` - :dtcompatible:`nuvoton,numicro-gpio` - :dtcompatible:`nuvoton,numicro-pinctrl` - NXP Semiconductors (nxp): - :dtcompatible:`nxp,css-v2` - :dtcompatible:`nxp,fxas21002` - :dtcompatible:`nxp,fxos8700` - :dtcompatible:`nxp,imx-flexspi-aps6408l` - :dtcompatible:`nxp,imx-flexspi-s27ks0641` - :dtcompatible:`nxp,imx-mu-rev2` - :dtcompatible:`nxp,imx93-pinctrl` - :dtcompatible:`nxp,mcux-qdec` - :dtcompatible:`nxp,mcux-xbar` - :dtcompatible:`nxp,pca9420` - :dtcompatible:`nxp,pca9685-pwm` - :dtcompatible:`nxp,pcf8574` - :dtcompatible:`nxp,pdcfg-power` - :dtcompatible:`nxp,s32-gpio` - :dtcompatible:`nxp,s32-linflexd` - :dtcompatible:`nxp,s32-mru` - :dtcompatible:`nxp,s32-netc-emdio` - :dtcompatible:`nxp,s32-netc-psi` - :dtcompatible:`nxp,s32-netc-vsi` - :dtcompatible:`nxp,s32-siul2-eirq` - :dtcompatible:`nxp,s32-spi` - :dtcompatible:`nxp,s32-swt` - :dtcompatible:`nxp,s32-sys-timer` - :dtcompatible:`nxp,s32ze-pinctrl` - OpenThread (openthread): - :dtcompatible:`openthread,config` - QuickLogic Corp. (quicklogic): - :dtcompatible:`quicklogic,usbserialport-s3b` - Raspberry Pi Foundation (raspberrypi): - :dtcompatible:`raspberrypi,pico-flash-controller` - :dtcompatible:`raspberrypi,pico-temp` - Richtek Technology Corporation (richtek): - :dtcompatible:`richtek,rt1718s` - :dtcompatible:`richtek,rt1718s-gpio-port` - Smart Battery System (sbs): - :dtcompatible:`sbs,sbs-gauge-new-api` - Silicon Laboratories (silabs): - :dtcompatible:`silabs,gecko-pinctrl` - :dtcompatible:`silabs,gecko-stimer` - Synopsys, Inc. (snps): - :dtcompatible:`snps,ethernet-cyclonev` - SparkFun Electronics (sparkfun): - :dtcompatible:`sparkfun,pro-micro-gpio` - STMicroelectronics (st): - :dtcompatible:`st,stm32-bbram` - :dtcompatible:`st,stm32-qdec` - :dtcompatible:`st,stm32-rcc-rctl` - :dtcompatible:`st,stm32wb-rf` - Texas Instruments (ti): - :dtcompatible:`ti,cc13xx-cc26xx-adc` - :dtcompatible:`ti,cc13xx-cc26xx-watchdog` - :dtcompatible:`ti,tca6424a` - A stand-in for a real vendor which can be used in examples and tests (vnd): - :dtcompatible:`vnd,emul-tester` - Zephyr-specific binding (zephyr): - :dtcompatible:`zephyr,ec-host-cmd-periph-espi` - :dtcompatible:`zephyr,fake-can` - :dtcompatible:`zephyr,fake-eeprom` - :dtcompatible:`zephyr,fake-regulator` - :dtcompatible:`zephyr,flash-disk` - :dtcompatible:`zephyr,gpio-emul-sdl` - :dtcompatible:`zephyr,gpio-keys` - :dtcompatible:`zephyr,ipc-icmsg-me-follower` - :dtcompatible:`zephyr,ipc-icmsg-me-initiator` - :dtcompatible:`zephyr,mmc-disk` - :dtcompatible:`zephyr,psa-crypto-rng` - :dtcompatible:`zephyr,udc-virtual` - :dtcompatible:`zephyr,uhc-virtual` - :dtcompatible:`zephyr,usb-c-vbus-adc` Removed bindings: - Generic or vendor-independent: - ``regulator-pmic`` - Intel Corporation (intel): - ``intel,adsp-lps`` - NXP Semiconductors (nxp): - ``nxp,imx-flexspi-hyperram`` - STMicroelectronics (st): - ``st,stm32f0-flash-controller`` - ``st,stm32f3-flash-controller`` - ``st,stm32l0-flash-controller`` - ``st,stm32l1-flash-controller`` - ``st,stm32u5-flash-controller`` Modified bindings: - Generic or vendor-independent: - All sensor devices now have a ``friendly-name`` property, which is a human-readable string describing the sensor. See :zephyr_file:`dts/bindings/sensor/sensor-device.yaml` for more information. - All DMA controller devices have had their ``dma-buf-alignment`` properties renamed to ``dma-buf-addr-alignment``. Additionally, all DMA controller devices have new ``dma-buf-size-alignment`` and ``dma-copy-alignment`` properties. See :zephyr_file:`dts/bindings/dma/dma-controller.yaml` for more information. - :dtcompatible:`ns16550`: - new property: ``vendor-id`` - new property: ``device-id`` - property ``reg`` is no longer required - :dtcompatible:`pci-host-ecam-generic`: - new property: ``interrupt-map-mask`` - new property: ``interrupt-map`` - new property: ``bus-range`` - :dtcompatible:`regulator-fixed`: - removed property: ``supply-gpios`` - removed property: ``vin-supply`` - :dtcompatible:`gpio-keys`: - new property: ``debounce-interval-ms`` - Altera Corp. (altr): - :dtcompatible:`altr,jtag-uart`: - new property: ``write-fifo-depth`` - ARM Ltd. (arm): - :dtcompatible:`arm,pl011`: - new property: ``pinctrl-0`` - new property: ``pinctrl-1`` - new property: ``pinctrl-2`` - new property: ``pinctrl-3`` - new property: ``pinctrl-4`` - new property: ``pinctrl-names`` - Atmel Corporation (atmel): - :dtcompatible:`atmel,sam-pwm`: - specifier cells for space "pwm" are now named: ['channel', 'period', 'flags'] (old value: ['channel', 'period']) - property ``#pwm-cells`` const value changed from 2 to 3 - :dtcompatible:`atmel,sam-spi`: - new property: ``loopback`` - Espressif Systems (espressif): - :dtcompatible:`espressif,esp32-twai`: - property ``clkout-divider`` enum value changed from [1, 2, 4, 6, 8, 10, 12, 14] to None - :dtcompatible:`espressif,esp32-i2c`: - new property: ``scl-timeout-us`` - :dtcompatible:`espressif,esp32-spi`: - new property: ``dma-enabled`` - new property: ``dma-clk`` - new property: ``dma-host`` - removed property: ``dma`` - GigaDevice Semiconductor (gd): - :dtcompatible:`gd,gd32-dma`: - specifier cells for space "dma" are now named: ['channel', 'config'] (old value: ['channel']) - new property: ``gd,mem2mem`` - removed property: ``resets`` - removed property: ``reset-names`` - property ``#dma-cells`` const value changed from 1 to 2 - ILI Technology Corporation (ILITEK) (ilitek): - :dtcompatible:`ilitek,ili9341` (on spi bus): - property ``disctrl`` default value changed from [10, 130, 39] to [10, 130, 39, 4] - Infineon Technologies (infineon): - :dtcompatible:`infineon,xmc4xxx-uart`: - new property: ``fifo-start-offset`` - new property: ``fifo-tx-size`` - new property: ``fifo-rx-size`` - Intel Corporation (intel): - :dtcompatible:`intel,adsp-power-domain`: - removed property: ``lps`` - :dtcompatible:`intel,e1000`: - new property: ``vendor-id`` - new property: ``device-id`` - property ``reg`` is no longer required - :dtcompatible:`intel,dai-dmic`: - new property: ``fifo`` - property ``shim`` type changed from array to int - ITE Tech. Inc. (ite): - :dtcompatible:`ite,it8xxx2-pinctrl-func`: - new property: ``pp-od-mask`` - new property: ``pullup-mask`` - new property: ``gpio-group`` - property ``volt-sel-mask`` is no longer required - property ``func4-gcr`` is no longer required - property ``func3-en-mask`` is no longer required - property ``func3-gcr`` is no longer required - property ``func4-en-mask`` is no longer required - property ``volt-sel`` is no longer required - JEDEC Solid State Technology Association (jedec): - :dtcompatible:`jedec,spi-nor` (on spi bus): - new property: ``mxicy,mx25r-power-mode`` - Microchip Technology Inc. (microchip): - :dtcompatible:`microchip,xec-uart`: - new property: ``wakerx-gpios`` - :dtcompatible:`microchip,xec-pcr`: - new property: ``clk32kmon-period-min`` - new property: ``clk32kmon-period-max`` - new property: ``clk32kmon-duty-cycle-var-max`` - new property: ``clk32kmon-valid-min`` - new property: ``xtal-enable-delay-ms`` - new property: ``pll-lock-timeout-ms`` - new property: ``clkmon-bypass`` - new property: ``internal-osc-disable`` - new property: ``pinctrl-0`` - new property: ``pinctrl-names`` - new property: ``pinctrl-1`` - new property: ``pinctrl-2`` - new property: ``pinctrl-3`` - new property: ``pinctrl-4`` - property ``interrupts`` is no longer required - :dtcompatible:`microchip,xec-qmspi-ldma`: - new property: ``port-sel`` - new property: ``chip-select`` - removed property: ``port_sel`` - removed property: ``chip_select`` - property ``lines`` enum value changed from None to [1, 2, 4] - Nordic Semiconductor (nordic): - :dtcompatible:`nordic,nrf21540-fem`: - new property: ``supply-voltage-mv`` - :dtcompatible:`nordic,qspi-nor` (on qspi bus): - new property: ``mxicy,mx25r-power-mode`` - Nuvoton Technology Corporation (nuvoton): - :dtcompatible:`nuvoton,numicro-uart`: - new property: ``pinctrl-0`` - new property: ``pinctrl-1`` - new property: ``pinctrl-2`` - new property: ``pinctrl-3`` - new property: ``pinctrl-4`` - new property: ``pinctrl-names`` - :dtcompatible:`nuvoton,adc-cmp`: - new property: ``status`` - new property: ``compatible`` - new property: ``reg`` - new property: ``reg-names`` - new property: ``interrupts`` - new property: ``interrupts-extended`` - new property: ``interrupt-names`` - new property: ``interrupt-parent`` - new property: ``label`` - new property: ``clocks`` - new property: ``clock-names`` - new property: ``#address-cells`` - new property: ``#size-cells`` - new property: ``dmas`` - new property: ``dma-names`` - new property: ``io-channel-names`` - new property: ``mboxes`` - new property: ``mbox-names`` - new property: ``wakeup-source`` - new property: ``power-domain`` - NXP Semiconductors (nxp): - :dtcompatible:`nxp,kinetis-lpuart`: - new property: ``nxp,rs485-mode`` - new property: ``nxp,rs485-de-active-low`` - :dtcompatible:`nxp,fxas21002` (on i2c bus): - new property: ``reset-gpios`` - :dtcompatible:`nxp,imx-pwm`: - specifier cells for space "pwm" are now named: ['channel', 'period', 'flags'] (old value: ['channel', 'period']) - new property: ``nxp,prescaler`` - new property: ``nxp,reload`` - property ``#pwm-cells`` const value changed from 2 to 3 - :dtcompatible:`nxp,imx-usdhc`: - new property: ``mmc-hs200-1_8v`` - new property: ``mmc-hs400-1_8v`` - :dtcompatible:`nxp,lpc-sdif`: - new property: ``mmc-hs200-1_8v`` - new property: ``mmc-hs400-1_8v`` - QEMU, a generic and open source machine emulator and virtualizer (qemu): - :dtcompatible:`qemu,ivshmem`: - new property: ``vendor-id`` - new property: ``device-id`` - Renesas Electronics Corporation (renesas): - :dtcompatible:`renesas,smartbond-uart`: - property ``current-speed`` enum value changed from [1200, 2400, 4800, 9600, 14400, 19200, 28800, 38400, 57600, 115200, 230400, 460800, 921600, 1000000] to [4800, 9600, 14400, 19200, 28800, 38400, 57600, 115200, 230400, 500000, 921600, 1000000, 2000000] - Silicon Laboratories (silabs): - :dtcompatible:`silabs,gecko-usart`: - new property: ``pinctrl-0`` - new property: ``pinctrl-1`` - new property: ``pinctrl-2`` - new property: ``pinctrl-3`` - new property: ``pinctrl-4`` - new property: ``pinctrl-names`` - property ``location-rx`` is no longer required - property ``location-tx`` is no longer required - property ``peripheral-id`` is no longer required - :dtcompatible:`silabs,gecko-gpio-port`: - property ``peripheral-id`` is no longer required - :dtcompatible:`silabs,gecko-spi-usart`: - new property: ``pinctrl-0`` - new property: ``pinctrl-1`` - new property: ``pinctrl-2`` - new property: ``pinctrl-3`` - new property: ``pinctrl-4`` - new property: ``pinctrl-names`` - property ``location-clk`` is no longer required - property ``location-rx`` is no longer required - property ``location-tx`` is no longer required - property ``peripheral-id`` is no longer required - Sitronix Technology Corporation (sitronix): - :dtcompatible:`sitronix,st7735r` (on spi bus): - new property: ``rgb-is-inverted`` - Synopsys, Inc. (snps): - :dtcompatible:`snps,designware-i2c`: - new property: ``vendor-id`` - new property: ``device-id`` - property ``reg`` is no longer required - STMicroelectronics (st): - :dtcompatible:`st,stm32-adc`: - the ``has-temp-channel``, ``has-vref-channel`` and ``has-vbat-channel`` properties were respectively replaced by ``temp-channel``, ``vref-channel`` and ``vbat-channel`` - :dtcompatible:`st,stm32-ethernet`: - the built-in driver for this compatible now supports the ``local-mac-address`` and ``zephyr,random-mac-address`` properties for setting MAC addresses, and the associated Kconfig options (``CONFIG_ETH_STM32_HAL_RANDOM_MAC``, ``CONFIG_ETH_STM32_HAL_USER_STATIC_MAC``) are now deprecated - :dtcompatible:`st,stm32-qspi-nor` (on qspi bus): - new property: ``reset-cmd`` - new property: ``reset-cmd-wait`` - :dtcompatible:`st,stm32-uart`: - new property: ``resets`` - new property: ``tx-rx-swap`` - new property: ``reset-names`` - :dtcompatible:`st,stm32-usart`: - new property: ``resets`` - new property: ``tx-rx-swap`` - new property: ``reset-names`` - :dtcompatible:`st,stm32-lpuart`: - new property: ``resets`` - new property: ``tx-rx-swap`` - new property: ``reset-names`` - :dtcompatible:`st,stm32-exti`: - new property: ``num-lines`` - new property: ``line-ranges`` - new property: ``interrupt-controller`` - new property: ``#interrupt-cells`` - property ``interrupts`` is now required - property ``interrupt-names`` is now required - :dtcompatible:`st,stm32-ospi`: - property ``clock-names`` is now required - :dtcompatible:`st,stm32f105-pll2-clock`: - new property: ``otgfspre`` - :dtcompatible:`st,stm32f105-pll-clock`: - new property: ``otgfspre`` - :dtcompatible:`st,stm32f100-pll-clock`: - new property: ``otgfspre`` - :dtcompatible:`st,stm32f1-pll-clock`: - property ``usbpre`` type changed from int to boolean - :dtcompatible:`st,stm32-lse-clock`: - new property: ``lse-bypass`` - :dtcompatible:`st,lis2dh12` (on i2c bus): - new property: ``anym-no-latch`` - new property: ``anym-mode`` - :dtcompatible:`st,lsm6dso` (on i2c bus): - new property: ``drdy-pulsed`` - :dtcompatible:`st,lis2dh` (on i2c bus): - new property: ``anym-no-latch`` - new property: ``anym-mode`` - :dtcompatible:`st,lsm303agr-accel` (on spi bus): - new property: ``anym-no-latch`` - new property: ``anym-mode`` - :dtcompatible:`st,lis3dh` (on i2c bus): - new property: ``anym-no-latch`` - new property: ``anym-mode`` - :dtcompatible:`st,lsm6dso` (on spi bus): - new property: ``drdy-pulsed`` - :dtcompatible:`st,lis2dw12` (on spi bus): - new property: ``odr`` - new property: ``ff-duration`` - new property: ``ff-threshold`` - :dtcompatible:`st,lsm6dso32` (on spi bus): - new property: ``drdy-pulsed`` - :dtcompatible:`st,lsm303dlhc-accel` (on i2c bus): - new property: ``anym-no-latch`` - new property: ``anym-mode`` - :dtcompatible:`st,lis2dh` (on spi bus): - new property: ``anym-no-latch`` - new property: ``anym-mode`` - :dtcompatible:`st,lis2dw12` (on i2c bus): - new property: ``odr`` - new property: ``ff-duration`` - new property: ``ff-threshold`` - :dtcompatible:`st,lsm303agr-accel` (on i2c bus): - new property: ``anym-no-latch`` - new property: ``anym-mode`` - :dtcompatible:`st,lsm6dso32` (on i2c bus): - new property: ``drdy-pulsed`` - :dtcompatible:`st,stm32-sdmmc`: - new property: ``resets`` - new property: ``reset-names`` - :dtcompatible:`st,stm32-ucpd`: - new property: ``dead-battery`` - new property: ``pinctrl-0`` - new property: ``pinctrl-names`` - new property: ``pinctrl-1`` - new property: ``pinctrl-2`` - new property: ``pinctrl-3`` - new property: ``pinctrl-4`` - :dtcompatible:`st,stm32-timers`: - new property: ``resets`` - new property: ``reset-names`` - :dtcompatible:`st,stm32-lptim`: - new property: ``st,static-prescaler`` - new property: ``reset-names`` - :dtcompatible:`st,stm32-usb`: - removed property: ``enable-pin-remap`` - Texas Instruments (ti): - :dtcompatible:`ti,ina230` (on i2c bus): - new property: ``current-lsb-microamps`` - new property: ``rshunt-milliohms`` - new property: ``alert-gpios`` - removed property: ``irq-gpios`` - removed property: ``current-lsb`` - removed property: ``rshunt`` - :dtcompatible:`ti,ina237` (on i2c bus): - new property: ``current-lsb-microamps`` - new property: ``rshunt-milliohms`` - new property: ``alert-gpios`` - removed property: ``irq-gpios`` - removed property: ``current-lsb`` - removed property: ``rshunt`` - A stand-in for a real vendor which can be used in examples and tests (vnd): - :dtcompatible:`vnd,pinctrl`: - new property: ``bias-disable`` - new property: ``bias-high-impedance`` - new property: ``bias-bus-hold`` - new property: ``bias-pull-up`` - new property: ``bias-pull-down`` - new property: ``bias-pull-pin-default`` - new property: ``drive-push-pull`` - new property: ``drive-open-drain`` - new property: ``drive-open-source`` - new property: ``drive-strength`` - new property: ``drive-strength-microamp`` - new property: ``input-enable`` - new property: ``input-disable`` - new property: ``input-schmitt-enable`` - new property: ``input-schmitt-disable`` - new property: ``input-debounce`` - new property: ``power-source`` - new property: ``low-power-enable`` - new property: ``low-power-disable`` - new property: ``output-disable`` - new property: ``output-enable`` - new property: ``output-low`` - new property: ``output-high`` - new property: ``sleep-hardware-state`` - new property: ``slew-rate`` - new property: ``skew-delay`` - Zephyr-specific binding (zephyr): - :dtcompatible:`zephyr,cdc-acm-uart` (on usb bus): - new property: ``tx-fifo-size`` - new property: ``rx-fifo-size`` - :dtcompatible:`zephyr,sdhc-spi-slot` (on spi bus): - bus list changed from [] to ['sd'] Other ===== Shields * In order to avoid name conflicts with devices that may be defined at board level, it is advised, specifically for shields devicetree descriptions, to provide a device nodelabel in the form ``<device>_<shield>``. In-tree shields have been updated to follow this recommendation. * Others * STM32F1 SoCs * Added new pinctrl definitions for STM32F1xx PWM input. In PWM capture mode STM32F1xx pins have to be configured as input and not as alternate. The new names takes the form tim1_ch1_pwm_in_pa8 for example. * Renamed pinctrl definitions for STM32F1xx PWM output to differentiate them from newly created inputs. The new names takes the form tim1_ch1_pwm_out_pa8 instead of tim1_ch1_pwm_pa8. Libraries / Subsystems ********************** * C Library * Newlib nano variant is no longer selected by default when :kconfig:option:`CONFIG_NEWLIB_LIBC` is selected. :kconfig:option:`CONFIG_NEWLIB_LIBC_NANO` must now be explicitly selected in order to use the nano variant. * Picolibc now supports all architectures supported by Zephyr. * Added C11 ``aligned_alloc`` support to the minimal libc. * C++ Library * C++ support in Zephyr is no longer considered a "subsystem" because it mainly consists of the C++ ABI runtime library and the C++ standard library, which are "libraries" that are dissimilar to the existing Zephyr subsystems. C++ support components are now located in ``lib/cpp`` as "C++ library." * C++ ABI runtime library components such as global constructor/destructor and initialiser handlers, that were previously located under ``subsys/cpp``, have been moved to ``lib/cpp/abi`` in order to provide a clear separation between the C++ ABI runtime library and the C++ standard library. * C++ minimal library components have been moved to ``lib/cpp/minimal``. * C++ tests have been moved to ``tests/lib/cpp``. * C++ samples have been moved to ``samples/cpp``. * :kconfig:option:`CONFIG_CPLUSPLUS` has been renamed to :kconfig:option:`CONFIG_CPP`. * :kconfig:option:`CONFIG_EXCEPTIONS` has been renamed to :kconfig:option:`CONFIG_CPP_EXCEPTIONS`. * :kconfig:option:`CONFIG_RTTI` has been renamed to :kconfig:option:`CONFIG_CPP_RTTI`. * :kconfig:option:`CONFIG_LIB_CPLUSPLUS` is deprecated. A toolchain-specific C++ standard library Kconfig option from :kconfig:option:`CONFIG_LIBCPP_IMPLEMENTATION` should be selected instead. * Zephyr subsystems and modules that require the features from the full C++ standard library (e.g. Standard Template Library) can now select :kconfig:option:`CONFIG_REQUIRES_FULL_LIBC`, which automatically selects a compatible C++ standard library. * Introduced :kconfig:option:`CONFIG_CPP_MAIN` to support defining ``main()`` function in a C++ source file. Enabling this option makes the Zephyr kernel invoke ``int main(void)``, which is required by the ISO C++ standards, as opposed to the Zephyr default ``void main(void)``. * Added no-throwing implementation of new operator to the C++ minimal library. * Added support for new operator with alignment request (C++17) to the C++ minimal library. * Added GNU C++ standard library support with Picolibc when using a suitably configured toolchain (e.g. the upcoming Zephyr SDK 0.16.0 release). * Cache * Introduced new Cache API * ``CONFIG_HAS_ARCH_CACHE`` has been renamed to :kconfig:option:`CONFIG_ARCH_CACHE` * ``CONFIG_HAS_EXTERNAL_CACHE`` has been renamed to :kconfig:option:`CONFIG_EXTERNAL_CACHE` * DSP * Introduced DSP (digital signal processing) subsystem with CMSIS-DSP as the default backend. * CMSIS-DSP now supports all architectures supported by Zephyr. * File systems * Added new API call `fs_mkfs`. * Added new sample `samples/subsys/fs/format`. * FAT FS driver has been updated to version 0.15 w/patch1. * Added the option to disable CRC checking in :ref:`fcb_api` by enabling the Kconfig option :kconfig:option:`CONFIG_FCB_ALLOW_FIXED_ENDMARKER` and setting the `FCB_FLAGS_CRC_DISABLED` flag in the :c:struct:`fcb` struct. * IPC * Added :c:func:`ipc_rpmsg_deinit`, :c:func:`ipc_service_close_instance` and :c:func:`ipc_static_vrings_deinit` functions * Added deregister API support for icmsg backend * Added a multi-endpoint feature to icmsg backend * Added no-copy features to icmsg backend * ISO-TP * Rewrote the ISO-TP API to not reuse definitions from the CAN controller API. * Logging * Added support for logging on multiple domains. * :kconfig:option:`CONFIG_LOG_PRINTK` is now by default enabled which means that when logging is enabled then printk is by directed to the logging subsystem. * Added option to use custom logging header. * Management * MCUmgr functionality deprecated in 3.1 has been removed: CONFIG_FS_MGMT_UL_CHUNK_SIZE, CONFIG_IMG_MGMT_UL_CHUNK_SIZE, CONFIG_OS_MGMT_ECHO_LENGTH * MCUmgr fs_mgmt issue with erasing a file prior to writing the first block of data has been worked around by only truncating/deleting the file data if the file exists. This can help work around an issue whereby logging is enabled and the command is sent on the same UART as the logging system, in which a filesystem error was emitted. * A MCUmgr bug when using the smp_svr sample with Bluetooth transport that could have caused a stack overflow has been fixed. * A MCUmgr issue with Bluetooth transport that could cause a deadlock of the mcumgr thread if the remote device disconnected before the output message was sent has been fixed. * A MCUmgr img_mgmt bug whereby the state of an image upload could persist when it was no longer valid (e.g. after an image erase command) has been fixed. * MCUmgr fs_mgmt command has been added that allows querying/listing the supported hash/checksum types. * MCUmgr Bluetooth transport will now clear unprocessed commands sent if a remote device disconnects instead of processing them. * A new MCUmgr transport function pointer has been added which needs registering in ``smp_transport_init`` for removing invalid packets for connection-orientated transports. If this is unimplemented, the function pointer can be set to NULL. * MCUmgr command handler definitions have changed, the ``mgmt_ctxt`` struct has been replaced with the ``smp_streamer`` struct, the zcbor objects need to replace ``cnbe`` object access with ``writer`` and ``cnbd`` object access with ``reader`` to successfully build. * MCUmgr callback system has been reworked with a unified singular interface which supports status passing to the handler (:ref:`mcumgr_callbacks`). * MCUmgr subsystem directory structure has been flattened and contents of the lib subdirectory has been redistributed into following directories: .. table:: :align: center +----------------+-------------------------------------------+ \| Subdirectory \| MCUmgr area \| +================+===========================================+ \| mgmt \| MCUmgr management functions, group \| \| \| registration, and so on; \| +----------------+-------------------------------------------+ \| smp \| Simple Management Protocol processing; \| +----------------+-------------------------------------------+ \| transport \| Transport support and transport API; \| +----------------+-------------------------------------------+ \| grp \| Command groups, formerly lib/cmd; \| \| \| each group, which has Zephyr built in \| \| \| support has its own directory here; \| +----------------+-------------------------------------------+ \| util \| Utilities used by various subareas of \| \| \| MCUmgr. \| +----------------+-------------------------------------------+ Public API interfaces for above areas are now exported through zephyr_interface, and headers for them reside in ``zephyr/mgmt/mcumgr/<mcumgr_subarea>/``. For example to access mgmt API include ``<zephyr/mgmt/mcumgr/mgmt/mgmt.h>``. Private headers for above areas can be accessed, when required, using paths: ``mgmt/mcumgr/mgmt/<mcumgr_subarea>/``. * MCUmgr os_mgmt info command has been added that allows querying details on the kernel and application, allowing application-level extensibility see :ref:`mcumgr_os_application_info` for details. * MCUMgr :kconfig:option:`CONFIG_APP_LINK_WITH_MCUMGR` has been removed as it has not been doing anything. * MCUmgr Kconfig option names have been standardised. Script :zephyr_file:`scripts/utils/migrate_mcumgr_kconfigs.py` has been provided to make transition to new Kconfig options easier. Below table provides information on old names and new equivalents: .. table:: :align: center +------------------------------------------------+-------------------------------------------------------+ \| Old Kconfig option name \| New Kconfig option name \| +================================================+=======================================================+ \| MCUMGR_SMP_WORKQUEUE_STACK_SIZE \| MCUMGR_TRANSPORT_WORKQUEUE_STACK_SIZE \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_WORKQUEUE_THREAD_PRIO \| MCUMGR_TRANSPORT_WORKQUEUE_THREAD_PRIO \| +------------------------------------------------+-------------------------------------------------------+ \| MGMT_MAX_MAIN_MAP_ENTRIES \| MCUMGR_SMP_CBOR_MAX_MAIN_MAP_ENTRIES \| +------------------------------------------------+-------------------------------------------------------+ \| MGMT_MIN_DECODING_LEVELS \| MCUMGR_SMP_CBOR_MIN_DECODING_LEVELS \| +------------------------------------------------+-------------------------------------------------------+ \| MGMT_MIN_DECODING_LEVEL_1 \| MCUMGR_SMP_CBOR_MIN_DECODING_LEVEL_1 \| +------------------------------------------------+-------------------------------------------------------+ \| MGMT_MIN_DECODING_LEVEL_2 \| MCUMGR_SMP_CBOR_MIN_DECODING_LEVEL_2 \| +------------------------------------------------+-------------------------------------------------------+ \| MGMT_MIN_DECODING_LEVEL_3 \| MCUMGR_SMP_CBOR_MIN_DECODING_LEVEL_3 \| +------------------------------------------------+-------------------------------------------------------+ \| MGMT_MIN_DECODING_LEVEL_4 \| MCUMGR_SMP_CBOR_MIN_DECODING_LEVEL_4 \| +------------------------------------------------+-------------------------------------------------------+ \| MGMT_MIN_DECODING_LEVEL_5 \| MCUMGR_SMP_CBOR_MIN_DECODING_LEVEL_5 \| +------------------------------------------------+-------------------------------------------------------+ \| MGMT_MAX_DECODING_LEVELS \| MCUMGR_SMP_CBOR_MAX_DECODING_LEVELS \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_CMD_FS_MGMT \| MCUMGR_GRP_FS \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_MAX_FILE_SIZE_64KB \| MCUMGR_GRP_FS_MAX_FILE_SIZE_64KB \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_MAX_FILE_SIZE_4GB \| MCUMGR_GRP_FS_MAX_FILE_SIZE_4GB \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_MAX_OFFSET_LEN \| MCUMGR_GRP_FS_MAX_OFFSET_LEN \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_DL_CHUNK_SIZE_LIMIT \| MCUMGR_GRP_FS_DL_CHUNK_SIZE_LIMIT \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_DL_CHUNK_SIZE \| MCUMGR_GRP_FS_DL_CHUNK_SIZE \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_FILE_STATUS \| MCUMGR_GRP_FS_FILE_STATUS \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_CHECKSUM_HASH \| MCUMGR_GRP_FS_CHECKSUM_HASH \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_CHECKSUM_HASH_CHUNK_SIZE \| MCUMGR_GRP_FS_CHECKSUM_HASH_CHUNK_SIZE \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_CHECKSUM_IEEE_CRC32 \| MCUMGR_GRP_FS_CHECKSUM_IEEE_CRC32 \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_HASH_SHA256 \| MCUMGR_GRP_FS_HASH_SHA256 \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_FILE_ACCESS_HOOK \| MCUMGR_GRP_FS_FILE_ACCESS_HOOK \| +------------------------------------------------+-------------------------------------------------------+ \| FS_MGMT_PATH_SIZE \| MCUMGR_GRP_FS_PATH_LEN \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_CMD_IMG_MGMT \| MCUMGR_GRP_IMG \| +------------------------------------------------+-------------------------------------------------------+ \| IMG_MGMT_USE_HEAP_FOR_FLASH_IMG_CONTEXT \| MCUMGR_GRP_IMG_USE_HEAP_FOR_FLASH_IMG_CONTEXT \| +------------------------------------------------+-------------------------------------------------------+ \| IMG_MGMT_UPDATABLE_IMAGE_NUMBER \| MCUMGR_GRP_IMG_UPDATABLE_IMAGE_NUMBER \| +------------------------------------------------+-------------------------------------------------------+ \| IMG_MGMT_VERBOSE_ERR \| MCUMGR_GRP_IMG_VERBOSE_ERR \| +------------------------------------------------+-------------------------------------------------------+ \| IMG_MGMT_DUMMY_HDR \| MCUMGR_GRP_IMG_DUMMY_HDR \| +------------------------------------------------+-------------------------------------------------------+ \| IMG_MGMT_DIRECT_IMAGE_UPLOAD \| MCUMGR_GRP_IMG_DIRECT_UPLOAD \| +------------------------------------------------+-------------------------------------------------------+ \| IMG_MGMT_REJECT_DIRECT_XIP_MISMATCHED_SLOT \| MCUMGR_GRP_IMG_REJECT_DIRECT_XIP_MISMATCHED_SLOT \| +------------------------------------------------+-------------------------------------------------------+ \| IMG_MGMT_FRUGAL_LIST \| MCUMGR_GRP_IMG_FRUGAL_LIST \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_CMD_OS_MGMT \| MCUMGR_GRP_OS \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_GRP_OS_OS_RESET_HOOK \| MCUMGR_GRP_OS_RESET_HOOK \| +------------------------------------------------+-------------------------------------------------------+ \| OS_MGMT_RESET_MS \| MCUMGR_GRP_OS_RESET_MS \| +------------------------------------------------+-------------------------------------------------------+ \| OS_MGMT_TASKSTAT \| MCUMGR_GRP_OS_TASKSTAT \| +------------------------------------------------+-------------------------------------------------------+ \| OS_MGMT_TASKSTAT_ONLY_SUPPORTED_STATS \| MCUMGR_GRP_OS_TASKSTAT_ONLY_SUPPORTED_STATS \| +------------------------------------------------+-------------------------------------------------------+ \| OS_MGMT_TASKSTAT_MAX_NUM_THREADS \| MCUMGR_GRP_OS_TASKSTAT_MAX_NUM_THREADS \| +------------------------------------------------+-------------------------------------------------------+ \| OS_MGMT_TASKSTAT_THREAD_NAME_LEN \| MCUMGR_GRP_OS_TASKSTAT_THREAD_NAME_LEN \| +------------------------------------------------+-------------------------------------------------------+ \| OS_MGMT_TASKSTAT_SIGNED_PRIORITY \| MCUMGR_GRP_OS_TASKSTAT_SIGNED_PRIORITY \| +------------------------------------------------+-------------------------------------------------------+ \| OS_MGMT_TASKSTAT_STACK_INFO \| MCUMGR_GRP_OS_TASKSTAT_STACK_INFO \| +------------------------------------------------+-------------------------------------------------------+ \| OS_MGMT_ECHO \| MCUMGR_GRP_OS_ECHO \| +------------------------------------------------+-------------------------------------------------------+ \| OS_MGMT_MCUMGR_PARAMS \| MCUMGR_GRP_OS_MCUMGR_PARAMS \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_CMD_SHELL_MGMT \| MCUMGR_GRP_SHELL \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_CMD_SHELL_MGMT_LEGACY_RC_RETURN_CODE \| MCUMGR_GRP_SHELL_LEGACY_RC_RETURN_CODE \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_CMD_STAT_MGMT \| MCUMGR_GRP_STAT \| +------------------------------------------------+-------------------------------------------------------+ \| STAT_MGMT_MAX_NAME_LEN \| MCUMGR_GRP_STAT_MAX_NAME_LEN \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_GRP_ZEPHYR_BASIC \| MCUMGR_GRP_ZBASIC \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_GRP_BASIC_CMD_STORAGE_ERASE \| MCUMGR_GRP_ZBASIC_STORAGE_ERASE \| +------------------------------------------------+-------------------------------------------------------+ \| MGMT_VERBOSE_ERR_RESPONSE \| MCUMGR_SMP_VERBOSE_ERR_RESPONSE \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_REASSEMBLY \| MCUMGR_TRANSPORT_REASSEMBLY \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_BUF_COUNT \| MCUMGR_TRANSPORT_NETBUF_COUNT \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_BUF_SIZE \| MCUMGR_TRANSPORT_NETBUF_SIZE \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_BUF_USER_DATA_SIZE \| MCUMGR_TRANSPORT_NETBUF_USER_DATA_SIZE \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_BT \| MCUMGR_TRANSPORT_BT \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_REASSEMBLY_BT \| MCUMGR_TRANSPORT_BT_REASSEMBLY \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_REASSEMBLY_UNIT_TESTS \| MCUMGR_TRANSPORT_REASSEMBLY_UNIT_TESTS \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_BT_AUTHEN \| MCUMGR_TRANSPORT_BT_AUTHEN \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_BT_CONN_PARAM_CONTROL \| MCUMGR_TRANSPORT_BT_CONN_PARAM_CONTROL \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_BT_CONN_PARAM_CONTROL_MIN_INT \| MCUMGR_TRANSPORT_BT_CONN_PARAM_CONTROL_MIN_INT \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_BT_CONN_PARAM_CONTROL_MAX_INT \| MCUMGR_TRANSPORT_BT_CONN_PARAM_CONTROL_MAX_INT \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_BT_CONN_PARAM_CONTROL_LATENCY \| MCUMGR_TRANSPORT_BT_CONN_PARAM_CONTROL_LATENCY \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_BT_CONN_PARAM_CONTROL_TIMEOUT \| MCUMGR_TRANSPORT_BT_CONN_PARAM_CONTROL_TIMEOUT \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_BT_CONN_PARAM_CONTROL_RESTORE_TIME \| MCUMGR_TRANSPORT_BT_CONN_PARAM_CONTROL_RESTORE_TIME \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_BT_CONN_PARAM_CONTROL_RETRY_TIME \| MCUMGR_TRANSPORT_BT_CONN_PARAM_CONTROL_RETRY_TIME \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_DUMMY \| MCUMGR_TRANSPORT_DUMMY \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_DUMMY_RX_BUF_SIZE \| MCUMGR_TRANSPORT_DUMMY_RX_BUF_SIZE \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_SHELL \| MCUMGR_TRANSPORT_SHELL \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_SHELL_MTU \| MCUMGR_TRANSPORT_SHELL_MTU \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_SHELL_RX_BUF_COUNT \| MCUMGR_TRANSPORT_SHELL_RX_BUF_COUNT \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UART \| MCUMGR_TRANSPORT_UART \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UART_ASYNC \| MCUMGR_TRANSPORT_UART_ASYNC \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UART_ASYNC_BUFS \| MCUMGR_TRANSPORT_UART_ASYNC_BUFS \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UART_ASYNC_BUF_SIZE \| MCUMGR_TRANSPORT_UART_ASYNC_BUF_SIZE \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UART_MTU \| MCUMGR_TRANSPORT_UART_MTU \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UDP \| MCUMGR_TRANSPORT_UDP \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UDP_IPV4 \| MCUMGR_TRANSPORT_UDP_IPV4 \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UDP_IPV6 \| MCUMGR_TRANSPORT_UDP_IPV6 \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UDP_PORT \| MCUMGR_TRANSPORT_UDP_PORT \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UDP_STACK_SIZE \| MCUMGR_TRANSPORT_UDP_STACK_SIZE \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UDP_THREAD_PRIO \| MCUMGR_TRANSPORT_UDP_THREAD_PRIO \| +------------------------------------------------+-------------------------------------------------------+ \| MCUMGR_SMP_UDP_MTU \| MCUMGR_TRANSPORT_UDP_MTU \| +------------------------------------------------+-------------------------------------------------------+ * MCUmgr responses where ``rc`` (result code) is 0 (no error) will no longer be present in responses and in cases where there is only an ``rc`` result, the resultant response will now be an empty CBOR map. The old behaviour can be restored by enabling :kconfig:option:`CONFIG_MCUMGR_SMP_LEGACY_RC_BEHAVIOUR`. * MCUmgr now has log outputting on most errors from the included fs, img, os, shell, stat and zephyr_basic group commands. The level of logging can be controlled by adjusting: :kconfig:option:`CONFIG_MCUMGR_GRP_FS_LOG_LEVEL`, :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_LOG_LEVEL`, :kconfig:option:`CONFIG_MCUMGR_GRP_OS_LOG_LEVEL`, :kconfig:option:`CONFIG_MCUMGR_GRP_SHELL_LOG_LEVEL`, :kconfig:option:`CONFIG_MCUMGR_GRP_STAT_LOG_LEVEL` and :kconfig:option:`CONFIG_MCUMGR_GRP_ZBASIC_LOG_LEVEL`. * MCUmgr img_mgmt has a new field which is sent in the final packet (if :kconfig:option:`CONFIG_IMG_ENABLE_IMAGE_CHECK` is enabled) named ``match`` which is a boolean and is true if the uploaded data matches the supplied hash, or false otherwise. * MCUmgr img_mgmt will now skip receiving data if the provided hash already matches the hash of the data present (if :kconfig:option:`CONFIG_IMG_ENABLE_IMAGE_CHECK` is enabled) and finish the upload operation request instantly. * MCUmgr img_mgmt structs are now packed, which fixes a fault issue on processors that do not support unaligned memory access. * If MCUmgr is used with the shell transport and ``printk()`` functionality is used, there can be an issue whereby the ``printk()`` calls output during a MCUmgr frame receive, this has been fixed by default in zephyr by routing ``printk()`` calls to the logging system, For user applications, :kconfig:option:`CONFIG_LOG_PRINTK` should be enabled to include this fix. * A bug when MCUmgr shell transport is used (issue was observed over USB CDC but could also occur with UART) whereby the default shell receive ring buffer is insufficient has been fixed by making the default size 256 bytes instead of 64 when the shell MCUmgr transport is selected. * UpdateHub: * The integrity check was reworked to allow use by other libraries. Since then UpdateHub uses mbedTLS library as default crypto library. * Added a new Storage Abstraction to isolate both flash operations and MCUboot internals. * The UpdateHub User API was moved as a Zephyr public API and the userspace now is available. This added :c:func:`updatehub_confirm` and :c:func:`updatehub_reboot` functions. * LwM2M * The ``lwm2m_senml_cbor_`` files have been regenerated using zcbor 0.6.0. POSIX API * Harmonized posix type definitions across the minimal libc, newlib and picolibc. * Abstract ``pthread_t``, ``pthread_key_t``, ``pthread_cond_t``, ``pthread_mutex_t``, as ``uint32_t``. * Defined :c:macro:`PTHREAD_KEY_INITIALIZER`, :c:macro:`PTHREAD_COND_INITIALIZER`, :c:macro:`PTHREAD_MUTEX_INITIALIZER` to align with POSIX 1003.1. * Allowed non-prefixed standard include paths with :kconfig:option:`CONFIG_POSIX_API`. * I.e. ``#include <unistd.h>`` instead of ``#include <zephyr/posix/unistd.h>``. * Primarily to ease integration with external libraries. * Internal Zephyr code should continue to use prefixed header paths. * Enabled ``eventfd()``, ``getopt()`` by default with :kconfig:option:`CONFIG_POSIX_API`. * Moved / renamed header files to align with POSIX specifications. * E.g. move ``fcntl.h``, ``sys/stat.h`` from the minimal libc into the ``include/zephyr/posix`` directory. Rename ``posix_sched.h`` to ``sched.h``. * Move :c:macro:`O_ACCMODE`, :c:macro:`O_RDONLY`, :c:macro:`O_WRONLY`, :c:macro:`O_WRONLY`, to ``fcntl.h``. * Added :kconfig:option:`CONFIG_TIMER_CREATE_WAIT`, :kconfig:option:`CONFIG_MAX_PTHREAD_KEY_COUNT`, :kconfig:option:`CONFIG_MAX_PTHREAD_COND_COUNT`, :kconfig:option:`CONFIG_MAX_PTHREAD_MUTEX_COUNT`. * Defined :c:macro:`SEEK_SET`, :c:macro:`SEEK_CUR`, :c:macro:`SEEK_END`. * SD Subsystem * Added support for eMMC protocol in Zephyr. - Speed modes up to HS400 are supported using 1.8v operation. - Additional protocol tests have been added to verify eMMC functionality. - Disk subsystem tests have been updated to function with eMMC. * Card and host combinations that cannot utilize UHS (ultra high speed) mode will now use 4 bit bus width when possible. This will greatly improve performance for these systems. * Settings * Replaced all :c:func:`k_panic` invocations within settings backend initialization with returning / propagating error codes. * Shell * New features: * SHELL_AUTOSTART configuration option. When SHELL_AUTOSTART is set to n, the shell is not started after boot but can be enabled later from the application code. * Added support for setting the help description for each entry in a dictionary. * Bugfix: * Updated to clear command buffer when leaving bypass mode to prevent undefined behaviour on consecutive shell operations. * Set RX size default to 256 if shell MCUmgr is enabled. * Fixed log message queue size for all backends. * Documentation: * Added information explaining commands execution. * Utilities * Added the linear range API to map values in a linear range to a range index :zephyr_file:`include/zephyr/sys/linear_range.h`. * Zbus * Added the :ref:`zbus` to Zephyr. * Channel-centric multi-paradigm (message-passing and publish-subscribe) communication message bus. * Virtual Distributed Event Dispatcher. * Observers can be listeners (synchronous) and subscribers (asynchronous). * One-to-one, one-to-many, and many-to-many communications. * Persistent messages distributed by shared-memory approach. * Delivery guarantee only for listeners. * Uses mutex to control channels access. * Added the following samples: * :zephyr:code-sample:`zbus-hello-world` * :zephyr:code-sample:`zbus-work-queue` * :zephyr:code-sample:`zbus-dyn-channel` * :zephyr:code-sample:`zbus-uart-bridge` * :zephyr:code-sample:`zbus-remote-mock` * :zephyr:code-sample:`zbus-runtime-obs-registration` * :zephyr:code-sample:`zbus-benchmark` * Added zbus channels APIs: * :c:func:`zbus_chan_pub` * :c:func:`zbus_chan_read` * :c:func:`zbus_chan_notify` * :c:func:`zbus_chan_claim` * :c:func:`zbus_chan_finish` * :c:func:`zbus_chan_name` * :c:func:`zbus_chan_msg` * :c:func:`zbus_chan_const_msg` * :c:func:`zbus_chan_msg_size` * :c:func:`zbus_chan_user_data` * :c:func:`zbus_chan_add_obs` * :c:func:`zbus_chan_rm_obs` * :c:func:`zbus_runtime_obs_pool` * :c:func:`zbus_obs_set_enable` * :c:func:`zbus_obs_name` * :c:func:`zbus_sub_wait` * :c:func:`zbus_iterate_over_channels` * :c:func:`zbus_iterate_over_observers` * Added the related configuration options: * :kconfig:option:`CONFIG_ZBUS_CHANNEL_NAME` * :kconfig:option:`CONFIG_ZBUS_OBSERVER_NAME` * :kconfig:option:`CONFIG_ZBUS_STRUCTS_ITERABLE_ACCESS` * :kconfig:option:`CONFIG_ZBUS_RUNTIME_OBSERVERS_POOL_SIZE` HALs **** * Atmel * sam0: Added support for SAMC20/21. * sam4l: Added ``US_MR_CHRL_{n}_BIT`` Register Aliases for USART Driver. * GigaDevice * Added support for gd32l23x. * Added support for gd32a50x. * Nordic * Updated nrfx to version 2.10.0. * STM32 * stm32cube: updated stm32h7 to cube version V1.11.0. * stm32cube: updated stm32l5 to cube version V1.5.0. * stm32cube: updated stm32wl to cube version V1.3.0. * Espressif * Added Ethernet driver support * Added light-sleep and deep-sleep support over PM interface * Added ADC and DAC driver support * Added GDMA driver support Storage ******* * Flash Map API drops ``fa_device_id`` from :c:struct:`flash_area`, as it is no longer needed by MCUboot, and has not been populated for a long time now. Trusted Firmware-M ****************** * Updated to TF-M 1.7.0 (and MbedTLS 3.2.1). * Initial attestation service has been disabled by default due to license issues with the QCBOR dependency. To enable it, set the path for QCBOR via ``CONFIG_TFM_QCBOR_PATH`` or set the path to ``DOWNLOAD``. * Firmware update sample removed pending update to 1.0 FWU service. * psa_crypto sample removed pending resolution of PSA API conflicts w/MbedTLS. zcbor ***** Upgraded zcbor to 0.6.0. Among other things, this brings in a few convenient changes for Zephyr: * In the zcbor codebase, the ``ARRAY_SIZE`` macro has been renamed to ``ZCBOR_ARRAY_SIZE`` to not collide with Zephyr's :c:macro:`ARRAY_SIZE` macro. * The zcbor codebase now better supports being used in C++ code. The entire release notes can be found at path_to_url Documentation ************* * Upgraded to Doxygen 1.9.6. * It is now possible to link to Kconfig search results. Issue Related Items ******************* Known Issues ============ - :github:`33747` - gptp does not work well on NXP rt series platform - :github:`37193` - mcumgr: Probably incorrect error handling with udp backend - :github:`37731` - Bluetooth: hci samples: Unable to allocate command buffer - :github:`40023` - Build fails for ``native_posix`` board when using C++ <atomic> header - :github:`42030` - can: "bosch,m-can-base": Warning "missing or empty reg/ranges property" - :github:`43099` - CMake: ARCH roots issue - :github:`43249` - MBEDTLS_ECP_C not build when MBEDTLS_USE_PSA_CRYPTO - :github:`43555` - Variables not properly initialized when using data relocation with SDRAM - :github:`43562` - Setting and/or documentation of Timer and counter use/requirements for Nordic Bluetooth driver - :github:`44339` - Bluetooth:controller: Implement support for Advanced Scheduling in refactored LLCP - :github:`44948` - cmsis_dsp: transform: error during building cf64.fpu and rf64.fpu for mps2_an521_remote - :github:`45241` - (Probably) unnecessary branches in several modules - :github:`45323` - Bluetooth: controller: llcp: Implement handling of delayed notifications in refactored LLCP - :github:`45814` - Armclang build fails due to missing source file - :github:`46121` - Bluetooth: Controller: hci: Wrong periodic advertising report data status - :github:`46401` - ARM64: Relax 4K MMU mapping alignment - :github:`46846` - lib: libc: newlib: strerror_r non-functional - :github:`47120` - shell uart: busy wait for DTR in ISR - :github:`47732` - Flash map does not fare well with MCU who do bank swaps - :github:`47908` - tests/kernel/mem_protect/stack_random works unreliably and sporadically fails - :github:`48094` - pre-commit scripts fail when there is a space in zephyr_base - :github:`48102` - JSON parses uses recursion (breaks rule 17.2) - :github:`48287` - malloc_prepare ASSERT happens when enabling newlib libc with demand paging - :github:`48608` - boards: mps2_an385: Unstable system timer - :github:`48841` - Bluetooth: df: Assert in lower link layer when requesting CTE from peer periodically with 7.5ms connection interval - :github:`48992` - qemu_leon3: tests/posix/common/portability.posix.common fails - :github:`49213` - logging.add.log_user test fails when compiled with GCC 12 - :github:`49390` - shell_rtt thread can starve other threads of the same priority - :github:`49484` - CONFIG_BOOTLOADER_SRAM_SIZE should not be defined by default - :github:`49492` - kernel.poll test fails on qemu_arc_hs6x when compiled with GCC 12 - :github:`49494` - testing.ztest.ztress test fails on qemu_cortex_r5 when compiled with GCC 12 - :github:`49614` - acrn_ehl_crb: The testcase tests/kernel/sched/schedule_api failed to run. - :github:`49816` - ISOTP receive fails for multiple binds with same CAN ID but different extended ID - :github:`49889` - ctf trace: unknown event id when parsing samples/tracing result on reel board - :github:`50084` - drivers: nrf_802154: nrf_802154_trx.c - assertion fault when enabling Segger SystemView tracing - :github:`50095` - ARC revision Kconfigs wrongly mixed with board name - :github:`50196` - LSM6DSO interrupt handler not being called - :github:`50501` - STM32 SPI does not work properly with async + interrupts - :github:`50506` - nxp,mcux-usbd devicetree binding issues - :github:`50546` - drivers: can: rcar: likely inconsistent behavior when calling can_stop() with pending transmissions - :github:`50598` - UDP over IPSP not working on nRF52840 - :github:`50652` - RAM Loading on i.MXRT1160_evk - :github:`50766` - Disable cross-compiling when using host toolchain - :github:`50777` - LE Audio: Receiver start ready command shall only be sent by the receiver - :github:`50875` - net: ip: race in access to writable net_if attributes - :github:`50941` - sample.logger.syst.catalog.deferred_cpp fails on qemu_cortex_m0 - :github:`51024` - aarch32 excn vector not pinned in mmu causing newlib heap overlap - :github:`51127` - UART HW DMA ( UART Communication based on HW DMA ) - Buffer Overflow test in STM32H743 Controller - :github:`51133` - Bluetooth: audio: Sink ASE does not go to IDLE state - :github:`51250` - ESP32-C3 pin glitches during start-up - :github:`51317` - Confusing license references in nios2f-zephyr - :github:`51342` - Bluetooth ISO extra ``stream_sent`` callback after ``seq_num`` 16-bit rollover - :github:`51420` - tests: subsys: logging: log_links: logging.log_links fails - :github:`51422` - nsim_em: tests/subsys/logging/log_link_order run failed on nsim_em - :github:`51449` - device: device_get_binding is broken for nodes with the same name - :github:`51604` - doc: is the documentation GDPR compliant since it uses Google Analytics without prompting the user about tracking? - :github:`51637` - shell: bypass shell_fprintf ASSERT fail - :github:`51728` - soc: xtensa: esp32_net: Remove binary blobs from source tree - :github:`51774` - thread safety of adv_new in Bluetooth subsys - :github:`51814` - ARC irq_offload doesn't honor thread switches - :github:`51820` - Longer strings aren't logged - :github:`51825` - west: runners: jlink: JLink.exe name collision - :github:`51977` - newlib integration: _unlink isn't mapped to unlink - :github:`52055` - Bluetooth: Controller: Broadcast scheduling issues - :github:`52269` - UART documentation for uart_irq_tx_enable/disable incomplete - :github:`52271` - west sign: imgtool: zephyr.signed.hex and zephyr.signed.bin do not have the same contents - :github:`52362` - nrf_qspi_nor driver crash if power management is enabled - :github:`52395` - Cannot build applications with dts having (unused) external flash partition and disabling those drivers - :github:`52491` - Value of EVENT_OVERHEAD_START_US is set to low - :github:`52494` - SPI NOR DPD comment is misleading/wrong - :github:`52510` - twister: truncated handler.log reports test as "failed" - :github:`52513` - sample.modules.chre fails on qemu_leon3 - :github:`52575` - Kconfig: excessive ``select`` usage - :github:`52585` - PDM event handler shouldn't stop driver on allocation failure - :github:`52589` - Add support for different SDHC high-speed modes (currently defaults to SDR25) - :github:`52605` - esp32-usb-serial tx-complete interrupt not working in interrupt mode on esp32c3 - :github:`52623` - qemu_x86: thousands of timer interrupts per second - :github:`52667` - nrf_rtc_timer: Booting application with zephyr < 3.0.0 from mcuboot with zephyr >= 3.0.0 - :github:`52700` - posix: getopt: implement standards-compliant reset - :github:`52702` - drivers: wifi: esp_at: Some issues on Passive Receive mode - :github:`52705` - RNDIS fails to enumerate on Raspberry Pi Pico - :github:`52741` - bl5340_dvk_cpuapp has wrong button for mcuboot button - :github:`52764` - boards: esp32c3_devkitm: unable to read memory-mapped flash memory - :github:`52792` - ATWINC1500 : (wifi_winc1500_nm_bsp.c : nm_bsp_reset) The reset function is not logical and more - :github:`52825` - Overflow in settime posix function - :github:`52830` - Annoying Slirp Message console output from qemu_x86 board target - :github:`52868` - ESP32 Wifi driver returns EIO (-5) if connecting without a sleep sometime before calling - :github:`52869` - ESP32 Counter overflow, with no API to reset it - :github:`52885` - modem: gsm_ppp: CONFIG_GSM_MUX: Unable to reactivate modem after executing gsm_ppp_stop() - :github:`52886` - tests: subsys: fs: littlefs: filesystem.littlefs.default and filesystem.littlefs.custom fails - :github:`52887` - Bluetooth: LL assert with chained adv packets - :github:`52924` - ESP32 get the build message "IRAM0 segment data does not fit." - :github:`52941` - Zephyr assumes ARM M7 core has a cache - :github:`52954` - check_zephyr_package() only checks the first zephyr package rather than all the considered ones. - :github:`52998` - tests: drivers: can: Build failure with sysroot path not quoted on Windows - :github:`53000` - Delaying logging via CONFIG_LOG_PROCESS_THREAD_STARTUP_DELAY_MS doesn't work if another backend is disabled - :github:`53006` - Hawbkit with b_l4s5i_iot01a - wifi_eswifi: Cannot allocate rx packet - :github:`53008` - Invalid ISO interval configuration - :github:`53088` - Unable to chage initialization priority of logging subsys - :github:`53123` - Cannot run a unit test on Mac OSX with M1 Chip - :github:`53124` - cmake: incorrect argument passing and dereference in zephyr_check_compiler_flag() and zephyr_check_compiler_flag_hardcoded() - :github:`53137` - Bluetooth: Controller: HCI 0x45 error after 3rd AD fragment with data > 248 bytes - :github:`53148` - Bluetooth: Controller: BT_HCI_OP_LE_BIG_TERMINATE_SYNC on syncing BIG sync returns invalid BIG handle - :github:`53172` - SHTCx driver wrong negative temperature values - :github:`53173` - HCI-UART: unable to preform a DFU - GATT CONN timeout - :github:`53198` - Bluetooth: Restoring security level fails and missing some notifications - :github:`53265` - Bluetooth: Controller: ISO interleaved broadcast not working - :github:`53319` - USB CDC ACM UART driver's interrupt-driven API hangs when no host is connected - :github:`53334` - Bluetooth: Peripheral disconnected with BT_HCI_ERR_LL_RESP_TIMEOUT reason and SMP timeout - :github:`53343` - subsys: logging: use of timestamping during early boot may crash MMU-based systems - :github:`53348` - Bluetooth: Restoring connection to peripheral issue - :github:`53375` - net: lwm2m: write method when floating point - :github:`53475` - The ATT_MTU value for EATT should be set as the minimum MTU of ATT Client and ATT Server - :github:`53505` - Some device tree integers may be signed or unsigned depending on their value - :github:`53522` - k_busy_wait function hangs on when CONFIG_SYSTEM_CLOCK_SLOPPY_IDLE is set with CONFIG_PM. - :github:`53537` - TFM-M doesn't generate tfm_ns_signed.bin image for FOTA firmware upgrade - :github:`53544` - Cannot see both bootloader and application RTT output - :github:`53546` - zephyr kernel Kconfig USE_STDC_LSM6DS3TR and hal_st CMakeLists.txt lsm6ds3tr-c variable name mismatched (hyphen sign special case) - :github:`53552` - LE Audio: Device executes receiver start ready before the CIS is connected - :github:`53555` - ESP32-C3 Is RV32IMA, Not RV32IMC? - :github:`53570` - SDHC SPI driver should issue CMD12 after receiving data error token - :github:`53587` - Issue with Auto-IP and Multicast/socket connection - :github:`53605` - tests: posix: common: portability.posix.common fails - posix_apis.test_clock_gettime_rollover - :github:`53613` - tests: drivers: uart: uart_mix_fifo_poll: tests ``drivers.uart.uart_mix_poll_async_api_`` fail - :github:`53643` - Invalid warning when BLE advertising times out - :github:`53674` - net: lwm2m: senml cbor formatter relying on implementation detail / inconsistency of lwm2m_path_to_string - :github:`53680` - HawkBit Metadata Error - :github:`53728` - Sensor API documentation: no mention of blocking behaviour - :github:`53729` - Can not build for ESP32 sample program - Zephyr using CMake build - :github:`53767` - `@kconfig` is not allowed in headline - :github:`53780` - sysbuild with custom board compilation failed to find the board - :github:`53790` - Flash Init fails when CONFIG_SPI_NOR_IDLE_IN_DPD=y - :github:`53800` - Raspberry Pi Pico - ssd1306 display attempts to initialize before i2c bus is ready for communication - :github:`53801` - k_busy_wait adds 1us delay unnecessarily - :github:`53823` - Bluetooth init failed on nrf5340_audio_dk_nrf5340_cpuapp - :github:`53855` - mimxrt1050_evk invalid writes to flash - :github:`53858` - Response on the shell missing with fast queries - :github:`53867` - kconfig: Linked code into external SEMC-controlled memory without boot header - :github:`53871` - Bluetooth: IPSP Sample Crash on nrf52840dk_nrf52840 - :github:`53873` - Syscall parser creates syscall macro for commented/ifdefed out syscall prototype - :github:`53917` - clang-format key incompatible with IntelliJ IDEs - :github:`53933` - tests: lib: spsc_pbuf: lib.spsc_pbuf... hangs - :github:`53937` - usb: stm32g0: sometimes get write error during CDC ACM enumeration when using USB hub - :github:`53939` - USB C PD stack no callback for MSG_NOT_SUPPORTED_RECEIVED policy notify - :github:`53964` - gpio_emul: ``gpio_`` functions not callable within an ISR - :github:`53980` - Bluetooth: hci: spi: race condition leading to deadlock - :github:`53993` - platform: Raspberry Pi Pico area: USB Default config should be bus powered device for the Raspberry Pi Pico - :github:`53996` - bt_conn_foreach() includes invalid connection while advertising - :github:`54014` - usb: using Bluetooth HCI class in composite device leads to conflicts - :github:`54037` - Unciast_audio_client sample application cannot work with servers with only sinks. - :github:`54047` - Bluetooth: Host: Invalid handling of Service Changed indication if GATT Service is registered after Bluetooth initialization and before settings load - :github:`54064` - doc: mgmt: mcumgr: img_mgmt: Documentation specifies that hash in state of images is a required field - :github:`54076` - logging fails to build with LOG_ALWAYS_RUNTIME=y - :github:`54085` - USB MSC Sample does not work for native_posix over USBIP - :github:`54092` - ZCBOR code generator generates names not compatible with C++ - :github:`54101` - bluetooth: shell: Lots of checks of type (unsigned < 0) which is bogus - :github:`54121` - Intel CAVS: tests/subsys/zbus/user_data fails - :github:`54122` - Intel CAVS: tests/subsys/dsp/basicmath fails (timeout) - :github:`54162` - Mass-Storage-Sample - USB HS support for the stm32f723e_disco board - :github:`54179` - DeviceTree compile failures do not stop build - :github:`54198` - reel board: Mesh badge demo fails to send BT Mesh message - :github:`54199` - ENC28J60: dns resolve fails after few minutes uptime - :github:`54200` - bq274xx incorrect conversions - :github:`54211` - tests: kernel: timer: timer_behavior: kernel.timer.timer fails - :github:`54226` - Code coverage collection is broken - :github:`54240` - twister: --runtime-artifact-cleanup has no effect - :github:`54275` - net: socket: tls: cannot send when using blocking socket - :github:`54288` - modem: hl7800: power off draws excessive current - :github:`54289` - Twister jobserver support eliminates parallel build for me - :github:`54301` - esp32: Console doesn't work with power management enabled - :github:`54317` - kernel: events: SMP race condition and one enhancement - :github:`54330` - West build command execution takes more time or fails sometimes - :github:`54336` - picolibc is incompatible with xcc / xcc-clang toolchains - :github:`54364` - CANopen SYNC message is not received - :github:`54373` - Mcuboot swap type is ``test`` when update fails - :github:`54377` - mec172xevb: benchmark.kernel.core (and adc_api/drivers.adc) failing - :github:`54407` - Bluetooth: Controller: ISO Central with continuous scanning asserts - :github:`54411` - mgmt: mcumgr: Shell transport can lock shell up until device is rebooted - :github:`54435` - mec172xevb: sample.drivers.sample.drivers.peci failing - :github:`54439` - Missing documentation of lwm2m_rd_client_resume and lwm2m_rd_client_pause - :github:`54444` - samples/modules/chre/sample.modules.chre should not attempt to build on toolchains w/o newlib - :github:`54459` - hawkbit: wrong header size used while reading the version of the app - :github:`54460` - Build system should skip ``zephyr/drivers/ethernet`` module if TAP & SLIP already provides a network driver in ``zephyr/drivers/net/slip.c`` - :github:`54498` - net: openthread: echo server do not work in userspace - :github:`54500` - jwt: memory allocation problem after multiple jwt_sign calls - :github:`54504` - LwM2M: Connection resume does not work after network error - :github:`54506` - net: ieee802154_6lo: wrong fragmentation of packets with specific payload sizes - :github:`54531` - Bluetooth: Controller: le_ext_create_connection fails with initiating_PHYs == 0x03 - :github:`54532` - Tests: Bluetooth: tester: BTP communication is not fully reliable on NRF52 board using UART - :github:`54538` - LE Audio: BAP Unicast Client Idle/CIS disconnect race condition - :github:`54539` - LE Audio: Unicast client should only disconnect CIS if both ASEs are not in streaming state - :github:`54542` - Bluetooth pending tx packets assert on disable - :github:`54554` - arch.arm.swap.tz fails to build for v2m_musca_b1_ns - :github:`54576` - Errors during IPv4 defragmenting - :github:`54577` - IPv6 defragmenting fails when segments do not overlap - :github:`54581` - STM32H7 adc sequence init function unstable logic return - :github:`54599` - net stats: many received TCP packets count as "dropped" - :github:`54609` - driver: led: kconfig symbols mix up - :github:`54610` - samples: kernel: metairq_dispatch: sample.kernel.metairq_dispatch hangs - :github:`54630` - memcpy crashes with NEW_LIBC on stm32 cortex m7 with debugger attached - :github:`54668` - shell: "log backend" command causes shell to lock up - :github:`54670` - stm32: memcpy crashes with NEWLIBC - :github:`54674` - modem: hl7800: DNS resolver does not start for IPv6 only - :github:`54683` - Missing input validation in gen_driver_kconfig_dts.py - :github:`54695` - usb mass storage on mimxrt595_evk_cm33 mount very slow - :github:`54705` - CDC USB shell receives garbage when application starts - :github:`54713` - LVGL Module File System Memory Leaks - :github:`54717` - --generate-hardware-map produces TypeError: expected string or bytes-like object on Windows - :github:`54719` - STM32 clock frequency calculation error - :github:`54720` - QEMU bug with branch delay slots on ARC - :github:`54726` - LittleFS test only works for specific device parameters - :github:`54731` - USB DFU sample does not reliably upload image on RT1050 - :github:`54737` - Wrong order of member initialization for macro Z_DEVICE_INIT - :github:`54739` - C++ Compatibility for DEVICE_DT_INST_DEFINE - :github:`54746` - ESP32 SPI word size is not respected - :github:`54754` - outdated version of rpi_pico hal configures USB PLL incorrectly - :github:`54755` - small timer periods take twice as much time as they should - :github:`54768` - nrf9160dk_nrf52840: flow control pins crossed - :github:`54769` - Error when flashing to LPCXpresso55S06 EVK. - :github:`54770` - Bluetooth: GATT: CCC and CF values written by privacy-disabled peer before bonding may be lost - :github:`54773` - Bluetooth: GATT: Possible race conditions related to GATT database hash calculation after settings load - :github:`54779` - file write gives -5 after file size reaches cache size - :github:`54783` - stm32: NULL dereference in net_eth_carrier_on - :github:`54785` - .data and .bss relocation to DTCM & CCM is broken with SDK 0.15+ - :github:`54798` - net: ipv4: IP packets get dropped in Zephyr when an application is receiving high rate data - :github:`54805` - when invoke dma_stm32_disable_stream failed in interrupt callback, it will endless loop - :github:`54813` - Bluetooth: host: Implicit sc_indicate declaration when Service Changed is disabled - :github:`54824` - BT: Mesh: Utilizes some not initialized variables - :github:`54826` - Clang/llvm build is broken: Error: initializer element is not a compile-time constant - :github:`54833` - ESPXX failing in gpio tests - :github:`54841` - Drivers: I2S: STM32: Mishandling of Master Clock output (MCK) - :github:`54844` - RAK5010 board has wrong LIS3DH INT pin configured - :github:`54846` - ESP32C3 SPI DMA host ID - :github:`54855` - ESP32: Compilation errors after migrating to zephyr 3.2.0 - :github:`54856` - nRF52840 nRF52833 Bluetooth: Timeout in ``net_config_init_by_iface`` but interface is up - :github:`54859` - LE Audio: BT_AUDIO_UNICAST_CLIENT_GROUP_STREAM_COUNT invalid descsi - :github:`54861` - up_squared: CHRE sample output mangling fails regex verification Addressed issues ================ * :github:`54873` - doc: Remove Google Analytics tracking code from generated documentation. * :github:`54858` - espressif blobs does not follow zephyr requirements * :github:`54872` - west flash --elf-file is not flashing using .elf file, but using zephyr.hex to flash * :github:`54813` - Bluetooth: host: Implicit sc_indicate declaration when Service Changed is disabled * :github:`54804` - Warning (simple_bus_reg): /soc/can: missing or empty reg/ranges property * :github:`54786` - doc: Version selector should link to latest LTS version instead of 2.7.0 * :github:`54782` - nrf_rtc_timer may not properly handle a timeout that is set in specific conditions * :github:`54770` - Bluetooth: GATT: CCC and CF values written by privacy-disabled peer before bonding may be lost * :github:`54760` - net_lwm2m_engine: fcntl(F_GETFL) failed (-22) on es-wifi * :github:`54730` - intel_adsp_ace15_mtpm: cpp.main.minimal test failing * :github:`54718` - The rf2xx driver uses a wrong bit mask on TRAC_STATUS * :github:`54710` - Sending NODE_RX_TYPE_CIS_ESTABLISHED messes up LLCP * :github:`54703` - boards: thingy53: Inconsistent method of setting USB related log level * :github:`54702` - boards: thingy53: USB remote wakeup is not correctly disabled * :github:`54686` - RP2040: Cleanup incorrect comment and condition from the USB driver * :github:`54685` - drivers: serial: rp2040: fix rpi pico address mapping * :github:`54671` - Bluetooth: spurious error when using hci_rpmsg * :github:`54666` - LE Audio: EALREADY error of ase_stream_qos() not mapped * :github:`54659` - boards: arm: nrf52840dongle_nrf52840: Defaults to UART which is not connected (and mcuboot build fails) * :github:`54654` - LE Audio: Kconfig typo in ``pacs.c`` * :github:`54642` - Bluetooth: Controller: Assertion on disconnecting CIS and assertion on synchronizing to first encrypted BIS * :github:`54614` - Cannot flash b_l4s5i_iot01a samples/hello_world * :github:`54613` - Bluetooth: Unable to enable PAST as advertiser without periodic sync support * :github:`54605` - native_posix_64 platform broken in Twister * :github:`54597` - SRAM2 wrong on certain stm32h7 SOC (system crashes during startup) * :github:`54580` - samples/subsys/task_wdt fails with timeout on s32z270dc2_r52 boards * :github:`54575` - Automatic termination with return code from a native_posix main function * :github:`54574` - USB RNDIS Reception and Descriptor Issue(s) * :github:`54573` - gpio_hogs test uses an incorrect GPIO spec handle * :github:`54572` - QEMU networking breakage (Updating nrf-sdk 2.1->2.2 , implies zephyr 3.1 -> 3.2) * :github:`54569` - MMC subsys shares sdmmc kconfigs * :github:`54567` - Assertion in z_add_timeout() fails in drivers.uart.uart_mix_poll_async_api test * :github:`54563` - Variable uninitialised in flash_stm32_page_layout * :github:`54558` - LPTIM Kconfig-related build failures for nucleo_g431rb * :github:`54557` - sample.drivers.flash.shell fails to build for adafruit_kb2040 * :github:`54556` - sample.display.lvgl.gui fails to build for stm32f429i_disc1 * :github:`54545` - boards: rpi_pico: Bad MPU settings * :github:`54544` - Bluetooth: controller: HCI/CCO/BI-45-C setHostFeatureBit failing * :github:`54540` - psa_crypto variants of drivers/entropy/api and crypto/rand32 tests fail to build for nrf9160dk_nrf9160_ns and nrf5340dk_nrf5340_cpuapp_ns * :github:`54537` - logging.add.async build fails on mtpm with xcc-clang * :github:`54534` - PSoC6/Cat1 add binary blob for Cortex-M0+ core * :github:`54533` - tests/drivers/can/timing fails on nucleo_f746zg * :github:`54529` - Bluetooth: shell: Missing help messages and parameters * :github:`54528` - log switch_format, mipi_syst tests failing on intel_adsp_ace15_mtpm * :github:`54522` - Can we embrace GNU Build IDs? * :github:`54516` - twister: Quarantine verify works incorrectly with integration mode * :github:`54509` - Zephyr does not configure TF-M correctly for Hard-Float * :github:`54507` - CONFIG_PM=y results to hard fault system for STM32L083 * :github:`54499` - stm32u5 lptimer driver init must wait after interrupt reg * :github:`54493` - samples/drivers/counter/alarm/ fails on nucleo_f746zg * :github:`54492` - west: twister return code ignored by west * :github:`54484` - Intel CAVS25: tests/boards/intel_adsp/ssp/ fails * :github:`54472` - How to enable a node in main. * :github:`54469` - nsim_sem and nsim_em7d_v22 failed in zdsp.basicmath test * :github:`54462` - usb_dc_rpi_pico driver enables some interrupts it doesn't handle * :github:`54461` - SAM spi bus inoperable when interrupted on fast path * :github:`54457` - DHCPv4 starts even when interface is not operationally up * :github:`54455` - Many tests have wrong component and are wrongly categorized * :github:`54454` - Twister summary in some cases provides an irrelevant example * :github:`54450` - nuvoton_pfm_m487 failed to build due to missing M48x-pinctrl.h * :github:`54440` - tests/net/lib/lwm2m/lwm2m_registry/subsys.net.lib.lwm2m.lwm2m_registry fails to build w/toolchains that don't support newlib * :github:`54438` - question: why lwm2m_rd_client_stop might block * :github:`54431` - adafruit kb2040 board configuration is invalid and lack flash controller * :github:`54428` - esp32 invalid flash dependencies * :github:`54427` - stm32 uart driver ``LOG_`` msg crashes when entering sleep mode * :github:`54422` - modules: openthread: multiple definition in openthread config * :github:`54417` - Intel CAVS18: tests/subsys/dsp/basicmath fails * :github:`54414` - stm32u5 dma driver does not support repeated start-stop * :github:`54412` - [hci_uart] nrf52840 & BlueZ 5.55 - start / stop scanning breaks * :github:`54410` - [BUG] TLB driver fails to unmap L2 HPSRAM region when assertions are enabled * :github:`54409` - ETH MAC config for STM32H7X and STM32_HAL_API_V2 too late and fails * :github:`54405` - Nominate @Vge0rge as contributor * :github:`54401` - Uninitialized has_param struct sometimes causes BSIM "has.sh" test to fail * :github:`54399` - Intel CAVS18: tests/subsys/zbus/user_data/user_data.channel_user_data FAILED * :github:`54397` - Test posix_header fails on some STM32 Nucleo boards * :github:`54395` - mgmt: mcumgr: img_grp: Upload inspect fails when using swap using scratch * :github:`54393` - Bluetooth: Controller: Starting a second BIG causes them to overlap and have twice the interval * :github:`54387` - soc: arm: st_stm32: Incorrect SRAM devicetree definition for the STM32L471xx * :github:`54384` - Removal of old runner options caused downstream breakage * :github:`54378` - Net pkt PPP dependency bug * :github:`54374` - ARC: west runner: mdb: incorrect handling of unsupported jtag adapters * :github:`54372` - ARC: west runner: mdb: unexpected empty argument pass to MDB executable * :github:`54366` - tests: pin_get_config failed on it8xxx2_evb, again * :github:`54361` - Incorrect network stats for Neighbour Discovery packets * :github:`54360` - enable HTTPS server on Zephyr RTOS * :github:`54356` - Bluetooth: Scanner consumption while scanning * :github:`54351` - Tests: bluetooth: failing unittests * :github:`54347` - zephyr/posix/fcntl.h header works differently on native_posix platform * :github:`54344` - Bluetooth: Controller: Central ACL connections overlap Broadcast ISO BIG event * :github:`54342` - Bluetooth: Controller: Connected ISO Central causes Peripheral to drop ISO data PDUs * :github:`54341` - Bluetooth: Controller: Direction finding samples do not reconnect after disconnection * :github:`54335` - tests/kernel/fatal/no-multithreading/kernel.no-mt.cpu_exception failing on qemu_cortex_m3 * :github:`54334` - Need support to define partitions for usage with mcuboot * :github:`54332` - LwM2M engine is does not go into non-block mode anymore in native_posix target * :github:`54327` - intel_adsp: ace: various multicore bugs, timeouts * :github:`54321` - ARC: unusable console after west flash or west debug with mdb runners * :github:`54318` - boards: nucleo_g474re: openocd runner is not stable enough for intensive testing * :github:`54316` - RTT is not working correctly on STM32U5 series * :github:`54315` - Problem seen with touch screen on RT1170 when running the LVGL sample * :github:`54310` - Using NOCOPY code relocation generates a warning flag * :github:`54287` - modem: hl7800: PSM hibernate draws excessive current * :github:`54274` - newlib: Document CONFIG_NEWLIB_LIBC_NANO default change * :github:`54258` - boards: arm: twr_ke18f: LPTMR always enabled, resulting in low system timer resolution * :github:`54254` - tests: canbus: isotp: conformance: test fails with CONFIG_SYS_CLOCK_TICKS_PER_SEC=100 * :github:`54253` - v3.3.0-rc1: stm32: IPv6 neighbour solicitation packets are not received without CONFIG_ETH_STM32_MULTICAST_FILTER * :github:`54247` - tests: net: tcp: net.tcp.simple fails * :github:`54246` - Sample:subsys/ipc/rpmsg_server:The two cores cannot communicate in nRF5340 * :github:`54241` - The cy8c95xx I2C GPIO expander support was broken in #47841 * :github:`54236` - b_u585i_iot02a_ns: Can't build TFM enabled samples (TF-M 1.7.0) * :github:`54230` - STM32H7: Kernel crash with BCM4=0 * :github:`54225` - Intel CAVS: tests/lib/c_lib/ fails * :github:`54224` - Issues with picolibc on xtensa platforms * :github:`54223` - Intel CAVS: tests/kernel/common/kernel.common.picolibc fails * :github:`54214` - Display framebuffer allocation * :github:`54210` - tests: drivers: udc drivers.udc fails * :github:`54209` - USB C PD dead battery support * :github:`54208` - Various RISC-V FPU context switching issues * :github:`54205` - Regression: RiscV FPU regs not saved in multithreaded applications * :github:`54202` - decawave_dwm1001_dev: i2c broken due to pinctrl_nrf fix * :github:`54190` - RP2040 cannot be compiled with C11 enabled * :github:`54173` - Bluetooth: GATT: Change awareness of bonded GATT Client is not maintained on reconnection after reboot * :github:`54172` - Bluetooth: GATT: Written value of gatt_cf_cfg data may be dropped on power down * :github:`54148` - qemu_x86_tiny places picolibc text outside of pinned.text * :github:`54140` - BUS FAULT when running nmap towards echo_async sample * :github:`54139` - Bluetooth: Audio: race hazard bt_audio_discover() callback vs unicast_client_ase_cp_discover() * :github:`54138` - Buetooth: shell: `bt adv-data` isn't working properly * :github:`54136` - Socket error after deregistration causes RD client state machine to re-register * :github:`54123` - Intel CAVS 25: tests/boards/intel_adsp/ssp fails * :github:`54117` - West flash fails on upload to Nucleo F303K8 * :github:`54104` - Bluetooth: Host: Bonding information distribution in the non-bondable mode * :github:`54087` - tests:igmp:frdm_k64f: igmp test fails * :github:`54086` - test:rio:frdm_k64f: rio user_space test fails with zephyr-v3.2.0-3842-g7ffc20082023 * :github:`54078` - No activity on can_tx when running the ISO-TP sample * :github:`54072` - Bluetooth: Host: Periodic scanner does not differentiate between partial and incomplete data * :github:`54065` - How To Change C++ Version Compilation Option For Freestanding Application? * :github:`54053` - CI:frdm_k64f: kernel.common.stack_protection test failure * :github:`54034` - QSPI: Unable to build the project when introduced DMA into external flash interfacing * :github:`54017` - Modules: TF-M: Resolve QCBOR issues with TF-M 1.7.0 * :github:`54005` - esp32 Severe crash using modules with embedded PSRAM (eg esp32-wroom-32E-n8r2) * :github:`54002` - mgmt: mcumgr: bluetooth transport: Inability to use refactored transport as a library in some circumstances * :github:`53995` - drivers: ethernet: stm32: Enable ethernet statistics in the driver * :github:`53994` - net: ethernet: Multicast receive packets statistics are not getting updated * :github:`53991` - LE Audio: samples/bluetooth/broadcast_audio_sink configure error * :github:`53989` - STM32 usb networking stack threading issue * :github:`53967` - net: http client: HTTP timeout can lead to deadlock of global system queue * :github:`53954` - tests: lib: ringbuffer: libraries.ring_buffer hangs * :github:`53952` - USB C PD sink sample stops working when connected to a non-PD source * :github:`53942` - Websocket: No close message on websocket close * :github:`53936` - Enabling CONFIG_TRACING and CONFIG_EVENTS causes undefined reference error * :github:`53935` - stm32 iwdt wdt_install_timeout not working properly * :github:`53926` - Bluetooth Mesh stack question * :github:`53916` - Multichannel PWM for STM32U575 * :github:`53913` - net: ip: igmp: IGMP doesn't get initialised because the iface->config.ip.ipv4 pointer is not initialised * :github:`53911` - Info request: SMP Hash * :github:`53900` - led_set_brightness() is not setting brightness after led_blink() for STM32U575 * :github:`53885` - Ethernet TCP Client Issue description with iperf/zperf * :github:`53876` - The handle of att indication violates the spec * :github:`53862` - Switching from USB to UART * :github:`53859` - RFC: Board porting guide: Do not assume OS or default ports for board files * :github:`53808` - Improve PLLI2S VCO precision * :github:`53805` - peripheral_dis compilation reports RAM overflow for BBC microbit * :github:`53799` - Info request: SMP hash definition * :github:`53786` - BLE:DF: slot_plus_us is not set properly * :github:`53782` - nrf5340dk: missing i2c bias pull up * :github:`53781` - Allow resetting STM32 peripherals through RCC peripheral reset register * :github:`53777` - mgmt: mcumgr: Change transport selects to depends on * :github:`53773` - drivers: ethernet: stm32: Completion of enabling the multicast hash filter * :github:`53756` - esp32 - Wrong value for the default cpu freq -> crash on assert * :github:`53753` - [DOC] Mismatch of driver sample overview * :github:`53744` - ztest: assert() functions does not always retuns * :github:`53723` - device tree macro: GPIO_DT_SPEC_INST_GET_BY_IDX_OR does not work * :github:`53720` - Bluetooth: Controller: Incorrect address type for PA sync established * :github:`53715` - mec15xxevb_assy6853: broken UART console output * :github:`53707` - fs: fcb: Add option to disable CRC for FCB entries * :github:`53697` - Can not run the usb mass storage demo on NXP mimxrt595_evk_cm33 * :github:`53696` - sysbuild should not parse the board revision conf * :github:`53689` - boards: nrf52840dongle_nrf52840 is missing storage partition definition * :github:`53676` - net: lwm2m: inconsistent path string handling throughout the codebase * :github:`53673` - samples: posix: gettimeofday does not build on native_posix * :github:`53663` - Error while trying to flash nucleo_f446re: TARGET: stm32f4x.cpu - Not halted * :github:`53656` - twister: samples: Bogus yaml for code_relocation sample * :github:`53654` - SPI2 not working on STM32L412 * :github:`53652` - samples: mgmt: mcumgr: fs overlay does not work * :github:`53642` - Display driver sample seems to mix up RGB565 and BGR565 * :github:`53636` - cdc_acm fails on lpcxpresso55s69 board * :github:`53630` - net: ieee802154_6lo: REGRESSION: L2 MAC byte swapping results in wrong IPHC decompression * :github:`53617` - unicast_audio_client and unicast_audio_server example assert * :github:`53612` - file system (LFS?): failure to expand file with truncate * :github:`53610` - k_malloc and settings * :github:`53604` - testsuite: Broken Kconfig prevents building tests for nrf52840dk_nrf52840 platform * :github:`53584` - STM32F1 PWM Input Capture Issue * :github:`53579` - add_compile_definitions does not "propagate upwards" as supposed to when using west * :github:`53568` - Kconfig search has white on white text * :github:`53566` - Use fixup commits during code review * :github:`53559` - mgmt: mcumgr: explore why UART interface is so slow (possible go application fault) * :github:`53556` - Cannot add multiple out-of-the-tree secure partitions * :github:`53549` - mgmt: mcumgr: callbacks: Callbacks events for a single group should be able to be combined * :github:`53548` - net: ip: igmp: Mechanism to add MAC address for IGMP all systems multicast address to an ethernet multicast hash filter * :github:`53535` - define a recommended process in zephyr for a CI framework integration * :github:`53520` - tests: drivers: gpio: gpio_api_1pin: peripheral.gpio.1pin fails * :github:`53513` - STM32 PWM Input Capture Issue * :github:`53500` - ``net_tcp: context->tcp == NULL`` error messages during TCP connection * :github:`53495` - RFC: treewide: python: argparse default configuration allows shortened command arguments * :github:`53490` - Peridic current spike using tickless Zephyr * :github:`53488` - Missing UUID for PBA and TMAS * :github:`53487` - west: flash: stm32cubeprogrammer: Reset command line argument is wrong * :github:`53474` - Sysbuild cmake enters infinite loop if 2 images are added to a build with the same name * :github:`53470` - Unable to build using Arduino Zero * :github:`53468` - STM32 single-wire UART not working when poll-out more than 1 char * :github:`53466` - Nucleo F413ZH CAN bus support * :github:`53458` - IPv4 address autoconfiguration leaks TX packets/buffers * :github:`53455` - GATT: Deadlock while sending GATT notification from system workqueue thread * :github:`53451` - USB: Suspending CDC ACM can lead to endpoint/transfer state mismatch * :github:`53446` - Bluetooth: Controller: ll_setup_iso_path not working if both CIS and BIS supported * :github:`53438` - unable to wakeup from Stop2 mode * :github:`53437` - WaveShare xnucleo_f411re: Error: `` Unable to reset target `` * :github:`53433` - flash content erase in bootloader region at run time * :github:`53430` - drivers: display: otm8009a: import 3rd-party source * :github:`53425` - Do we have support for rtc subsecond calculation in zephyr. * :github:`53424` - Reopen issue #49390 * :github:`53423` - [bisected] logging.log_msg_no_overflow is failing on qemu_riscv64 * :github:`53421` - cpp: defined popcount macro prevents use of std::popcount * :github:`53419` - net: stats: DHCP packets are not counted as part of UDP counters * :github:`53417` - CAN-FD / MCAN driver: Possible variable overflow for some MCUs * :github:`53407` - Support of regex * :github:`53385` - SWD not working on STM32F405 * :github:`53366` - net: ethernet: provide a way to get ethernet config * :github:`53361` - Adding I2C devices SX1509B to Devicetree with the same address on different busses generates FATAL ERROR. * :github:`53360` - kernel: k_msgq: add peek_more function * :github:`53347` - WINC1500 socket recv fail * :github:`53340` - net: lwm2m: add BinaryAppDataContainer object (19) * :github:`53335` - Undeclared constants in devicetree_generated.h * :github:`53326` - usb: device: usb_dfu: k_mutex is being called from isr * :github:`53315` - Fix possible underflow in tcp flags parse. * :github:`53306` - scripts: utils: migrate_mcumgr_kconfigs.py: Missing options * :github:`53301` - Bluetooth: Controller: Cannot recreate CIG * :github:`53294` - samples: mgmt: mcumgr: smp_svr: UDP file can be removed * :github:`53293` - mgmt: mcumgr: CONFIG_MCUMGR_GRP_IMG_REJECT_DIRECT_XIP_MISMATCHED_SLOT causes a build failure * :github:`53285` - SNTP & DATE_TIME & SERVER ADDRESS configuration and behavior * :github:`53280` - Bluetooth: security level failure with multiple links * :github:`53276` - doc: mgmt: mcumgr: fix "some unspecified" error * :github:`53271` - modules: segger: KConfigs are broken * :github:`53259` - RFC: API Change: dma: callback status * :github:`53254` - Bluetooth: bt_conn_foreach() reports unstable conn ref before the connection is completed * :github:`53247` - ATT timeout followed by a segmentation fault * :github:`53242` - Controller in HCI UART RAW mode responds to Stop Discovery mgmt command with 0x0b status code * :github:`53240` - Task Watchdog Fallback Timeout Before Installing Timeout - STM32 * :github:`53236` - Make USB VBUS sensing configurable for STM32 devices * :github:`53231` - drivers/flash/flash_stm32l5_u5.c : unable to use full 2MB flash with TF-M activated * :github:`53227` - mgmt: mcumgr: Possible instability with USB CDC data transfer * :github:`53223` - LE Audio: Add interleaved packing for LE audio * :github:`53221` - Systemview trace id overlap * :github:`53209` - LwM2M: Replace pathstrings from the APIs * :github:`53194` - tests: kernel: timer: starve: DTS failure stm32f3_seco_d23 * :github:`53189` - Mesh CI failure with BT_MESH_LPN_RECV_DELAY * :github:`53175` - Select pin properties from shield overlay * :github:`53164` - mgmt: mcumgr: NMP Timeout with smp_svr example * :github:`53158` - SPIM transaction timeout leads to crash * :github:`53151` - fs: FAT_FS_API MKFS test uses driver specific calls * :github:`53147` - usb: cdc_acm: log related warning promoted to error * :github:`53141` - For pinctrl on STM32 pin cannot be defined as push-pull with low level * :github:`53129` - Build fails on ESP32 when enabling websocket client API * :github:`53103` - Zephyr shell on litex : number higher than 10 are printed as repeated hex * :github:`53101` - esp32: The startup code hangs after reboot via sys_reboot(...) * :github:`53094` - Extend Zperf command * :github:`53093` - ARM: Ability to query CFSR on exception * :github:`53059` - Bluetooth: peripheral GATT notification call takes a lot of time * :github:`53049` - Bluetooth: LL assertion fail with peripherals connect/disconnect rounds * :github:`53048` - Bluetooth: legacy advertising doesn't resume if CONFIG_BT_EXT_ADV=y * :github:`53046` - Bluetooth: Failed to set security level for the second connection * :github:`53043` - Bluetooth: Peripheral misses notifications from Central after setting security level * :github:`53033` - tests-ci : libraries: encoding: jwt test Failed * :github:`53034` - tests-ci : os: mgmt: info_net test No Console Output(Timeout) * :github:`53035` - tests-ci : crypto: rand32: random_ctr_drbg test No Console Output(Timeout) * :github:`53036` - tests-ci : testing: ztest: base.verbose_1 test No Console Output(Timeout) * :github:`53037` - tests-ci : net: mqtt_sn: client test No Console Output(Timeout) * :github:`53038` - tests-ci : net: socket: mgmt test No Console Output(Timeout) * :github:`53039` - tests-ci : net: socket: af_packet.ipproto_raw test No Console Output(Timeout) * :github:`53040` - tests-ci : net: ipv4: fragment test No Console Output(Timeout) * :github:`53019` - random: Zephyr enables TEST_RANDOM_GENERATOR when it should not * :github:`53012` - stm32u5: timer api: lptim: k_msleep is twice long as expected * :github:`53010` - timers: large drift if hardware timer has a low resolution * :github:`53007` - Bluetooth: Notification callback is called with incorrect connection reference * :github:`53002` - Incorrect hardware reset cause sets for watchdog reset on stm32h743zi * :github:`52996` - kconfig: Use of multiple fragment files with OVERLAY_CONFIG not taking effect * :github:`52995` - Add triage permissions for dianazig * :github:`52983` - Bluetooth: Audio: BT_CODEC_LC3_CONFIG_DATA fails to compile with _frame_blocks_per_sdu > 1 * :github:`52981` - LOG_MODE_MINIMAL do not work with USB_CDC for nRF52840 * :github:`52975` - posix: clock: current method of capturing elapsed time leads to loss in seconds * :github:`52970` - samples/net/wifi example does not work with ESP32 * :github:`52962` - Bluetooth non-functional on nRF5340 target * :github:`52935` - Missing Libraries * :github:`52931` - Filesystem Write Fails with Some SD-Cards * :github:`52925` - Using #define LOG_LEVEL 0 does not filter out logs * :github:`52920` - qemu_cortex_r5: tests/ztest/base * :github:`52918` - qemu_cortex_r5` CI fails * :github:`52914` - drivers: adc: ADC_CONFIGURABLE_INPUTS confict between 2 ADCs * :github:`52913` - twister build fails but returns exit code of 0 * :github:`52909` - usb: usb don't work after switch from Zephyr 2.7.3 to 3.2.99 on i.MX RT1020 * :github:`52898` - mgmt: mcumgr: replace cmake functions without zephyr prefix to have zephyr prefix * :github:`52882` - Sample applications that enable USB and error if it fails are incompatible with boards like thingy53 with auto-USB init (i.e. USB CDC for logging) * :github:`52878` - Bluetooth: Unable use native_posix with shell demo * :github:`52872` - Logging to USB CDC ACM limited to very low rate * :github:`52870` - ESP32-C3 System clock resolution improvements * :github:`52857` - Adafruit WINC1500 Wifi Shield doesn't work on nRF528XX * :github:`52855` - Improve artifact generation for split build/test operation of twister * :github:`52854` - twister build fails but returns exit code of 0 * :github:`52838` - Bluetooth: audioinvalid ase state transition * :github:`52833` - Bluetooth Controller assertion on sys_reboot() with active connections (lll_preempt_calc: Actual EVENT_OVERHEAD_START_US) * :github:`52829` - kernel/sched: Fix SMP race on pend * :github:`52818` - samples: subsys: usb: shell: sample.usbd.shell fails - no output from console * :github:`52817` - tests: drivers: udc: dirvers.udc fails * :github:`52813` - stm32h7: dsi: ltdc: clock: PLL3: clock not set up correctly or side effect * :github:`52812` - Various problems with pipes (Not unblocking, Data Access Violation, unblocking wrong thread...) * :github:`52805` - Code crashing due to ADC Sync operation (STM32F4) * :github:`52803` - Kconfig: STM32F4 UF2 family ID * :github:`52795` - Remove deprecated tinycbor module * :github:`52794` - Possible regression for printk() output of i2c sensor data on amg88xx sample * :github:`52788` - Re-enable LVGL support for M0 processors. * :github:`52784` - NRF_DRIVE_S0D1 option is not always set in the nordic,nrf-twi and nordic,nrf-twim nodes, when using shield? * :github:`52779` - Error While adding the mcuboot folder in repo. * :github:`52776` - ite: eSPI driver: espi_it8xxx2_send_vwire() is not setting valid flag along with respective virtual wire when invoked from app code. * :github:`52754` - tests/drivers/bbram: Refactor to use a common prj.conf * :github:`52749` - posix: getopt: cannot use getopt() in a standard way * :github:`52739` - Newlib defines POSIX primitives when -std=gnu * :github:`52721` - Minimal logging does not work if printk and boot banner are disabled * :github:`52718` - Simplify handling of fragments in ``net_buf`` * :github:`52709` - samples: subsys: nvs: sample.nvs.basic does not complete within twister default timeout * :github:`52708` - samples: drivers: watchdog: sample.drivers.watchdog loops endlessly * :github:`52707` - samples: subsys: task_wdt: sample.subsys.task_wdt loops endlessly * :github:`52703` - tests: subsys: usb: device: usb.device USAGE FAULT exception * :github:`52691` - cannot read octospi flash when partition size exceeds 4mb * :github:`52690` - coredump: stm32l5: I-cache error on coredump backend in flash * :github:`52675` - I2C: STM32F0 can't switch to HSI clock by default and change timing * :github:`52673` - mcux: flexcan: forever waiting semaphore in can_send() * :github:`52670` - tests: subsys: usb: device: usb.device hangs * :github:`52652` - drivers: sensors: bmi08x config file * :github:`52641` - armv7: mpu: RASR size field incorrectly initialized * :github:`52632` - MQTT over WebSockets: After hours of running time receiving published messages is strongly delayed * :github:`52628` - spi: NXP MCUX LPSPI driver does not correctly change baud rate once configured * :github:`52626` - Improve LLCP unit tests * :github:`52625` - USB device: mimxrt685_evk_cm33: premature ZLP during control IN transfer * :github:`52614` - Empty "west build --test-item" doesn't report warnings/errors * :github:`52602` - tests: subsys: settings: file_littlefs: system.settings.file_littlefs.raw fails * :github:`52598` - esp32c3 Unable to do any timing faster than 1ms * :github:`52595` - Twister: unable to run tests on real hardware * :github:`52588` - ESP32c3 SPI driver DMA mode limited to 64 byte chunks * :github:`52566` - Error while build esp32 samples/hello_world * :github:`52563` - spi_transceive with DMA for STM32 does not work for devices with 16 bit words. * :github:`52561` - fsl_flexcan missing flags * :github:`52559` - Compiler cannot include C++ headers when both PICOLIBC and LIB_CPLUSPLUS options are set * :github:`52556` - adc driver sample was failing with STM32 nucleo_f429zi board * :github:`52548` - Late device driver initialization * :github:`52539` - Broken linker script for the esp32 platform * :github:`52534` - Missing include to src/core/lv_theme.h in src/themes/mono/lv_theme_mono.h * :github:`52528` - Zephyr support for Nordic devices Thingy with TFLM * :github:`52527` - net: lwm2m: wrong SenML CBOR object link encoding * :github:`52526` - Simplify lvgl.h file by creating more header files inside module's sub-filoders (src/widgets and src/layouts) * :github:`52518` - lib: posix: usleep() does not follow the POSIX spec * :github:`52517` - lib: posix: sleep() does not return the number of seconds left if interrupted * :github:`52506` - GPIO multiple gaps cause incorrect pinout check * :github:`52493` - net: lwm2m: add 32 bits floating point support * :github:`52486` - Losing connection with JLink on STM32H743IIK6 with Zephyr 2.7.2 * :github:`52479` - incorrect canopennode SDO CRC * :github:`52472` - Set compiler options only for a custom/external module * :github:`52464` - LE Audio: Unicast Client failing to create the CIG * :github:`52462` - uart: stm32: UART clock source not initialized * :github:`52457` - compilation error with "west build -b lpcxpresso54114_m4 samples/subsys/ipc/openamp/ " * :github:`52455` - ARC: MWDT: minimal libc includes * :github:`52452` - drivers: pwm: loopback test fails on frdm_k64f * :github:`52449` - net: ip: igmp: IGMP v2 membership reports are sent to 224.0.0.2 instead of the group being reported * :github:`52448` - esp32: subsys: settings: not working properly on esp_wrover_kit * :github:`52443` - Concerns with maintaining separate kernel device drivers for fuel-gauge and charger ICs * :github:`52415` - tests: kernel: timer: timer_behavior: kernel.timer.timer fails * :github:`52412` - doc: mgmt: mcumgr: Clarify that hash in img_mgmt is a full sha256 hash and required * :github:`52409` - STM32H7: ethernet: Device fails to receive any IP packets over ethernet after receiving UDP/IP multicast at a constant rate for some time * :github:`52407` - tests: subsys: mgmt: mcumgr: Test needed that enables all features/Kconfigs * :github:`52404` - mgmt: mcumgr: Callback include file has file name typo * :github:`52401` - mgmt: mcumgr: Leftover files after directory update * :github:`52399` - cmake error * :github:`52393` - Controller: ACL packets NACKed after Data Length Update * :github:`52376` - Cannot build apps with main in a .cpp file * :github:`52366` - LE Audio: Missing released callback for streams on ACL disconnect * :github:`52360` - samples/net/sockets/socketpair does not run as expected * :github:`52353` - bug: sysbuild lost board reversion here * :github:`52352` - Questions about newlib library * :github:`52351` - Bluetooth: Controller: ISOAL ASSERT failure * :github:`52344` - Software-based Debounced GPIO * :github:`52339` - usb: USB device re-enabling does not work on Nordic devices (regression) * :github:`52327` - websocket: websocket_recv_msg breaks when there is no data after header * :github:`52324` - Bluetooth Mesh example seems broken on v3.2.99 - worked ok with v3.1.99 * :github:`52317` - drivers: wifi: eswifi: Offload sockets accessing invalid net_context, resulting in errors in FLASH_SR and blocking flash use * :github:`52309` - SAM0 flash driver with page emulated enabled will not write data at 0 block * :github:`52308` - pip3 is unable to build wheel for cmsis-pack-manager as part of the requirements.txt on Fedora 37. * :github:`52307` - Linker Error using CONSOLE_GETCHAR and CONSOLE_GETLINE * :github:`52301` - Zephyr-Hello World is not working * :github:`52298` - CI fail multiple times due to download package from path_to_url failed. * :github:`52296` - Regulator shell does not build due to missing atoi define * :github:`52291` - boards: thingy53: Enable USB-CDC by default * :github:`52284` - unable to malloc during tests/lib/cmsis_dsp/transform.cf64 * :github:`52280` - boards: thingy53 non-secure (thingy53_nrf5340_cpuapp_ns) does not build * :github:`52276` - stm32: ST Kit B-L4S5I-IOT01A Octospi flash support * :github:`52267` - http client includes chunking data in response body when making a non-chunked request and server responds with chunked data * :github:`52262` - west flash --file * :github:`52242` - Fatal exception LoadProhibited from mcuboot when enabling newlib in wifi sample (esp32) * :github:`52235` - counter_basic_api test fails to build on STM32 platforms * :github:`52228` - Bluetooth: L2CAP: receive a K-frame with payload longer than MPS if Enhanced ATT enabled * :github:`52219` - jlink runner doesn't flash bin file if a hex file is present * :github:`52218` - ADC read locked forever with CONFIG_DEBUG_OPTIMISATION=y on STM32U5 * :github:`52216` - spi_transceive with DMA on a STM32 slave returns value incorrect * :github:`52211` - MCUX based QDEC driver * :github:`52196` - Calling ``bt_le_ext_adv_stop()`` can causes failures in connections when support for multiple connections are enabled * :github:`52195` - Bluetooth: GATT: add_subscriptions not respecting encryption * :github:`52190` - [lpcxpresso55s28] flash range starts from Secure address which is not compatible with latest Jlink(v7.82a) * :github:`52189` - Flash file system not working on stm32h735g_disco * :github:`52181` - ADC Channel SCAN mode for STM32U5 * :github:`52171` - Bluetooth: BR/EDR: Inappropriate l2cap channel state set/get * :github:`52169` - Mesh provisioning static OOB incorrect zero padding * :github:`52167` - twister: Mechanism to pass CLI args through to ztest executable * :github:`52154` - mgmt: mcumgr: Add Kconfig to automatically register handlers and mcumgr functionality * :github:`52139` - ppp modem doesn't send NET_EVENT_L4_CONNECTED event * :github:`52131` - tests-ci : kernel: timer: starve test No Console Output(Timeout) * :github:`52125` - Timer accuracy issue with STM32U5 board * :github:`52114` - Can't make JerryScript Work with Zephyr * :github:`52113` - Binary blobs in ``hal_telink`` submodules * :github:`52111` - Incompatible LTO version of liblt_9518_zephyr.a * :github:`52103` - STM32u5 dual bank flash issue * :github:`52101` - ``bt_gatt_notify`` function does not notify data larger than 20 bytes * :github:`52099` - mgmt: mcumgr: Rename fs_mgmt hash/checksum functions * :github:`52095` - dfu/mcuboot: dfu/mcuboot.h used BOOT_MAX_ALIGN and BOOT_MAGIC_SZ but does not include ``bootutil/bootutil_public.h`` * :github:`52094` - STM32MP157 Debugging method use wrong GDB port when execute command ``west debug`` * :github:`52085` - can: SAM M_CAN regression * :github:`52079` - TLS handshake failure (after client-hello) with big_http_download sample * :github:`52073` - ESP32-C3 UART1 not available after zephyr update to v3.2.99 * :github:`52065` - west: debugserver command does not work * :github:`52059` - Bluetooth: conn: in multi role configuration incorrect address is set after advertising resume * :github:`52057` - tests: kernel: timer: starve: kernel.timer.starve hangs * :github:`52056` - Bluetooth: Missing LL data length update callback on Central and Peripheral sides * :github:`52055` - Bluetooth: Controller: Broadcast scheduling issues * :github:`52049` - Update mps2_an521_remote for compatibility with mps2_an521_ns * :github:`52022` - RFC: API Change: mgmt: mcumgr: transport: Add query valid check function * :github:`52021` - RFC: API Change: mgmt: mcumgr: Replace mgmt_ctxt struct with smp_streamer * :github:`52009` - tests: kernel: fifo: fifo_timeout: kernel.fifo.timeout fails on nrf5340dk_nrf5340_cpuapp * :github:`51998` - Nominate Attie Grande as zephyr Collaborator * :github:`51997` - microTVM or zephyr bugs, No SOURCES given to Zephyr library * :github:`51989` - stm32f303v(b-c)tx-pinctrl.dtsi, No such file or directory * :github:`51984` - Bluetooth: Central rejects connection parameters update request from a connected peripheral * :github:`51973` - Coding style problem, clang-format formatted code cannot pass CI. * :github:`51951` - Zephyr Getting Started steps fail with Python v3.11 * :github:`51944` - lsm6dso sensnsor driver: to enable drdy in pulsed mode call ``lsm6dso_data_ready_mode_set()`` * :github:`51939` - mgmt: mcumgr: SMP is broken * :github:`51931` - Failing unit test re. missing PERIPHERAL_ISO_SUPPORT KConfig selection * :github:`51893` - LSM303dlhc sensor example not compiling for nRF52840 * :github:`51874` - Zephyr 3.1 bosch,bme280 device is in the final DTS and accessible, but DT_HAS_BOSCH_BME280_ENABLED=n * :github:`51873` - sensor: bmp388: missing if check around i2c device ready function * :github:`51872` - Race condition in workqueue can lead to work items being lost * :github:`51870` - Nucleo_h743zi fails to format storage flash partition * :github:`51855` - openocd: targeting wrong serial port / device * :github:`51829` - qemu_x86: upgrading to q35 breaks networking samples. * :github:`51827` - picolibc heap lock recursion mismatch * :github:`51821` - native_posix: Cmake must be run at least twice to find ${CMAKE_STRIP} * :github:`51815` - Bluetooth: bt_disable in loop with babblesim gatt test causes Zephyr link layer assert * :github:`51798` - mgmt: mcumgr: image upload, then image erase, then image upload does not restart upload from start * :github:`51797` - West espressif install not working * :github:`51796` - LE Audio: Improve stream coupling for CIS as the unicast client * :github:`51788` - Questionable test code in ipv6_fragment test * :github:`51785` - drivers/clock_control: stm32: Can support configure stm32_h7 PLL2 ? * :github:`51780` - windows-curses Python package in requirements.txt can't install if using Python 3.11 * :github:`51778` - stm32l562e-dk: Broken TF-M psa-crypto sample * :github:`51776` - POSIX API is not portable across arches * :github:`51761` - Bluetooth : HardFault in hci_driver on sample/bluetooth/periodic_sync using nRF52833DK * :github:`51752` - CAN documentation points to old sample locations * :github:`51731` - Twister has a hard dependency on ``west.log`` * :github:`51728` - soc: xtensa: esp32_net: Remove binary blobs from source tree * :github:`51720` - USB mass sample not working for FAT FS * :github:`51714` - Bluetooth: Application with buffer that cannot unref it in disconnect handler leads to advertising issues * :github:`51713` - drivers: flash: spi_nor: init fails when flash is busy * :github:`51711` - Esp32-WROVER Unable to include the header file ``esp32-pinctrl.h`` * :github:`51693` - Bluetooth: Controller: Transmits packets longer than configured max len * :github:`51687` - tests-ci : net: socket: tcp.preempt test Failed * :github:`51688` - tests-ci : net: socket: tcp test Failed * :github:`51689` - tests-ci : net: socket: poll test Failed * :github:`51690` - tests-ci : net: socket: select test Failed * :github:`51691` - tests-ci : net: socket: tls.preempt test Failed * :github:`51692` - tests-ci : net: socket: tls test Failed * :github:`51676` - stm32_hal -- undefined reference to "SystemCoreClock" * :github:`51653` - mgmt: mcumgr: bt: issue with queued packets when device is busy * :github:`51650` - Bluetooth: Extended adv reports with legacy data should also be discardable * :github:`51631` - bluetooth: shell: linker error * :github:`51629` - BLE stack execution fails with CONFIG_NO_OPTIMIZATIONS=y * :github:`51622` - ESP32 mcuboot not support chip revision 1 * :github:`51621` - APPLICATION_CONFIG_DIR, CONF_FILE do not always pick up local ``boards/.conf`` :github:`51620` - Add Apache Thrift Module (from GSoC 2022 Project) * :github:`51617` - RFC: Add Apache Thrift Upstream Module (from GSoC 2022 Project) * :github:`51611` - check_compliance.py generates file checkpath.txt which isn't in .gitingore * :github:`51607` - DT_NODE_HAS_COMPAT does not consider parents/path * :github:`51604` - doc: is the documentation GDPR compliant since it uses Google Analytics without prompting the user about tracking? * :github:`51602` - Stack overflow when using mcumgr fs_mgmt * :github:`51600` - Bluetooth assert on flash erase using mcumgr * :github:`51594` - mgmt: mcumgr: bt: thread freezes if device disconnects * :github:`51588` - Doc: Broken link in the "Electronut Labs Papyr" documentation page * :github:`51566` - broken network once lwM2M is resumed after pause * :github:`51559` - lwm2m tests are failing * :github:`51549` - Memory report generation breaks if app and Zephyr is located on different Windows drives * :github:`51546` - The blinky_pwm sample does not work on raspberry pi pico * :github:`51544` - drivers/pwm/pwm_sam.c - update period and duty cycle issue (workaround + suggestions for fix) * :github:`51529` - frdm_k64f: tests/net/socket/tls run failed on frdm_k64f * :github:`51528` - spurious warnings when EXTRA_CFLAGS=-save-temps=obj is passed * :github:`51521` - subsys: bluetooth: shell: gatt.c build fails with CONFIG_DEBUG_OPTIMIZATIONS and CONFIG_BT_SHELL=y * :github:`51520` - samples: compression lz4 fails on small-ram stm32 platforms * :github:`51508` - openocd: can't flash STM32H7 board using STLink V3 * :github:`51506` - it8xxx2_evb: Test suite after watchdog test will display fail in the daily test * :github:`51505` - drivers: modem: gsm: gsm_ppp_stop() does not change gsm->state * :github:`51488` - lis2dw12 function latch is misunderstood with drdy latch * :github:`51480` - tests-ci : drivers: watchdog test Build failure of mimxrt1064_evk * :github:`51476` - Please add documentation or sample how to use TLS_SESSION_CACHE socket option * :github:`51475` - Twister: Mistake timeout as skipped * :github:`51474` - driver: stm32: usb: add detach function support * :github:`51471` - Network protocol MQTT: When qos=1, there is a bug in the subscription and publication * :github:`51470` - tests-ci : drivers: mipi_dsi: api test Build failure * :github:`51469` - Intel CAVS: Failed in tests/kernel/spinlock * :github:`51468` - mps3_an547:tests/lib/cmsis_dsp/filtering bus fault * :github:`51464` - samples: drivers: peci: Code doesn't build for npcx7m6fb_evb board * :github:`51458` - Only one instance of mcp2515 * :github:`51454` - Cmake error for Zephyr Sample Code in Visual Studio * :github:`51446` - The PR #50334 breaks twister execution on various HW boards * :github:`51437` - LoRaWan problem with uplink messages sent as a response to class C downlink * :github:`51438` - tests-ci : net: http: test Build failure * :github:`51436` - tests-ci : drivers: drivers.watchdog: nxp-imxrt11xx series : watchdog build failure * :github:`51435` - tests-ci : drivers: hwinfo: api test Failed * :github:`51432` - Bluetooth: ISO: Remove checks for and change seq_num to uint16_t * :github:`51424` - tests: net: socket: tls: v4 dtls sendmsg test is testing v6 * :github:`51421` - tests: net: socket: tls: net.socket.tls region ``FLASH`` overflowed * :github:`51418` - Intel CAVS: Assertion failed in tests/subsys/logging/log_links * :github:`51406` - Blinky not executing on Windows * :github:`51376` - Silabs WFX200 Binary Blob * :github:`51375` - tests/lib/devicetree/devices/libraries.devicetree.devices: build failure (bl5340_dvk_cpuapp) * :github:`51371` - hal: nxp: ARRAY_SIZE collision * :github:`51370` - Driver error precision LPS22HH * :github:`51368` - tests: tests/subsys/cpp/cxx/cpp.main.picolibc: build failure * :github:`51364` - ESP32 WIFI: when allocating system_heap to PSRAM(extern ram), wifi station can't connet to ap(indicate that ap not found) * :github:`51360` - I2C master read failure when 10-bit addressing is used with i2c_ll_stm32_v1 * :github:`51351` - I2C: ESP32 driver does not support longer clock stretching * :github:`51349` - Turn power domains on/off directly * :github:`51343` - qemu_x86_tiny doesn't place libc-hooks data in z_libc_partition * :github:`51331` - lvgl: LV_FONT_CUSTOM_DECLARE does not work as string * :github:`51323` - kernel: tests: Evaluate "platform_allow" usage in kernel tests. * :github:`51322` - tests: kernel: timer: timer_behavior: kernel.timer.timer fails * :github:`51318` - x86_64: Thread Local Storage pointer not setup before first thread started * :github:`51301` - CI: mps3_an547: test failures * :github:`51297` - Bluetooth: Implement H8 function from cryptographic toolbox * :github:`51294` - ztest: Broken tests in main branch due to API-breaking change ``ZTEST_FAIL_ON_ASSUME`` * :github:`51290` - samples: application_development: external_lib: does not work on windows * :github:`51276` - CAN driver for ESP32 (TWAI) does not enable the transceiver * :github:`51265` - net: ip: cloning of net_pkt produces dangling ll address pointers and may flip overwrite flag * :github:`51264` - drivers: ieee802154: nrf: wrapped pkt attribute access * :github:`51263` - drivers: ieee802154: IEEE 802.15.4 L2 does not announce (but uses) promisc mode * :github:`51261` - drivers: ieee802154: Drivers allocate RX packets from the TX pool * :github:`51247` - Bluetooth: RPA expired callback inconsistently called * :github:`51235` - nominate me as zephyr contributor * :github:`51234` - it8xxx2_evb: The testcase tests/kernel/sleep/failed to run. * :github:`51233` - up_squared: samples/boards/up_squared/gpio_counter run failed * :github:`51228` - Bluetooth: Privacy in scan roles not updating RPA on timeout * :github:`51223` - Problem when using fatfs example in a out_of_tree_driver with the file ff.h * :github:`51214` - enc28j60 appears to be unable to correctly determine network state * :github:`51208` - Bluetooth: Host: ``bt_le_oob_get_local`` gives incorrect address * :github:`51202` - twister: Integration errors not reported nor counted in the console output but present in the reports. * :github:`51194` - samples/subsys/lorawan building failed * :github:`51185` - tests/drivers/counter/counter_basic_api fails to build on mimxrt685_evk_cm33 * :github:`51177` - Change SPI configuration (bitrate) with MCUXpresso SPI driver fails * :github:`51174` - Bluetooth: l2cap needs check rx.mps when le_recv * :github:`51168` - ITERABLE_SECTION_ROM stores data in RAM instead of ROM * :github:`51165` - tools/fiptool/fiptool: Permission denied * :github:`51156` - esp32 wifi: how to use ap mode and ap+station mode? * :github:`51153` - modem: ppp: extract access technology when MODEM_CELL_INFO is enabled * :github:`51149` - Esp32 wifi compilation error * :github:`51146` - Running test: drivers: disk: disk_access with RAM disk fails * :github:`51144` - PR #51017 Broke GPIO builds for LPC11u6x platforms * :github:`51142` - TestPlan generation not picking up tests missing ``test_`` prefix * :github:`51138` - Testing tests/lib/cmsis_dsp/ fails on some stm32 boards * :github:`51126` - Bluetooh: host: df: wrong size of a HCI command for connectionless CTE enable in AoD mode * :github:`51117` - tests: kernel: workq: work: kernel.work.api fails test_1cpu_drain_wait * :github:`51108` - Ethernet: Error frames are displayed when DHCP is suspended for a long time: <inf> net_dhcpv4: Received: 192.168.1.119 * :github:`51107` - Ethernet: Error frames are often displayed: <err> eth_mcux: ENET_GetRxFrameSize return: 4001 * :github:`51105` - esp32 wifi: http transmit rate is too slow * :github:`51102` - issue installing zepyhr when i am using west cmd * :github:`51076` - ADC channels 8-12 not working on LPC55s6X * :github:`51074` - logging: syst: sample failure * :github:`51070` - ModuleNotFoundError: No module named 'elftools' * :github:`51068` - ModuleNotFoundError: No module named 'elftools' * :github:`51065` - building tests/subsys/jwt failed on disco_l475_iot1 with twister * :github:`51062` - lora_recv_async receives empty buffer after multiple receptions on sx12xx * :github:`51060` - 10-bit addressing not supported by I2C slave driver for STM32 target * :github:`51057` - Retrieve gpios used by a device (pinctrl) * :github:`51048` - Firmware Upgrade Issue with Mcumgr On STM32H743 controller * :github:`51025` - mbedtls: build warnings * :github:`51021` - openthread: build warnings * :github:`51019` - NVS should allow overwriting existing index even if there's no room to keep the old value * :github:`51016` - mgmt: mcumgr: Add dummy shell buffer size Kconfig entry to shell mgmt * :github:`51015` - Build Error for ST Nucleo F103RB * :github:`51010` - Unable to communicate with LIS2DS12 on 52840DK or custom board * :github:`51007` - Improve process around feature freeze exceptions * :github:`51003` - Crash when using flexcomm5 as i2c on LPC5526 * :github:`50989` - Invalid ASE State Machine Transition * :github:`50983` - RPI Pico usb hangs up in interrupt handler for composite devices * :github:`50976` - JSON array encoding fails on array of objects * :github:`50974` - DHCP (IPv4) NAK not respected when in renewing state * :github:`50973` - DHCP (IPv4) seemingly dies by trying to assign an IP of 0.0.0.0 * :github:`50970` - SAME54_xpro network driver not attached * :github:`50953` - LE Audio: Add support for setting ISO data path for broadcast sink * :github:`50948` - SSD1306+lvgl sample fails to display * :github:`50947` - stm32 static IPv4 networking in smp_svr sample application does not seem to work until a ping is received * :github:`50940` - logging.log_output_ts64 fails on qemu_arc_hs5x * :github:`50937` - Error when building for esp32c3_devkitm * :github:`50923` - RFC: Stable API change: Rework and improve mcumgr callback system * :github:`50895` - ADC Voltage Reference issue with STM32U5 MCU * :github:`50874` - Cant disable bluetooth for BLE peripheral after connection with Central * :github:`50872` - Error while installing python dependecies * :github:`50868` - DHCP never binds if a NAK is received during the requesting state * :github:`50853` - STM32F7 series can't run at frequencies higher than 180MHz * :github:`50844` - zcbor module apis which are used for mcu boot functionality are not building in cpp file against v3.1.0 * :github:`50812` - MCUmgr udp sample fails with shell - BUS FAULT * :github:`50801` - JSON parser fails on multidimensional arrays * :github:`50789` - west: runners: blackmagicprobe: Doesn't work on windows due to wrong path separator * :github:`50786` - Bluetooth: Host: Extended advertising reports may block the host * :github:`50784` - LE Audio: Missing Media Proxy checks for callbacks * :github:`50783` - LE Audio: Reject ISO data if the stream is not in the streaming state * :github:`50782` - LE Audio: The MPL shell module should not use opcodes * :github:`50781` - LE Audio: ``mpl init`` causes warnings when adding objects * :github:`50780` - LE Audio: Bidirectional handling of 2 audio streams as the unicast server when streams are configured separately not working as intended * :github:`50778` - LE Audio: Audio shell: Unicast server cannot execute commands for the default_stream * :github:`50776` - CAN Drivers allow sending FD frames without device being set to FD mode * :github:`50768` - storage: DT ``fixed-partition`` with ``status = "okay"`` requires flash driver * :github:`50746` - Stale kernel memory pool API references * :github:`50744` - net: ipv6: Allow on creating incomplete neighbor entries and routes in case of receiving Router Advertisement * :github:`50735` - intel_adsp_cavs18: tests/boards/intel_adsp/hda_log/boards.intel_adsp.hda_log.printk failed * :github:`50732` - net: tests/net/ieee802154/l2/net.ieee802154.l2 failed on reel_board due to build failure * :github:`50709` - tests: arch: arm: arm_thread_swap fails on stm32g0 or stm32l0 * :github:`50684` - After enabling CONFIG_SPI_STM32_DMA in project config file for STM32MP157-dk2 Zephyr throwing error * :github:`50665` - MEC15xx/MEC1501: UART and special purpose pins missing pinctrl configuration * :github:`50658` - Bluetooth: BLE stack notifications blocks host side for too long (``drivers/bluetooth/hci/spi.c`` and ``hci_spi``) * :github:`50656` - Wrong definition of bank size for intel memory management driver. * :github:`50655` - STM32WB55 Bus Fault when connecting then disconnecting then connecting then disconnecting then connecting * :github:`50620` - fifo test fails with CONFIG_CMAKE_LINKER_GENERATOR enabled on qemu_cortex_a9 * :github:`50614` - Zephyr if got the ip is "10.xxx.xxx.xxx" when join in the switchboard, then the device may can not visit the outer net, also unable to Ping. * :github:`50603` - Upgrade to loramac-node 4.7.0 when it is released to fix async LoRa reception on SX1276 * :github:`50596` - Documentation: Broken links in the previous release documentation * :github:`50592` - mgmt: mcumgr: Remove code/functions deprecated in zephyr 3.1 release * :github:`50590` - openocd: Can't flash on various STM32 boards * :github:`50587` - Regression in Link Layer Control Procedure (LLCP) * :github:`50570` - samples/drivers/can/counter fails in twister for native_posix * :github:`50567` - Passed test cases are reported as "Skipped" because of incomplete test log * :github:`50565` - Fatal error after ``west flash`` for nucleo_l053r8 * :github:`50554` - Test uart async failed on Nucleo F429ZI * :github:`50525` - Passed test cases reported as "Skipped" because test log lost * :github:`50515` - Non-existing test cases reported as "Skipped" with reason No results captured, testsuite misconfiguration? in test report * :github:`50461` - Bluetooth: controller: LLCP: use of legacy ctrl Tx buffers * :github:`50452` - mec172xevb_assy6906: The testcase tests/lib/cmsis_dsp/matrix failed to run. * :github:`50446` - MCUX CAAM is disabled temporarily * :github:`50438` - Bluetooth: Conn: Bluetooth stack becomes unusable when communicating with both centrals and peripherals * :github:`50427` - Bluetooth: host: central connection context leak * :github:`50426` - STM32: using SPI after STOP2 sleep causes application to hang * :github:`50404` - Intel CAVS: tests/subsys/logging/log_immediate failed. * :github:`50389` - Allow twister to be called directly from west * :github:`50381` - BLE: Connection slows down massively when connecting to a second device * :github:`50354` - ztest_new: _zassert_base : return without post processing * :github:`50345` - Network traffic occurs before Bluetooth NET L2 (IPSP) link setup complete * :github:`50284` - Generated linker scripts break when ZEPHYR_BASE and ZEPHYR_MODULES share structure that contains symlinks * :github:`50256` - I2C on SAMC21 sends out stop condition incorrectly * :github:`50193` - Impossible to connect with a peripheral with BLE and zephyr 2.7.99, BT_HCI_ERR_UNKNOWN_CONN_ID error * :github:`50192` - nrf_qspi_nor driver might crash if power management is enabled * :github:`50188` - Avoid using extra net buffer for L2 header * :github:`50149` - tests: drivers: flash fails on nucleo_l152re because of wrong erase flash size * :github:`50139` - net: ipv4: Add DSCP/ToS based QoS support * :github:`50070` - LoRa: Support on RFM95 LoRa module combined with a nRF52 board * :github:`50040` - shields: Settle on nodelabels naming scheme * :github:`50028` - flash_stm32_ospi Write enable failed when building with TF-M * :github:`49996` - tests: drivers: clock_control: nrf_lf_clock_start and nrf_onoff_and_bt fails * :github:`49963` - Random crash on the L475 due to work->handler set to NULL * :github:`49962` - RFC: Stable API Change: SMP (Simple Management Protocol) transport API within MCUMgr drops ``zephyr_`` prefix in functions and type definitions and drop zst parameter from zephyr_smp_transport_out_fn * :github:`49917` - http_client_req() sometimes hangs when peer disconnects * :github:`49871` - zperf: Add support to stop/start download * :github:`49870` - stm32 enables HSI48 clock with device tree * :github:`49844` - shell: Add abort support * :github:`49843` - net: shell: Extend ping command * :github:`49821` - USB DFU implementation does not work with WinUSB because of missing device reset API * :github:`49811` - DHCP cannot obtain IP, when CONFIG_NET_VLAN is enabled * :github:`49783` - net: ipv4: packet fragmentation support * :github:`49746` - twister: extra test results * :github:`49740` - LE Audio: Support for application-controlled advertisement for BAP broadcast source * :github:`49711` - tests/arch/common/timing/arch.common.timing.smp fails for CAVS15, 18 * :github:`49648` - tests/subsys/logging/log_switch_format, log_syst build failures on CAVS * :github:`49624` - Bluetooth: Controller: Recent RAM usage increase for hci_rpmsg build * :github:`49621` - STM32WB55 BLE Extended Advertising support * :github:`49620` - Add picolibc documentation * :github:`49614` - acrn_ehl_crb: The testcase tests/kernel/sched/schedule_api failed to run. * :github:`49611` - ehl_crb: Failed to run timer testcases * :github:`49588` - Json parser is incorrect with undefined parameter * :github:`49584` - STM32WB55 Failed read remote feature, remote version and LE set PHY * :github:`49530` - Bluetooth: Audio: Invalid behavior testing * :github:`49451` - Treat carrier UP/DOWN independently to interface UP/DOWN * :github:`49413` - TI-AM62x: Add Zephyr Support for M4 and R5 cores * :github:`49373` - BLE scanning - BT RX thread hangs on. * :github:`49338` - Antenna switching for Bluetooth direction finding with the nRF5340 * :github:`49313` - nRF51822 sometimes hard fault on connect * :github:`49298` - cc3220sf: add a launchpad_connector.dtsi * :github:`49266` - Bluetooth: Host doesn't seem to handle INCOMPLETE per adv reports * :github:`49234` - option to configure coverage data heap size * :github:`49228` - ti: cc13xx_cc26xx: ADC support * :github:`49210` - BL5340 board cannot build bluetooth applications * :github:`49208` - drivers: modem: bg9x: not supporting UDP * :github:`49148` - Asynchronous UART API triggers Zephyr assertion on STM32WB55 * :github:`49112` - lack of support for lpsram cache * :github:`49069` - log: cdc_acm: hard fault message does not output * :github:`49066` - Mcumgr img_mgmt_impl_upload_inspect() can cause unaligned memory access hard fault. * :github:`49054` - STM32H7 apps are broken in C++ mode due to HAL include craziness * :github:`49032` - espi saf testing disabled * :github:`49026` - Add a CI check on image file sizes (specifically around boards) * :github:`49021` - uart async api does not provide all received data * :github:`48954` - several NXP devicetree bindings are missing * :github:`48953` - 'intel,sha' is missing binding and usage * :github:`48886` - Documenting the process for treewide changes * :github:`48857` - samples: Bluetooth: Buffer size mismatch in samples/bluetooth/hci_usb for nRF5340 * :github:`48850` - Bluetooth: LLCP: possible access to released control procedure context * :github:`48726` - net: tests/net/ieee802154/l2/net.ieee802154.l2 failed on reel board * :github:`48625` - GSM_PPP api keeps sending commands to muxed AT channel * :github:`48616` - RFC: Change to clang-format coding style rules re binary operators * :github:`48609` - drivers: gpio: expose gpio_utils.h to external GPIO drivers * :github:`48603` - LoRa driver asynchronous receive callback clears data before the callback. * :github:`48520` - clang-format: #include reorder due to default: SortIncludesOptions != SI_Never * :github:`48505` - BLE stack can get stuck in connected state despite connection failure * :github:`48473` - Setting CONFIG_GSM_MUX_INITIATOR=n results in a compile error * :github:`48468` - GSM Mux does not transmit all queued data when uart_fifo_fill is called * :github:`48394` - vsnprintfcb writes to ``str`` if it is NULL :github:`48390` - [Intel Cavs] Boot failures on low optimization levels * :github:`48317` - drivers: fpga: include driver for Lattice iCE40 parts * :github:`48304` - bt_disable() does not work properly on nRF52 * :github:`48299` - SHT3XD_CMD_WRITE_TH_LOW_SET should be SHT3XD_CMD_WRITE_TH_LOW_CLEAR * :github:`48150` - Sensor Subsystem: data types * :github:`48148` - Sensor Subsystem: Base sensor DTS bindings * :github:`48147` - ztest: before/after functions may run on different threads, which may cause potential issues. * :github:`48037` - Grove LCD Sample Not Working * :github:`48018` - ztest: static threads are not re-launched for repeated test suite execution. * :github:`47988` - JSON parser not consistent on extra data * :github:`47877` - ECSPI support for NXP i.MX devices * :github:`47872` - Differentiating Samples, Tests & Demos * :github:`47833` - Intel CAVS: cavstool.py fails to extract complete log from winstream buffer when logging is frequent * :github:`47830` - Intel CAVS: Build failure due to #47713 PR * :github:`47817` - samples/modules/nanopb/sample.modules.nanopb fails with protobuf > 3.19.0 * :github:`47611` - ci: workflows: compliance: Add commit title to an error msg * :github:`47607` - Settings with FCB backend does not pass test on stm32h743 * :github:`47576` - undefined reference to ``__device_dts_ord_20`` When building with board hifive_unmatched on flash_shell samples * :github:`47500` - twister: cmake: Failure of "--build-only -M" combined with "--test-only" for --device-testing * :github:`47477` - qemu_leon3: tests/kernel/fpu_sharing/generic/ failed when migrating to new ztest API * :github:`47329` - Newlib nano variant footprint reduction * :github:`47326` - drivers: WINC1500: issues with buffer allocation when using sockets * :github:`47324` - drivers: modem: gsm_ppp: support common gpios * :github:`47315` - LE Audio: CAP Initiator skeleton Implementation * :github:`47299` - LE Audio: Advertising (service) data for one or more services/roles * :github:`47296` - LE Audio: Move board files for nRF5340 Audio development kit upstream * :github:`47274` - mgmt/mcumgr/lib: Rework of event callback framework * :github:`47243` - LE Audio: Add support for stream specific codec configurations for broadcast source * :github:`47242` - LE Audio: Add subgroup support for broadcast source * :github:`47092` - driver: nrf: uarte: new dirver breaks our implementation for uart. * :github:`47040` - tests: drivers: gpio_basic_api and gpio_api_1pin: convert to new ztest API * :github:`47014` - can: iso-tp: implementation test failed with twister on nucleo_g474re * :github:`46988` - samples: net: openthread: coprocessor: RCP is missing required capabilities: tx-security tx-timing * :github:`46986` - Logging (deferred v2) with a lot of output causes MPU fault * :github:`46897` - tests: posix: fs: improve tests to take better advantage of new ztest features * :github:`46844` - Timer drivers likely have off-by-one in rapidly-presented timeouts * :github:`46824` - Prevent new uses of old ztest API * :github:`46598` - Logging with RTT backend on STM32WB strange behavier * :github:`46596` - STM32F74X RMII interface does not work * :github:`46491` - Zephyr SDK 0.15.0 Checklist * :github:`46446` - lvgl: Using sw_rotate with SSD1306 shield causes memory fault * :github:`46351` - net: tcp: Implement fast-retransmit * :github:`46326` - Async UART for STM32 U5 support * :github:`46287` - Zephyr 3.2 release checklist * :github:`46268` - Update RNDIS USB class codes for automatic driver loading by Windows * :github:`46126` - pm_device causes assertion error in sched.c with lis2dh * :github:`46105` - RFC: Proposal of Integrating Trusted Firmware-A * :github:`46073` - IPSP (IPv6 over BLE) example stop working after a short time * :github:`45921` - Runtime memory usage * :github:`45910` - [RFC] Zbus: a message bus system * :github:`45891` - mgmt/mcumgr/lib: Refactoring of callback subsystem in image management (DFU) * :github:`45814` - Armclang build fails due to missing source file * :github:`45756` - Add overlay-bt-minimal.conf for smp_svr sample application * :github:`45697` - RING_BUF_DECLARE broken for C++ * :github:`45625` - LE Audio: Update CSIP API with new naming scheme * :github:`45621` - LE Audio: Update VCP API with new naming scheme * :github:`45427` - Bluetooth: Controller: LLCP: Data structure for communication between the ISR and the thread * :github:`45222` - drivers: peci: user space handlers not building correctly * :github:`45218` - rddrone_fmuk66: I2C configuration incorrect * :github:`45094` - stm32: Add USB HS device support to STM32H747 * :github:`44908` - Support ESP32 ADC * :github:`44861` - WiFi support for STM32 boards * :github:`44410` - drivers: modem: shell: ``modem send`` doesn't honor line ending in modem cmd handler * :github:`44399` - Zephyr RTOS support for Litex SoC with 64 bit rocket cpu. * :github:`44377` - ISO Broadcast/Receive sample not working with coded PHY * :github:`44324` - Compile error in byteorder.h * :github:`44318` - boards: arm: rpi_pico: Enable CONFIG_ARM_MPU=y for raspberry pi pico board * :github:`44281` - Bluetooth: Use hardware encryption for encryption * :github:`44164` - Implement the equivalent of PR #44102 in LLCP * :github:`44055` - Immediate alert client * :github:`43998` - posix: add include/posix to search path based on Kconfig * :github:`43986` - interrupt feature for gpio_mcp23xxx * :github:`43836` - stm32: g0b1: RTT doesn't work properly after stop mode * :github:`43737` - Support compiling ```native_posix`` targets on Windows using the MinGW * :github:`43696` - mgmt/mcumgr: RFC: Standardize Kconfig option names for MCUMGR * :github:`43655` - esp32c3: Connection fail loop * :github:`43647` - Bluetooth: LE multirole: connection as central is not totally unreferenced on disconnection * :github:`43604` - Checkpatch: Support in-code ignore tags * :github:`43411` - STM32 SPI DMA issue * :github:`43330` - usb_dc_nrfx.c starts usbd_work_queue with no name * :github:`43308` - driver: serial: stm32: uart will lost data when use dma mode[async mode] * :github:`43294` - LoRaWAN stack & user ChannelsMask * :github:`43286` - Zephyr 3.1 Release Checklist * :github:`42998` - Should board.dts enable peripherals by default? * :github:`42910` - Bluetooth: Controller: CIS Data path setup: HCI ISO Data * :github:`42908` - Bluetooth: Controller: CIG: LE Remove CIG * :github:`42907` - Bluetooth: Controller: CIG: Disconnect: ACL disconnection leading to CIS Disconnection complete * :github:`42906` - Bluetooth: Controller: CIG: Disconnect: Using HCI Disconnect: Generate LL_CIS_TERMINATE_IND * :github:`42905` - Bluetooth: Controller: CIG: LL Rejects: Remote request being rejected * :github:`42902` - Bluetooth: Controller: CIG: Host reject: LE Reject CIS Request * :github:`42900` - Bluetooth: Controller: CIG: LE Setup ISO Data Path * :github:`42899` - Bluetooth: Controller: CIG: LE CIS Established Event * :github:`42898` - Bluetooth: Controller: CIG: LE Accept CIS * :github:`42897` - Bluetooth: Controller: CIG: LE CIS Request Event * :github:`42896` - Bluetooth: Controller: CIG: LE Create CIS: NULL PDU scheduling * :github:`42895` - Bluetooth: Controller: CIG: LE Create CIS: Control procedure with LL_CIS_REQ/RSP/IND PDU * :github:`42894` - Bluetooth: Controller: CIG: LE Set CIG Parameters * :github:`42700` - Support module.yml in zephyr repo * :github:`42590` - mgmt/mcumgr/lib: RFC: Allow leaving out "rc" in successful respones and use "rc" only for SMP processing errors. * :github:`42432` - i2c: unable to configure SAMD51 i2c clock frequency for standard (100 KHz) speeds * :github:`42420` - mgmt/mcumgr/lib: Async image erase command with status check * :github:`42374` - STM32L5: Entropy : Power Management not working due to entropy driver & stop mode * :github:`42361` - OpenOCD flashing not working on cc1352r1_launchxl/cc26x2r1_launchxl * :github:`41956` - Bluetooth: Controller: BIG: Synchronized receiver encryption support * :github:`41955` - Bluetooth: Controller: BIG: Broadcaster encryption support * :github:`41830` - CONF_FILE, OVERLAY_CONFIG parsing expands ``${ZEPHYR_<whatever>_MODULE_DIR}`` * :github:`41823` - Bluetooth: Controller: llcp: Remote request are dropped due to lack of free proc_ctx * :github:`41822` - BLE IPSP sample cannot handle large ICMPv6 Echo Request * :github:`41784` - virtio device driver * :github:`41771` - tests: drivers: adc: Test doesn't build for mec172xevb_assy6906 * :github:`41765` - assert.h should not include non libc headers * :github:`41694` - undefined reference to ``_open`` * :github:`41622` - Infinite mutual recursion when SMP and ATOMIC_OPERATIONS_C are set * :github:`41606` - stm32u5: Re-implement VCO input and EPOD configuration * :github:`41581` - STM32 subghzspi fails pinctrl setup * :github:`41380` - stm32h7: Ethernet: Migrate driver to the new eth HAL api * :github:`41213` - LE Audio: Update GA services to use the multi-instance macro * :github:`41212` - LE Audio: Store of bonded data * :github:`41209` - LE Audio: MCS support for multiple instances * :github:`41073` - twister: no way to specify arguments for the binary zephyr.exe * :github:`40982` - Build system: West: Add a warning when used repository does not match manifest * :github:`40972` - Power management support for MEC172x * :github:`40944` - BUILTIN_STACK_CHECKER and MPU_STACK_GUARD with a thread using the FPU will fault the bulltin stack checker * :github:`40928` - mgmt/mcumgr/lib: Check image consistency after writing last chunk * :github:`40924` - mgmt/mcumgr/lib: Do not re-upload image, by default, to the secondary slot * :github:`40868` - Add a pre and post initialization among CONFIG_APPLICATION_INIT_PRIORITY * :github:`40850` - Add Zephyr logging support to mgmt/mcumgr/lib * :github:`40833` - driver: i2c: TCA9546a: Have compilation fails when driver init priority missmatch * :github:`40642` - Why does CMake wrongly believe the rimage target is changing? * :github:`40582` - how the zephyr supportting with running cadence hifi4 lx7,reset_vectorXEA2.s ? * :github:`40561` - BLE notification and indication callback data are difficult to pass to other threads... * :github:`40560` - Callbacks lack context information... * :github:`39740` - Road from pinmux to pinctrl * :github:`39712` - bq274xx sensor - Fails to compile when CONFIG_PM_DEVICE enabled * :github:`39598` - use of __noinit with ecc memory hangs system * :github:`39520` - Add support for the BlueNRG-LP SoC * :github:`39431` - arduino_nano_33_ble_sense: Add More Devices to the Device Tree * :github:`39331` - ti: cc13xx_cc26xx: watchdog timer driver * :github:`39234` - Add support for the Sensririon SCD30 CO2 sensor * :github:`39194` - Process: investigate GitHub code review replacements * :github:`39037` - CivetWeb samples fail to build with CONFIG_NEWLIB_LIBC * :github:`39025` - Bluetooth: Periodic Advertising, Filter Accept List, Resolving list related variable name abbreviations * :github:`38947` - Issue with SMP commands sent over the UART * :github:`38880` - ARC: ARCv2: qemu_arc_em / qemu_arc_hs don't work with XIP disabled * :github:`38668` - ESP32S I2S * :github:`38570` - Process: binary blobs in Zephyr * :github:`38450` - Python script for checking PR errors * :github:`38346` - twister command line parameter clean up and optimizate twister documents * :github:`38291` - Make Zephyr modules compatible with PlatformIO libdeps * :github:`38251` - cmake: DTC_OVERLAY_FILE flags cancel board <board>.overlay files * :github:`38041` - Logging-related tests fails on qemu_arc_hs6x * :github:`37855` - STM32 - kconfigs to determine if peripheral is available * :github:`37346` - STM32WL LoRa increased the current in "suspend_to_idle" state * :github:`37056` - Clarify device power states * :github:`36953` - <err> lorawan: MlmeConfirm failed : Tx timeout * :github:`36951` - twister: report information about tests instability * :github:`36882` - MCUMGR: fs upload fail for first time file upload * :github:`36724` - The road to a stable Controller Area Network driver API * :github:`36601` - Add input support to audio_codec * :github:`36553` - LoRaWAN Sample: ``join accept`` but "Join failed" * :github:`36544` - RFC: API Change: Bluetooth: Read Multiple * :github:`36343` - Bluetooth: Mesh: Modularizing the proxy feature * :github:`36301` - soc: cypress: Port Zephyr to Cypress CYW43907 * :github:`36297` - Move BSS section to the end of image * :github:`35986` - POSIX: multiple definition of posix_types * :github:`35812` - ESP32 Factory app partition is not bootable * :github:`35316` - log_panic() hangs kernel * :github:`35238` - ieee802.15.4 support for stm32wb55 * :github:`35237` - build: Enhance twister to follow all module.yml in module list * :github:`35177` - example-application: Add example library & tests * :github:`34949` - console Bluetooth LE backend * :github:`34597` - Mismatch between ``ot ping`` and ``net ping`` * :github:`34536` - Simple event-driven framework * :github:`34324` - RTT is not working on STM32 * :github:`34269` - LOG_MODE_MINIMAL BUILD error * :github:`34049` - Nordic nrf9160 switching between drivers and peripherals * :github:`33876` - Lora sender sample build error for esp32 * :github:`33704` - BLE Shell Scan application filters * :github:`32875` - Benchmarking Zephyr vs. RIOT-OS * :github:`32756` - Enable mcumgr shell management to send responses to UART other than assigned to shell * :github:`32733` - RS-485 support * :github:`32339` - reimplement tests/kernel/timer/timer_api * :github:`32288` - Enhance the ADC functionality on the STM32 devices to all available ADC channels * :github:`32213` - Universal error code type * :github:`31959` - BLE firmware update STM32WB stuck in loop waiting for CPU2 * :github:`31298` - tests/kernel/gen_isr_table failed on hsdk and nsim_hs_smp sometimes * :github:`30391` - Unit Testing in Zephyr * :github:`30348` - XIP can't be enabled with ARC MWDT toolchain * :github:`30212` - Disk rewrites same flash page multiple times. * :github:`30159` - Clean code related to dts fixup files * :github:`30042` - usbd: support more than one configuration descriptors * :github:`30023` - Device model: add debug helpers for when device_get_binding() fails * :github:`29986` - Add support for a single node having multiple bus types * :github:`29832` - Redundant error check of function uart_irq_update() in ``tests/drivers/uart/uart_basic_api/src/test_uart_fifo.c`` * :github:`29495` - SD card slow write SPI/Fatfs/stm32 * :github:`29160` - arm: Always include arch/arm/include * :github:`29136` - usb: add USB device stack shell support * :github:`29135` - usb: allow the instances of a USB class to be enabled and disabled at runtime * :github:`29134` - usb: allow more extensive settings of the device descriptor * :github:`29133` - usb: USB device stack should store and validate the device state * :github:`29132` - usb: USB device stack should track and check the state of control transfers * :github:`29087` - Moving (some) boards to their own repo/module * :github:`28998` - net: if: extend list of admin/operational states of network interface * :github:`28872` - Support ESP32 as Bluetooth controller * :github:`28864` - sanitycheck: Make sanitycheck test specifiacation compatible * :github:`28617` - enable CONFIG_TEST for all samples * :github:`27819` - Memory Management for MMU-based devices for LTS2 * :github:`27258` - Ring buffer does not allow to partially put/get data * :github:`26796` - Interrupts on Cortex-M do not work with CONFIG_MULTITHREADING=n * :github:`26392` - e1000 ethernet driver needs to be converted to DTS * :github:`26109` - devicetree: overloaded DT_REG_ADDR() and DT_REG_SIZE() for PCI devices * :github:`25917` - Bluetooth: Deadlock with TX of ACL data and HCI commands (command blocked by data) * :github:`25417` - net: socket: socketpair: check for ISR context * :github:`25407` - No tests/samples covering socket read()/write() calls * :github:`25055` - Redundant flash shell commands * :github:`24653` - device_pm: clarify and document usage * :github:`23887` - drivers: modem: question: Should modem stack include headers to put into zephyr/include? * :github:`23165` - macOS setup fails to build for lack of "elftools" Python package * :github:`23161` - I2C and sensor deinitialization * :github:`23072` - #ifdef __cplusplus missing in tracking_cpu_stats.h * :github:`22049` - Bluetooth: IRK handling issue when using multiple local identities * :github:`21995` - Bluetooth: controller: split: Porting of connection event length * :github:`21724` - dts: edtlib: handle child-binding or child-child-binding as 'normal' binding with compatible * :github:`21446` - samples: add SPI slave * :github:`21239` - devicetree: Generation of the child-bindigs items as a common static initializer * :github:`20707` - Define GATT service at run-time * :github:`20262` - dt-binding for timers * :github:`19713` - usb: investigate if Network Buffer can be used in USB device stack and USB drivers * :github:`19496` - insufficient test case coverage for log subsystem * :github:`19356` - LwM2M sample reorganization: split out LwM2M source into object-based .c files * :github:`19259` - doc: two-column tricks for HTML breaks PDF * :github:`19243` - Support SDHC & samples/subsys/fs on FRDM-K64F * :github:`19152` - MK22F51212 MPU defines missing * :github:`18892` - POSIX subsys: transition to #include_next for header consistency * :github:`17171` - Insufficient code coverage for lib/os/fdtable.c * :github:`16961` - Modules: add a SHA1 check to avoid updating module in the past * :github:`16942` - Missing test case coverage for include/misc/byteorder.h functions * :github:`16851` - west flash error on zephyr v1.14.99 * :github:`16444` - drivers/flash/flash_simulator: Support for required read alignment * :github:`16088` - Verify POSIX PSE51 API requirements * :github:`15453` - Kconfig should enforce that at most one Console driver is enabled at a time * :github:`15181` - ztest issues * :github:`14753` - nrf52840_pca10056: Leading spurious 0x00 byte in UART output * :github:`14577` - Address latency/performance in nRF51 timer ISR * :github:`13170` - Porting guide for advanced board (multi CPU SoC) * :github:`12504` - STM32: add USB_OTG_HS example * :github:`12401` - Target Capabilities / Board Directory Layout Capabilities * :github:`12367` - Power management strategy of Zephyr can't work well on nRF52 boards. * :github:`11594` - Cleanup GNUisms to make the code standards compliant * :github:`9045` - A resource-saving programming model * :github:`6198` - unit test: Add unit test example which appends source files to SOURCES list * :github:`5697` - Driver API review/cleanup/rework * :github:`3849` - Reduce the overall memory usage of the LwM2M library * :github:`2837` - Ability to use hardware-based block ciphers * :github:`2647` - Better cache APIs needed. ```	/content/code_sandbox/doc/releases/release-notes-3.3.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	53,828
```restructuredtext :orphan: .. _zephyr_2.0: Zephyr 2.0.0 ############ We are pleased to announce the release of Zephyr RTOS version 2.0.0. Major enhancements with this release include: * The kernel now supports both 32- and 64-bit architectures. * We added support for SOCKS5 proxy. SOCKS5 is an Internet protocol that exchanges network packets between a client and server through a proxy server. * Introduced support for 6LoCAN, a 6Lo adaption layer for Controller Area Networks. * We added support for :ref:`Point-to-Point Protocol (PPP) <ppp>`. PPP is a data link layer (layer 2) communications protocol used to establish a direct connection between two nodes. * We added support for UpdateHub, an end-to-end solution for large scale over-the-air device updates. * We added support for ARM Cortex-R Architecture (Experimental). The following sections provide detailed lists of changes by component. Security Vulnerability Related ****************************** The following security vulnerability (CVE) was addressed in this release: * Fixes CVE-2019-9506: The Bluetooth BR/EDR specification up to and including version 5.1 permits sufficiently low encryption key length and does not prevent an attacker from influencing the key length negotiation. This allows practical brute-force attacks (aka "KNOB") that can decrypt traffic and inject arbitrary ciphertext without the victim noticing. Kernel ****** * New kernel API for per-thread disabling of Floating Point Services for ARC, ARM Cortex-M, and x86 architectures. * New system call to set the clock frequency at runtime. * Additional support for compatibility with 64-bit architectures. * Userspace mutexes are now supported through the new k_futex primitive. * Improvements to the slab allocator. * Fixed the implementation of k_thread_name_set() with userspace enabled. * Boosted the default tick rate for tickless kernels to improve the precision of timeouts. Architectures ************* * ARM: * Added initial support for ARM Cortex-R architecture (Experimental) * We enhanced the support for Floating Point Services in Cortex-M architecture, implementing and enabling lazy-stacking for FPU capable threads and fixing stack overflow detection for FPU capable supervisor threads * Added QEMU support for ARMv8-M Mainline architecture * Optimized the IRQ locking time in thread context switch * Fixed several critical bugs in User Mode implementation * Added test coverage for ARM-specific kernel features * Improved support for linking TrustZone Secure Entry functions into Non-Secure firmware * ARC: * Added support for ARC HS architecture * Added SMP support for ARC HS architecture * Added support for ARC SecureShield based TEE (Experimental) * Fixed several critical bugs in interrupt and exception handling * Enhance the support for Floating Point Services * POSIX: * Fixed race condition with terminated threads which had never been scheduled by kernel. On very loaded systems it could cause swap errors. * x86: * Dropped support for the Intel Quark microcontroller family. * A new lightweight PCI implementation has been introduced which supports MSI and other features required for PCIe devices. The previous PCI implementation has been deprecated and will be removed in 2.1. * RISC-V: * Added support for the SiFive HiFive1 Rev B development board. * Added support for LiteX VexRiscv soft core. * Added support for 64-bit RISC-V, renaming the architecture from "riscv32" to "riscv". * Added 64-bit QEMU support. * Added DeviceTree bindings for RISC-V memory devices, CPU interrupt controllers, and platform-local interrupt controllers. Boards & SoC Support ******************** * Added native_posix_64: A 64 bit variant of native_posix * Added support for these ARC boards: .. rst-class:: rst-columns * emsdp * hsdk * nsim for hs * Added support for these ARM boards: .. rst-class:: rst-columns * atsamr21_xpro * cc1352r1_launchxl * cc26x2r1_launchxl * holyiot_yj16019 * lpcxpresso55s69 * mec15xxevb_assy6853 * mikroe_mini_m4_for_stm32 * mimxrt1015_evk * mps2_an521 * nrf51_pca10031 * nrf52811_pca10056 * nucleo_g071rb * nucleo_wb55rg * qemu_cortex_r5 * stm32h747i_disco * stm32mp157c_dk2 * twr_ke18f * v2m_musca_b1 * 96b_avenger96 * 96b_meerkat96 * 96b_wistrio * Added support for these RISC-V boards: .. rst-class:: rst-columns * hifive1_revb * litex_vexriscv * qemu_riscv64 * Added support for the gpmrb x86 board * Added support for these following shields: .. rst-class:: rst-columns * frdm_cr20a * link_board_can * sparkfun_sara_r4 * wnc_m14a2a * x_nucleo_iks01a3 * Removed support for these boards: .. rst-class:: rst-columns * arduino_101 * arduino_101_sss * curie_ble * galileo * quark_d2000_crb * quark_se_c1000_devboard * quark_se_c1000_ss_devboard * quark_se_c1000_ble * tinytile * x86_jailhouse Drivers and Sensors ******************* * ADC * Added API to support calibration * Enabled ADC on STM32WB * Removed Quark D2000 ADC driver * Added NXP ADC12 and SAM0 ADC drivers * Added ADC shell * Audio * Added support for two microphones (stereo) in the mpxxdtyy driver * CAN * Added support for canbus Ethernet translator * Added 6LoCAN implementation * Added MCP2515, NXP FlexCAN, and loopback drivers * Added CAN shell * Clock Control * Added NXP Kinetis MCG, SCG, and PCC drivers * Added STM32H7, STM32L1X, and STM32WB support * Removed Quark SE driver * Counter * Added optional flags to alarm configuration structure and extended set channel alarm flags * Added top_value setting configuration structure to API * Enabled counter for STM32WB * Added NXP GPT, "CMOS" RTC, SiLabs RTCC, and SAM0 drivers * Removed Quark D2000 support from QMSI driver * Display * Added ST7789V based LCD driver * Renamed ssd1673 driver to ssd16xx * Added framebuffer driver with multiboot support * Added support for Seeed 2.8" TFT touch shield v2.0 * DMA * Added API to retrieve runtime status * Added SAM0 DMAC driver * Removed Quark SE C1000 support from QMSI driver * Entropy * Added TI CC13xx / CC26xx driver * ESPI * Added Microchip XEC driver * Ethernet * Added LiteEth driver * Flash * Removed Quark SE C1000 driver * Removed support for Quark D2000 from QMSI driver * Added STM32G0XX and STM32WB support to STM32 driver * Added RV32M1 and native POSIX drivers * GPIO * Added stm32f1x SWJ configuration * Removed Quark SE C1000 and D2000 support from DesignWare driver * Added support for STM32H7, STM32L1X, and STM32WB to STM32 driver * Added Microchip XEC and TI CC13x2 / CC26x2 drivers * Added HT16K33 LED driver * Added interrupt support to SAM0 driver * Hardware Info * Added ESP32 and SAM0 drivers * I2C * Added support for STM32MP1, STM32WB, and STM32L1X to STM32 driver * Added STM32F10X slave support * Added power management to nrf TWI and TWIM drivers * Added TI CC13xx / CC26xx, Microchip MEC, SAM0, and RV32M1 drivers * Rewrote DesignWare driver for PCI(e) support * IEEE 802.15.4 * Fixed KW41z fault and dBm mapping * Interrupt Controller * Added initial support for ARC TCC * Added GIC400, LiteX, and SAM0 EIC drivers * Added support for STM32G0X, STM32H7, STM32WB, and STM32MP1 to STM32 driver * Removed MVIC driver * IPM * Removed Quark SE driver * Added MHU and STM32 drivers * LED * Added Holtek HT16K33 LED driver * Modem * Introduced socket helper layer * Introduced command handler and UART interface driver layers * Introduced modem context helper driver * Added u-blox SARA-R4 modem driver * Pinmux * Added SPI support to STM32MP1 * Enabled ADC, PWM, I2C, and SPI pins on STM32WB * Added Microchip XEC and TI CC13x2 / CC26x2 drivers * PWM * Added NXP PWM driver * Added support for STM32G0XX to STM32 driver * Sensor * Added STTS751 temperature sensor driver * Added LSM6DSO and LPS22HH drivers * Renamed HDC1008 driver to ti_hdc and added support for 1050 version * Added LED current, proximity pulse length, ALS, and proximity gain configurations to APDS9960 driver * Reworked temperature and acceleration conversions, and added interrupt handling in ADXL362 driver * Added BME680 driver and AMS ENS210 drivers * Serial * Added Xilinx ZynqMP PS, LiteUART, and TI CC12x2 / CC26x2 drivers * Added support for virtual UARTS over RTT channels * Added support for STM32H7 to STM32 driver * Removed support for Quark D2000 from QMSI driver * Enabled interrupts in LPC driver * Implemented ASYNC API in SAM0 driver * Added PCI(e) support to NS16550 driver * SPI * Added support for STM32MP1X and STM32WB to STM32 driver * Removed support for Quark SE C1000 from DesignWare driver * Added TI CC13xx / CC26xx driver * Implemented ASYNC API in SAM0 driver * Timer * Added Xilinx ZynqMP PS ttc driver * Added support for SMP to ARC V2 driver * Added MEC1501 32 KHZ, local APIC timer, and LiteX drivers * Replaced native POSIX system timer driver with tickless support * Removed default selection of SYSTICK timer for ARM platforms * USB * Added NXP EHCI driver * Implemented missing API functions in SAM0 driver * WiFi * Implemented TCP listen/accept and UDP support in eswifi driver Networking ********** * Added support for `SOCKS5 proxy <path_to_url`__. See also `RFC1928 <path_to_url`__ for details. * Added support for 6LoCAN, a 6Lo adaption layer for Controller Area Networks. * Added support for :ref:`Point-to-Point Protocol (PPP) <ppp>`. * Added support for UpdateHub, an end-to-end solution for large scale over-the-air update of devices. See `UpdateHub.io <path_to_url`__ for details. * Added support to automatically register network socket family. * Added support for ``getsockname()`` function. * Added SO_PRIORITY support to ``setsockopt()`` * Added support for VLAN tag stripping. * Added IEEE 802.15.4 API for ACK configuration. * Added dispatching support to SocketCAN sockets. * Added user mode support to PTP clock API. * Added user mode support to network interface address functions. * Added AF_NET_MGMT socket address family support. This is for receiving network event information in user mode application. * Added user mode support to ``net_addr_ntop()`` and ``net_addr_pton()`` * Added support for sending network management events when DNS server is added or deleted. * Added LiteEth Ethernet driver. * Added support for ``sendmsg()`` API. * Added `civetweb <path_to_url`__ HTTP API support. * Added LWM2M IPSO Accelerometer, Push Button, On/Off Switch and Buzzer object support. * Added LWM2M Location and Connection Monitoring object support. * Added network management L4 layer. The L4 management events are used when monitoring network connectivity. * Allow net-mgmt API to pass information length to application. * Removed network management L1 layer as it was never used. * By default a network interface is set to UP when the device starts. If this is not desired, then it is possible to disable automatic start. * Allow collecting network packet TX throughput times in the network stack. This information can be seen in net-shell. * net-shell Ping command overhaul. * Accept UDP packet with missing checksum. * 6lo compression rework. * Incoming connection handling refactoring. * Network interface refactoring. * IPv6 fragmentation fixes. * TCP data length fixes if TCP options are present. * SNTP client updates. * Trickle timer re-init fixes. * ``getaddrinfo()`` fixes. * Fixes in DHCPv4, LWM2M, gPTP, and MQTT * DNS fixes for non-compressed answers. * mDNS and LLMNR resolver fixes. * Ethernet ARP fixes. * OpenThread updates and fixes. * Network device driver fixes for: .. rst-class:: rst-columns - Ethernet e1000 - Ethernet enc28j60 - Ethernet mcux - Ethernet stellaris - Ethernet gmac - Ethernet stm32 - WiFi eswifi - IEEE 802.15.4 kw41z - IEEE 802.15.4 nrf5 Bluetooth ********* * Host: * GATT: Added support for database hashes, Read Using Characteristic UUID, static services, disabling the dynamic database, and notifying and indicating by UUID * GATT: Simplified the bt_gatt_notify_cb() API * GATT: Added additional attributes to the Device Information Service * GATT: Several protocol and database fixes * Settings: Transitioned to new optimized settings model and support for custom backends * Completed support for directed advertising and Out-Of-Band (OOB) pairing * Added support for fine-grained control of security establishment, including forcing a pairing procedure in case of key loss * Switched to separate, dedicated pools for discardable events and number of completed packets events * Extended and improved the Bluetooth shell with several commands * BLE qualification up to the 5.1 specification * BLE Mesh: Several fixes and improvements * BLE split software Controller: * The split software Controller is now the default * Added support for the Data Length Update procedure * Improved and documented the ticker packet scheduler for improved conflict resolution * Added support for out-of-tree user-defined commands and events, Zephyr Vendor Specific Commands, and user-defined protocols * Converted several control procedures to be queueable * Nordic: Decorrelated address generation from resolution * Nordic: Added support for Controller-based privacy, fast encryption setup, RSSI, low-latency ULL processing of messages, nRF52811 IC BLE radio, PA/LNA on Port 1 GPIO pins, and radio event abort * BLE qualification up to the 5.1 specification * BLE legacy software Controller: * BLE qualification up to the 5.1 specification * Multiple control procedures fixes and improvements Build and Infrastructure ************************ * The devicetree Python scripts have been rewritten to be more robust and easier to understand and change. The new scripts are these three files: - :zephyr_file:`scripts/dts/dtlib.py` -- a low-level :file:`.dts` parsing library - :zephyr_file:`scripts/dts/edtlib.py` -- a higher-level library that adds information from bindings - :zephyr_file:`scripts/dts/gen_defines.py` -- generates a C header from the devicetree files for the board The new scripts verify ``category: optional/required`` and ``type:`` settings given in bindings for nodes, and add some new types, like ``phandle-array``. Error messages and other output is now more helpful. See the updated documentation in :zephyr_file:`dts/binding-template.yaml`. The old scripts are kept around to generate a few deprecated ``#define``\ s. They will be removed in the Zephyr 2.2 release. * Changed ARM Embedded toolchain to default to nano variant of newlib Libraries / Subsystems *********************** * File Systems: Added support for littlefs HALs **** * HALs are now moved out of the main tree as external modules and reside in their own standalone repositories. Documentation ************* * We've made many updates to component, subsystem, and process documentation bringing our documentation up-to-date with code changes, additions, and improvements, as well as new supported boards and samples. Tests and Samples ***************** * We have implemented additional tests and significantly expanded the amount of test cases in existing tests to increase code coverage. Issue Related Items ******************* These GitHub issues were addressed since the previous 1.14.0 tagged release: .. comment List derived from GitHub Issue query: ... * :github:`issuenumber` - issue title * :github:`18964` - [Coverity CID :203911]Memory - corruptions in /tests/bluetooth/uuid/src/main.c * :github:`18963` - [Coverity CID :203910]Memory - corruptions in /tests/bluetooth/uuid/src/main.c * :github:`18959` - [Coverity CID :203907]Parse warnings in /include/bluetooth/conn.h * :github:`18923` - (BLE) Dynamic TX Power Control * :github:`18906` - Problem on build when calling objcopy to generate isrList.bin * :github:`18865` - Fatal Usage Fault When Bluetooth And OpenThread Are Enabled On NRF52840 Multiprotocol Support * :github:`18828` - Bluetooth: controller: crash terminating link during encryption procedure * :github:`18821` - Documentation: parent vs child in DeviceTree nodes * :github:`18819` - Bluetooth: LL split assert upon disconnection * :github:`18814` - Module Request: LoRaMac-Node * :github:`18813` - fs: nvs: Cannot delete entries * :github:`18808` - Docs for gpmrb board incorrectly refer to up_squared board * :github:`18804` - Channel Selection Algorithm Modification In Zephyr * :github:`18802` - Bluetooth: UUID: Missing tests and confusing documentation * :github:`18799` - bt_uuid_create_le() and bt_uuid_create() have endianness issues, and only one of them is needed * :github:`18795` - FS:NVS: garbage collection when restart * :github:`18784` - Can not build link_board_can shield * :github:`18774` - (nRF51) NVS example doesn't work * :github:`18765` - LwM2M: DNS handling via offload socket API is broken * :github:`18760` - hello_world sample instructions don't work * :github:`18739` - k_uptime_get_32() does not behave as documented * :github:`18732` - net: mDNS name resolving issue between 2 Zephyr nodes * :github:`18726` - arc: should not rely on that ERET has a copy of ilink * :github:`18725` - arc: the IRM bit of SEC_STAT is not handled corrected * :github:`18724` - arc: interrupt stack is not switched correctly * :github:`18717` - USB broken on disco l475 iot board * :github:`18705` - SMP fails to allocate buffer and pairing times out * :github:`18693` - POSIX: Some headers were missing from PR #16621 * :github:`18687` - [Coverity CID :203623]Memory - illegal accesses in /tests/subsys/settings/fcb_init/src/settings_test_fcb_init.c * :github:`18686` - [Coverity CID :203622]Parse warnings in /opt/zephyr-sdk-0.10.3/nios2-zephyr-elf/nios2-zephyr-elf/include/c++/8.3.0/bits/refwrap.h * :github:`18685` - [Coverity CID :203621]Parse warnings in /opt/zephyr-sdk-0.10.3/nios2-zephyr-elf/nios2-zephyr-elf/include/c++/8.3.0/bits/refwrap.h * :github:`18684` - [Coverity CID :203620]Parse warnings in /opt/zephyr-sdk-0.10.3/nios2-zephyr-elf/nios2-zephyr-elf/include/c++/8.3.0/bits/refwrap.h * :github:`18683` - [Coverity CID :190988]Memory - illegal accesses in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/drivers/imx/fsl_elcdif.c * :github:`18682` - [Coverity CID :190984]Memory - illegal accesses in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/drivers/imx/fsl_elcdif.c * :github:`18681` - [Coverity CID :190979]Memory - illegal accesses in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/drivers/imx/fsl_elcdif.c * :github:`18680` - [Coverity CID :190959]Memory - illegal accesses in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/drivers/imx/fsl_elcdif.c * :github:`18679` - [Coverity CID :198643]Incorrect expression in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/MKE18F16/fsl_clock.c * :github:`18678` - [Coverity CID :198642]Incorrect expression in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/MKE18F16/fsl_clock.c * :github:`18677` - [Coverity CID :198641]Incorrect expression in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/MKE18F16/fsl_clock.c * :github:`18676` - [Coverity CID :190994]Incorrect expression in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/MK64F12/fsl_clock.c * :github:`18675` - [Coverity CID :190982]Incorrect expression in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/MK64F12/fsl_clock.c * :github:`18674` - [Coverity CID :190962]Incorrect expression in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/MK64F12/fsl_clock.c * :github:`18673` - [Coverity CID :190947]Incorrect expression in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/MK64F12/fsl_clock.c * :github:`18672` - [Coverity CID :198948]Control flow issues in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/LPC55S69/fsl_clock.c * :github:`18671` - [Coverity CID :198947]Integer handling issues in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/LPC55S69/fsl_clock.c * :github:`18670` - [Coverity CID :182600]Integer handling issues in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/devices/LPC54114/fsl_clock.c * :github:`18669` - [Coverity CID :158891]Memory - illegal accesses in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nxp/mcux/components/phyksz8081/fsl_phy.c * :github:`18668` - [Coverity CID :203544]Integer handling issues in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nordic/nrfx/drivers/src/nrfx_usbd.c * :github:`18667` - [Coverity CID :203513]Integer handling issues in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nordic/nrfx/drivers/src/nrfx_usbd.c * :github:`18666` - [Coverity CID :203506]Integer handling issues in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nordic/nrfx/drivers/src/nrfx_usbd.c * :github:`18665` - [Coverity CID :203436]Memory - illegal accesses in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/hal/nordic/nrfx/drivers/src/nrfx_usbd.c * :github:`18664` - [Coverity CID :203416]Uninitialized variables in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/fs/littlefs/lfs.c * :github:`18663` - [Coverity CID :203413]Null pointer dereferences in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/fs/littlefs/lfs.c * :github:`18662` - [Coverity CID :61908]Insecure data handling in /home/aasthagr/zephyrproject-external-coverity-new/zephyrproject/modules/crypto/mbedtls/library/ssl_tls.c * :github:`18658` - Bluetooth BR/EDR encryption key negotiation vulnerability * :github:`18654` - cc3220sf_launchxl fails tests/kernel/interrupt/arch.interrupt * :github:`18645` - Disconnect because of data packets during encryption procedure * :github:`18615` - sam e70 xplained failed to build hello world * :github:`18599` - tests/kernel/fifo/fifo_timeout fails on cc3220sf_launchxl * :github:`18598` - tests/net/trickle failed on multiple plartforms * :github:`18595` - USB CDC endless loop with BLE on NRF52 * :github:`18593` - tests/arch/arm/arm_zero_latency_irqs fails on cc3220sf_launchxl * :github:`18592` - (nRF51) The RSSI signal does not rise above -44 dBm * :github:`18590` - tests/kernel/fatal/kernel.common.stack_sentinel fails on FRDM-KW41Z * :github:`18587` - tests/kernel/fifo/fifo_timeout/kernel.fifo.timeout fails to run on lpcxpresso54114_m4 * :github:`18584` - BT LL assert on LL/CON/ADV/BV-04-C * :github:`18580` - Bluetooth: Security fail on initial pairing * :github:`18574` - Some platforms: reel_board, frdm_k64f and sam_e70_xplained are be built failure * :github:`18572` - Bluetooth: GATT: Unable to indicate by UUID * :github:`18563` - log_strdup missing error messages seen when running wifi sample * :github:`18547` - Bluetooth: GATT: Fix using variable size storage for CCC * :github:`18546` - Hard Fault when connecting to BLE device * :github:`18524` - No disconnection event during "heavy" indication stream * :github:`18522` - BLE: Mesh: When transport send seg_msg to LPN * :github:`18521` - BLE: Mesh: when friend send msg to LPN * :github:`18508` - tests/net/trickle failed on frdm_k64f board * :github:`18476` - Custom module with west * :github:`18462` - potential buffer overrun in logging infrastructure * :github:`18461` - [Coverity CID :203487]Parse warnings in /usr/lib/gcc/x86_64-redhat-linux/8/include/stdint-gcc.h * :github:`18460` - [Coverity CID :203527]Parse warnings in /usr/include/unistd.h * :github:`18459` - [Coverity CID :203509]Null pointer dereferences in /tests/subsys/usb/desc_sections/src/desc_sections.c * :github:`18458` - [Coverity CID :203422]Memory - illegal accesses in /tests/subsys/fs/littlefs/src/testfs_util.c * :github:`18457` - [Coverity CID :203419]Security best practices violations in /tests/net/traffic_class/src/main.c * :github:`18456` - [Coverity CID :203401]Security best practices violations in /tests/net/traffic_class/src/main.c * :github:`18455` - [Coverity CID :203490]Error handling issues in /tests/net/socket/net_mgmt/src/main.c * :github:`18454` - [Coverity CID :203499]Null pointer dereferences in /tests/net/icmpv6/src/main.c * :github:`18453` - [Coverity CID :203480]Null pointer dereferences in /tests/net/context/src/main.c * :github:`18446` - [Coverity CID :203532]Incorrect expression in /tests/kernel/sched/schedule_api/src/user_api.c * :github:`18445` - [Coverity CID :203507]Error handling issues in /tests/kernel/mutex/sys_mutex/src/main.c * :github:`18444` - [Coverity CID :203516]Memory - corruptions in /tests/kernel/mem_protect/userspace/src/main.c * :github:`18443` - [Coverity CID :203454]Error handling issues in /tests/kernel/mem_protect/sys_sem/src/main.c * :github:`18442` - [Coverity CID :203465]Memory - corruptions in /tests/kernel/mem_protect/protection/src/main.c * :github:`18439` - [Coverity CID :203437]Incorrect expression in /tests/kernel/fp_sharing/float_disable/src/k_float_disable.c * :github:`18438` - [Coverity CID :203407]Incorrect expression in /tests/kernel/fp_sharing/float_disable/src/k_float_disable.c * :github:`18437` - [Coverity CID :203478]Program hangs in /tests/kernel/common/src/sflist.c * :github:`18436` - [Coverity CID :203424]Control flow issues in /tests/kernel/common/src/sflist.c * :github:`18434` - [Coverity CID :203486]Memory - corruptions in /tests/bluetooth/uuid/src/main.c * :github:`18433` - [Coverity CID :203431]Memory - corruptions in /tests/bluetooth/uuid/src/main.c * :github:`18432` - [Coverity CID :203502]Error handling issues in /tests/bluetooth/tester/src/gap.c * :github:`18431` - [Coverity CID :203391]Null pointer dereferences in /tests/bluetooth/gatt/src/main.c * :github:`18430` - [Coverity CID :203540]Incorrect expression in /tests/arch/arm/arm_zero_latency_irqs/src/arm_zero_latency_irqs.c * :github:`18429` - [Coverity CID :203525]Incorrect expression in /tests/arch/arm/arm_thread_swap/src/arm_thread_arch.c * :github:`18428` - [Coverity CID :203479]Incorrect expression in /tests/arch/arm/arm_thread_swap/src/arm_thread_arch.c * :github:`18427` - [Coverity CID :203392]Incorrect expression in /tests/arch/arm/arm_thread_swap/src/arm_thread_arch.c * :github:`18426` - [Coverity CID :203455]Incorrect expression in /tests/arch/arm/arm_ramfunc/src/arm_ramfunc.c * :github:`18424` - [Coverity CID :203489]Memory - corruptions in /tests/application_development/gen_inc_file/src/main.c * :github:`18423` - [Coverity CID :203473]Null pointer dereferences in /subsys/usb/usb_descriptor.c * :github:`18421` - [Coverity CID :203504]Uninitialized variables in /subsys/net/lib/sockets/sockets_net_mgmt.c * :github:`18420` - [Coverity CID :203468]Control flow issues in /subsys/net/lib/sockets/sockets_net_mgmt.c * :github:`18419` - [Coverity CID :203397]Control flow issues in /subsys/net/lib/sockets/sockets_net_mgmt.c * :github:`18418` - [Coverity CID :203445]Error handling issues in /subsys/net/lib/sockets/getnameinfo.c * :github:`18417` - [Coverity CID :203501]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_timer.c * :github:`18416` - [Coverity CID :203475]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_timer.c * :github:`18415` - [Coverity CID :203420]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_timer.c * :github:`18414` - [Coverity CID :203496]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_push_button.c * :github:`18413` - [Coverity CID :203488]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_push_button.c * :github:`18412` - [Coverity CID :203482]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_push_button.c * :github:`18411` - [Coverity CID :203450]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_onoff_switch.c * :github:`18410` - [Coverity CID :203448]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_onoff_switch.c * :github:`18409` - [Coverity CID :203427]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_onoff_switch.c * :github:`18408` - [Coverity CID :203533]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_light_control.c * :github:`18407` - [Coverity CID :203519]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_light_control.c * :github:`18406` - [Coverity CID :203511]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_buzzer.c * :github:`18405` - [Coverity CID :203426]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_buzzer.c * :github:`18404` - [Coverity CID :203414]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_buzzer.c * :github:`18403` - [Coverity CID :203539]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_accelerometer.c * :github:`18402` - [Coverity CID :203530]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_accelerometer.c * :github:`18401` - [Coverity CID :203438]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_accelerometer.c * :github:`18400` - [Coverity CID :203483]Control flow issues in /subsys/net/lib/conn_mgr/events_handler.c * :github:`18399` - [Coverity CID :203457]Control flow issues in /subsys/net/l2/ppp/lcp.c * :github:`18398` - [Coverity CID :203514]Control flow issues in /subsys/net/l2/ppp/ipv6cp.c * :github:`18397` - [Coverity CID :203512]Memory - corruptions in /subsys/net/l2/ppp/ipv6cp.c * :github:`18396` - [Coverity CID :203435]Error handling issues in /subsys/net/l2/ppp/fsm.c * :github:`18395` - [Coverity CID :203471]Memory - corruptions in /subsys/net/l2/ethernet/gptp/gptp_mi.c * :github:`18394` - [Coverity CID :203464]Memory - corruptions in /subsys/net/l2/ethernet/gptp/gptp_mi.c * :github:`18393` - [Coverity CID :203541]Integer handling issues in /subsys/net/ip/6lo.c * :github:`18392` - [Coverity CID :203494]Integer handling issues in /subsys/fs/littlefs_fs.c * :github:`18391` - [Coverity CID :203403]Memory - corruptions in /subsys/disk/disk_access_usdhc.c * :github:`18390` - [Coverity CID :203441]Null pointer dereferences in /subsys/bluetooth/mesh/transport.c * :github:`18389` - [Coverity CID :203396]Null pointer dereferences in /subsys/bluetooth/mesh/access.c * :github:`18388` - [Coverity CID :203545]Memory - corruptions in /subsys/bluetooth/host/smp.c * :github:`18387` - [Coverity CID :203536]Memory - corruptions in /subsys/bluetooth/host/smp.c * :github:`18385` - [Coverity CID :203534]Memory - corruptions in /subsys/bluetooth/host/hci_core.c * :github:`18384` - [Coverity CID :203495]Control flow issues in /subsys/bluetooth/host/gatt.c * :github:`18383` - [Coverity CID :203447]Memory - corruptions in /subsys/bluetooth/host/att.c * :github:`18382` - [Coverity CID :203524]Incorrect expression in /subsys/bluetooth/controller/ticker/ticker.c * :github:`18381` - [Coverity CID :203393]Control flow issues in /subsys/bluetooth/controller/ll_sw/ull_conn.c * :github:`18380` - [Coverity CID :203461]Null pointer dereferences in /subsys/bluetooth/controller/ll_sw/ull.c * :github:`18379` - [Coverity CID :203493]Control flow issues in /soc/arm/st_stm32/stm32h7/soc_m7.c * :github:`18377` - [Coverity CID :203535]Error handling issues in /samples/net/sockets/civetweb/src/main.c * :github:`18376` - [Coverity CID :203462]Error handling issues in /samples/net/sockets/civetweb/src/main.c * :github:`18375` - [Coverity CID :203440]Null pointer dereferences in /samples/net/nats/src/main.c * :github:`18374` - [Coverity CID :203523]Error handling issues in /samples/drivers/counter/alarm/src/main.c * :github:`18372` - [Coverity CID :203543]Memory - illegal accesses in /samples/bluetooth/eddystone/src/main.c * :github:`18371` - [Coverity CID :203542]Error handling issues in /lib/posix/pthread.c * :github:`18370` - [Coverity CID :203469]Memory - corruptions in /drivers/wifi/eswifi/eswifi_core.c * :github:`18369` - [Coverity CID :203425]Memory - corruptions in /drivers/wifi/eswifi/eswifi_core.c * :github:`18368` - [Coverity CID :203411]Memory - corruptions in /drivers/wifi/eswifi/eswifi_core.c * :github:`18367` - [Coverity CID :203409]Memory - corruptions in /drivers/wifi/eswifi/eswifi_core.c * :github:`18366` - [Coverity CID :203452]Control flow issues in /drivers/timer/xlnx_psttc_timer.c * :github:`18365` - [Coverity CID :203434]Control flow issues in /drivers/timer/xlnx_psttc_timer.c * :github:`18364` - [Coverity CID :203467]Memory - corruptions in /drivers/sensor/lis2dh/lis2dh_trigger.c * :github:`18363` - [Coverity CID :203492]Memory - corruptions in /drivers/net/ppp.c * :github:`18362` - [Coverity CID :203412]Control flow issues in /drivers/net/ppp.c * :github:`18361` - [Coverity CID :203515]Uninitialized variables in /drivers/flash/flash_stm32l4x.c * :github:`18360` - [Coverity CID :203531]Memory - corruptions in /drivers/espi/espi_mchp_xec.c * :github:`18359` - [Coverity CID :203521]Memory - illegal accesses in /drivers/espi/espi_mchp_xec.c * :github:`18358` - [Coverity CID :203497]Memory - corruptions in /drivers/espi/espi_mchp_xec.c * :github:`18357` - [Coverity CID :203485]Memory - illegal accesses in /drivers/espi/espi_mchp_xec.c * :github:`18356` - [Coverity CID :203430]Integer handling issues in /drivers/espi/espi_mchp_xec.c * :github:`18355` - [Coverity CID :203466]Memory - illegal accesses in /drivers/can/can_mcux_flexcan.c * :github:`18354` - [Coverity CID :203449]Memory - illegal accesses in /boards/posix/native_posix/cmdline_common.c * :github:`18353` - [Coverity CID :203522]Null pointer dereferences in /arch/arm/core/cortex_m/fault.c * :github:`18352` - devicetree: support multiple values in io-channels * :github:`18334` - DNS resolution is broken for some addresses in master/2.0-pre * :github:`18326` - Bluetooth: Mesh: LPN: Remove msg from cache on rejection Enhancement * :github:`18320` - tests/drivers/can/api/peripheral.can fail on FRDM-K64F * :github:`18306` - Unable to reconnect paired devices with controller privacy disabled (host privacy enabled) * :github:`18301` - menuconfig target can corrupt build configuration * :github:`18298` - Unable to build mesh-demo for BBC micro:bit * :github:`18292` - tests/net/lib/dns_addremove failed on frdm_k64f board. * :github:`18284` - tests/kernel/fp_sharing/float_disable and tests/kernel/mutex/mutex_api and tests/kernel/sleep fails on twr_ke18f * :github:`18283` - tests/crypto/tinycrypt_hmac_prng and tests/crypto/mbedtls and tests/posix/fs build failure on mimxrt1015_evk * :github:`18281` - tests/kernel/mem_protect/protection fails on LPC54114_m4 * :github:`18272` - xtensa ASM2 has no support for dynamic interrupts * :github:`18269` - Documentation improvement for macOS * :github:`18263` - flash sector erase fails on stm32f412 * :github:`18261` - CONFIG_TIMESLICING=n breaks kernel * :github:`18258` - sys_get_be64() is missing from sys/byteorder.h * :github:`18253` - Network samples echo_client doesn't work if only IPv4 enabled. * :github:`18246` - Build failures with current tree * :github:`18238` - drivers/modem/modem_socket: modem_socket_put() sock_fd parameter not handled correctly * :github:`18232` - drivers: can: mcux: TX callback and can_detach don't work propperly * :github:`18231` - MCUBoot not cleaning up properly before booting Zephyr? * :github:`18228` - stm32h747i_disco: Fix SYS_CLOCK_TICKS_PER_SEC * :github:`18212` - README file missing for civetweb sample * :github:`18205` - tests/net/socket/udp fails when code coverage is enabled on qemu_x86 * :github:`18202` - Disable Duplicate scan, no longer available * :github:`18201` - bug: west flash with --hex-file param used to work w/o path specified * :github:`18198` - SDK 0.10.2 rv32m1_vega samples/subsys/logging/logger build fails * :github:`18194` - [zephyr 1.14][MESH/NODE/CFG/HBP/BV-05-C] Zephyr does not send Heartbeat message on friendship termination * :github:`18188` - [zephyr 1.14] Re-enabling CCC gets broken when used along with Robust Caching * :github:`18183` - [zephyr 1.14][GATT/SR/GAS/BV-07-C] GATT Server does not inform change-unaware client about DB changes * :github:`18181` - Some platforms(e.g. sam_e70_xplained) will be flashed failure if the platforms have not generated HEX file although they are built successfully. * :github:`18178` - BLE Mesh When Provisioning Use Input OOB Method * :github:`18171` - gen_defines creates identical labels for multicell pwms definition * :github:`18155` - i2c_ll_stm32_v1: I2C_CR1:STOP is not cleared * :github:`18154` - Qemu: mps2+: missing documentation * :github:`18150` - [zephyr 1.14] Host does not change the RPA * :github:`18141` - arc: the caculation of exception stack is wrong * :github:`18140` - xtensa passes NULL esf on fatal error * :github:`18132` - getting_started should indicate upgrade rather than just install west * :github:`18131` - devicetree should check input against declared type * :github:`18092` - Assert in BT controller on RPA timeout * :github:`18090` - [zephyr 1.14][MESH/NODE/FRND/FN/BV-08-C] Mesh Friend queues more messages than indicates it's Friend Cache * :github:`18080` - LWM2M bootstrap issue * :github:`18059` - k_busy_wait passed milliseconds instead of microseconds * :github:`18052` - z_fatal_error missing log_strdup * :github:`18048` - [zephyr 1.14] Zephyr with privacy does not disconnect device with unresolvable RPA * :github:`18042` - Only corporate members can join the slack channel * :github:`18034` - It's impossible to build Zephyr via cmake/make with west 0.6.0 installed * :github:`18029` - why kconfiglib.py doesn't throw error for file drivers/serial/Kconfig.nrfx * :github:`18021` - Socket vtable can access null pointer callback function * :github:`18019` - BT scan via shell fatal error * :github:`18013` - BLE Mesh On Net Buffer free issue * :github:`18011` - arc: the offset generation of accl_regs is wrong * :github:`18009` - Dead link in documentation * :github:`18005` - BLE Mesh When Friend Clear Procedure Timeout * :github:`18002` - Flash using open source stlink, instead of SEGGER jlink? * :github:`17997` - fix extern "C" use throughout Zephyr * :github:`17996` - BUILD_ASSERT not active in three of five shippable platforms * :github:`17990` - BLE Mesh When IV update test procedure * :github:`17979` - Security level cannot be elevated after re-connection with privacy * :github:`17977` - BLE Mesh When IV Update Procedure * :github:`17971` - [zephyr 1.14] Unable to register GATT service that was unregistered before * :github:`17967` - drivers/pwm/pwm_api test failed on frdm_k64f board. * :github:`17965` - kernel/sleep/ test failed on reel_board. * :github:`17962` - BLE Mesh Recommended memory allocation due to who is assigned who releases the strategy * :github:`17956` - Is POSIX I/O supported on peripheral? * :github:`17951` - RFC: update FS API for readdir consistency * :github:`17948` - Bluetooth: privacy: Reconnection issue * :github:`17944` - [zephyr 1.14] LE Enhanced Connection Complete indicates Resolved Public once connected to Public peer address * :github:`17936` - Bluetooth: Mesh: The canceled buffer is not free, causing a memory leak * :github:`17932` - BLE Mesh When Friend Send Seg Message To LPN * :github:`17926` - CAN \| nrf52 \| device tree error: zephyrproject/zephyr/dts/bindings/can/microchip,mcp2515.yaml (in 'reg'): 'category' from !included file overwritten ('required' replaced with 'optional') * :github:`17923` - SPI1 on nrf52_pca10040 is dead by default * :github:`17922` - Driver: modem helper should make it easier to implement a modem * :github:`17920` - Bluetooth: Security problem * :github:`17907` - BLE Mesh when resend use GATT bearer * :github:`17899` - tests/kernel/mem_protect/stackprot/kernel.memory_protection fails on nsim_em * :github:`17897` - k_busy_wait not working when using 32KHz timer driver * :github:`17891` - fs/nvs: nvs_init can hang if no nvs_ate available * :github:`17882` - [zephyr 1.14] Database Out of Sync error is not returned as expected * :github:`17880` - Unable to re-connect to privacy enabled peer when using stack generated Identity * :github:`17876` - BME680 sensor sample not building * :github:`17870` - Incorrect report received lenght and offset in async API * :github:`17869` - Unlocking nested k_sched_lock() cause forced preemption * :github:`17864` - cpp_synchronization sample not working on nucleo_l476rg * :github:`17861` - Tester application lacks BTP Discover All Primary Services handler * :github:`17857` - GATT: Incorrect byte order for GATT database hash * :github:`17853` - kernel panic in tests/kernel/sched/schedule_api * :github:`17851` - riscv/m2gl025: timer tests broken * :github:`17843` - Bluetooth: controller: v1.14.x release conformance test failures * :github:`17821` - Mesh Bug on access.c * :github:`17820` - Mesh bug report In access.c * :github:`17816` - LVGL V5.3 build error if CONFIG_LVGL_COLOR_16_SWAP=y * :github:`17812` - pthread_cond_timedwait interprets timeout wrong * :github:`17809` - Bluetooth Mesh message cached too early when LPN * :github:`17802` - [zephyr 1.14] Address type 0x02 is used by LE Create Connection in device privacy mode * :github:`17800` - Bluetooth: GATT: Write Without Reponse to invalid handle asserts * :github:`17794` - Timeutil_api test fails with sanitycheck on iotdk board. * :github:`17790` - MEC1501 configure warnings in eSPI (dts) * :github:`17789` - Bluetooth: host: conn.c missing parameter copy * :github:`17787` - openocd unable to flash hello_world to cc26x2r1_launchxl * :github:`17784` - failing network tests with code coverage enabled in qemu_x86 not failing when run with gdb * :github:`17783` - network tests failing with code coverage enabled in qemu_x86 (coverage.c) * :github:`17782` - network tests failing with 'unexpected eof' with code coverage enabled in qemu_x86 (TSS) * :github:`17778` - Microchip XEC rtos Timer breaks gpios and k_sleep? * :github:`17772` - Compilation error of soc/arm/nxp_imx/rt/soc.c * :github:`17764` - Broken link to latest development version of docs * :github:`17751` - build is broken for mec15xxevb_assy6853 * :github:`17738` - STATIC_ASSERT no longer defined when CONFIG_NEWLIB_LIBC is enabled * :github:`17732` - cannot use bt_conn_security in connected callback * :github:`17727` - how to make zephyr as a ble mesh provisioner to other BLE based board having ble mesh * :github:`17726` - How to make Zephyr as a ble mesh provisioner ? * :github:`17723` - Advertiser never clears state flags * :github:`17715` - Missing 'reg-names' string in riscv32-litex-vexriscv.dtsi * :github:`17703` - Add prop 'clock-frequency' to STM32 targets * :github:`17697` - usb_dc_nrfx driver gets stuck after USB3CV HID Tests are performed on hid sample * :github:`17692` - Proper way for joining a multicast group (NRF52840/OpenThread) * :github:`17690` - samples/subsys/shell/fs does not work? * :github:`17671` - ADC not supported by nrf52840_pca10059 DTS file * :github:`17665` - Missing 'label' on most nodes with 'compatible = "pwm-leds"' * :github:`17664` - Missing 'clocks' on most nodes with 'compatible = "nxp,kinetis-usbd"' * :github:`17663` - Missing 'label' on most nodes with 'compatible = "fixed-clock"' * :github:`17662` - Missing 'label' on nodes with 'compatible = "jedec,spi-nor"' * :github:`17657` - subsis/disk/disk_access_spi_sdhc: response data eaten by idle byte consumption * :github:`17650` - devicetree: missing preferred instance presence macro * :github:`17635` - UnicodeDecodeError is raised while executing west build * :github:`17630` - efr32mg_sltb004a tick clock error * :github:`17613` - POSIX arch: occasional failures of tests/kernel/sched/schedule_api on CI * :github:`17608` - NMP timeout when uploading image with mcumgr over BLE under Linux * :github:`17600` - Enable Mesh Friend support in Bluetooth tester application * :github:`17595` - two userspace tests fail if stack canaries are enabled in board configuration * :github:`17591` - ARM: z_arch_except() is too permissive in user mode * :github:`17590` - ARC: unable to induce kernel_oops or stack check fail errors from user mode * :github:`17586` - stack canary storage area should be read-only to user mode? * :github:`17584` - k_mutex is not SMP-safe * :github:`17581` - linker script packing failure with subsys/fb fonts and native_posix_64 * :github:`17564` - Missing 'stdlib.h' include when C++ standard library is used. * :github:`17559` - Assertion failed: zephyr toolchain variant invalid * :github:`17557` - samples/net/wifi fails to build on cc3220sf_launchxl * :github:`17555` - CONFIG_LOG doesn't work on x86_64 due to no working backends * :github:`17554` - pyocd flash does not support the -b option for board ID so that the sanitycheck script cant specified the board ID to flash when the host connected with multiple boards. * :github:`17550` - SimpleLink WiFi host driver should revert back to using static memory model * :github:`17547` - incorrect documentation for debugging nsim_em / nsim_sem * :github:`17543` - dtc version 1.4.5 with ubuntu 18.04 and zephyr sdk-0.10.1 * :github:`17534` - Race condition in GATT API. * :github:`17532` - List of missing device tree properties with 'category: required' in the binding for the node * :github:`17525` - L2CAP: On insufficient authentication error received, Zephyr does unauthenticated pairing * :github:`17511` - _bt_br_channels_area section missing in sanitycheck whitelist * :github:`17508` - RFC: Change/deprecation in display API * :github:`17507` - system timer drivers using the "new" API should not be configured with CONFIG_TICKLESS_KERNEL * :github:`17497` - Bluetooth: Mesh: How to Write provision and configure data to flash? * :github:`17488` - CDC_ACM USB on nRF device fails after suspend * :github:`17487` - v1.14-branch: SDK 0.10.1 support? * :github:`17486` - nRF52: SPIM: Errata work-around status? * :github:`17485` - sanitycheck: Over-zealous checking for binary sections * :github:`17483` - mec15xxevb_assy6853 board documentation is erroneous * :github:`17480` - holyiot_yj16019 cannot compile IEEE 802.15.4 L2 * :github:`17478` - net/buf test fails for qemu_x86_64 * :github:`17475` - [RTT] compile error when RTT console enabled * :github:`17463` - Bluetooth: API limits usage of MITM flags in Pairing Request * :github:`17460` - sample: gui/lvgl * :github:`17450` - net: IPv6/UDP datagram with unspecified addr and zero hop limit causes Zephyr to quit * :github:`17439` - sanitycheck: nrf52840-pca10056 (dev kit) picks up sample/drivers items which will fail due to missing HW * :github:`17427` - net: IPv4/UDP datagram with zero src addr and TTL causes Zephyr to segfault * :github:`17419` - arch:arc: remove the extra vairables used in irq and exception handling * :github:`17415` - Settings Module - settings_line_val_read() returning -EINVAL instead of 0 for deleted setting entries * :github:`17410` - k_work should have a user_data field * :github:`17408` - LwM2M: engine doesn't support offloaded TLS stack * :github:`17401` - LwM2M: requires that CONFIG_NET_IPV* be enabled (can't use 100% offloaded IP stack) * :github:`17399` - LwM2M: Can't use an alternate mbedtls implementation * :github:`17381` - DTS compatible property processing assumes specific driver exists * :github:`17379` - Wrong hex file generated for MCUboot * :github:`17378` - samples: net: echo-server: no return packet * :github:`17376` - device tree diagnostic failure in enum * :github:`17368` - Time Slicing cause system sleep short time * :github:`17366` - Regression: sanitycheck coverage generation defaults will error out for POSIX arch targets * :github:`17365` - Documentation: sanitycheck coverage generation instructions lead to errors and no coverage report for POSIX boards * :github:`17363` - SPI driver does not reset master mode fault on STM32 * :github:`17353` - Configuring with POSIX_API disables NET_SOCKETS_POSIX_NAMES * :github:`17342` - CODEOWNERS is broken (III) * :github:`17340` - Bluetooth Mesh: Unable to receive messages when RPL is full. * :github:`17338` - kernel objects address check in elf_helper.py * :github:`17313` - drivers: usb_dc_mcux_ehci does not compile * :github:`17307` - device tree bindings disallow strings that begin with integers * :github:`17294` - DB corruption when adding/removing service * :github:`17288` - Bluetooth: controller: Fix handling of L2CAP start frame with zero PDU length * :github:`17284` - unrecognized binary sections: ['_settings_handlers_area'] * :github:`17281` - sanitycheck error on mimxrt1050_evk samples/gui/lvgl/sample.gui.lvgl with no network connection * :github:`17280` - How to use UART1 for nrf52_pca10040 * :github:`17277` - no code coverage for k_float_disable() in user mode * :github:`17266` - CDC_ACM USB not recognized by windows as serial port * :github:`17262` - insufficient code coverage for lib/os/base64.c * :github:`17251` - w25q: erase operations must be erase-size aligned * :github:`17250` - After first GC operation the 1st sector had become scratch and the 2nd sector had became write sector. * :github:`17231` - Posix filesystem wrapper leaks internal FS desc structures * :github:`17226` - [Coverity CID :61894]Security best practices violations in /home/aasthagr/zephyrproject/modules/crypto/mbedtls/library/rsa.c * :github:`17225` - [Coverity CID :61905]Insecure data handling in /home/aasthagr/zephyrproject/modules/crypto/mbedtls/library/ssl_cli.c * :github:`17224` - [Coverity CID :78542]Null pointer dereferences in /home/aasthagr/zephyrproject/modules/crypto/mbedtls/library/rsa.c * :github:`17223` - [Coverity CID :149311]Control flow issues in /home/aasthagr/zephyrproject/modules/crypto/mbedtls/library/cipher.c * :github:`17222` - [Coverity CID :173947]Uninitialized variables in /home/aasthagr/zephyrproject/modules/lib/mcumgr/cborattr/src/cborattr.c * :github:`17221` - [Coverity CID :173979]Control flow issues in /home/aasthagr/zephyrproject/modules/lib/tinycbor/src/cborparser.c * :github:`17220` - [Coverity CID :173986]Control flow issues in /home/aasthagr/zephyrproject/modules/lib/mcumgr/cborattr/src/cborattr.c * :github:`17219` - [Coverity CID :174014]Incorrect expression in /home/aasthagr/zephyrproject/modules/lib/tinycbor/src/cborparser.c * :github:`17218` - [Coverity CID :186031]Control flow issues in /home/aasthagr/zephyrproject/modules/lib/mcumgr/cmd/fs_mgmt/src/fs_mgmt.c * :github:`17217` - [Coverity CID :186038]Control flow issues in /home/aasthagr/zephyrproject/modules/lib/mcumgr/cmd/img_mgmt/src/img_mgmt.c * :github:`17216` - [Coverity CID :186052]Control flow issues in /home/aasthagr/zephyrproject/modules/lib/mcumgr/cmd/fs_mgmt/src/fs_mgmt.c * :github:`17215` - [Coverity CID :186054]Control flow issues in /home/aasthagr/zephyrproject/modules/lib/mcumgr/cmd/img_mgmt/src/img_mgmt_state.c * :github:`17214` - [Coverity CID :186060]Control flow issues in /home/aasthagr/zephyrproject/modules/lib/mcumgr/cmd/img_mgmt/src/img_mgmt_state.c * :github:`17213` - [Coverity CID :186188]Memory - illegal accesses in /home/aasthagr/zephyrproject/modules/lib/open-amp/open-amp/lib/rpmsg/rpmsg.c * :github:`17212` - [Coverity CID :187076]Control flow issues in /home/aasthagr/zephyrproject/modules/hal/silabs/gecko/emlib/src/em_cmu.c * :github:`17211` - [Coverity CID :188746]Memory - illegal accesses in /home/aasthagr/zephyrproject/modules/hal/cypress/PDL/3.1.0/drivers/source/cy_syslib.c * :github:`17210` - [Coverity CID :190643]Error handling issues in /home/aasthagr/zephyrproject/modules/debug/segger/systemview/SEGGER_SYSVIEW.c * :github:`17209` - [Coverity CID :190927]Uninitialized variables in /home/aasthagr/zephyrproject/modules/lib/open-amp/open-amp/lib/remoteproc/remoteproc.c * :github:`17208` - [Coverity CID :190941]Insecure data handling in /home/aasthagr/zephyrproject/modules/crypto/mbedtls/library/ssl_tls.c * :github:`17207` - [Coverity CID :190963]Code maintainability issues in /home/aasthagr/zephyrproject/modules/fs/nffs/src/nffs_restore.c * :github:`17206` - [Coverity CID :190975]Memory - illegal accesses in /home/aasthagr/zephyrproject/modules/lib/open-amp/open-amp/lib/include/openamp/rpmsg.h * :github:`17205` - [Coverity CID :190999]Insecure data handling in /home/aasthagr/zephyrproject/modules/lib/open-amp/open-amp/lib/rpmsg/rpmsg_virtio.c * :github:`17204` - [Coverity CID :191000]Memory - corruptions in /home/aasthagr/zephyrproject/modules/lib/open-amp/open-amp/lib/remoteproc/remoteproc.c * :github:`17203` - [Coverity CID :198951]Code maintainability issues in /home/aasthagr/zephyrproject/modules/debug/segger/systemview/SEGGER_SYSVIEW.c * :github:`17202` - [Coverity CID :199436]Uninitialized variables in /subsys/net/lib/sockets/sockets.c * :github:`17201` - [Coverity CID :199437]Null pointer dereferences in /tests/net/ip-addr/src/main.c * :github:`17200` - [Coverity CID :199438]Memory - illegal accesses in /drivers/interrupt_controller/exti_stm32.c * :github:`17190` - net-mgmt should pass info element size to callback * :github:`17188` - k_uptime_delta returns wrong times * :github:`17182` - "tests/subsys/usb/device/" fails on reel_board. * :github:`17177` - ARM: userspace/test_bad_syscall fails on ARMv8-M * :github:`17176` - deprecated counter_set_alarm is referenced in documentation * :github:`17172` - insufficient code coverage for lib/os/mempool.c * :github:`17170` - x86_64 crash with spinning child thread * :github:`17167` - ARC crash with spinning user thread * :github:`17166` - arch/x86: eliminate support for CONFIG_REALMODE * :github:`17158` - Bluetooth: Update PICS for latest PTS 7.4.1 * :github:`17147` - UARTE device has no API when run on nrf52810 * :github:`17114` - drivers: usb_dc_stm32 broken after west update * :github:`17111` - nucleo_f030r8 build error * :github:`17095` - Building with Xtensa toolchain fails * :github:`17092` - Bluetooth: GAP/IDLE/NAMP/BV-01-C requires Read by UUID * :github:`17065` - Misspelled CONFIG use in is_rodata() for CONFIG_RISCV32 * :github:`17063` - tests/kernel/tickless/tickless_concept (qemu_x86) fails even outside of CI * :github:`17057` - Bluetooth: Mesh: Implementation doesn't conform to latest errata and 1.0.1 version * :github:`17055` - net: Incorrect data length after the connection is established * :github:`17053` - Bluetooth Mesh: Periodic Publishing * :github:`17043` - compile "hello-world" sample for esp32 board error * :github:`17041` - [1.14] Bluetooth: Mesh: RPL handling is not in line with the spec * :github:`17038` - code relocation generating different memory layout cause user mode not working * :github:`17037` - MQTT with TLS support over SOCKS * :github:`17031` - Compiler warnings in settings module in Zephyr 1.14 * :github:`17017` - #16827 Breaks Ethernet on FRDM-K64F * :github:`17015` - #15910 Breaks Ethernet on STM32F7 * :github:`17013` - Bluetooth: Add error reason to pairing failed callbacks * :github:`17007` - USB mass demo format fails on frdm_k64f * :github:`16989` - Errors when building application in Eclipse * :github:`16971` - DFU supported for hci_uart sample ? * :github:`16946` - characteristic value handle vs characteristic handle * :github:`16944` - Insufficient test coverage for lib/os/json.c * :github:`16943` - Missing test coverage for lib/os/crc.c :github:`16934` - drivers: flash: stm32l4: Erase wait time is not enough * :github:`16931` - logging: Assertion when in panic mode * :github:`16926` - NXP LPC54102LPC54114: question about dual core(M4 and M0) running on flash * :github:`16924` - Add DNS server added/removed events to net_mgmt * :github:`16915` - stack_sentinel: rare ASSERTION FAIL [!(z_arch_curr_cpu()->nested != 0U)] @ ZEPHYR_BASE/kernel/thread.c:429 Threads may not be created in ISRs * :github:`16911` - tests/kernel/sched/schedule_api crash on qemu_x86_64 with SCHED_MULTIQ enabled * :github:`16907` - native_posix build fails with X86_64 on macOS * :github:`16901` - No test coverage for CONFIG_ZERO_LATENCY_IRQS * :github:`16899` - fs/nvs: might loop-up if storage was not erased before first run * :github:`16898` - bluetooth stack change affects timer behavior * :github:`16894` - ARM: alignment problems in libc/newlib * :github:`16893` - Bluetooth: Multiple local IDs, privacy problem * :github:`16887` - ARM: threads' privilege stack alignment is not optimal * :github:`16872` - Bluetooth: LL: Peripheral crashes after a while with multiple Centrals * :github:`16864` - Bluetooth: Mesh: Rx buffer exhaustion causes deadlock * :github:`16862` - arc: -mfpu=fpuda_all is not set when CONFIG_FLOAT is configured * :github:`16861` - nRF52: UARTE: Data corruption right after resuming device * :github:`16830` - Bluetooth: controller: Follow up on ticker conflict resolution * :github:`16823` - k_busy_wait() on nRF5x boards isn't waiting long enough * :github:`16803` - Deferred bt_conn_tx causes sysworkq deadlock * :github:`16799` - Bluetooth: L2CAP: Interpretation of SCID and DCID in Disconnect is wrong * :github:`16797` - [Zephyr v1.14.0] stm32: MCUboot bootloader results in Hardware exception * :github:`16793` - kernel timeout_list repeatedly add a thread * :github:`16787` - [Coverity CID :198945]Null pointer dereferences in /subsys/bluetooth/controller/ll_sw/ull_conn.c * :github:`16786` - [Coverity CID :198946]Memory - corruptions in /subsys/bluetooth/host/gatt.c * :github:`16785` - [Coverity CID :198949]Error handling issues in /tests/net/socket/register/src/main.c * :github:`16779` - [Zephyr v1.14] ARM: fix the start address of MPU guard in stack-fail checking (when building with no user mode) * :github:`16778` - Build failures in various mimxrt boards * :github:`16773` - DTS: generated output for each flash-controller * :github:`16770` - Complete FP support for ARC * :github:`16761` - nrf52840 usb driver with openthread * :github:`16760` - K_THREAD_STACK_EXTERN() confuses gen_kobject_list.py * :github:`16750` - counter: lack of interrupt when CC=0 * :github:`16749` - IRQ_CONNECT and irq_enable calls in the SiFive UART driver is misconfigured * :github:`16747` - bluetooth: peripheral: RX buffer size issues * :github:`16746` - boards: nrf52840_pca10059: Configure NFC pins as GPIOs by default * :github:`16745` - PTHREAD_MUTEX_DEFINE(): don't store into the _k_mutex section * :github:`16739` - spi: stm32: pinmux: default configuration does not opt for low power consumption * :github:`16734` - Bluetooth: GATT: Writing 1 byte to a CCC access invalid memory * :github:`16733` - soc/stm32: Remove useless package digit for STM32 SoC Kconfig symbols * :github:`16720` - drivers/loapic_timer.c is buggy, needs cleanup * :github:`16716` - soc: stm32: Is the setting of NUM_IRQS in the F3 series wrong? * :github:`16707` - Problem with k_sleep * :github:`16695` - code coverage: kernel/device.c * :github:`16687` - basic disco sample fails * :github:`16678` - LPN establishment of Friendship never completes if there is no response to the initial Friend Poll * :github:`16676` - Settings enhancements * :github:`16672` - nrf: spi: Excess current * :github:`16670` - Memory reports do not work when Nordic proprietary LL is selected * :github:`16661` - Symmetric multiprocessing (SMP) for ARC HS cores * :github:`16639` - eth: pinging frdm k64f eventually leads to unresponsive ethernet device * :github:`16634` - GATT indicate API inconsistent when using characteristic declaration attribute as argument * :github:`16631` - SDK_VERSION * :github:`16624` - Building Grub fails when using gcc9 * :github:`16623` - Building with Openthread fails * :github:`16607` - Building hello_world fails for xtensa: xt-xcc ERROR parsing -Wno-address-of-packed-member: unknown flag * :github:`16606` - Fault in CPU stats * :github:`16604` - Zephyr fails to build with CPU load measurement enabled * :github:`16603` - Bluetooth: Gatt Discovery: BT_GATT_DISCOVER_PRIMARY returns all services while BT_GATT_DISCOVER_SECONDARY returns none * :github:`16602` - Bluetooth: GATT Discovery: Descriptor Discovery by range Seg Fault * :github:`16600` - Bluetooth: Mesh: Proxy SAR timeout is not implemented * :github:`16594` - net: dns: Zephyr is unable to unpack mDNS answers produced by another Zephyr node * :github:`16584` - [Coverity CID :198863]Error handling issues in /subsys/net/lib/sntp/sntp.c * :github:`16583` - [Coverity CID :198864]Parse warnings in /subsys/logging/log_backend_rtt.c * :github:`16582` - [Coverity CID :198865]Null pointer dereferences in /drivers/usb/device/usb_dc_stm32.c * :github:`16581` - [Coverity CID :198866]Null pointer dereferences in /subsys/net/lib/dns/llmnr_responder.c * :github:`16580` - [Coverity CID :198867]Parse warnings in /tests/subsys/fs/nffs_fs_api/common/nffs_test_system_01.c * :github:`16579` - [Coverity CID :198868]Parse warnings in /drivers/watchdog/wdt_qmsi.c * :github:`16578` - [Coverity CID :198869]Parse warnings in /subsys/shell/shell_rtt.c * :github:`16577` - [Coverity CID :198870]Error handling issues in /subsys/net/lib/lwm2m/lwm2m_obj_firmware_pull.c * :github:`16576` - [Coverity CID :198871]Parse warnings in /drivers/i2c/i2c_qmsi_ss.c * :github:`16575` - [Coverity CID :198872]Parse warnings in /tests/subsys/settings/nffs/src/settings_setup_nffs.c * :github:`16574` - [Coverity CID :198873]Incorrect expression in /tests/drivers/uart/uart_async_api/src/test_uart_async.c * :github:`16573` - [Coverity CID :198874]Null pointer dereferences in /drivers/usb/device/usb_dc_stm32.c * :github:`16572` - [Coverity CID :198875]Memory - corruptions in /drivers/flash/flash_simulator.c * :github:`16571` - [Coverity CID :198876]Parse warnings in /tests/subsys/fs/multi-fs/src/test_nffs.h * :github:`16570` - [Coverity CID :198877]Null pointer dereferences in /subsys/net/ip/net_if.c * :github:`16569` - [Coverity CID :198878]Error handling issues in /samples/net/sockets/echo_server/src/tcp.c * :github:`16568` - [Coverity CID :198879]Parse warnings in /tests/subsys/fs/fat_fs_dual_drive/src/test_fat_mount.c * :github:`16567` - [Coverity CID :198880]Possible Control flow issues in /samples/net/lwm2m_client/src/lwm2m-client.c * :github:`16566` - [Coverity CID :198881]Parse warnings in /drivers/serial/uart_qmsi.c * :github:`16565` - [Coverity CID :198882]Parse warnings in /drivers/console/rtt_console.c * :github:`16564` - [Coverity CID :198883]Parse warnings in /drivers/gpio/gpio_qmsi_ss.c * :github:`16563` - [Coverity CID :198884]Parse warnings in /drivers/counter/counter_qmsi_aon.c * :github:`16524` - FXOS8700 is not well supported in twr_ke18f * :github:`16519` - USAGE FAULT occurs when i2c_write is called * :github:`16518` - USB_UART_DTR_WAIT not working on nrf52840_pca10059 * :github:`16508` - tests/subsys/storage/flash_map Instruction bus error on frdmk64 board * :github:`16506` - tests/posix/fs missing ff.h * :github:`16501` - Code Coverage for qemu_x86 is not getting generated due to a build error * :github:`16493` - [Coverity CID :198640]Resource leaks in /tests/net/socket/register/src/main.c * :github:`16492` - [Coverity CID :198644]Incorrect expression in /tests/drivers/uart/uart_async_api/src/test_uart_async.c * :github:`16487` - tests/kernel/timer/timer_api/kernel.timer sporadically (high frequency) fails in CI on qemu-xtensa * :github:`16483` - net: ipv6: udp: Zephyr replies to datagram with illegal checksum 0 * :github:`16478` - Bluetooth: Improper bonded peers handling * :github:`16470` - Superfluous USB suspend after USB configured * :github:`16463` - tests/subsys/settings/fcb_init fails on second run * :github:`16453` - sockets: getaddrinfo: AF_UNSPEC handling was recently broken * :github:`16432` - Weird link error of the console sample! * :github:`16428` - samples/gui/lvgl does not work on PCA10056 * :github:`16426` - Missing included dependencies in many header files * :github:`16419` - Bluetooth: XTAL feature regression * :github:`16418` - drivers: watchdog: sam0: check if timeout is valid * :github:`16417` - issues with can filter mode set * :github:`16416` - sram size for RT1015 and RT1020 needs to be update. * :github:`16415` - Build errors with C++ * :github:`16414` - Backport west build --pristine * :github:`16413` - Missing dependency in cmake * :github:`16412` - on reel_board the consumption increases because TX pin is floating * :github:`16411` - bad regex for west version check in host-tools.cmake * :github:`16389` - ninja flash to intel quark d2000 zephyr * :github:`16387` - STM32wb55 bluetooth samples fail * :github:`16379` - net: ipv6: udp: Zephyr replies with illegal UDP checksum zero * :github:`16375` - net: ipv4: udp: Zephyr does not reply to a valid datagram with checksum zero * :github:`16366` - Build error on QEMU x86 and quark_se_c1000_devboard * :github:`16365` - lwm2m: enable with CONFIG_NET_RAW_MODE * :github:`16363` - Error building x_nucleo_iks01a1 sample on nucleo_wb55rg after activating I2C Bus * :github:`16360` - ARM: Implement configurable MPU-based stack overflow guards * :github:`16354` - net: ipv6: Zephyr does not reply to fragmented packet * :github:`16341` - Bluetooth: GATT Server failed to send Service Change Indication * :github:`16339` - openthread: off-by-one error when calculating ot_flash_offset for settings * :github:`16327` - doc: networking: overview has out of date info for LwM2M * :github:`16326` - USB3CV Chapter 9 Tests failures * :github:`16323` - net: ipv6: tcp: unexpected reply to malformed HBH in TCP/IPv6 SYN * :github:`16318` - net: Network Offloading: Particle Boron * :github:`16316` - ST modules organization * :github:`16313` - LMP Response Timeout / LL Response Timeout (0x22) after ~40s when using LE Secure Connections * :github:`16307` - cannot move location counter backwards error happen * :github:`16303` - mbedtls: config-tls-generic.h: MBEDTLS_PLATFORM_NO_STD_FUNCTIONS seems ungrounded * :github:`16296` - dts generation in correct for 2 registers and no-size * :github:`16289` - Driver: modem ublox-sara-r4 not compiling * :github:`16278` - [Zepyhr v1.14.0] Unable to update FW with mcumgr over UART * :github:`16276` - net: ipv4: Zephyr replies to link-layer broadcast packet * :github:`16275` - setting_init crashes on qemu_x86 when setting BT_SETTINGS * :github:`16273` - Calling k_work_submit can reenable interrupts * :github:`16272` - bluetooth mesh proxy filter * :github:`16268` - Add 32K RAM support for nRF51822 REVC/microbit board * :github:`16257` - net: icmpv4: Zephyr sends echo reply with multicast source address * :github:`16243` - std::vector push_back() not working correctly * :github:`16240` - USB Bluetooth and DFU classes cannot be enabled simultaneously on nRF52840 * :github:`16238` - k_cycle_get_32() API is useless in some Zephyr configurations * :github:`16236` - [docs] Windows installation guide, git part, is installed with non-intended configuration * :github:`16234` - tests/benchmarks/latency_measure can not calculate the real time thread switch for twr_ke18f * :github:`16229` - tests/kernel/common fails at test_atomic on twr_ke18f board * :github:`16227` - Zephyr env: unset var in conditional activation * :github:`16226` - ARM: IsInIsr(): inconsistencies between doc and implementation * :github:`16225` - tests/kernel/msgq/msgq_api twr_ke18f fails with assert * :github:`16224` - tests/subsys/storage/flash_map meet mpu hardfault in twr_ke18f board. * :github:`16216` - tests/kernel/timer/timer_api fails on nrf51_pca10028 board * :github:`16215` - FIFO queue data seems to get overwritten * :github:`16211` - NVS: sector erase at startup (2-sectors configuration) * :github:`16204` - Build STM32 : generate hex file fail * :github:`16191` - boards/arm/{olimexino_stm32, stm32_min_dev}: USB pinmux setup is skipped * :github:`16185` - Compile error using entropy.h in C++ code * :github:`16177` - STM32: Could not compile with CONFIG_PINMUX=n * :github:`16170` - CI fails because warning in LOG_ERR() in drivers/i2s_ll_stm32.c * :github:`16164` - [Coverity CID :198584]Uninitialized variables in /drivers/led/ht16k33.c * :github:`16163` - [Coverity CID :198587]Incorrect expression in /tests/subsys/usb/desc_sections/src/desc_sections.c * :github:`16162` - [Coverity CID :198588]Control flow issues in /drivers/gpio/gpio_cc13xx_cc26xx.c * :github:`16161` - [Coverity CID :198589]Control flow issues in /drivers/i2c/i2c_sam0.c * :github:`16160` - [Coverity CID :198590]Control flow issues in /drivers/i2c/i2c_sam0.c * :github:`16159` - [Coverity CID :198591]Control flow issues in /drivers/sensor/adxl362/adxl362.c * :github:`16158` - LwM2M: Fix incorrect last_block handling in the firmware write callback * :github:`16156` - Remove the LWM2M maximum number of instances limitation * :github:`16155` - drivers: can: wrong value used for filter mode set * :github:`16154` - Fix various issues with handling of floating values within the LWM2M subsystem * :github:`16148` - ARM: Enable building with TRUSTED_EXECUTION_SECURE * :github:`16145` - question: Using OpenThread API in Zephyr application * :github:`16143` - posix: clock_settime calculates the base time incorrectly * :github:`16142` - NET: llmnr responder sends malformed packets * :github:`16141` - posix: CONFIG_POSIX_API and CONFIG_NET_SOCKETS_POSIX_NAMES don't make sense to use together, and conflict when doing so * :github:`16138` - is this right for clock announcing in every CORE? * :github:`16132` - The nRF mesh APP report Invalid Publish Parameters * :github:`16110` - net: arp: request from own hardware but different IP address not dropped * :github:`16107` - Using bt_gatt_read() with 'by_uuid' method returns 3 extra bytes * :github:`16103` - nrf5 802.15.4 driver requires Log subsys to be enabled * :github:`16098` - net: arp: sender hardware address not used by ICMP/TCP/UDP * :github:`16090` - mpu align support for code relocation on non-XIP system * :github:`16089` - Mcux Ethernet driver does not detect carrier anymore (it's alway on) * :github:`16080` - Zephyr UART shell crashes on start if main() is blocked * :github:`16079` - SAM0/SAMR SERIAL subsystem broken? * :github:`16078` - Shell subsystem or SERIAL no longer works on SAM0/SAMR * :github:`16072` - boards/up_squared: k_sleep() too long with local APIC timer * :github:`16054` - Bluetooth sample app 'peripheral' failing to build for nRF52840 * :github:`16052` - Adafruit Trinket M0 Bossac Offset is Wrong * :github:`16046` - modules are being processed too late. * :github:`16042` - NDP should be enhanced with Security, RFC 3971 * :github:`16027` - support for no-flash systems * :github:`16025` - webusb example app not reading data * :github:`16012` - Source IP address for DHCP renewal messages is unset * :github:`16010` - Coverage reporting fails on many tests * :github:`16006` - The ArgonKey board documentation needs to align to the official information * :github:`16002` - the spi base reg address in arc_iot.dtsi has an error * :github:`16001` - ARC iotdk supports MPU and fpu in hardware but not enabled in kconfig * :github:`16000` - We need a CI check for commas in CODEOWNERS * :github:`15998` - CODEOWNERS is broken (Again) * :github:`15997` - Fix compile warning in samples/net/sockets/dumb_http_server * :github:`15996` - tests/kernel/sched/schedule_api/testcase.yaml#kernel.sched.slice_reset fails on nrf52840_pca10056, nrf52_pca10040, nrf51_pca10028 * :github:`15991` - [Coverity CID :198389]Memory - illegal accesses in /subsys/settings/src/settings_runtime.c * :github:`15990` - [Coverity CID :198390]Memory - illegal accesses in /subsys/settings/src/settings_runtime.c * :github:`15989` - [Coverity CID :198391]Memory - illegal accesses in /subsys/settings/src/settings_runtime.c * :github:`15988` - [Coverity CID :198392]Insecure data handling in /tests/net/socket/getaddrinfo/src/main.c * :github:`15987` - [Coverity CID :198393]Error handling issues in /tests/net/socket/socket_helpers.h * :github:`15986` - [Coverity CID :198394]Error handling issues in /tests/net/socket/socket_helpers.h * :github:`15985` - [Coverity CID :198395]Memory - corruptions in /soc/arm/microchip_mec/mec1501/soc.c * :github:`15983` - Kernel tests assume SYS_CLOCK_TICKS_PER_SEC=100 * :github:`15981` - ARM: k_float_disable() as system call * :github:`15975` - Openthread - fault with dual network interfaces * :github:`15971` - Fail to connect sample bluetooth HID with Tizen OS (BT_HCI_ERR_DIFF_TRANS_COLLISION) * :github:`15970` - samples: microbit pong demo * :github:`15964` - ARM: Cortex-M: enhance Sharing Floating-Point Registers Mode * :github:`15961` - bug: west: 'west flash' doesn't use specified hex file * :github:`15941` - Stale 1.3.99 documentation under /latest * :github:`15924` - Bluetooth: PTS: GATT server tests fail after merge of #15524 * :github:`15922` - BLE mesh:The Provisioner APP can't find the micro:bit which is running the mesh sample * :github:`15918` - stm32f7 GPIO Ports F & G Disabled by Default * :github:`15917` - USB disconnect/reconnect * :github:`15916` - [BLE] Mesh example qemu kernel panic * :github:`15911` - Stack size is smaller than it should be * :github:`15909` - stm32f7: DTCM included in sram0 * :github:`15906` - WEST ERROR: extension command build was improperly defined * :github:`15904` - concerns with use of CONFIG_BT_MESH_RPL_STORE_TIMEOUT in examples * :github:`15893` - code coverage is not tested in CI * :github:`15884` - tests/net/socket/getaddrinfo fails on mps2_an385 * :github:`15878` - tests/net/lib/mqtt_publisher/net.mqtt.tls fails to build on sam_e70_xplained * :github:`15877` - all qemu_x86_64 tests hang on Ubuntu 18.04 * :github:`15864` - disk partitioning should not specified in DTS * :github:`15844` - Network management API should support user space * :github:`15842` - cdc_acm: stm32: uart_fifo_fill() can't transmit data out * :github:`15835` - "#if XIP" block in qemu_x86 DTS always evaluates to false * :github:`15831` - qemu_x86 DTS does not reflect actual emulated hardware layout * :github:`15827` - ARM: Update ARM CMSIS to latest version * :github:`15823` - Build failure for spi_loopback on atsamr21_xpro * :github:`15817` - nrf52: HFXO is not turned off as expected * :github:`15814` - [Coverity CID :186196]Unchecked return value in samples/sensor/lsm6dsl/src/main.c * :github:`15794` - mps2_an385 crashes if CONFIG_INIT_STACKS=y and CONFIG_COVERAGE=y * :github:`15789` - Networking documentation missing * :github:`15778` - [Coverity CID :198001]Control flow issues in /subsys/bluetooth/host/mesh/settings.c * :github:`15777` - [Coverity CID :198002]Null pointer dereferences in /subsys/net/l2/ethernet/arp.c * :github:`15776` - [Coverity CID :198003]Error handling issues in /tests/net/net_pkt/src/main.c * :github:`15775` - [Coverity CID :198005]Memory - corruptions in /subsys/bluetooth/shell/gatt.c * :github:`15774` - [Coverity CID :198006]Control flow issues in /subsys/bluetooth/host/settings.c * :github:`15773` - [Coverity CID :198007]Memory - corruptions in /subsys/bluetooth/host/hci_core.c * :github:`15772` - [Coverity CID :198009]Memory - corruptions in /subsys/bluetooth/shell/gatt.c * :github:`15771` - [Coverity CID :198010]Control flow issues in /samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app/src/storage.c * :github:`15770` - [Coverity CID :198011]Incorrect expression in /tests/subsys/usb/desc_sections/src/desc_sections.c * :github:`15769` - [Coverity CID :198012]Memory - corruptions in /drivers/flash/flash_simulator.c * :github:`15768` - [Coverity CID :198013]Control flow issues in /subsys/bluetooth/host/mesh/settings.c * :github:`15767` - [Coverity CID :198014]Memory - corruptions in /drivers/flash/flash_simulator.c * :github:`15766` - [Coverity CID :198016]Security best practices violations in /subsys/settings/src/settings_runtime.c * :github:`15765` - [Coverity CID :198018]Control flow issues in /subsys/bluetooth/host/mesh/settings.c * :github:`15764` - [Coverity CID :198019]Security best practices violations in /subsys/settings/src/settings_runtime.c * :github:`15763` - [Coverity CID :198021]Control flow issues in /drivers/clock_control/clock_stm32_ll_mp1x.c * :github:`15762` - [Coverity CID :198022]Security best practices violations in /subsys/settings/src/settings_runtime.c * :github:`15759` - usb: cdc_acm: uart_line_ctrl_set(dev, LINE_CTRL_DTR, &dtr) should always return 0 if USB port is not opened by host * :github:`15751` - Incorrect flash map * :github:`15749` - [question] errors using custom command in CMakeLists.txt * :github:`15748` - 'ninja flash' does not work for IMXRT1052 target * :github:`15736` - Generalize and improve async context for SPI, ADC, etc. * :github:`15734` - Power management doesn't work with CONFIG_I2C=y on nRF52 * :github:`15733` - Bluetooth: controller: Central Encryption setup overlaps Length Request procedure * :github:`15728` - tests/benchmarks/timing_info: wrong value for context switch duration * :github:`15720` - "z_clock_elapsed" implementation seems to be missing #linking #sched * :github:`15719` - tests/ztests/mock/ : Stuck at test_parameter_tests * :github:`15714` - samples/bluetooth/peripheral: could not connect with disco_l475_iot1 board * :github:`15710` - [question] how about the current consumption on NRF52DK running power_mgr sample? * :github:`15709` - CODEOWNERS ignored in GitHub * :github:`15706` - tunslip6: main: open: No such file or directory * :github:`15698` - bluetooth: bt_conn: No proper ID handling * :github:`15696` - [question] why bt_setting is dependant of printk in menuconfig? * :github:`15679` - Can GPTP support multiple slave nodes * :github:`15678` - Watchdog peripheral api docs aren't generated correctly. * :github:`15675` - DTS question about pinmix/GPIO * :github:`15672` - net: socket send return error(-110) when http request 100 times * :github:`15668` - Support request: Issue with documentation warning * :github:`15664` - Zephyr modules failure report * :github:`15652` - document the mailing list for nightly build results * :github:`15639` - [question] how to get the bd_addr from scan callback as shown on nrf-connect app? * :github:`15637` - Support of device tree gpio-map * :github:`15627` - Application compiled with CONFIG_POSIX_API doesn't have access to POSIX headers * :github:`15625` - target_compile_features in CMakeLists.txt triggers an error * :github:`15622` - NXP RT10XX: Load code to ITCM * :github:`15612` - bt_set_id_addr() to allow public address as argument * :github:`15608` - [question] my board won't boot without debugger attached but no issue using nordic SDK * :github:`15607` - nRF52: 2.4 GHz proprietary RF support * :github:`15606` - trickle.c can't work for multiple triggerings * :github:`15605` - Unaligned memory access by ldrd * :github:`15601` - pwm: nRF default prescalar value is wrong * :github:`15597` - [question] How to include mesh related header files in my own source file * :github:`15596` - net: Zephyr's SNTP API time precision is not adequate * :github:`15594` - net shell "net tcp send" command failed when repeated many times * :github:`15588` - Does zephyr support different time slices for each thread? * :github:`15587` - Zephyr was unable to find the toolchain * :github:`15580` - SAMD21 Adafruit examples no longer run on boards * :github:`15571` - Fix sanitycheck failures for v2m_musca_b1_nonsecure * :github:`15570` - Unbonded peripheral gets 'Tx Buffer Overflow' when erasing bond on master * :github:`15565` - undefined references to 'sys_rand32_get' * :github:`15558` - support for power-of-two MPUs on non-XIP systems * :github:`15551` - CMake enables -fmacro-prefix-map on GCC 7 * :github:`15549` - [FCB question] Is it true that fcb storage won't overwrite old records which limits the max num? * :github:`15546` - tests/kernel/mem_protect/protection/: Reached unreachable code * :github:`15526` - Unhandled identity in bt_conn_create_slave_le * :github:`15522` - Extra padding in IPv4 link local ARP packets * :github:`15520` - tests/ztest/mock: test_multi_value_test: Unused mocked return value * :github:`15516` - Implementation of CONFIG_MAX_PTHREAD_COUNT * :github:`15513` - nRF timer unnecessary configuration? * :github:`15508` - No space to store CCC cfg * :github:`15507` - NRF52840: usb composite MSC + HID (with CONFIG_ENABLE_HID_INT_OUT_EP) * :github:`15504` - Can I use one custom random static bd_addr before provision? * :github:`15501` - smp_svr build issue * :github:`15499` - gpio_intel_apl: gpio_pin_read() pin value doesn't match documentation * :github:`15497` - USB DFU: STM32: usb dfu mode doesn't work * :github:`15495` - tests/drivers/spi/spi_loopback/peripheral.spi fails to build on several boards * :github:`15486` - usb composite MSC + HID (with CONFIG_ENABLE_HID_INT_OUT_EP) * :github:`15483` - add mpu and fpu support for arc iotdk * :github:`15481` - object_access in common-rom.ld missed GROUP_LINK_IN(ROMABLE_REGION) * :github:`15477` - Zephyr network stack will up the Ethernet interface after its driver initialized (regardless of actual status) * :github:`15472` - DNS resolver sample sends only one A query * :github:`15465` - Fix build failures for test_newlib & tests/lib/mem_alloc/libraries.libc.newlib w/ARM gcc * :github:`15451` - doc: settings Misleading examples * :github:`15448` - help to use zephyr-ninja flash of st_nucleo_l476rg * :github:`15447` - sanitycheck --coverage -p qemu_x86: Fatal failures with tests/kernel/pipe/pipe/kernel.pipe * :github:`15446` - ssanitycheck --coverage -p mps2_an385: Some remaing test cases that are still failing * :github:`15444` - Error initiating sdhc disk * :github:`15443` - usb_dc_stm32: Missing semaphore initialization and missing pin remapping configuration * :github:`15419` - reset and halt function * :github:`15411` - tests/kernel/critical: Continuous reboot at test_critical * :github:`15408` - [Coverity CID :197596]Memory - corruptions in /tests/net/lib/mqtt_packet/src/mqtt_packet.c * :github:`15391` - [Coverity CID :197613]Possible Control flow issues in /subsys/net/ip/net_core.c * :github:`15374` - PR 15230 introduces test failure for particle_argon * :github:`15373` - IPv4 link local packets are not sent with ARP ethernet type * :github:`15355` - Driver for U-Blox SARA modem (used by Particle Boron) * :github:`15354` - counter: stm32: Issue with LSE clock source selection * :github:`15339` - RISC-V: RV32M1: Load access fault when accessing GPIO port E * :github:`15334` - Unable to reset nRF52840 from nRF9160 on pca10090 DK * :github:`15331` - CONFIG_CODE_DATA_RELOCATION does not work with Cache enabled MCUs. * :github:`15316` - printf causing usage fault * :github:`15315` - doc: simplify cmake examples thanks to cmake's new -B option * :github:`15305` - add QEMU target for armv8-M with MPU support * :github:`15282` - Enhance networking tests/net/all tests * :github:`15279` - mempool alignment might cause a memory block allocated twice * :github:`15272` - sanitycheck reports build errors as "handler crash" * :github:`15246` - doc: confusion about dtc version * :github:`15232` - tests/bluetooth/tester fails build if CONFIG_TEST_USERSPACE=n * :github:`15193` - tests/net/socket/getaddrinfo tests too little * :github:`15180` - testing flash driver clients in CI * :github:`15159` - undefined reference to 'bsearch' #stdlib * :github:`15156` - GH labels reorg * :github:`15144` - West: how to set up for external modules * :github:`15139` - implement sys_sem that can reside in user memory * :github:`15133` - Is the level2 interrupt supported for ARM cortex-M0P core? * :github:`15119` - GPIO callback not disabled from an interrupt * :github:`15116` - nrfx_twim: (nRF52) driver unable to perform i2c_burst_write() correctly * :github:`15115` - ARM: Cortex-M: enhance non-sharing floating point services * :github:`15074` - ARM: Fix/Enhance Floating Point for ARM Cortex-M architecture * :github:`15046` - Native_posix: command line handling: Hint users why an option does not exist * :github:`15003` - init_iface in net_if.c should check api->init * :github:`14997` - Convert samples/sensor/bme280/src/main.c to use printk instead of printf * :github:`14970` - samples/drivers/watchdog: Not showing "Waiting for reset..." for nrf boards * :github:`14918` - olimexino stm32 CAN errors * :github:`14904` - Sanitycheck report not clear if built or ran a test * :github:`14828` - ARM: MPU-based HW thread stack protection not working properly when building with CONFIG_FLOAT * :github:`14826` - USB reset in suspended state * :github:`14791` - Bluetooth: GATT Notification callbacks should have conn as argument * :github:`14769` - kernel/userspace.c: Improve code coverage to 100% * :github:`14744` - ARM: Core Stack Improvements/Bug fixes for 2.0 release * :github:`14736` - kernel/include/kswap.h: Improve code coverage to 100% * :github:`14734` - kernel/include/kernel_structs.h: Improve code coverage to 100% * :github:`14733` - kernel/work_q.c: Improve code coverage to 100% * :github:`14731` - kernel/userspace_handler.c: Improve code coverage to 100% * :github:`14730` - kernel/userspace.c: Improve code coverage to 100% * :github:`14729` - kernel/timer.c: Improve code coverage to 100% * :github:`14728` - kernel/timeout.c: Improve code coverage to 100% * :github:`14727` - kernel/thread_abort.c: Improve code coverage to 100% * :github:`14726` - kernel/thread.c: Improve code coverage to 100% * :github:`14725` - kernel/system_work_q.c: Improve code coverage to 100% * :github:`14724` - kernel/stack.c: Improve code coverage to 100% * :github:`14723` - kernel/sem.c: Improve code coverage to 100% * :github:`14722` - kernel/sched.c: Improve code coverage to 100% * :github:`14721` - kernel/queue.c: Improve code coverage to 100% * :github:`14720` - kernel/poll.c: Improve code coverage to 100% * :github:`14719` - kernel/pipes.c: Improve code coverage to 100% * :github:`14718` - kernel/mutex.c: Improve code coverage to 100% * :github:`14717` - kernel/msg_q.c: Improve code coverage to 100% * :github:`14716` - kernel/mempool.c: Improve code coverage to 100% * :github:`14715` - kernel/mem_slab.c: Improve code coverage to 100% * :github:`14713` - kernel/mem_domain.c: Improve code coverage to 100% * :github:`14712` - kernel/mailbox.c: Improve coverage to 100% * :github:`14711` - kernel/idle.c: Improve code coverage to 100% * :github:`14710` - kernel/errno.c: Improve code coverage to 100% * :github:`14709` - kernel/device.c: Improve code coverage to 100% * :github:`14708` - kernel/include/ksched.h: Improve code coverage to 100% * :github:`14707` - kernel/include/kernel_offsets.h: Improve code coverage to 100% * :github:`14706` - kernel/include/kernel_internal.h: Imrpove code coverage to 100% * :github:`14705` - kernel/smp.c: Improve code coverage to 100% * :github:`14704` - kernel/int_latency_bench.c: Improve code coverage to 100% * :github:`14703` - kernel/compiler_stack_protect.c: Improve code coverage to 100% * :github:`14702` - kernel/atomic_c.c : Improve code coverage to 100% * :github:`14675` - Bluetooth: Controller privacy support (platforms with HW acceleration) * :github:`14652` - Gitlint is more strict than checkpatch.pl * :github:`14633` - undefined reference to 'mbedtls_debug_set_threshold' when MBEDTLS_DEBUG is enabled * :github:`14605` - mimxrt1060_evk cpp_synchronization meets Hardware exception * :github:`14604` - BLE disconnection caused by channel map request or connection parameter update request * :github:`14599` - Can you add a ADC sample? * :github:`14588` - static IP support on cc3220sf_launchxl * :github:`14547` - Kconfig shell prompt configuration * :github:`14517` - LPCXpresso55S69 board support * :github:`14493` - implement Zephyr futexes * :github:`14467` - New HTTP API implementation * :github:`14459` - usb: samples: mass: doesn't build with FLASH overlay * :github:`14292` - Typo "QPSI" in QSPI macros in some stm32 drivers * :github:`14283` - tests/drivers/watchdog/wdt_basic_api fails on test_wdt_callback_1() for Ardruino and quark_se_c1000_ss_devboard:arc * :github:`14123` - Particle boards need a board initialization module for antenna configuration * :github:`14082` - Update Segger host library to V2.52f * :github:`14037` - Generic device driver object type * :github:`14034` - Support for PPP protocol * :github:`13963` - up_squared: evaluate removal of SBL-related special configurations * :github:`13935` - tests/crypto/rand32/crypto.rand32.random_hw_xoroshiro: Usage fault "Fatal fault in ISR! Spinning..." * :github:`13897` - CONFIG_LOG_IMMEDIATE leads to unobvious faults in unrelated rotines due to stack overflow * :github:`13817` - tests/ztest/test/mock fails to complete on nios2 * :github:`13799` - usb cdc acm fails when writing big chunks of data on stm32 * :github:`13766` - mimxrt1060_evk tests/kernel/fatal meet many unwanted exceptions * :github:`13749` - Can CONFIG_SOC_WATCH-related code be removed? * :github:`13610` - kernel: Non-deterministic and very high ISR latencies * :github:`13602` - How to get the port number for an ephemeral (randomly assigned) port * :github:`13574` - Missing documentation for fcb and nffs * :github:`13560` - STM32 USB: netusb: kernel crash when testing example echo_server with nucleo_f412zg (ECM on Windows) * :github:`13444` - Build failure when including both socket.h and posix/time.h * :github:`13441` - optimize x86 userspace page table memory usage * :github:`13347` - tests/drivers/watchdog/wdt_basic_api fails on test_wdt_callback_1() for Quark SE / arc * :github:`13316` - Notification enabled before connection * :github:`13288` - Disable JTAG debug port for free use GPIO PA15, PB3, PB4 on STM32F1 series * :github:`13197` - LwM2M: support Connectivity Monitoring object (object id 4) * :github:`13148` - Build on nucleo_stm32f429zi * :github:`13097` - openthread default configuration * :github:`13075` - Review memory protection Kconfig policies for consistency and sanity * :github:`13065` - CONFIG_BT leads Fatal fault in ISR on esp32 * :github:`13003` - context switch in x86 memory domains needs optimization * :github:`12942` - openthread: sleepy end device not supported by zephyr router * :github:`12825` - SystemView Feature Not working * :github:`12728` - docs: Hard to find guidelines for ext/ maintenance * :github:`12681` - BLE Split Link Layer * :github:`12633` - tests/boards/altera_max10/i2c_master failed with "failed to read HPD control" on altera_max10 * :github:`12602` - STM32F415RG Support * :github:`12553` - List of tests that keep failing sporadically * :github:`12542` - nrf timers unstable with ticks faster than 100 Hz * :github:`12478` - tests/drivers/ipm/peripheral.mailbox failing sporadically on qemu_x86_64 (timeout) * :github:`12261` - i2c_ll_stm32_v1 driver gets stuck * :github:`12257` - GNU Arm Embedded Toolchain 8-2018-q4-major can't produce hex files on Windows * :github:`12245` - LWM2M registration timeout * :github:`12228` - How to build images for client or server in bluetooth mesh examples? * :github:`12160` - settings: NVS back-end * :github:`12129` - Include: Clean up header file namespace * :github:`12119` - 64bit architecture support * :github:`12044` - [Question] [Blutooth Mesh] How proxy client create the proxy PDU * :github:`12039` - clock_control: API should allow callback to be specified * :github:`11993` - drivers: Supporting driver-specific extensions to existing generic APIs * :github:`11922` - ADC generic driver missing features: calibration, reference voltage value * :github:`11918` - Dynamic pin configuration * :github:`11740` - LL_ASSERT in event_common_prepare in Zephyr v1.13 * :github:`11712` - Add support for newlib-nano * :github:`11681` - Mesh Friend does not reply within ReceiveWindow * :github:`11626` - k_busy_wait exits early on Nordic chips * :github:`11617` - net: ipv4: udp: broadcast delivery not supported * :github:`11535` - serial: uart_irq_tx_ready() needs better documentation or correction of the test * :github:`11455` - cdc_acm uart_fifo_fill sample app doesn't comply with the documentation * :github:`11107` - clock_control: API should support asynchronous and synchronous variants of turning on clocks * :github:`10965` - wncm14a2a modem should be moved to a shield configuration * :github:`10942` - Declaring an API Stable * :github:`10935` - Support all UARTs on ESP32 WROOM module * :github:`10915` - ESP 32 failed to boot while running crypto/rand32 tests * :github:`10896` - Add STM32 ADC driver * :github:`10739` - Cannot flash to STM32 Nucleo F446RE with SEGGER JLink * :github:`10664` - FOTA: nRF52: integration of samples/bluetooth/mesh & smp_srv * :github:`10657` - tests/net/ieee802154/crypto does not work as expected * :github:`10603` - Hard to find "todo" * :github:`10463` - can: stm32: Update to new API * :github:`10450` - usb/stm32: use dts extracted information to populate clock settings * :github:`10420` - gcc: "Exec format error" - WSL in Windows 10 1803 * :github:`10150` - Getting LLVM work on ARM * :github:`9954` - samples/hello_world build failed on Windows/MSYS * :github:`9898` - 1.14 Release Checklist * :github:`9762` - Bluetooth mesh reliability issue? * :github:`9570` - Network stack cleanup: deep TCP cleanup * :github:`9509` - Unable to upload firmware over serial with mcumgr * :github:`9333` - Support for STM32 L1-series * :github:`9247` - Get ST Disco and Eval boards compliant with default configuration guidelines * :github:`9070` - bluetooth BR The sample is incomplete * :github:`9047` - Interrupt APIs. * :github:`8978` - soc: Intel S1000: add low power memory management support * :github:`8851` - Allow creation of Zephyr libraries outside of Zephyr tree * :github:`8734` - USB: DFU timeout on nRF52840 due to long flash erase * :github:`8728` - Network stack cleanup: Net IF * :github:`8726` - Network stack cleanup: TCP * :github:`8725` - Network stack cleanup: Net Context * :github:`8723` - Network stack cleanup * :github:`8722` - Network stack cleanup: connection * :github:`8464` - sdk_version file missing * :github:`8419` - Bluetooth: tester: LPN Poll issue * :github:`8404` - Bluetooth: controller: Reuse get_entropy_isr API * :github:`8275` - when zephyr can support popular IDE develop? * :github:`8125` - About BMI160 reading issue. * :github:`8081` - Bluetooth: Deprecate TinyCrypt and use mbedTLS * :github:`8062` - [Coverity CID :186196] Error handling issues in /samples/sensor/mcp9808/src/main.c * :github:`7908` - tests/boards/altera_max10/qspi fails on max10 * :github:`7589` - Migrate Websocket to BSD sockets * :github:`7585` - Migrate HTTP to socket API * :github:`7503` - LwM2M client: No registration retry after error? * :github:`7462` - Convert mcr20a to be a shield when that functionality is merged * :github:`7403` - RAM flash driver emulator * :github:`7316` - native_posix supersedes ztest mocking * :github:`6906` - QM (Quality Managed) level qualification * :github:`6823` - Optimize rendering of Kconfig documentation * :github:`6817` - Question: Is supported for stack sharing among tasks in Zephyr? Or any plan? * :github:`6816` - Question: Is KProbes supported in Zephyr? Or any plan? * :github:`6773` - Publish doxygen-generated API pages * :github:`6770` - Multiple Git Repositories * :github:`6636` - Enable hardware flow control in mcux uart shim driver * :github:`6605` - Question: Does WAMP protocol has any usecase for Zephyr * :github:`6545` - ARM Cortex R Architecture support * :github:`6370` - I can't find adc name which is f429zi board * :github:`6183` - sensor: Handling sensors with long measurement times * :github:`6086` - Ideas/requirements for improved TLS support in Zephyr * :github:`6039` - Implement interrupt driven USART on LPC54114 * :github:`5579` - Address untested options in kernel * :github:`5529` - Explore Little File System (littlefs) support * :github:`5460` - scripts: extract_dts_includes: check yaml dts binding property "category: " * :github:`5457` - Add SDHC card support * :github:`5423` - [nRF] on-target tests accidentally run twice * :github:`5365` - Revisit DHCPv4 test, convert to ztest * :github:`4628` - Sample app enabling sensors on disco_l475_iot1 board * :github:`4506` - rework GPIO flags * :github:`4505` - sanitycheck should distinguish compile errors from link errors * :github:`4375` - Provide a script to find files not owned per the CODEOWNERS file * :github:`4178` - Openweave Support * :github:`3936` - BT: bt_conn_create_le(): No way to find out error cause * :github:`3930` - Need a CPU frequency driver for ESP-32 * :github:`3928` - [TIMER] k_timer_start should take 0 value for duration parameter * :github:`3846` - to use {k_wakeup} to cancel the delayed startup of one thread * :github:`3805` - [test] test scheduling of threads along with networking conditions * :github:`3767` - reconsider k_mem_pool APIs * :github:`3759` - reconsider k_mbox APIs * :github:`3754` - Support static BT MAC address * :github:`3749` - ESP32: Deep Sleep * :github:`3722` - Enable Flash Cache for ESP32 * :github:`3710` - 802.15.4 Soft MAC 2015 version support * :github:`3678` - Implement the Read Static Addresses Command * :github:`3673` - reconsider k_queue APIs * :github:`3651` - add tickless idle and kernel support to RISCV32 pulpino * :github:`3648` - Ability to unpair devices * :github:`3640` - BLE central scan ignores changes in payload * :github:`3547` - IP stack: Ideas for optimizations * :github:`3500` - ESP8266 Architecture Configuration * :github:`3499` - evaluate Emul8 as a replacement for QEMU in sanitycheck * :github:`3442` - TCP connection locally isn't possible * :github:`3426` - Only supports classic Bluetooth compilation options * :github:`3418` - Bluetooth True Wireless Stereo * :github:`3417` - BT Phonebook Access Profles * :github:`3399` - Texas Instruments CC2538 Support * :github:`3396` - LLDP: Implement local MIB support with advertisement of mandatory TLVs * :github:`3295` - Advanced Power Management * :github:`3286` - Native Zephyr IP Stack Advanced Features * :github:`3155` - xtensa: fix tests/kernel/mem_protect/stackprot * :github:`3040` - Add support for the Arduino Ethernet Shield V2 * :github:`2994` - The build system crashes when GCCARMEMB_TOOLCHAIN_PATH has a space in it * :github:`2984` - frdm_k64f bus exception bug due to peculiar RAM configuration * :github:`2933` - Add zephyr support to openocd upstream * :github:`2900` - Support for the BBC micro:bit Bluetooth Profile * :github:`2856` - Customer: Floating Point samples * :github:`2780` - Set the _Swap() return value on ARC the same way it is now done on ARM ? * :github:`2766` - BMI160 Oversampling Configuration * :github:`2682` - Add support for UART A1 for TI CC3200 SoC * :github:`2623` - nRF52 UART behaviour sensitive to timing of baud rate initialization. * :github:`2611` - SDP client * :github:`2587` - Support for BR/EDR SSP out-of-band pairing * :github:`2586` - Support for LE SC out-of-band pairing * :github:`2401` - 802.15.4 - LLDN frame support * :github:`2400` - 802.15.4 - Multipurpose frame support * :github:`2399` - 802.15.4 - TSCH Radio protocol support * :github:`2398` - 802.15.4 - Update existing Management commands * :github:`2397` - 802.15.4 - IE list support * :github:`2396` - 802.15.4 - Management service: FFD level support * :github:`2333` - Get IPv6 Ready approval * :github:`2049` - Enable ARM M4F FPU lazy stacking * :github:`2046` - Add a driver to support timer functions using the PWM H/W periphral timers * :github:`1933` - nios2: implement nested interrupts * :github:`1860` - Add support for getting OOB data * :github:`1843` - nios2: enable interrupt driven serial console for JTAG UART * :github:`1766` - nios2: implement asm atomic operations * :github:`1392` - No module named 'elftools' * :github:`335` - images for the wiki ```	/content/code_sandbox/doc/releases/release-notes-2.0.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	28,857
```restructuredtext :orphan: .. _zephyr_2.5: Zephyr 2.5.0 ############# We are pleased to announce the release of Zephyr RTOS version 2.5.0. Major enhancements with this release include: * Introduced support for the SPARC processor architecture and the LEON processor implementation. * Added Thread Local Storage (TLS) support * Added support for per thread runtime statistics * Added support for building with LLVM on X86 * Added new synchronization mechanisms using Condition Variables * Add support for demand paging, initial support on X86. The following sections provide detailed lists of changes by component. Security Vulnerability Related ****************************** The following CVEs are addressed by this release: * CVE-2021-3323: Under embargo until 2021-04-14 * CVE-2021-3321: Under embargo until 2021-04-14 * CVE-2021-3320: Under embargo until 2021-04-14 More detailed information can be found in: path_to_url Known issues ********** You can check all currently known issues by listing them using the GitHub interface and listing all issues with the `bug label <path_to_url`_. API Changes ********* * Removed SETTINGS_USE_BASE64 support as its been deprecated for more than two releases. * The :c:func:`lwm2m_rd_client_start` function now accepts an additional ``flags`` parameter, which allows to configure current LwM2M client session, for instance enable bootstrap procedure in the current session. * LwM2M execute now supports arguments. The execute callback :c:type:`lwm2m_engine_execute_cb_t` is extended with an ``args`` parameter which points to the CoAP payload that comprises the arguments, and an ``args_len`` parameter to indicate the length of the ``args`` data. * Changed vcnl4040 dts binding default for property 'proximity-trigger'. Changed the default to match the HW POR state for this property. * The :c:func:`clock_control_async_on` function will now take ``callback`` and ``user_data`` as arguments instead of structure which contained list node, callback and user data. * The :c:func:`mqtt_keepalive_time_left` function now returns -1 if keep alive messages are disabled by setting ``CONFIG_MQTT_KEEPALIVE`` to 0. * The ``CONFIG_LEGACY_TIMEOUT_API`` mode has been removed. All kernel timeout usage must use the new-style k_timeout_t type and not the legacy/deprecated millisecond counts. * The :c:func:`coap_pending_init` function now accepts an additional ``retries`` parameter, allowing to specify the maximum retransmission count of the confirmable message. * The ``CONFIG_BT_CTLR_CODED_PHY`` is now disabled by default for builds combining both Bluetooth host and controller. * The :c:func:`coap_packet_append_payload` function will now take a pointer to a constant buffer as the ``payload`` argument instead of a pointer to a writable buffer. * The :c:func:`coap_packet_init` function will now take a pointer to a constant buffer as the ``token`` argument instead of a pointer to a writable buffer. * A new :ref:`regulator_api` API has been added to support controlling power sources. Regulators can also be associated with devicetree nodes, allowing drivers to ensure the device they access has been powered up. For simple GPIO-only regulators a devicetree property ``supply-gpios`` is defined as a standard way to identify the control signal in nodes that support power control. * :c:type:`fs_tile_t` objects must now be initialized by calling :c:func:`fs_file_t_init` before their first use. * :c:type:`fs_dir_t` objects must now be initialized by calling :c:func:`fs_dir_t_init` before their first use. Deprecated in this release ========================== * Nordic nRF5340 PDK board deprecated and planned to be removed in 2.6.0. * ARM Musca-A board and SoC support deprecated and planned to be removed in 2.6.0. * DEVICE_INIT was deprecated in favor of utilizing DEVICE_DEFINE directly. * DEVICE_AND_API_INIT was deprecated in favor of DEVICE_DT_INST_DEFINE and DEVICE_DEFINE. * Bluetooth * Deprecated the :c:func:`bt_set_id_addr` function, use :c:func:`bt_id_create` before calling :c:func:`bt_enable` instead. When ``CONFIG_PRIVACY`` is enabled a valid IRK has to be supplied by the application for this case. Removed APIs in this release ============================ * Bluetooth * The deprecated BT_LE_SCAN_FILTER_DUPLICATE define has been removed, use BT_LE_SCAN_OPT_FILTER_DUPLICATE instead. * The deprecated BT_LE_SCAN_FILTER_WHITELIST define has been removed, use BT_LE_SCAN_OPT_FILTER_WHITELIST instead. * The deprecated bt_le_scan_param::filter_dup argument has been removed, use bt_le_scan_param::options instead. * The deprecated bt_conn_create_le() function has been removed, use bt_conn_le_create() instead. * The deprecated bt_conn_create_auto_le() function has been removed, use bt_conn_le_create_auto() instead. * The deprecated bt_conn_create_slave_le() function has been removed, use bt_le_adv_start() instead with bt_le_adv_param::peer set to the remote peers address. * The deprecated BT_LE_ADV_* macros have been removed, use the BT_GAP_ADV_* enums instead. * The deprecated bt_conn_security function has been removed, use bt_conn_set_security instead. * The deprecated BT_SECURITY_* defines NONE, LOW, MEDIUM, HIGH, FIPS have been removed, use the L0, L1, L2, L3, L4 defines instead. * The deprecated BT_HCI_ERR_AUTHENTICATION_FAIL define has been removed, use BT_HCI_ERR_AUTH_FAIL instead. * Kernel * The deprecated k_mem_pool API has been removed entirely (for the past release it was backed by a k_heap, but maintained a compatible API). Now all instantiated heaps must be sys_heap/k_heaps. Note that the new-style heap is a general purpose allocator and does not make the same promises about block alignment/splitting. Applications with such requirements should look at porting their logic, or perhaps at the k_mem_slab utility. Stable API changes in this release ================================== Kernel ****** * Added support for per thread runtime statistics * Added new synchronization mechanisms using Condition Variables * Thread Local Storage (TLS) * Introduced thread local storage support for the following architectures: * ARC * Arm Cortex-M * Arm Cortex-R * AArch64 * RISC-V * Sparc * x86 and x86_64 * Xtensa * This allows variables declared with ``__thread`` keyword to be allocated on a per-thread basis, and every thread has its own copy of these variables. * Enable via :kconfig:option:`CONFIG_THREAD_LOCAL_STORAGE`. * ``errno`` can be stored inside TLS if :kconfig:option:`CONFIG_ERRNO_IN_TLS` is enabled (together with :kconfig:option:`CONFIG_ERRNO`). This allow user threads to access the value of ``errno`` without making a system call. * Memory Management * Added page frame management for physical memory to keep track of the status of each page frame. * Added :c:func:`k_mem_map` which allows applications to increase the data space available via anonymous memory mappings. * Added :c:func:`k_mem_free_get` which returns the amount of physical anonymous memory remaining. * Paging structure must now be pre-allocated so that there is no need to do memory allocations when mapping memory. Because of this, :c:func:`arch_mem_map` may no longer fail. * Demand Paging * Introduced the framework for demand paging and infrastructure for custom eviction algorithms and implementation of backing stores. * Currently the whole kernel is pinned and remaining physical memory can be used for paging. Architectures ************* * ARC * Fixed execution on ARC HS with one interrupt bank and fast interrupts (FIRQ) enabled * Hardened SMP support * Improved mdb west runner to support simulation on SMP nSIM-based configurations * Improved mdb west runner to support nSIM-based configurations execution on real HW (FPGA-based) * Added documentation page with Zephyr support status on ARC processor * Added coverage support for nSIM-based configurations * Switched to upstream OpenOCD for ARC * Various minor fixes/improvements for ARC MWDT toolchain infrastructure * ARM * AARCH32 * Introduced the functionality for chain-loadable Zephyr firmware images to force the initialization of internal architecture state during early system boot (Cortex-M). * Changed the default Floating Point Services mode to Shared FP registers mode. * Enhanced Cortex-M Shared FP register mode by implementing dynamic lazy FP register stacking in threads. * Added preliminary support for Cortex-R7 variant. * Fixed inline assembly code in Cortex-M system calls. * Enhanced and fixed Cortex-M TCS support. * Enabled interrupts before switching to main in single-thread Cortex-M builds (CONFIG_MULTITHREADING=n). * Fixed vector table relocation in non-XIP Cortex-M builds. * Fixed exception exit routine for fatal error exceptions in Cortex-R. * Fixed interrupt nesting in ARMv7-R architecture. * AARCH64 * Fixed registers printing on error and beautified crash dump output * Removed CONFIG_SWITCH_TO_EL1 symbol. By default the execution now drops to EL1 at boot * Deprecated booting from EL2 * Improved assembly code and errors catching in EL3 and EL1 during the start routine * Enabled support for EL0 in the page tables * Fixed vector table alignment * Introduced support to boot Zephyr in NS mode * Fixed alignment fault in z_bss_zero * Added PSCI driver * Added ability to generate image header * Improved MMU code and driver * RISC-V * Added support for PMP (Physical Memory Protection). Integrate PMP in Zephyr allow to support userspace (with shared memory) and stack guard features. * SPARC * Added support for the SPARC architecture, compatible with the SPARC V8 specification and the SPARC ABI. * FPU is supported in both shared and unshared FP register mode. * x86 * Enabled soft float support for Zephyr SDK * ``CONFIG_X86_MMU_PAGE_POOL_PAGES`` is removed as paging structure must now be pre-allocated. * Mapping of physical memory has changed: * This allows a smaller virtual address space thus requiring a smaller paging structure. * Only the kernel image is mapped when :kconfig:option:`CONFIG_ACPI` is not enabled. * When :kconfig:option:`CONFIG_ACPI` is enabled, the previous behavior to map all physical memory is retained as platforms with ACPI are usually not memory constrained and can accommodate bigger paging structure. * Page fault handler has been extended to support demand paging. Boards & SoC Support ******************** * Added support for these SoC series: * Cypress PSoC-63 * Intel Elkhart Lake * Made these changes in other SoC series: * Changes for ARC boards: * Added icount support for ARC QEMU boards * Added MWDT compiler options for HSDK board * Added missing taps into JTAG chain for the dual-core configuration of the HSDK board * Added support for these ARM boards: * Cypress CY8CKIT_062_BLE board * Added support for these x86 boards: * Elkhart Lake CRB board * ACRN configuration on Elkhart Lake CRB board * Slim Bootloader configuration on Elkhart Lake CRB board * Added support for these SPARC boards: * GR716-MINI LEON3FT microcontroller development board * Generic LEON3 board configuration for GRLIB FPGA reference designs * SPARC QEMU for emulating LEON3 processors and running kernel tests * Added support for these NXP boards: * LPCXpresso55S28 * MIMXRT1024-EVK * Added support for these STM32 boards and SoCs : * Cortex-M Trace Reference Board V1.2 (SEGGER TRB STM32F407) * MikroE Clicker 2 for STM32 * STM32F103RCT6 Mini * ST Nucleo F303K8 * ST Nucleo F410RB * ST Nucleo H723ZG * ST Nucleo L011K4 * ST Nucleo L031K6 * ST Nucleo L433RC-P * ST STM32L562E-DK Discovery * STM32F105xx and STM32F103xG SoC variants * STM32G070xx SoC variants * STM32G474xB/C SoC variants * STM32L071xx SoC variants * STM32L151xC and STM32L152xC SoC variants * Made these global changes in STM32 boards and SoC series: * Pin control configuration is now done through devicetree and existing macros to configure pins in pinmux.c files are tagged as deprecated. The new pin settings are provided thanks to .dtsi files distributed in hal_stm32 module. * Generic LL headers, also distributed in hal_stm32 module, are now available to abstract series references in drivers. * Hardware stack protection is now default on all boards with enabled MPU (SRAM > 64K ), excluding F0/G0/L0 series. * West flash STM32CubeProgrammer runner was added as a new option for STM32 boards flashing (to be installed separately). * Made these changes in other boards: * CY8CKIT_062_WIFI_BT_M0: was renamed to CY8CKIT_062_WIFI_BT. * CY8CKIT_062_WIFI_BT_M4: was moved into CY8CKIT_062_WIFI_BT. * CY8CKIT_062_WIFI_BT: Now M0+/M4 are at same common board. * nRF5340 DK: Selected TF-M as the default Secure Processing Element (SPE) when building Zephyr for the non-secure domain. * SAM4E_XPRO: Added support to SAM-BA ROM bootloader. * SAM4S_XPLAINED: Added support to SAM-BA ROM bootloader. * Extended LPCXpresso55S69 to support dual-core. * Enhanced MIMXRT1064-EVK to support QSPI flash storage and LittleFS. * Updated MIMXRT685-EVK to increase the core clock frequency. * Updated NXP i.MX RT, Kinetis, and LPC boards to enable hardware stack protection by default. * Fixed Segger RTT and SystemView support on NXP i.MX RT boards. * Demand paging is turned on by default for ``qemu_x86_tiny``. * Updated zefi.py to use cross-compiler while building Zephyr. * Enabled code coverage report for ``qemu_x86_64``. * Removed support for legacy APIC timer driver. * Added common memory linker for x86 SoCs. * Enabled configuration to reserve the first megabyte in x86 SoCs. * Added support for these following shields: * Inventek es-WIFI shield * Sharp memory display generic shield Drivers and Sensors ******************* * ADC * Added support for ADC on STM32G0 Series. * Introduced the ``adc_sequence_options::user_data`` field. * CAN * We reworked the configuration API. A user can now specify the timing manually (define prop segment, phase segment1, phase segment2, and prescaler) or use a newly introduced algorithm to calculate optimal timing values from a bitrate and sample point. The bitrate and sample point can be specified in the devicetree too. It is possible to change the timing values at runtime now. * We reworked the zcan_frame struct due to undefined behavior. The std_id (11-bit) and ext_id (29-bit) are merged to a single id field (29-bit). The union of both IDs was removed. * We made the CANbus API CAN-FD compatible. The zcan_frame data-field can have a size of >8 bytes now. A flag was introduced to mark a zcan_frame as CAN-FD frame. A flag was introduced that enables a bitrate switch in CAN-FD frames. The configuration API supports an additional timing parameter for the CAN-FD data-phase. * drivers are converted to use the new DEVICE_DT_* macros. * Clock Control * Added NXP LPC driver. * DAC * STM32: Enabled support for G0 and H7 series. * Added TI DACx3608 driver. * DMA * kmalloc was removed from STM32 DMAMUX driver initialization. * EEPROM * Marked the EEPROM API as stable. * Added support for AT24Cxx devices. * Ethernet * Added support for Distributed Switch Architecture (DSA) devices. Currently only ip_k66f board supports DSA. * Added support for w5500 Ethernet controller. * Reworked the NXP MCUX driver to use DT_INST_FOREACH. * Flash * CONFIG_NORDIC_QSPI_NOR_QE_BIT has been removed. The quad-enable-requirements devicetree property should be used instead. * MPU_ALLOW_FLASH_WRITE is now default on STM32 boards when MPU is enabled. * Add driver for STM32H7 and STM32L1 SoC series. * Add QSPI NOR Flash controller support for STM32 family. * Added NXP LPC legacy flash driver. * Added NXP FlexSPI flash driver for i.MX RT SoCs. * Added support for nRF53 Series SoCs in the nRF QSPI NOR flash driver (nrf_qspi_nor). * GPIO * Added Cypress PSoC-6 driver. * Added Atmel SAM4L driver. * Hardware Info * Added Cypress PSoC-6 driver. * I2C * Added driver support for lmx6x, it8xxx2, and npcx7 platforms. * Added Atmel SAM4L TWIM driver. * Added I2C slave support in the microchip i2c driver. * Reversed 2.4 decision to downgrade I2C eeprom slave driver to a test. It's a driver again. * I2S * IEEE 802.15.4 * nRF: * Added IEEE 802.15.4 support for nRF5340. * Added support for failed rx notification. * cc13xx/cc26xx: * Added multi-protocol radio support. * Added sub-ghz support. * Added raw mode support. * Interrupt Controller * Added Cypress PSoC-6 Cortex-M0+ interrupt multiplexer driver. * memc * Added FMC/SDRAM memory controller for STM32 family * Modem * Improved RX with HW flow control in modem interface API. * Improved reading from interface in command handler. * Fixed race condition when waiting on cmd reply. * Added support for Quectel bg95 modem. * Constified modem command structures to reduce RAM usage. * hl7800: * Fixed buffer handling issues. * Fixed setting DNS address. * Fixed file open in fw update. * Fixed cases where socket would not close. * sara-r4: * Added sanity timeout for @ prompt. * Fixed redundant wait after sendto. * Improved offload_sendmsg() support. * Added Kconfig to configure RSSI work. * Added direct CMD to catch @ when sending data. * Sanitize send_socket_data() semaphore handling. * bg96: * Fixed UDP packet management. * GSM: * Added start/stop API support so that application can turn off the GSM/PPP modem if needed to save power. * Avoid wrapping each byte in muxing headers in PPP. * Added support to remove PPP IPv4 ipcp address on network down. * PECI * Pinmux * STM32 pinmux driver has been reworked to allow pin configuration using devicetree definitions. The previous C macros are now deprecated. * PWM * Added support for generating PWM signal based on RTC in the pwm_nrf5_sw driver. * Added optional API for capturing the PWM pulse width and period. * Added PWM capture driver for the NXP Kinetis Pulse Width Timer (PWT). * Removed the DesignWare and PCA9685 controller drivers. * Sensor * Fixed current conversion to milliamps in the MAX17055 driver. * Added multi-instance support to the FXOS8700, IIS2DLPC, and IIS2ICLX drivers. * Added Invensense ICM42605 driver. * Added NXP MCUX ACMP driver. * Fixed gyro units in the FXAS21002 driver. * Fixed pressure and temperature registers in the DPS310 driver. * Added I2C support to the BMI160 driver. * Added IIS2ICLX driver. * Aligned ST sensor drivers to stmemsc HAL i/f v1.03. * Fixed temperature units in the IIS2MDC driver. * Added emulator for Bosch BMI160 accelerometer. * Added device power management support to the LIS2MDL driver. * Serial * Added ASYNC API support on STM32 family. * SPI * Enhanced NXP MCUX Flexcomm driver to support DMA. * Timer * USB * Reworked nrfx driver to use mem_slab for event elements and and static memory for OUT endpoints. * Fixed ZLP handling for nrfx driver. * Added support for USB Device mode on STM32F105xx parts. * Video * Watchdog * Added NXP i.MX RT driver. * WiFi * eswifi: * Added uart bus interface. This enables all Inventek modules with IWIN AT Commands firmware. * esp: * Fixed thread-safety access on esp_socket operations. * Fixed scheduling each RX packet on separate work thread. * Fixed initializing socket work structures only once. * Reworked +IPD and +CIPRECVDATA handling. * Stopped locking scheduler when sending data. * Added DHCP/Static IP Support. * Added support using DNS servers. * Enhanced CWMODE support. * Added support for configuring hostname. * Added support for power-gpios to enable ESP module. * Added support 32-bit length in +IPD. * Added support for reconfiguring UART baudrate after initial communication. * Improved packet allocation failure handling by closing stream sockets. Networking ********** * CoAP: * Fixed discovery response formatting according to RFC6690. * Randomized initial ACK timeout. * Reworked pending retransmission logic. * Fixed long options encoding. * DHCPv4: * Added start/bound/stop network management events for DHCPv4. * Fixed timeout scheduling with multiple network interfaces. * Fixed timeout on entry to bound state. * Fixed invalid timeout on send failure. * Fixed bounds checking in timeout. * Fixed endian issue. * Added randomization to message interval. * Limited message interval to a maximum of 64 seconds. * DNS: * Added resolving literal IP addresses even when DNS is disabled. * Added support for DNS Service Discovery (dns-sd). * Fixed getaddrinfo() to respect socket type hints. * HTTP: * Added chunked encoding body support to HTTP client API. * IPv6: * Tweaked IPv6 DAD and RS timeout handling. * Fixed multiple endian issues. * Fixed unaligned access to IPv6 address. * LwM2M: * Added dimension discovery support. * Implemented bootstrap discovery. * Fixed message find based on pending/reply. * Reworked bootstrap DELETE operation. * Added path generation macro. * Added a way to notify the application on network error. * Added a callback to notify socket errors to applications. * Send Registration Update on lifetime changes. * Fixed PULL FW update in case of URI parse errors. * Fixed separate response handling. * Start notify sequence numbers on 0. * Enhanced packing of TLV integers more efficiently. * Improved token generation. * Fixed the bootstrap to be optional. * Misc: * Allow user to select pre-emptive or co-operative RX/TX threads. * Refactored RX and TX thread priorities. * Only start the network logging backend if the autostarting is enabled. * Added support for simultaneous UDP/TCP and raw sockets in applications. * Enabled solicit node multicast group registration for Bluetooth IPSP connections. * Added net_buf_remove API to manipulate data at the end of network buffers. * Added checks to syslog-net that ensure immediate logging mode is not set as the network logging is not compatible with it. * Implemented SO_RCVTIMEO socket receive timeout option. * Added support to update unique hostname on link address changes. * Added locking to IPv6, CAN and packet socket bind calls. * Added network management events monitor support. * MQTT: * Reset client state before notifying application with MQTT_EVT_DISCONNECT event. * OpenThread: * Added support for RCP (Radio Co-Processor) mode. * Made radio workqueue stack size configurable. * Added joining thread multicast addresses which are added to Zephyr. * Added SRP Kconfig options. * Enabled CSL and TREL config options. * Added option to enable software CSMA backoff. * Added support to configure platform info. * Added Kconfigs to change values in Zephyr. * Removed unused defines from platform configuration. * Samples: * Added TagoIO IoT Cloud HTTP post sample. * Fixed the return code in MQTT Docker tests. * Added support to allow DHCPv4 or manually set addresses in zperf sample. * Use IPv4 instead of IPv6 in coap-server to support Docker based testing. * Added connection manager support to dumb_http_server_mt sample. * Added support for large file in dumb_http_server_mt sample. * Added support for running the gptp sample X seconds to support Docker based testing. * Added Docker based testing to http_client sample. * Refractored code structure and reduced RAM usage of civetweb sample. * Added suspend/resume shell commands to gsm_modem sample. * Added Docker based testing support to network logging sample. * TCP: * The new TCP stack is enabled by default. Legacy TCP stack is deprecated but still available and scheduled for removal in next 2.6 release. * Added support to queue received out-of-order TCP data. * Added connection termination if the TCP handshake is not finalized. * Enhanced received TCP RST packet handling. * Fixed TCP connection from Windows 10. * TLS: * Use Maximum Fragment Length (MFL) extension by default. * Added ALPN extension option to TLS. * Fixed TLS context leak on socket allocation failure. Bluetooth ********* * Host * When privacy has been enabled in order to advertise towards a privacy-enabled peer the BT_LE_ADV_OPT_DIR_ADDR_RPA option must now be set, same as when privacy has been disabled. * Mesh * The ``bt_mesh_cfg_srv`` structure has been deprecated in favor of a standalone Heartbeat API and Kconfig entries for default state values. * BLE split software Controller * HCI Driver USB *** * USB synchronous transfer * Fixed possible deadlock in usb_transfer_sync(). * Check added to prevent starting new transfer if an other transfer is already ongoing on same endpoint. * USB DFU class * Made USB DFU class compatible with the target configuration that does not have a secondary image slot. * Support to use USB DFU within MCUBoot with single application slot mode. * Separate PID for DFU mode added to avoid problems caused by the host OS caching the remaining descriptors when switching to DFU mode. * Added timer for appDETACH state and revised descriptor handling to meet specification requirements. * USB HID class * Reworked transfer handling after suspend and resume events. * Samples * Reworked disk and FS configuration in MSC sample. MSC sample can be built with none or one of two supported file systems, LittleFS or FATFS. Disk subsystem can be flash or RAM based. Build and Infrastructure ************************ * Improved support for additional toolchains: * Devicetree * Support for legacy devicetree macros via ``CONFIG_LEGACY_DEVICETREE_MACROS`` was removed. All devicetree-based code should be using the new devicetree API introduced in Zephyr 2.3 and documented in :ref:`dt-from-c`. Information on flash partitions has moved to :ref:`flash_map_api`. * It is now possible to resolve at build time the device pointer associated with a device that is defined in devicetree, via ``DEVICE_DT_GET``. See :ref:`dt-get-device`. * Enhanced support for enumerated property values via new macros: - :c:macro:`DT_ENUM_IDX_OR` - :c:macro:`DT_ENUM_TOKEN` - :c:macro:`DT_ENUM_UPPER_TOKEN` * New hardware specific macros: - :c:macro:`DT_GPIO_CTLR_BY_IDX` - :c:macro:`DT_GPIO_CTLR` - :c:macro:`DT_MTD_FROM_FIXED_PARTITION` * Miscellaneous new node-related macros: - :c:macro:`DT_GPARENT` - :c:macro:`DT_INVALID_NODE` - :c:macro:`DT_NODE_PATH` - :c:macro:`DT_SAME_NODE` * Property access macro changes: - :c:macro:`DT_PROP_BY_PHANDLE_IDX_OR`: new macro - :c:macro:`DT_PROP_HAS_IDX` now expands to a literal 0 or 1, not an expression that evaluates to 0 or 1 * Dependencies between nodes are now exposed via new macros: - :c:macro:`DT_DEP_ORD`, :c:macro:`DT_INST_DEP_ORD` - :c:macro:`DT_REQUIRES_DEP_ORDS`, :c:macro:`DT_INST_REQUIRES_DEP_ORDS` - :c:macro:`DT_SUPPORTS_DEP_ORDS`, :c:macro:`DT_INST_SUPPORTS_DEP_ORDS` * West * Improve bossac runner. It supports now native ROM bootloader for Atmel MCUs and extended SAM-BA bootloader like Arduino and Adafruit UF2. The devices supported depend on bossac version inside Zephyr SDK or in users path. The recommended Zephyr SDK version is 0.12.0 or newer. Libraries / Subsystems ********************** * File systems * API * Added :c:func:`fs_file_t_init` function for initialization of :c:type:`fs_file_t` objects. * Added :c:func:`fs_dir_t_init` function for initialization of :c:type:`fs_dir_t` objects. * ``CONFIG_FS_LITTLEFS_FC_MEM_POOL`` has been deprecated and should be replaced by :kconfig:option:`CONFIG_FS_LITTLEFS_FC_HEAP_SIZE`. * Management * MCUmgr * Added support for flash devices that have non-0xff erase value. * Added optional verification, enabled via :kconfig:option:`CONFIG_IMG_MGMT_REJECT_DIRECT_XIP_MISMATCHED_SLOT`, of an uploaded Direct-XIP binary, which will reject any binary that is not able to boot from base address of offered upload slot. * updatehub * Added support to Network Manager and interface overlays at UpdateHub sample. Ethernet is the default interface configuration and overlays can be used to change default configuration * Added WIFI overlay * Added MODEM overlay * Added IEEE 802.15.4 overlay [experimental] * Added BLE IPSP overlay as [experimental] * Added OpenThread overlay as [experimental]. * Settings * Random * POSIX subsystem * Power management * Use a consistent naming convention using pm_ namespace. * Overhaul power states. New states :c:enum:`pm_state` are more meaningful and ACPI alike. * Move residency information and supported power states to devicetree and remove related Kconfig options. * New power state changes notification API :c:struct:`pm_notifier` * Cleanup build options. * LVGL * Library has been updated to minor release v7.6.1 * Storage * flash_map: Added API to get the value of an erased byte in the flash_area, see ``flash_area_erased_val()``. * DFU * boot: Reworked using MCUBoot's bootutil_public library which allow to use API implementation already provided by MCUboot codebase and remove zephyr's own implementations. * Crypto * mbedTLS updated to 2.16.9 HALs **** * HALs are now moved out of the main tree as external modules and reside in their own standalone repositories. MCUBoot ******* * bootloader * Added hardening against hardware level fault injection and timing attacks, see ``CONFIG_BOOT_FIH_PROFILE_HIGH`` and similar kconfig options. * Introduced Abstract crypto primitives to simplify porting. * Added ram-load upgrade mode (not enabled for zephy-rtos yet). * Renamed single-image mode to single-slot mode, see ``CONFIG_SINGLE_APPLICATION_SLOT``. * Added patch for turning off cache for Cortex M7 before chain-loading. * Fixed bootstrapping in swap-move mode. * Fixed issue causing that interrupted swap-move operation might brick device if the primary image was padded. * Fixed issue causing that HW stack protection catches the chain-loaded application during its early initialization. * Added reset of Cortex SPLIM registers before boot. * Fixesd build issue that occurs if CONF_FILE contains multiple file paths instead of single file path. * Added watchdog feed on nRF devices. See ``CONFIG_BOOT_WATCHDOG_FEED`` option. * Removed the flash_area_read_is_empty() port implementation function. * Initialize the ARM core configuration only when selected by the user, see ``CONFIG_MCUBOOT_CLEANUP_ARM_CORE``. * Allow the final data chunk in the image to be unaligned in the serial-recovery protocol. * Kconfig: allow xip-revert only for xip-mode. * ext: tinycrypt: update ctr mode to stream. * Use minimal CBPRINTF implementation. * Configure logging to LOG_MINIMAL by default. * boot: cleanup NXP MPU configuration before boot. * Fix nokogiri<=1.11.0.rc4 vulnerability. * bootutil_public library was extracted as code which is common API for MCUboot and the DFU application, see ``CONFIG_MCUBOOT_BOOTUTIL_LIB`` * imgtool * Print image digest during verify. * Add possibility to set confirm flag for hex files as well. * Usage of --confirm implies --pad. * Fixed 'custom_tlvs' argument handling. * Add support for setting fixed ROM address into image header. * Fixed verification with protected TLVs. Trusted-Firmware-M ****************** * Synchronized Trusted-Firmware-M module to the upstream v1.2.0 release. Documentation *********** Tests and Samples *************** * A sample was added to demonstrate how to use the ADC driver API. * Sanitycheck script was renamed to twister Issue Related Items ******************* These GitHub issues were addressed since the previous 2.4.0 tagged release: * :github:`32221` - Sporadic kernel panics on stm32g4 flash erase/writes * :github:`32203` - Cannot set static address when using hci_usb or hci_uart on nRF5340 attached to Linux Host * :github:`32181` - samples: tests: Tests from samples/boards/nrf/nrfx fail * :github:`32179` - samples: tests: Tests from samples/subsys/usb/audio fail * :github:`32112` - intel_adsp_cavs15: a part of testcases run failed with same error * :github:`31819` - intel_adsp_cavs15: signing not correct thus download firmware failed * :github:`31675` - [Coverity CID :216790] Division or modulo by zero in tests/drivers/can/timing/src/main.c * :github:`31607` - Bluetooth: host: bt_conn_auth_cb callbacks are not called when pairing to BLE 4.1 central in BT_SECURITY_L4 mode. * :github:`28685` - Bluetooth: Characteristic unsubscribe under indication load results in ATT timeout * :github:`26495` - Make k_poll work with KERNEL_COHERENCE * :github:`21033` - Read out heap space used and unallocated * :github:`19655` - Milestones toward generalized representation of timeouts * :github:`12028` - Enable 16550 UART driver on x86_64 * :github:`32206` - CMSIS-DSP support seems broken on link * :github:`32167` - Bluetooth: controller: conformance testcase failures * :github:`32153` - Use of deprecated macro's in dma_iproc_pax_v1, and dma_iproc_pax_v2 * :github:`32152` - DEVICE_AND_API_INIT and DEVICE_INIT deprecation marking is not working * :github:`32151` - Use of deprecated macro's in icm42605 * :github:`32143` - AArch64 idle loop corrupts IRQ state with CONFIG_TRACING * :github:`32142` - dtc: Unrecognized check name "unique_unit_address_if_enabled" * :github:`32136` - z_unpend1_no_timeout non-atomic * :github:`32095` - guiconfig search fails * :github:`32078` - build error with llvm: samples/subsys/fs/littlefs * :github:`32070` - How to manage power consumption when working with peripheral_hr sample on NRF52832 * :github:`32067` - Bluetooth: Mesh: Devkey and addr not stored correctly * :github:`32064` - Minimal libc malloc() is unprotected * :github:`32059` - Getting Started - Windows - Toolchain not found * :github:`32048` - doc: power management: Remove references to previous PM states terminology * :github:`32046` - LMP90xxx ADC driver fails to initialise more than one instance * :github:`32045` - boards: Inaccurate values for ram/flash in nrf5340dk_nrf5340_cpuapp.yaml * :github:`32040` - BT_AUDIO_UNICAST selection rejected in nightly tests * :github:`32033` - Bluetooth mesh : LPN doesn't receive messages from Friend * :github:`32030` - dma: stm32: remove dump stream info in irq * :github:`32015` - Thread local storage is broken when adding more thread variables * :github:`32014` - Is there a sample that uses SAADC (analog to digital converter)? * :github:`32007` - Wrong clock value at USART1 in STM32F2 dtsi file * :github:`32005` - stm32: async uart tests fail * :github:`32002` - Cannot build encrypted images on Zephyr * :github:`31996` - tests/bluetooth/init/bluetooth.init.test_ctlr_peripheral_iso fails to build on a few platforms * :github:`31994` - drivers: flash: stm32h7: fix int/long int warnings * :github:`31989` - nrfx_uarte serial driver does not go to low power mode after setting off state * :github:`31976` - dma: loop_transfer issue on nucleo_wb55rg * :github:`31973` - Stm32 uart async driver changes offset after callback * :github:`31952` - Linking fails with latest master on ARM64 platform * :github:`31948` - tests: drivers: spi: spi_loopback: became skipped whereas it used to be run * :github:`31947` - Cleanup devicetree warnings generated by dtc * :github:`31946` - arm,arm-timer dts compatible should be arm,armv8-timer * :github:`31944` - flashing not working with openocd runner * :github:`31938` - Invalid SPDX license identifier used in file * :github:`31937` - sample.bluetooth.peripheral_hr_rv32m1_vega_ri5cy does not build * :github:`31930` - uart_nrfx_uarte: ``CONFIG_UART_ASYNC_API`` with ``CONFIG_PM_DEVICE`` breaks * :github:`31928` - usb loopback not work on nrf52840 * :github:`31924` - IVSHMEM with ACRN not working * :github:`31921` - west flash not working with pyocd * :github:`31920` - BME280: Use of deprecated ``CONFIG_DEVICE_POWER_MANAGEMENT`` * :github:`31911` - Bluetooth: Mesh: Network buffer overflow on too long proxy messages * :github:`31907` - settings: Unhandled error in NVS backend * :github:`31905` - Question : Friend & Low power node with nRF52840 * :github:`31876` - west signing seems to be broken on windows * :github:`31867` - samples/scheduler/metairq_dispatc failed on iotdk boards * :github:`31858` - xtensa crt1.S hard coding * :github:`31853` - Devicetree API - Getting GPIO details from pin * :github:`31847` - BT ISO channel. error value set, but not returned. * :github:`31836` - Correct values of _msg_len arg in BT_MESH_MODEL_PUB_DEFINE macro * :github:`31835` - Type conflict (uint32_t) vs. (uint32_t:7) leads to overflow (276 vs. 20) * :github:`31822` - tests: drivers: timer: Test drivers.timer.nrf_rtc_timer.stress fails on nrf52 platforms * :github:`31817` - mec15xxevb_assy6853: tests/boards/mec15xxevb_assy6853/i2c_api/ failed * :github:`31807` - USB DFU Broken for STM32L4 * :github:`31800` - west build; west build --board=qemu_x86 fails with "unknown BOARD" * :github:`31797` - need 2.5 release notes on switch to k_heap from mem_pool * :github:`31791` - samples: hello-world: extra slash in path * :github:`31789` - samples/scheduler/metairq_dispatch: Regression after 30916 (sched: timeout: Do not miss slice timeouts) * :github:`31782` - adc: test and sample failed on STM32 * :github:`31778` - Calling k_sem_give causes MPU Fault on nRF52833 * :github:`31769` - Twister: AttributeError: 'NoneType' object has no attribute 'serial_pty' * :github:`31767` - twister: rename variable p * :github:`31749` - fs: fs_opendir can corrupt fs_dir_t object given via zdp parameter * :github:`31741` - tests:subsys_canbus_isotp: mimxrt1060 meet recv timeout * :github:`31735` - intel_adsp_cavs15: use twister to run kernel testcases has no output * :github:`31733` - Unable to build socket can with frdm_k64f * :github:`31729` - test: build fatal related testcase failed on qemu_cortex_m0 and run failed on qemu_nios2 * :github:`31727` - system_off fails to go into soft_off (deep sleep) state on cc1352r1_launchxl * :github:`31726` - RISC-V MIV SoC clock rate is specified 100x too slow * :github:`31721` - tests: nrf: posix: portability.posix.common.tls.newlib fails on nrf9160dk_nrf9160 * :github:`31704` - tests/bluetooth/init/bluetooth.init.test_ctlr_tiny Fails to build on nrf52dk_nrf52832 * :github:`31696` - UP Celeron version (not the Atom one) has no console * :github:`31693` - Bluetooth: controller: Compilation error when Encryption support is disabled * :github:`31684` - intel_adsp_cavs15: Cannot download firmware of kernel testcases * :github:`31681` - [Coverity CID :216796] Uninitialized scalar variable in tests/subsys/power/power_mgmt/src/main.c * :github:`31680` - [Coverity CID :216795] Unchecked return value in tests/kernel/msgq/msgq_api/src/test_msgq_contexts.c * :github:`31679` - [Coverity CID :216794] Pointless string comparison in tests/lib/devicetree/api/src/main.c * :github:`31678` - [Coverity CID :216793] Division or modulo by zero in tests/ztest/error_hook/src/main.c * :github:`31677` - [Coverity CID :216792] Out-of-bounds access in tests/net/lib/dns_addremove/src/main.c * :github:`31676` - [Coverity CID :216791] Side effect in assertion in tests/lib/p4workq/src/main.c * :github:`31674` - [Coverity CID :216788] Explicit null dereferenced in tests/ztest/error_hook/src/main.c * :github:`31673` - [Coverity CID :216787] Wrong sizeof argument in tests/kernel/mem_heap/mheap_api_concept/src/test_mheap_api.c * :github:`31672` - [Coverity CID :216786] Side effect in assertion in tests/kernel/threads/thread_apis/src/test_threads_cancel_abort.c * :github:`31671` - [Coverity CID :216785] Side effect in assertion in tests/lib/p4workq/src/main.c * :github:`31670` - [Coverity CID :216783] Side effect in assertion in tests/lib/p4workq/src/main.c * :github:`31669` - [Coverity CID :215715] Unchecked return value in tests/subsys/fs/littlefs/src/testfs_mount_flags.c * :github:`31668` - [Coverity CID :215714] Unchecked return value in tests/subsys/fs/fs_api/src/test_fs_mount_flags.c * :github:`31667` - [Coverity CID :215395] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31666` - [Coverity CID :215394] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31665` - [Coverity CID :215393] Argument cannot be negative in tests/net/lib/dns_sd/src/main.c * :github:`31664` - [Coverity CID :215390] Argument cannot be negative in tests/net/lib/dns_sd/src/main.c * :github:`31663` - [Coverity CID :215389] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31662` - [Coverity CID :215388] Argument cannot be negative in tests/net/lib/dns_sd/src/main.c * :github:`31661` - [Coverity CID :215387] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31660` - [Coverity CID :215385] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31659` - [Coverity CID :215384] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31658` - [Coverity CID :215383] Argument cannot be negative in tests/net/lib/dns_sd/src/main.c * :github:`31657` - [Coverity CID :215382] Operands don't affect result in tests/net/lib/dns_sd/src/main.c * :github:`31656` - [Coverity CID :215380] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31655` - [Coverity CID :215378] Argument cannot be negative in tests/net/lib/dns_sd/src/main.c * :github:`31654` - [Coverity CID :215377] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31653` - [Coverity CID :215375] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31652` - [Coverity CID :215374] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31651` - [Coverity CID :215371] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31650` - [Coverity CID :215370] Argument cannot be negative in tests/net/lib/dns_sd/src/main.c * :github:`31649` - [Coverity CID :215369] Out-of-bounds access in tests/net/lib/dns_sd/src/main.c * :github:`31648` - [Coverity CID :216800] Operands don't affect result in lib/os/heap.c * :github:`31647` - [Coverity CID :216789] Wrong sizeof argument in include/kernel.h * :github:`31646` - [Coverity CID :215712] Assignment of overlapping memory in lib/os/cbprintf_complete.c * :github:`31645` - [Coverity CID :215711] Wrong sizeof argument in include/kernel.h * :github:`31644` - [Coverity CID :216798] Unused value in subsys/net/lib/sockets/socketpair.c * :github:`31643` - [Coverity CID :215372] Logically dead code in subsys/net/lib/sockets/sockets_tls.c * :github:`31642` - [Coverity CID :216784] Uninitialized scalar variable in drivers/can/can_common.c * :github:`31640` - mcuboot build is broken * :github:`31631` - x86: ehl_crb_sbl: Booting fails with Slim Bootloader * :github:`31630` - Incorrect configuration override option for west flash * :github:`31629` - mcumgr-cli image upload is failing on shell channel after MCUBOOT_BOOTUTIL library was introduced * :github:`31627` - tests/subsys/power/power_mgmt/subsys.power.device_pm fails to build on nrf5340dk_nrf5340_cpunet & nrf5340pdk_nrf5340_cpunet * :github:`31616` - test: ipc: Test from samples/subsys/ipc/rpmsg_service fails on nrf5340dk_nrf5340_cpuapp * :github:`31614` - drivers: clock_control: Kconfig.stm32xxx PLL div range for each serie * :github:`31613` - Undefined reference errors when using External Library with k_msgq_* calls * :github:`31609` - CoAP discovery response does not follow CoRE link format specification * :github:`31599` - 64 bit race on timer counter in cavs_timer * :github:`31584` - Twister: json reports generation takes too much time * :github:`31582` - STM32F746ZG: No pwm signal output when running /tests/drivers/pwm/pwm_api * :github:`31579` - sam_e70_xplained: running tests/subsys/logging/log_core failed * :github:`31573` - Wrong log settings in can_stm32 driver * :github:`31569` - lora: sx126x: interrupt pin permanently enabled * :github:`31567` - lora: SX126x modems consume excess power until used for first time * :github:`31566` - up_squared: Couldn't get testcase log from console for all testcases. * :github:`31562` - unexpected sign-extension in Kconfig linker symbols on 64-bit platforms * :github:`31560` - Fix incorrect usage of default in dts bindings * :github:`31555` - tests:drivers_can_api: mimxrt1060 can api test meet assert failure * :github:`31551` - lorawan: setting datarate does not allow sending larger packets * :github:`31549` - tests/kernel/lifo/lifo_usage/kernel.lifo.usage fails on m2gl025_miv * :github:`31546` - DTS device dependency is shifting memory addresses between builds * :github:`31543` - Documentation: Spelling * :github:`31531` - STM32 can driver don't set prescaler * :github:`31528` - introduction of demand paging support causing qemu failures on x86_64, qemu_x86_64_nokpti * :github:`31524` - littlefs: Too small heap for file cache. * :github:`31517` - UP broken (git bisect findings inside) * :github:`31511` - AArch32 exception exit routine behaves incorrectly on fatal exceptions * :github:`31510` - Some drivers return invalid z_timer_cycle_get_32() value * :github:`31508` - up_squared: tests/kernel/sched/deadline/ failed. * :github:`31505` - qemu_cortex_m0: Cmake build failure * :github:`31504` - qemu_cortex_m0: Cmake build failure * :github:`31502` - it8xxx2_evb should not define TICKLESS_CAPABLE * :github:`31488` - build failure w/twister and SDK 0.12.1 related to * :github:`31486` - make htmldocs-fast not working in development workspace * :github:`31485` - west flash --runner=jlink should raise error when CONFIG_BUILD_OUTPUT_BIN=n * :github:`31472` - tests: kernel: poll: timeout with FPU enabled * :github:`31467` - samples: bluetooth: peripheral_hids: Pairing fails on the nucleo_wb55rg board. * :github:`31444` - Error in include/net/socket_select.h * :github:`31439` - nrf5340dk_nrf5340_cpunet configuring incomplete * :github:`31436` - compliance script broken * :github:`31433` - samples/bluetooth/hci_pwr_ctrl stack overflow on nRF52DK_nRF52832 * :github:`31419` - tests/ztest/error_hook failed on ARC boards * :github:`31414` - samples/net/mqtt_publisher link error: undefined reference to ``z_impl_sys_rand32_get`` * :github:`31400` - Extending ``zephyr,code-partition`` with ``zephyr,code-header-size`` * :github:`31386` - sam_e70b_xplained: running tests/drivers/watchdog/wdt_basic_api/ timeout for v1.14-branch * :github:`31385` - ARC version of sys_read32 only reads uint16_t on Zephyr v2.4 * :github:`31379` - Update CAN-API Documentation * :github:`31370` - Question about serial communication using virtual COM * :github:`31362` - kconfiglib.py _save_old() may rename /dev/null -- replacing /dev/null with a file * :github:`31358` - ``west build`` might destroy your repository, as it is defaulting doing pristine. * :github:`31344` - iotdk: running tests/ztest/error_hook/ failed * :github:`31343` - sam_e70_xplained: running tests/net/socket/af_packet/ failed * :github:`31342` - sam_e70_xplained: running tests/net/ptp/clock/ failed * :github:`31340` - sam_e70_xplained: running tests/subsys/logging/log_core/ failed * :github:`31339` - nsim_em: running tests/ztest/error_hook/ failed * :github:`31338` - mimxrt1050_evk: running tests/kernel/fpu_sharing/float_disable/ failed * :github:`31333` - adding a periodic k_timer causes k_msleep to never return in tests/kernel/context * :github:`31330` - Getting started guide outdated: Step 4 - Install a toolchain * :github:`31327` - ci compliance failures due to intel_adsp_cavs25 sample * :github:`31316` - Issue in UDP management for BG96 * :github:`31308` - Cannot set static address when using hci_usb or hci_uart on nRF5340 attached to Linux Host * :github:`31301` - intel_adsp_cavs15: run kernel testcases failed. * :github:`31289` - Problems building grub2 bootloader for Zephyr * :github:`31285` - LOG resulting in incorrect output * :github:`31282` - Kernel: Poll: Code Suspected Logic Problem * :github:`31272` - CANOpen Sample compilation fails * :github:`31262` - tests/kernel/threads/tls/kernel.threads.tls.userspace failing * :github:`31259` - uart.h: Clarification required on uart_irq_tx_ready uart_irq_rx_ready * :github:`31258` - watch dog (WWDT) timeout calculation for STM32 handles biggest timeout and rollover wrong * :github:`31235` - Cortex-M: vector table relocation is incorrect with XIP=n * :github:`31234` - twister: Add choice for tests sorting into subsets * :github:`31226` - tests/drivers/dma/loop_transfer does not use ztest * :github:`31219` - newlib printk float formatting not working * :github:`31207` - Non-existent event in asynchronous UART API * :github:`31206` - coap.c : encoding of options with lengths larger than 268 is not proper * :github:`31203` - fatal error: setjmp.h: No such file or directory * :github:`31194` - twister: using unsupported fixture without defined harness causes an infinite loop during on-target test execution * :github:`31168` - Wrong linker option syntax for printf and scanf with float support * :github:`31158` - Ethernet (ENC424J600) with dumb_http_server_mt demo does not work * :github:`31153` - twister build of samples/audio/sof/sample.audio.sof fails on most platforms * :github:`31145` - Litex-vexriscv address misaligned with dumb_http_server example * :github:`31143` - samples: audio: sof: compilation issue, include file not found. * :github:`31137` - Seems like the rule ".99 tag to signify major work started, minor+1 started " not used anymore ? * :github:`31134` - LittleFS: Error Resizing the External QSPI NOR Flash in nRF52840dk * :github:`31114` - Bluetooth: Which coding (S2 vs S8) is used during advertising on Coded PHY? * :github:`31100` - Recvfrom not returning -1 if UDP and len is too small for packet. * :github:`31091` - usb: usb_transfer_sync deadlocks on disconnect/cancel transfer * :github:`31086` - bluetooth: Resume peripheral's advertising after disconnection when using new bt_le_ext_adv_* API * :github:`31085` - networking / openthread: ipv6 mesh-local all-nodes multicast (ff03::1) packets are dropped by zephyr ipv6 stack * :github:`31079` - Receiving extended scans on an Adafruit nRF 52840 * :github:`31071` - board: arm: SiliconLabs: add support to development kit efm32pg_stk3401a * :github:`31069` - net: buf: remove data from end of buffer * :github:`31067` - usb: cdc_acm: compilation error without UART * :github:`31055` - nordic: west flash no longer supports changing ``CONFIG_GPIO_PINRESET`` when flashing * :github:`31053` - LwM2M FOTA pull not working with modem (offloaded socket) driver using UART * :github:`31044` - sample.bluetooth.peripheral_hr build fails on rv32m1_vega_ri5cy * :github:`31110` - How can I overwrite west build in command? * :github:`31028` - Cannot READ_BIT(RCC->CR, RCC_CR_PLL1RDY) on STM32H743 based board * :github:`31027` - Google tests run twice * :github:`31020` - CI build failed on intel_adsp_cavs18 when submitted a PR * :github:`31019` - Bluetooth: Mesh: Thread competition leads to failure to open or close the scanning. * :github:`31018` - up_squared: tests/kernel/pipe/pipe_api failed. * :github:`31014` - Incorrect timing calculation in can_mcux_flexcan * :github:`31008` - error: initializer element is not constant .attr = K_MEM_PARTITION_P_RX_U_RX * :github:`30999` - updatehub with openthread build update pkg failed * :github:`30997` - samples: net: sockets: echo_client: posix tls example * :github:`30989` - driver : STM32 Ethernet : Pin definition for PH6 * :github:`30979` - up_squared_adsp: Twister can not capture testcases log correctly * :github:`30972` - USB: SET_ADDRESS logic error * :github:`30964` - Sleep calls are off on qemu_x86 * :github:`30961` - esp32 broken by devicetree device updates * :github:`30955` - Bluetooth: userchan: k_sem_take failed with err -11 * :github:`30938` - samples/net/dhcpv4_client does not work with sam_e70_xplained * :github:`30935` - tests: net: sockets: tcp: add a tls tests * :github:`30921` - west flash failed with an open ocd error * :github:`30918` - up_squared: tests/kernel/mem_protect/mem_protect failed. * :github:`30893` - Remove LEGACY_TIMEOUT_API * :github:`30872` - Convert Intel GNA driver to devicetree * :github:`30871` - "warning: compound assignment with 'volatile'-qualified left operand is deprecated" when building with C++20 * :github:`30870` - Convert Intel DMIC to devicetree * :github:`30869` - Convert designware PWM driver to devicetree * :github:`30862` - Nordic system timer driver incompatible with LEGACY_TIMEOUT_API * :github:`30860` - legacy timeout ticks mishandled * :github:`30857` - SDRAM not working on STM32H747I-DISCO * :github:`30850` - iotdk: couldn't flash image into iotdk board using west flash. * :github:`30846` - devicetree: unspecified phandle-array elements cause errors * :github:`30822` - designator order for field 'zcan_filter::rtr' does not match declaration order in 'const zcan_filter' * :github:`30819` - twister: --generate-hardware-map crashes and deletes map * :github:`30810` - tests: kernel: kernel.threads.armv8m_mpu_stack_guard fails on nrf9160dk * :github:`30809` - new testcase is failing after 3f134877 on mec1501modular_assy6885 * :github:`30808` - Blueooth: Controller Response COMMAND DISALLOWED * :github:`30805` - Build error at tests/kernel/queue in mec15xxevb_assy6853(qemu) platform * :github:`30800` - STM32 usb clock from PLLSAI1 * :github:`30792` - Cannot build network echo_server for nucleo_f767zi * :github:`30752` - ARC: passed tests marked as failed when running sanitycheck on nsim_* platforms * :github:`30750` - Convert i2s_cavs to devicetree * :github:`30736` - Deadlock with usb_transfer_sync() * :github:`30730` - tests: nrf: Tests in tests/drivers/timer/nrf_rtc_timer are flaky * :github:`30723` - libc: malloc() returns unaligned pointer, causes CPU exception * :github:`30713` - doc: "Variable ZEPHYR_TOOLCHAIN_VARIANT is not defined" * :github:`30712` - "make zephyr_generated_headers" regressed again - ";" separator for Z_CFLAGS instead of spaces * :github:`30705` - STM32 PWM driver generates signal with wrong frequency on STM32G4 * :github:`30702` - Shell module broken on LiteX/VexRiscv after release zephyr-v2.1.0 * :github:`30698` - OpenThread Kconfigs should more closely follow Zephyr Kconfig recommendations * :github:`30688` - Using openthread based lwm2m_client cannot ping the external network address unless reset once * :github:`30686` - getaddrinfo() does not respect socket type * :github:`30685` - reel_board: tests/kernel/fatal/exception/ failure * :github:`30683` - intel_adsp_cavs15:running tests/kernel/sched/schedule_api failed * :github:`30679` - puncover worst-case stack analysis does not work * :github:`30673` - cmake: zephyr_module.cmake included before ZEPHYR_EXTRA_MODULES is evaluated * :github:`30663` - Support for TI's TMP117 Temperature Sensor. * :github:`30657` - BT Mesh: Friendship ends if LPN publishes to a VA it is subscribed to * :github:`30651` - sanitycheck samples/video/capture/sample.video.capture fails to build on mimxrt1064_evk * :github:`30649` - Trouble with gpio callback on frdm k64f * :github:`30638` - nrf pwm broken * :github:`30636` - TCP stack locks irq's for too long * :github:`30634` - frdm_kw41z: Current master fails compilation in drivers/pwm/pwm_mcux_tpm.c * :github:`30624` - BLE : ATT Timeout occurred during multilink central connection * :github:`30591` - build RAM usage printout uses prebuilt and not final binary * :github:`30582` - Doxygen doesn't catch errors in argument names in callback functions that are @typedef'd * :github:`30574` - up_squared: tests/kernel/semaphore/semaphore failed. * :github:`30573` - up_squared: slowdown on test execution and timing out on multiple tests * :github:`30566` - flashing issue with ST Nucleo board H745ZI-Q * :github:`30557` - i2c slave driver removed * :github:`30554` - tests/kernel/fatal/exception/sentinel test is failing for various nrf platforms * :github:`30553` - kconfig.py exits with error when using multiple shields * :github:`30548` - reel_board: tests/net/ieee802154/l2/ build failure * :github:`30547` - reel_board: tests/net/ieee802154/fragment/ build failure * :github:`30546` - LwM2M Execute arguments currently not supported * :github:`30541` - l2m2m: writing to resources with pre_write callback fails * :github:`30531` - When using ccache, compiler identity stored in ToolchainCapabilityDatabase is always the same * :github:`30526` - tests: drivers: timer: Tests from drivers.timer.nrf_rtc_timer.basic fail on all nrf platforms * :github:`30517` - Interrupt nesting is broken on ARMv7-R / LR_svc corrupted. * :github:`30514` - reel_board: tests/benchmarks/sys_kernel/ fails * :github:`30513` - reel_board: tests/benchmarks/latency_measure/ fails * :github:`30509` - k_timer_remaining_get returns incorrect value on long timers * :github:`30507` - nrf52_bsim fails on some tests after merging 29810 * :github:`30488` - Bluetooth: controller: swi.h should use CONFIG_SOC_NRF5340_CPUNET define * :github:`30486` - updatehub demo for nrf52840dk * :github:`30483` - Sanitycheck: When platform is nsim_hs_smp, process "west flash" become defunct, the grandchild "cld" process can't be killed * :github:`30480` - Bluetooth: Controller: Advertising can only be started 2^16 times * :github:`30477` - frdm_k64f: testcase samples/subsys/canbus/canopen/ failed to be ran * :github:`30476` - frdm_k64f: testcase samples/net/cloud/tagoio_http_post/ failed to be ran * :github:`30475` - frdm_k64f: testcase tests/kernel/fatal/exception/ failed to be ran * :github:`30473` - mimxrt1050_evk: testcase tests/kernel/fatal/exception/ failed to be ran * :github:`30472` - sam_e70_xplained: the samples/net/civetweb/http_server/. waits for interface unitl timeout * :github:`30470` - sam_e70_xplained: tesecase tests/subsys/log_core failed to run * :github:`30468` - mesh: cfg_svr.c app_key_del passes an incorrect parameter * :github:`30467` - replace device define macros with devicetree-based macro * :github:`30446` - fxas21002 gyroscope reading is in deg/s * :github:`30435` - NRFX_CLOCK_EVT_HFCLKAUDIO_STARTED not handled in clock_control_nrf.c * :github:`30434` - Memory map executing test case failed when code coverage enabled in x86_64 platform * :github:`30433` - zephyr client automatic joiner failed on nRF52840dk * :github:`30432` - No network interface was found when running socketcan sample * :github:`30426` - Enforce all checkpatch warnings and move to 100 characters per line * :github:`30423` - Devicetree: Child node of node on SPI bus itself needs reg property - Bug? * :github:`30418` - Logging: Using asserts with LOG in high pri ISR context blocks output * :github:`30408` - tests/kernel/sched/schedule_api is failing after 0875740 on m2gl025_miv * :github:`30397` - tests:latency_measure is not counting semaphore results on the ARM boards * :github:`30394` - TLS tests failing with sanitycheck (under load) * :github:`30393` - kernel.threads.tls.userspace fails with SDK 0.12.0-beta on ARM Cortex-M * :github:`30386` - Building confirmed images does not work * :github:`30384` - Scheduler doesn't activate sleeping threads on native_posix * :github:`30380` - Improve the use of CONFIG_KERNEL_COHERENCE * :github:`30378` - Bluetooth: controller: tx buffer overflow error * :github:`30364` - TCP2 does not implement queing for incoming packets * :github:`30362` - adc_read_async callback parameters are dereferenced pointers, making use of CONTAINER_OF impossible * :github:`30360` - reproducible qemu_x86_64 SMP failures * :github:`30356` - DAC header file not included in stm32 soc.h * :github:`30354` - Regression with 'local-mac-address' enet DTS property parsing (on i.MX K6x) * :github:`30349` - Memory protection unit fault when running socket CAN program * :github:`30344` - Bluetooth: host: Add support for multiple advertising sets for legacy advertising * :github:`30338` - BT Mesh LPN max. poll timeout calculated incorrectly * :github:`30330` - tests/subsys/usb/bos/usb.bos fails with native_posix and llvm/clang * :github:`30328` - Openthread build issues with clang/llvm * :github:`30322` - tests: benchmarks: latency_measure: timing measurement values are all 0 * :github:`30316` - updatehub with openthread * :github:`30315` - Build failure: zephyr/include/generated/devicetree_unfixed.h:627:29: error: 'DT_N_S_leds_S_led_0_P_gpios_IDX_0_PH_P_label' undeclared * :github:`30308` - Add optional user data field to device structure * :github:`30307` - up_squared: tests/kernel/device/ failed. * :github:`30306` - up_squared: tests/kernel/mem_protect/userspace failed. * :github:`30305` - up_squared: tests/kernel/mem_protect/mem_protect failed. * :github:`30304` - NRF52832 consumption too high 220uA * :github:`30298` - regression/change in master: formatting floats and doubles * :github:`30276` - Sanitycheck: can't find mdb.pid * :github:`30275` - up_squared: tests/kernel/common failed (timeout error) * :github:`30261` - File no longer at this location * :github:`30257` - test: kernel: Test kernel.common.stack_protection_arm_fpu_sharing.fatal fails on nrf52 platforms * :github:`30253` - tests: kernel: Test kernel.memory_protection.gap_filling fails on nrf5340dk_nrf5340_cpuapp * :github:`30372` - WEST Support clean build * :github:`30373` - out of tree board soc doc subsystem ...) * :github:`30240` - Bluetooth: Mesh: PTS Test failed in friend node * :github:`30235` - MbedTLS X509 certificate not parsing * :github:`30232` - CMake 3.19 doesn't work with Zephyr (tracking issue w/upstream CMake) * :github:`30230` - printk and power management incompatibility * :github:`30229` - BinaryHandler has no pid file * :github:`30224` - stm32f4_disco: User button press is inverted * :github:`30222` - boards: arm: nucleo_wb55rg: fails to build basic samples * :github:`30219` - drivers: gpio: gpio_cc13xx_cc26xx: Add drive strength configurability * :github:`30213` - usb: tests: Test usb.device.usb.device.usb_disable fails on nrf52840dk_nrf52840 * :github:`30211` - spi nor sfdp runtime: nph offset * :github:`30207` - Mesh_demo with a nRF52840 not working * :github:`30205` - Missing error check of function i2c_write_read() and dac_write_value() * :github:`30194` - qemu_x86 crashes when printing floating point. * :github:`30193` - reel_board: running tests/subsys/power/power_mgmt_soc failed * :github:`30191` - Missing checks of return values of settings_runtime_set() * :github:`30189` - Missing error check of function sensor_trigger_set() * :github:`30187` - usb: stm32: MCU fall in deadlock when calling sleep API during USB transfer * :github:`30183` - undefined reference to ``ring_buf_item_put`` * :github:`30179` - out of tree board soc doc subsystem ... * :github:`30178` - Is there any plan to support NXP RT600 HIFI4 DSP in the zephyr project? * :github:`30173` - OpenThread SED cannot join the network after "Update nRF5 ieee802154 driver to v1.9" * :github:`30157` - SW based BLE Link Layer Random Advertise delay not as expected * :github:`30153` - BSD recv() can not received huge package(may be 100kB) sustain . * :github:`30148` - STM32G474: Write to flash Bank 2 address 0x08040000 does not work in 256K flash version * :github:`30141` - qemu_x86 unexpected thread behavior * :github:`30137` - TCP2: Handling of RST flag from server makes poll() call unable to return indefinitely * :github:`30135` - LWM2M: Firmware URI writing does not work anymore * :github:`30134` - tests: drivers: uart: Tests from tests/drivers/uart/uart_mix_fifo_poll fails on nrf platforms * :github:`30133` - sensor: driver: lis2dh interrupt definitions * :github:`30130` - nrf_radio_power_set() should use bool * :github:`30129` - TCP2 send test * :github:`30126` - xtensa-asm2-util.s hard coding * :github:`30120` - sanitycheck fails for tests/bluetooth/init/bluetooth.init.test_ctlr_per_sync * :github:`30117` - Cannot compile Zephyr project with standard macros INT8_C, UINT8_C, UINT16_C * :github:`30106` - Refactor zcan_frame. * :github:`30100` - twister test case selection numbers don't make any sense * :github:`30099` - sanitycheck --build-only gets stuck * :github:`30098` - > very few are even tested with CONFIG_NO_OPTIMIZATIONS. What is the general consensus about this? * :github:`30094` - tests: kernel: fpu_sharing: Tests in tests/kernel/fpu_sharing fail on nrf platforms * :github:`30075` - dfu: mcuboot: fail to build with CONFIG_BOOTLOADER_MCUBOOT=n and CONFIG_IMG_MANAGER=y * :github:`30072` - tests/net/socket/socketpair appears to mis-use work queue APIs * :github:`30066` - CI test build with RAM overflow * :github:`30057` - LLVM built application crash * :github:`30037` - Documentation: Fix getting started guide for macOS around homebrew install * :github:`30031` - stm32f4 usb - bulk in endpoint does not work * :github:`30029` - samples: net: cloud: tagoio_http_post: Undefined initialization levels used. * :github:`30028` - sam_e70_xplained: MPU fault with CONFIG_NO_OPTIMIZATIONS=y * :github:`30027` - sanitycheck failures on ``tests/bluetooth/init/bluetooth.init.test_ctlr_peripheral_ext`` * :github:`30022` - The mailbox message.info in the receiver thread is not updated. * :github:`30014` - STM32F411RE PWM support * :github:`30010` - util or toolchain: functions for reversing bits * :github:`29999` - nrf52840 Slave mode is not supported on SPI_0 * :github:`29997` - format specifies type 'unsigned short' but the argument has type 'int' error in network stack * :github:`29995` - Bluetooth: l2cap: L2CAP/LE/REJ/BI-02-C test failure * :github:`29994` - High bluetooth ISR latency with CONFIG_BT_MAX_CONN=2 * :github:`29992` - dma tests fail with stm32wb55 and stm32l476 nucleo boards * :github:`29991` - Watchdog Example not working as expected on a Nordic chip * :github:`29977` - nrf9160: use 32Mhz HFCLK * :github:`29969` - sanitycheck fails on tests/benchmarks/latency_measure/benchmark.kernel.latency * :github:`29968` - sanitycheck fails a number of bluetooth tests on NRF * :github:`29967` - sanitycheck fails to build samples/bluetooth/peripheral_hr/sample.bluetooth.peripheral_hr_rv32m1_vega_ri5cy * :github:`29964` - net: lwm2m: Correctly Support Bootstrap-Delete Operation * :github:`29963` - RFC: dfu/boot/mcuboot: consider usage of boootloader/mcuboot code * :github:`29961` - Add i2c driver tests for microchip evaluation board * :github:`29960` - Checkpatch compliance errors do not fail CI * :github:`29958` - mcuboot hangs when CONFIG_BOOT_SERIAL_DETECT_PORT value not found * :github:`29957` - BLE Notifications limited to 1 per connection event on Zephyr v2.4.0 Central * :github:`29954` - intel_adsp_cavs18 fails with heap errors on current Zephyr * :github:`29953` - Add the sofproject as a module * :github:`29951` - ieee802154: cc13xx_cc26xx: raw mode support * :github:`29945` - Missing error check of function sensor_sample_fetch() and sensor_channel_get() * :github:`29943` - Missing error check of function isotp_send() * :github:`29937` - XCC Build offsets.c FAILED * :github:`29936` - XCC Build isr_tables.c fail * :github:`29925` - pinctrl error for disco_l475_iot1 board: * :github:`29921` - USB DFU with nrf52840dk (PCA10056) * :github:`29916` - ARC: tests fail on nsim_hs with one register bank * :github:`29913` - Question : Bluetooth mesh using long range * :github:`29908` - devicetree: Allow all GPIO flags to be used by devicetree * :github:`29896` - new documentation build warning * :github:`29891` - mcumgr image upload (with smp_svr) does not work over serial/shell on the nrf52840dk * :github:`29884` - x_nucleo_iks01a2 device tree overlay issue with stm32mp157c_dk2 board * :github:`29883` - drivers: ieee802154: cc13xx_cc26xx: use multi-protocol radio patch * :github:`29879` - samples/net/gptp compile failed on frdm_k64f board in origin/master (work well in origin/v2.4-branch) * :github:`29877` - WS2812 SPI LED strip driver produces bad SPI data * :github:`29869` - Missing error check of function entropy_get_entropy() * :github:`29868` - Bluetooth: Mesh: DST not checked on send * :github:`29858` - [v1.14, v2.4] Bluetooth: Mesh: RPL cleared on LPN disconnect * :github:`29855` - Bluetooth: Mesh: TTL max not checked on send * :github:`29853` - multiple PRs fail doc checks * :github:`29842` - 'imgtool' absent in requirements.txt * :github:`29833` - Test DT_INST_PROP_HAS_IDX() inside the macros for multi instances * :github:`29831` - flash support for stm32h7 SoC * :github:`29829` - On-PR CI needs to build a subset of tests for a subset of platforms regardless of the scope of the PR changes * :github:`29826` - SNTP doesn't work on v2.4.0 on eswifi * :github:`29822` - Redundant error check of function usb_set_config() in subsys/usb/class/usb_dfu.c * :github:`29809` - gen_isr_tables.py does not check that the IRQ number is in bounds * :github:`29805` - SimpleLink does not compile (simplelink_sockets.c) * :github:`29796` - Zephyr API for writing to flash for STM32G474 doesn't work as expected * :github:`29793` - Ninja generated error when setting PCAP option in west * :github:`29791` - spi stm32 dma: spi * :github:`29790` - The zephyr-app-commands macro does not honor :generator: option * :github:`29782` - smp_svr: Flashing zephyr.signed.bin does not seem to work on nrf52840dk * :github:`29780` - nRF SDK hci_usb sample disconnects after 40 seconds with extended connection via coded PHY * :github:`29776` - Check vector number and pointer to ISR in "_isr_wrapper" routine for aarch64 * :github:`29775` - TCP socket stream * :github:`29773` - sam_e70_xplained: running samples/net/sockets/civetweb/ failed * :github:`29772` - sam_e70_xplained:running testcase tests/subsys/logging/log_core failed * :github:`29771` - samples: net: sockets: tcp: tcp2 server not accepting with ipv6 bsd sockets * :github:`29769` - mimxrt1050_evk: build error at tests/subsys/usb/device/ * :github:`29762` - nRF53 Network core cannot start LFClk when using empty_app_core * :github:`29758` - edtlib not reporting proper matching_compat for led nodes (and other children nodes) * :github:`29740` - OTA using Thread * :github:`29737` - up_squared: tests/subsys/power/power_mgmt failed. * :github:`29733` - SAM0 will wake up with interrupted execution after deep sleep * :github:`29732` - issue with ST Nucleo H743ZI2 * :github:`29730` - drivers/pcie: In Kernel Mode pcie_conf_read crashes when used with newlib * :github:`29722` - West flash is not able to flash with openocd * :github:`29721` - drivers/sensor/lsm6dsl: assertion/UB during interrupt handling * :github:`29720` - samples/display/lvgl/sample.gui.lvgl fails to build on several boards * :github:`29716` - Dependency between userspace and memory protection features * :github:`29713` - nRF5340 - duplicate unit-address * :github:`29711` - Add BSD socket option SO_RCVTIMEO * :github:`29710` - drivers: usb_dc_mcux_ehci: driver broken, build error at all USB test and samples * :github:`29707` - xtensa xt-xcc -Wno-unused-but-set-variable not work * :github:`29706` - xtensa xt-xcc inline warning * :github:`29705` - reel_board: tests/kernel/sched/schedule_api/ fails on multiple boards * :github:`29704` - [Coverity CID :215255] Dereference before null check in tests/subsys/fs/fs_api/src/test_fs.c * :github:`29703` - [Coverity CID :215261] Explicit null dereferenced in subsys/emul/emul_bmi160.c * :github:`29702` - [Coverity CID :215232] Dereference after null check in subsys/emul/emul_bmi160.c * :github:`29701` - [Coverity CID :215226] Logically dead code in soc/xtensa/intel_adsp/common/bootloader/boot_loader.c * :github:`29700` - [Coverity CID :215253] Unintentional integer overflow in drivers/timer/stm32_lptim_timer.c * :github:`29699` - [Coverity CID :215249] Unused value in drivers/modem/ublox-sara-r4.c * :github:`29698` - [Coverity CID :215248] Dereference after null check in drivers/modem/hl7800.c * :github:`29697` - [Coverity CID :215243] Unintentional integer overflow in drivers/timer/stm32_lptim_timer.c * :github:`29696` - [Coverity CID :215241] Buffer not null terminated in drivers/modem/hl7800.c * :github:`29695` - [Coverity CID :215235] Dereference after null check in drivers/modem/hl7800.c * :github:`29694` - [Coverity CID :215233] Logically dead code in drivers/modem/hl7800.c * :github:`29693` - [Coverity CID :215224] Parse warning in drivers/modem/hl7800.c * :github:`29692` - [Coverity CID :215221] Unchecked return value in drivers/regulator/regulator_fixed.c * :github:`29690` - NUCLEO-H745ZI-Q + OpenOCD - connect under reset * :github:`29684` - Can not make multiple BLE IPSP connection to the same host * :github:`29683` - BLE IPSP sample doesn't work on raspberry pi 4 with nrf52840_mdk board * :github:`29681` - Add NUCLEO-H723ZG board support * :github:`29677` - stm32h747i_disco add ethernet support * :github:`29675` - Remove pinmux dependency on STM32 boards * :github:`29667` - RTT Tracing is not working using NXP mimxrt1064_evk * :github:`29657` - enc28j60 on nRF52840 stalls during enc28j60_init_buffers in zephyr 2.4.0 * :github:`29654` - k_heap APIs have no tests * :github:`29649` - net: context: add net_context api to check if a port is bound * :github:`29639` - Bluetooth: host: Security procedure failure can terminate GATT client request * :github:`29637` - 5g is microwave and 4LTE is radio or static? * :github:`29636` - Bluetooth: Controller: Connection Parameter Update indication timeout * :github:`29634` - Build error: (Bluetooth: Mesh: split prov.c into two separate modules #28457) * :github:`29632` - GPIO interrupt support for IO expander * :github:`29631` - kernel: provide aligned variant of k_heap_alloc * :github:`29629` - Creating a k_thread as runtime instantiated kernel object using k_malloc causes general protection fault * :github:`29616` - Lorawan subsystem stack: missing MLE_JOIN parameter set * :github:`29611` - usb/class/dfu: void wait_for_usb_dfu() terminates before DFU operation is completed * :github:`29608` - question: create runtime instantiated kernel objects in kernel mode * :github:`29594` - x86_64: RBX being clobbered in the idle thread * :github:`29590` - ARM: FPU: using Unshared FP Services mode can still result in corrupted floating point registers * :github:`29589` - Creating a k_thread and k_sem as runtime instantiated kernel object causes general protection fault * :github:`29574` - question: about CONFIG_NET_BUF_POOL_USAGE * :github:`29567` - Using openthread based echo_client and lwm2m_client cannot ping the external network address * :github:`29549` - doc: Zephyr module feature ``depends`` not documented. * :github:`29544` - Bluetooth: Mesh: Friend node unable relay message for lpn * :github:`29541` - CONFIG_THREAD_LOCAL_STORAGE=y build fails with ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb * :github:`29538` - eswifi recvfrom() not properly implemented on disco_l475_iot1 * :github:`29534` - reel_board:running tests/kernel/workq/work_queue_api/ failed * :github:`29533` - mec15xxevb_assy6853:running testcase tests/kernel/workq/work_queue_api/ failed. * :github:`29532` - mec15xxevb_assy6853:running testcase tests/portability/cmsis_rtos_v2/ failed. * :github:`29530` - display: nrf52840: adafruit_2_8_tft_touch_v2 shield not working with nrf-spim driver * :github:`29519` - kernel: provide aligned variants for allocators * :github:`29518` - sleep in qemu to short * :github:`29499` - x86 thread stack guards persist after thread exit * :github:`29497` - Warning in CR2 * :github:`29491` - usb: web USB sample fails Chapter9 USB3CV tests. * :github:`29478` - fs: fs_open can corrupt fs_open_t object given via zfp parameter * :github:`29468` - usb: ZEPHYR FATAL ERROR when running USB test for Nordic. * :github:`29467` - nrf_qspi_nor.c Incorrect value used for checking start of RAM address space * :github:`29446` - pwm: stm32: output signal delayed * :github:`29444` - Network deadlock * :github:`29442` - build failure w/sanitycheck for samples/bluetooth/hci_usb_h4/sample.bluetooth.hci_usb_h4 * :github:`29440` - Missing hw-flow-control; in hci_uart overlay files * :github:`29435` - SDCard via SD/SDIO/MMC interfaces * :github:`29430` - up_squared_adsp: Sanitycheck can not run test case on Up_Squared_ADSP board * :github:`29429` - net: dns: enable dns service discovery for mdns service * :github:`29418` - ieee802154: cc13xx_cc26xx: bug in rf driver library * :github:`29412` - sanitycheck: skipped tests marked as failed due to the reason SKIPPED (SRAM overflow) * :github:`29398` - ICMPv6 error sent with incorrect link layer addresses * :github:`29386` - unexpected behavior when doing syscall with 7 or more arguments * :github:`29382` - remove memory domain restriction on system RAM for memory partitions on MMU devices * :github:`29376` - sanitycheck: "TypeError: 'NoneType' object is not iterable" * :github:`29373` - Some altera DTS bindings have the wrong vendor prefix * :github:`29368` - STM32: non F1 -pinctrl.dtsi generation files: Limit mode to variants * :github:`29367` - usb: drivers: add USB support for UP squared * :github:`29364` - cdc_acm_composite fails USB3CV test for Nordic platform. * :github:`29363` - shell: inability to print 64-bit integers with newlib support * :github:`29357` - RFC: API Change: Bluetooth: Update indication callback parameters * :github:`29347` - Network deadlock because of mutex locking order * :github:`29346` - west boards doesn't display the arcitecture. * :github:`29330` - mec15xxevb_assy6853:running samples/boards/mec15xxevb_assy6853/power_management Sleep entry latency is higher than expected * :github:`29329` - tests: kernel.workqueue.api tests fail on multiple platforms * :github:`29328` - mec15xxevb_assy6853:running tests/kernel/workq/work_queue_api/ failed * :github:`29327` - mec15xxevb_assy6853:region ``SRAM`` overflowed during build * :github:`29319` - up_squared: tests/kernel/timer/timer_api failed. * :github:`29317` - mimxrt1015: kernel_threads_sched: application meet size issue * :github:`29315` - twr_kv58f220m: all application build failure * :github:`29312` - [RFC] [BOSSA] Improve offset parameter * :github:`29310` - ble central Repeat read and write to three peripherals error USAGE FAULT * :github:`29309` - ADC1 doesn't read correctly on STM32F7 * :github:`29308` - GPIO bit banging i2c init before gpio clock init in stm32f401 plantform,cause same gpio can't work. * :github:`29307` - samples/bluetooth/mesh-demo unable to send vendor button message * :github:`29300` - K_THREAD_DEFINE() uses const in a wrong way * :github:`29298` - xlnx_psttc_timer driver has an imprecise z_clock_set_timeout() implementation * :github:`29287` - spi: SPI_LOCK_ON does not hold the lock for multiple spi_transceive until spi_release * :github:`29284` - compilation issues for MinnowBoard/ UpSquared on documentation examples * :github:`29283` - quickfeather not listed in boards * :github:`29274` - Can't get Coded PHY type(S2 or S8) * :github:`29272` - nordic qspi: readoc / writeoc selection may not work * :github:`29263` - tests/kernel/mem_protect/obj_validation fails build on some boards after recent changes * :github:`29261` - boards: musca_b1: post build actions with TF-M might not be done in right order * :github:`29259` - sanitycheck: sanitycheck defines test expected to fail as FAILED * :github:`29258` - net: Unable to establish TCP connections from Windows hosts * :github:`29257` - Race condition in k_queue_append and k_queue_alloc_append * :github:`29248` - board: nrf52840_mdk: support for qspi flash missing * :github:`29244` - k_thread_resume can cause k_sem_take with K_FOREVER to return -EAGAIN and crash * :github:`29239` - i2c: mcux driver does not prevent simultaneous transactions * :github:`29235` - Endless build loop after adding pinctrl dtsi * :github:`29223` - BLE one central connect multiple peripherals * :github:`29220` - ARC: tickless idle exit code destroy exception status * :github:`29202` - core kernel depends on minimal libc ``z_prf()`` * :github:`29195` - west fails with custom manifest * :github:`29194` - Sanitycheck block after passing some test * :github:`29183` - DHCPv4 retransmission interval gets too large * :github:`29175` - x86 fails all tests if CONFIG_X86_KPTI is disabled * :github:`29173` - uart_nrfx_uart fails uart_async_api_test * :github:`29166` - sanitycheck ``--test-only --device-testing --hardware-map`` shouldn't run tests on all boards from ``--build-only`` * :github:`29165` - shell_print doesn't support anymore %llx when used with newlib * :github:`29164` - net: accept() doesn't return an immediately usable descriptor * :github:`29162` - Data Access Violation when LOG_* is called on ISR context * :github:`29155` - CAN BUS support on Atmel V71 * :github:`29150` - CONFIG_BT_SETTINGS_CCC_LAZY_LOADING never loads CCC * :github:`29148` - MPU: twr_ke18f: many kernel application fails when allocate dynamic MPU region * :github:`29146` - canisotp: mimxrt1064_evk: no DT_CHOSEN_ZEPHYR_CAN_PRIMARY_LABEL defined cause tests failure * :github:`29145` - net: frdmk64f many net related applications meet hardfault, hal driver assert * :github:`29139` - tests/kernel/fatal/exception failed on nsim_sem_mpu_stack_guard board * :github:`29120` - STM32: Few issues on pinctrl generation script * :github:`29113` - Build failure with OSPD * :github:`29111` - Atmel SAM V71 UART_0 fail * :github:`29109` - HAL STM32 Missing ETH pin control configurations in DT files * :github:`29101` - Bluetooth: assertion fail with basic repeated extended advertisement API * :github:`29099` - net: dns: dns-sd: support for dns service discovery * :github:`29098` - ATT timeout worker not canceled by destroy, and may operate on disposed object * :github:`29095` - zefi.py has incorrect assertions * :github:`29092` - tests/drivers/uart/uart_async_api fails on nrf52840dk_nrf52840 (and additional platforms) * :github:`29089` - doc: boards: cc1352r_sensortag: fix minor rst issue * :github:`29083` - Bluetooth: Host: Inconsistent permission value during discovery procedure * :github:`29078` - nRF52840 doesn't start legacy advertisment after extended advertisment * :github:`29074` - #27901 breaks mikroe_* shields overlay * :github:`29070` - NXP LPC GPIO driver masked set does not use the mask * :github:`29068` - chosen zephyr,code-partition has no effect on ELF linking start address * :github:`29066` - kernel: k_sleep doesn't handle relative or absolute timeouts >INT_MAX * :github:`29062` - samples/bluetooth/peripheral_hr/sample.bluetooth.peripheral_hr_rv32m1_vega_ri5cy fails to build on rv32m1_vega_ri5cy * :github:`29059` - HAL: mchp: Missing PCR ids to control PM for certain HW blocks * :github:`29056` - tests/bluetooth/init/bluetooth.init.test_ctlr_dbg fails to build on nrf51dk_nrf51422 * :github:`29050` - Ugrade lvgl library * :github:`29048` - Removing pwr-gpio of rt1052 from devicetree will cause build error * :github:`29047` - Boards: nucleo_stm32g474re does not build * :github:`29043` - dirvers: eth_stm32_hal: No interrupt is generated on the MII interface. * :github:`29042` - CONFIG_SHELL_HELP=n fails to compile * :github:`29034` - error in samples/subsys/usb/cdc_acm * :github:`29025` - [Coverity CID :214882] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`29024` - [Coverity CID :214878] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`29023` - [Coverity CID :214877] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`29022` - [Coverity CID :214876] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`29021` - [Coverity CID :214874] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`29020` - [Coverity CID :214873] Argument cannot be negative in tests/posix/eventfd/src/main.c * :github:`29019` - [Coverity CID :214871] Side effect in assertion in tests/kernel/sched/preempt/src/main.c * :github:`29018` - [Coverity CID :214881] Unchecked return value in subsys/mgmt/ec_host_cmd/ec_host_cmd_handler.c * :github:`29017` - [Coverity CID :214879] Explicit null dereferenced in subsys/emul/spi/emul_bmi160.c * :github:`29016` - [Coverity CID :214875] Dereference after null check in subsys/emul/spi/emul_bmi160.c * :github:`29015` - [Coverity CID :214880] Out-of-bounds access in subsys/net/ip/tcp2.c * :github:`29014` - [Coverity CID :214872] Bad bit shift operation in drivers/ethernet/eth_w5500.c * :github:`29008` - BLE Connection fails to establish between two nRF52840-USB Dongles with Zephyr controller * :github:`29007` - OOT manifest+module discovery/builds fail * :github:`29003` - memory corruption in pkt_alloc * :github:`28999` - STM32: Transition to device tree based pinctrl configuration * :github:`28990` - Docs: Dead links to sample source directories * :github:`28979` - Automatic reviewer assignment for PR does not seem to work anymore * :github:`28976` - sanitycheck failing all tests for nsim_em7d_v22 * :github:`28970` - clarify thread life-cycle documentation * :github:`28956` - API-less devices aren't findable * :github:`28955` - undesired kernel debug log * :github:`28953` - winc1500 driver blocks on listen * :github:`28948` - hci_usb: ACL transfer not restarted after USB Suspend - Resume * :github:`28942` - ARC: nsim_hs_smp: huge zephyr.hex file generated on build * :github:`28941` - Civetweb: create separate directory * :github:`28938` - EFR32BGx Bluetooth Support * :github:`28935` - support code coverage in unit tests * :github:`28934` - pinmux: stm32: port remaining pinctrl DT serial definitions for STM32 based boards * :github:`28933` - mcuboot: Brick when using BOOT_SWAP_USING_MOVE and reset happens during images swap * :github:`28925` - west failed due to empty value in self.path * :github:`28921` - MCUboot / smp_svr sample broken in 2.4.0 * :github:`28916` - net_if_down doesn't clear address * :github:`28912` - Incorrect macro being used to init a sflist * :github:`28908` - The same buffers are shared by the 2 Ethernet controllers in the eth_mcux driver * :github:`28898` - lwm2m_client can't start if mcuboot is enabled * :github:`28897` - SPI does not work for STM32 min dev board * :github:`28893` - Double-dot in path's may cause problems with gcc under Windows * :github:`28887` - Bluetooth encryption request overrides ongoing phy update * :github:`28881` - tests/kernel/mem_protect/sys_sem: qemu_x86_64 intermittent failure * :github:`28876` - -p doesn't run a pristine build * :github:`28872` - Support ESP32 as Bluetooth controller * :github:`28870` - Peripheral initiated connection parameter update is ignored * :github:`28867` - ARM Cortex-M4: Semaphores could not be used in ISRs with priority 0? * :github:`28865` - Doc: Generate documentation using dts bindings * :github:`28854` - ``CONFIG_STACK_POINTER_RANDOM`` may be undefined * :github:`28847` - code_relocation sample does not work on windows * :github:`28844` - Double quote prepended when exporting CMAKE compile option using zephyr_get_compile_options_for_lang() * :github:`28833` - STM32: SPI DMA Driver - HW CS handling not compatible with spi_nor (Winbond W25Q) * :github:`28826` - nRF QSPI flash driver broken for GD25Q16 * :github:`28822` - Improve STM32 LL HAL usage * :github:`28809` - Enable bt_gatt_notify() to overwrite notified value before sending rather than queue values * :github:`28794` - RFC: API Change: k_work * :github:`28791` - STM32: Clock recovery system (CRS) support * :github:`28787` - lwm2m-client sample can't be build with openthread and DTLS * :github:`28785` - shell: It should be possible to get list of commands without pressing tab * :github:`28777` - Memory pool issue * :github:`28775` - Update to TFM v1.2 release * :github:`28774` - build failure: several bluetooth samples fail to build on nrf51dk_nrf51422 * :github:`28773` - Lower Link Layer code use upper link layer function have " undefined reference to" * :github:`28758` - ASSERTION FAIL [conn->in_retransmission == 1] with civetweb sample application * :github:`28745` - Bug in drivers/modem/hl7800.c * :github:`28739` - Bluetooth: Mesh: onoff_level_lighting_vnd sample fails provisioning * :github:`28735` - NULL pointer access in zsock_getsockname_ctx with TCP2 * :github:`28723` - Does not respect python virtualenv * :github:`28722` - Bluetooth: provide ``struct bt_conn`` to ccc_changed callback * :github:`28714` - Bluetooth: PTS upper tester: GAP/CONN/NCON/BV-02-C Fails because of usage of NRPA * :github:`28709` - phandle-array doesn't allow array of just phandles * :github:`28706` - west build -p auto -b nrf52840dk_nrf52840 error: HAS_SEGGER_RTT * :github:`28701` - ASSERTION FAIL [!radio_is_ready()] * :github:`28699` - Bluetooth: controller: Speed up disconnect process when slave latency is used * :github:`28694` - k_wakeup follwed by k_thread_resume call causes system freeze * :github:`28693` - FCB support for non-0xFF flash erase values * :github:`28691` - tests: arch: arm: arm_thread_swap: fails with bus fault * :github:`28688` - Bluetooth: provide ``struct bt_gatt_indicate_params`` to ``bt_gatt_indicate_func_t`` * :github:`28670` - drivers: flash: bluetooth: stm32wb: attempt to erase internal flash before enabling Bluetooth cause fatal error * :github:`28664` - Decide whether to enable HW_STACK_PROTECTION by default * :github:`28650` - GCC-10.2 link issue w/g++ on aarch64 * :github:`28629` - tests: kernel: common: and common.misra are failing on nrf52840dk * :github:`28620` - 6LowPAN ipsp: ping host -> c failes, ping c -> host works. after that: ping host -> c works * :github:`28613` - cannot set GDB watchpoints on QEMU x86 with icount enabled * :github:`28590` - up_squared_adsp:running tests/kernel/smp/ failed * :github:`28589` - up_squared_adsp:running tests/kernel/workq/work_queue/ failed * :github:`28587` - Data corruption while serving large files via HTTP with TCP2 * :github:`28556` - mec15xxevb_assy6853:running tests/kernel/sched/schedule_api/ failed * :github:`28547` - up_squared: tests/subsys/debug/coredump failed using twister command. * :github:`28544` - Null pointer dereference in ll_adv_aux_ad_data_set * :github:`28533` - soc: ti_simplelink: cc13xx-cc26xx: kconfig for subghz 802.15.4 * :github:`28509` - series-push-hook.sh: Don't parse then-master-to-latest-master commits after rebase to lastest * :github:`28504` - dfu: dfu libraries might fails to compile on redefined functions while building MCUBoot * :github:`28502` - USB DFU class: support MCUBoot CONFIG_SINGLE_APPLICATION_SLOT * :github:`28493` - Sanitycheck on ARC em_starterkit_em7d has many tests timeout * :github:`28483` - Fix nanosleep(2) for sub-microsecond durations * :github:`28473` - Mcuboot fails to compile when using single image and usb dfu * :github:`28469` - Unable to capture adc signal at 8ksps when using nrf52840dk board. * :github:`28462` - SHIELD not handled correct in CMake when using custom board * :github:`28461` - ``HCI_CMD_TIMEOUT`` when setting ext adv data in the hci_usb project * :github:`28456` - TOOLCHAIN_LD_FLAGS setting of -mabi/-march aren't propagated to linker invocation on RISC-V * :github:`28442` - How handle IRQ_CONNECT const requirement? * :github:`28406` - Condition variables * :github:`28383` - bq274xx sample is not working * :github:`28363` - ssd16xx: off-by-one with non-multiple-of-eight heights * :github:`28355` - Document limitations of net_buf queuing functions * :github:`28309` - Sample/subsys/fs/littlefs with board=nucleo_f429zi don't work * :github:`28299` - net: lwm2m: Improve token handling * :github:`28298` - Deep sleep(system off) is not working with LVGL and display driver * :github:`28296` - test_essential_thread_abort: lpcxpresso55s16_ns test failure * :github:`28278` - PWM silently fails when changing output frequency on stm32 * :github:`28220` - flash: revise API to remove block restrictions on write operations * :github:`28177` - gPTP gptp_priority_vector struct field ordering is wrong * :github:`28176` - [Coverity CID :214217] Out-of-bounds access in tests/kernel/mem_protect/mem_map/src/main.c * :github:`28175` - [Coverity CID :214214] Uninitialized pointer read in tests/benchmarks/data_structure_perf/rbtree_perf/src/rbtree_perf.c * :github:`28170` - [Coverity CID :214222] Unrecoverable parse warning in include/ec_host_cmd.h * :github:`28168` - [Coverity CID :214218] Unused value in subsys/mgmt/osdp/src/osdp.c * :github:`28159` - [Coverity CID :214216] Logically dead code in drivers/pwm/pwm_stm32.c * :github:`28155` - sam_e70_xplained:running samples/net/sockets/civetweb/ failed * :github:`28124` - Linking external lib against POSIX API * :github:`28117` - CoAP/LWM2M: Clean Packet Retransmission Concept * :github:`28113` - Embed precise Zephyr version & platform name in sanitycheck output .xml * :github:`28094` - samples: drivers: spi_flash_at45: Not work for boards without internal flash driver * :github:`28092` - Make SPI speed of SDHC card configurable * :github:`28014` - tests: kernel: mem_protect: sys_sem: failed when CONFIG_FPU is activated * :github:`27999` - Add QSPI tests for microchip mec1521 board, drivers are in zephyr/drivers/spi, to be tested on mec15xxevb_assy6853 * :github:`27997` - Errors in copy paste lengthy script into Shell Console * :github:`27981` - Low UART utilization for hci_uart * :github:`27957` - flash signed binaries: key path and version * :github:`27914` - frdm_k64f async uart api * :github:`27892` - [v2.1.x] lib: updatehub: Improve download on slow networks and security fix * :github:`27890` - [v2.2.x] lib: updatehub: Improve download on slow networks and security fix * :github:`27881` - Zephyr requirements.txt fails to install on Python 3.9rc1 * :github:`27879` - Make i2c_slave callbacks public in the documentation * :github:`27856` - Support per thread runtime statistics * :github:`27846` - Weird ADC outliers on nrf52 * :github:`27841` - samples: disk: unable to access sd card * :github:`27829` - sys_mutex and futex missing documentation * :github:`27809` - Cannot enable MPU for nucleo_l552ze_q_ns * :github:`27785` - memory domain arch implementation not correct with respect to SMP on ARC * :github:`27716` - Bluetooth: Mesh: Devices relay their own messages (even with relay disabled!) * :github:`27677` - RFC: Get rid of shell UART device selection in Kconfig * :github:`27672` - [v2.2] BLE Transaction Collision * :github:`27633` - arm64 SMP * :github:`27628` - stm32: i2c bus failure when using USB * :github:`27622` - Power management for modems using PPP * :github:`27600` - JSON Api refuse to decode null value * :github:`27596` - logging: backend inconsistency with console and shell * :github:`27583` - sanitycheck does not fail on SRAM overflow, add option to make it fail on those cases. * :github:`27574` - mec15xxevb_assy6853:arch.arm.arch.arm.no.multithreading failed to run * :github:`27573` - coverage: When enable coverage, some testcases need more time * :github:`27570` - up_squared:logging.add.logging.add.async failed * :github:`27561` - drivers: gpio: pca9555 : Add GPIO driver enable interrupt support * :github:`27559` - How to use stm32cubeIDE to build and debug? * :github:`27525` - Including STM32Cube's USB PD support to Zephyr * :github:`27510` - [v1.14] Bluetooth: controller: Fix uninit conn context after invalid channel map * :github:`27506` - driver: peci: mchp: Ping command is failing due to improper tx wait timeout. * :github:`27490` - arch/common/isr_tables.c compilation fails with CONFIG_NUM_IRQS=0 * :github:`27487` - storage/stream: should use only flash driver public API * :github:`27468` - BT Host: Periodic Advertisement delayed receive * :github:`27467` - BT Host: Periodic Advertiser List * :github:`27466` - BT Host: Periodic Advertisement Sync Transfer (PAST) * :github:`27457` - Add support for Nordic nrfx PDM driver for Nordic Thingy52 * :github:`27423` - RFC: API change: clock_control: Change parameters of clock_control_async_on * :github:`27417` - CivetWeb Enable WebSocket * :github:`27396` - samples/subsys/logging/logger timeout when sanitycheck enable coverage, it needs a filter * :github:`27369` - spi: stm32: dma: rx transfer error when spi_write called * :github:`27367` - Sprintf - error while sending data to SD card * :github:`27350` - ADC: adc shell failure when mismatch with dts device label * :github:`27332` - [v2.3.x] lib: updatehub: Improve download on slow networks and security fix * :github:`27299` - espi: xec: Whenever eSPI host indicates we are entering DnX mode, notification doesn't reach application * :github:`27279` - CMSIS RTOS v1 Signals Implementation Issue * :github:`27231` - Sending data to .csv file on SD card - ERROR CS control inhibited (no GPIO device) * :github:`27195` - Sanitycheck: BinaryHandler can't kill children processes * :github:`27176` - [v1.14] Restore socket descriptor permission management * :github:`27174` - TCP Server don't get the right data from the client * :github:`27146` - [Coverity CID :211510] Unchecked return value in lib/posix/semaphore.c * :github:`27122` - Implement watchdog driver for mimxrt1050_evk * :github:`27068` - ESP-IDF Bootloader bootloop * :github:`27055` - BlueZ with ESP32 boards supported or not? * :github:`27047` - zefi.py assumes host GCC is x86 * :github:`27031` - Zephyr OpenThread Simulation * :github:`27020` - civetweb issues * :github:`27006` - unsynchronized newlib uintptr_t and PRIxPTR definition on xtensa * :github:`26987` - [Coverity CID :211475] Unintended sign extension in drivers/sensor/wsen_itds/itds.c * :github:`26975` - Control never returns from stm32_i2c_msg_write(), when SCL is pulled low permanently (hardware fault occurs) * :github:`26961` - occasional sanitycheck failures in samples/subsys/settings * :github:`26949` - sanitycheck gets overwhelmed by console output * :github:`26912` - arm: cortex_r: config_userspace: hang during early power-up * :github:`26873` - WIFI_ESP: sockets left opened after unexpected reset of ESP * :github:`26829` - GSM modem example on stm32f103 bluepill * :github:`26819` - drivers: modem: SARA modem driver leaks sockets * :github:`26807` - Bluetooth HCI USB sample is not working * :github:`26799` - Introduce p99 * :github:`26794` - arc: smp: different sanitycheck results of ARC hsdk's 2 cores and 4 cores configuration * :github:`26732` - Advertise only on single bluetooth channel * :github:`26722` - uarte_nrfx_poll_out() in NRF UARTE driver does not work with hardware flow control * :github:`26665` - Implement reset for ARC development boards * :github:`26656` - SAM0 USB transfer slot leak * :github:`26637` - How to identify sensor device? * :github:`26584` - Multicast emission is only possible for ipv4 starting with 224. * :github:`26533` - Support newlib for Aarch64 architecture * :github:`26522` - Reported "Supported shields" list includes boards * :github:`26515` - timers: platforms using cortex_m_systick does not enter indefinite wait on SLOPPY_IDLE * :github:`26500` - sanitycheck reports failing tests with test_slice_scheduling() * :github:`26488` - Bluetooth: Connection failure using frdm_kw41z shield * :github:`26486` - possible SMP race with k_thread_join() * :github:`26477` - GPIO sim driver * :github:`26443` - sanitycheck shall generate results and detailed information about tests and environment in json format. * :github:`26409` - Clearing of previously initialized data during IPv6 interface init causes infinite loop, memory corruption in timer ISR * :github:`26383` - OpenThread NCP radio-only * :github:`26372` - qspi driver does not work if multithreading is disabled * :github:`26330` - tcp: low bulk receive performance due to window handling * :github:`26315` - ieee802154: cc13xx_cc26xx: sub_ghz support * :github:`26312` - drivers: ieee802154: cc13xx_cc26xx: adopt hal/ti rf driverlib * :github:`26275` - USB MSC fails 'Command Set Test' from USB3CV. * :github:`26272` - Cannot use alternative simulation runner with sanitycheck * :github:`26227` - icount support for qemu_arc_{em,hs} * :github:`26225` - x86_64 doesn't seem to be handling spurious interrupts properly * :github:`26219` - sys/util: add support for mapping lists with per-element terminal symbols * :github:`26172` - Zephyr Master/Slave not conforming with Core Spec. 5.2 connection policies * :github:`26163` - qemu_arc_{em,hs} keeps failing in CI on tests/kernel/lifo/lifo_usage * :github:`26142` - cmake warning: "Policy CMP0077 is not set" * :github:`26084` - 2.4 Release Checklist * :github:`26072` - refactor struct device to reduce RAM demands * :github:`26051` - shell: uart: Allow a change in the shell initalisation to let routing it through USB UART * :github:`26050` - devicetree: provide access to node ordinal * :github:`26026` - RFC: drivers: pwm: add functions for capturing pwm pulse width and period * :github:`25956` - Including header files from modules into app * :github:`25927` - ARM: Core Stack Improvements/Bug fixes for 2.4 release * :github:`25918` - qemu_nios2 crash when enabled icount * :github:`25832` - [test][kernel][lpcxpresso55s69_ns] kernel cases meet ESF could not be retrieved successfully * :github:`25604` - USB: enable/disable a class driver at runtime * :github:`25600` - wifi_eswifi: Unable to start TCP/UDP client * :github:`25592` - Remove checks on board undocumented DT strings * :github:`25597` - west sign fails to find header size or padding * :github:`25508` - tests: add additonal power management tests * :github:`25507` - up_squared:tests/portability/cmsis_rtos_v2 failed. * :github:`25482` - outdated recommendations for SYS_CLOCK_TICKS_PER_SEC * :github:`25466` - log build errors are not helpful * :github:`25434` - nRF5340 Bluetooth peripheral_hr sample high power consumption * :github:`25413` - soc: ti_simplelink: kconfig: ble: placeholder for hal_ti * :github:`25409` - Inconsistent naming of Kconfig options related to stack sizes of various Zephyr components * :github:`25395` - Websocket Server API * :github:`25379` - Bluetooth mesh example not working * :github:`25314` - Bluetooth: controller: legacy: Backport conformance test related changes * :github:`25302` - lwm2m client sample bootstrap server support * :github:`25182` - Raspberry Pi 4B Support * :github:`25173` - k_sem_give(struct k_sem \sem) should report failure when the semaphore is full :github:`25164` - Remove ``default:`` functionality from devicetree bindings * :github:`25015` - Bluetooth Isochronous Channels Support * :github:`25010` - disco_l475_iot1 don't confirm MCUBoot slot-1 image * :github:`24803` - ADC driver test hangs on atsame54_xpro * :github:`24652` - sanitycheck doesn't keep my cores busy * :github:`24453` - docs: Allow to use the exact current zephyr version number in place of /latest/ in documentation URLs * :github:`24358` - deprecate and remove old k_mem_pool / sys_mem_pool APIs * :github:`24338` - UICR & FICR missing from nRF52* devicetree files * :github:`24211` - [v2.2.x] lib: updatehub: Not working on Zephyr 2.x * :github:`23917` - Kconfig: problems with using backslash-escapes in "default" value of "string" option * :github:`23874` - Test case to check registers data * :github:`23866` - sample hci_usb fails with zephyr 2.2.0 (worked with zephyr 2.1.0) * :github:`23729` - hifive1_revb fails to work with samples/subsys/console/getline * :github:`23314` - Bluetooth: controller: Use defines for 625 us and 1250 us * :github:`23302` - Poor TCP performance * :github:`23212` - ARC: SMP: Enable use of ARConnect Inter-core Debug Unit * :github:`23210` - mimxrt1050_evk:tests/net/iface failed with v1.14 branch. * :github:`23063` - CMSIS v2 osThreadJoin does not work if thread exits with osThreadExit * :github:`23062` - thread_num / thread_num_dynamic are never decremented in CMSIS v2 thread.c * :github:`22942` - Missing TX power options for nRF52833 * :github:`22771` - z_x86_check_stack_bounds() doesn't work right for nested IRQs on x86-64 * :github:`22703` - Implement ADC driver for lpcxpresso55s69 * :github:`22411` - AArch64 / Cortex-A port improvements / TODO * :github:`22333` - drivers: can: Check bus-timing values at compile-time * :github:`22247` - Discussion: Supporting the Arduino ecosystem * :github:`22198` - BMA280 Sample Code * :github:`22185` - Add Thread Local Storage (TLS) support * :github:`22060` - Build fails with gcc-arm-none-eabi-9-2019-q4-major * :github:`21991` - memory domain locking may not be entirely correct * :github:`21495` - x86_64: interrupt stack overflows are not caught * :github:`21462` - x86_64 exceptions are not safely preemptible, and stack overflows are not caught * :github:`21273` - devicetree: improved support for enum values * :github:`21238` - Improve Zephyr HCI VS extension detection * :github:`21216` - Ztest "1cpu" cases don't retarget interrupts on x86_64 * :github:`21179` - Reduce RAM consumption for civetweb HTTP sample * :github:`20980` - ESP32 flash error with segment count error using esptool.py from esp-idf * :github:`20925` - tests/kernel/fp_sharing/float_disable crashes on qemu_x86 with CONFIG_KPTI=n * :github:`20821` - Do USE\_$DT\_$CODE\_PARTITION and FLASH_LOAD_OFFSET/SIZE need to be user-configurable? * :github:`20792` - sys_pm: fragility in residency policy * :github:`20775` - sys_pm_ctrl: fragility in managing state control * :github:`20686` - tests/kernel/fp_sharing/float_disable failed when code coverage is enabled on qemu_x86. * :github:`20518` - [Coverity CID :205647]Memory - illegal accesses in /tests/arch/x86/info/src/memmap.c * :github:`20337` - sifive_gpio: gpio_basic_api test fails * :github:`20262` - dt-binding for timers * :github:`20118` - Zephyr BLE stack to work on the CC2650 Launchpad * :github:`19850` - Bluetooth: Mesh: Modular settings handling * :github:`19530` - Enhance sanitycheck/CI for separating build phase from testing * :github:`19523` - Can't build fade-led example for any Nordic board * :github:`19511` - net: TCP: echo server blocks after a packet with zero TCP options * :github:`19497` - log subsystem APIs need to be clearly namespaced as public or private * :github:`19467` - Error building samples with PWM * :github:`19448` - devicetree: support disabled devices * :github:`19435` - how to change uart tx rx pins in zephyr * :github:`19380` - Potential bugs re. 'static inline' and static variables * :github:`19244` - BLE throughput of DFU by Mcumgr is too slow * :github:`19138` - zassert prints to UART even when RTT is selected * :github:`19100` - LwM2M sample with DTLS: does not connect * :github:`19003` - bluetooth : Mesh: adv thread can be replace by other methods. * :github:`18927` - settings: deprecate base64 encoding * :github:`18778` - soc: arm: nordic_nrf: Defining DT\_..._DEV_NAME * :github:`18728` - sam_e70_xplained:tests/subsys/logging/log_core failed. * :github:`18608` - PCA9685 PWM driver is broken * :github:`18607` - DesignWare PWM driver is broken * :github:`18601` - LwM2M client sample: an overlay for OpenThread support * :github:`18551` - address-of-temporary idiom not allowed in C++ * :github:`18529` - fs/fcb: consider backport of mynewt fixes * :github:`18276` - irq_connect_dynamic() is not tested on all arches * :github:`17893` - dynamic threads don't work on x86 in some configurations * :github:`17787` - openocd unable to flash hello_world to cc26x2r1_launchxl * :github:`17743` - cross compiling for RISCV32 fails as compiler flags are not supplied by board but must be in target.cmake * :github:`17645` - VSCode debugging Zephyr application * :github:`17545` - Licensing and reference to public domain material * :github:`17300` - [Zephyr v1.14.0] mcumgr: stm32: Strange Build warnings when counter is enabled * :github:`17023` - userspace: thread indexes are not released when dynamic threads lose all references * :github:`17014` - reentrancy protection in counter drivers? * :github:`16766` - net: net_pkt_copy don't work as expected when data was pulled from destination * :github:`16544` - drivers: spi: spi_mcux_lpspi: inconsistent chip select behaviour * :github:`16438` - fs/FCB fs/NVS : requires unaligned flash read-out length capabilities, * :github:`16237` - disco_l475_iot1: samples/bluetooth/ipsp ko since 3151d26 * :github:`16195` - k_uptime_delta(): Defective by design * :github:`15944` - stm32: New Driver for FMC/FSMC * :github:`15713` - MCUMGR_LOG build error * :github:`15570` - Unbonded peripheral gets 'Tx Buffer Overflow' when erasing bond on master * :github:`15372` - logging can't dump exceptions without losing data with CONFIG_LOG_PRINTK * :github:`14591` - Infineon Tricore architecture support * :github:`14571` - TCP: sending lots of data deadlocks with slow peer * :github:`14300` - Bluetooth connection using central and peripheral samples in nrf52840 * :github:`13955` - stm32: Implement async uart api * :github:`13591` - tests/blutooth/tester: ASSERTION FAIL due to Recursive spinlock when running bt tester on qemu-cortex-m3 * :github:`13396` - Cannot connect to Galaxy S8 via BLE * :github:`13244` - How to encrypt advertise packet with zephyr and nrf52832 * :github:`12368` - File descriptors: Compile fails with non-POSIX out-of-tree libc * :github:`12353` - intel_s1000: SPI Flash Erase command doesn't work when booting from flash * :github:`12239` - BLE400 / nRF51822 (nRF51) PWM clock too low (servo-motor example) * :github:`12150` - Power management on nRF52 boards * :github:`11912` - net: SimpleLink: Create real cross-platform port * :github:`11770` - Multiprotocol feature for BLE/Thread * :github:`10904` - Requirements for driver devices generation using device tree * :github:`10857` - Migrating from CMSIS-Core to DeviceTree results in loss of type information * :github:`10460` - Bluetooth: settings: No space to store CCC config after successful pairing * :github:`10158` - Have support for probot with Zephyr * :github:`10022` - Porting Modbus Library: Need some guidance * :github:`9944` - sockets: Connect doesn't send new SYN in case the first connection attempt fails * :github:`9883` - DTS processing generates unit_address_vs_reg warning on entries with 'reg' * :github:`9875` - Bluetooth: Host LE Extended Advertising * :github:`9783` - LwM2M: Cannot create object instance without specifying instance number * :github:`9509` - Unable to upload firmware over serial with mcumgr * :github:`9406` - Generate DTS 'compatible' based compilation flags * :github:`9403` - is Support C++ standard library? * :github:`9087` - driver: CAN interface should be compatible with CAN-FD interface * :github:`8499` - Device Tree support overhaul * :github:`8393` - ``CONFIG_MULTITHREADING=n`` builds call ``main()`` with interrupts locked * :github:`8008` - net: Sockets (and likely net_context's) should not be closed behind application's back * :github:`7939` - Connections to TI CC254x break after conn_update * :github:`7404` - arch: arm: MSP initialization during early boot * :github:`7331` - Precise time sync through BLE mesh. * :github:`6857` - need to improve filtering and coverage in sanitycheck * :github:`6818` - Question: Is Lightweight OpenMP implementation supported in Zephyr? Or any plan? * :github:`6648` - Trusted Execution Framework: practical use-cases (high-level overview) * :github:`6199` - STM32: document dts porting rules * :github:`6040` - Implement flash driver for LPC54114 * :github:`5626` - Building samples failed * :github:`4420` - net: tcp: RST handling is weak * :github:`3675` - LE Adv. Ext.: Extended Scan with PHY selection for non-conn non-scan un-directed without aux packets * :github:`3674` - LE Adv. Ext.: Non-Connectable and Non-Scannable Undirected without auxiliary packet * :github:`3893` - Enhance k_stack_push() to check k_stack->top to avoid corruption * :github:`3719` - Multiple consoles support. * :github:`3441` - IP stack: No TCP send window handling * :github:`3102` - Make newlib libc the default c library * :github:`2247` - LE Controller: Change hal/ into a set of drivers ```	/content/code_sandbox/doc/releases/release-notes-2.5.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	31,000
```restructuredtext :orphan: .. _zephyr_3.5: Zephyr 3.5.0 ############ We are pleased to announce the release of Zephyr version 3.5.0. Major enhancements with this release include: * Added support for linkable loadable extensions (llext) * Added native_sim simulator target (successor to native_posix) * Added new battery charger driver API * Added new hardware spinlock driver API * Added new modem subsystem * Added support for 45+ new boards * Networking: improvements to CoAP, Connection Manager, DHCP, Ethernet, gPTP, ICMP, IPv6 and LwM2M * Bluetooth: improvements to the Controller, Audio, Mesh, as well as the host stack in general * Improved LVGL graphics library integration * Integrated support with the CodeChecker static analyzer * Picolibc is now the default C standard library An overview of the changes required or recommended when migrating your application from Zephyr v3.4.0 to Zephyr v3.5.0 can be found in the separate :ref:`migration guide<migration_3.5>`. 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: path_to_url * CVE-2023-3725 `Zephyr project bug tracker GHSA-2g3m-p6c7-8rr3 <path_to_url`_ * CVE-2023-4257 `Zephyr project bug tracker GHSA-853q-q69w-gf5j <path_to_url`_ * CVE-2023-4258 `Zephyr project bug tracker GHSA-m34c-cp63-rwh7 <path_to_url`_ * CVE-2023-4259 `Zephyr project bug tracker GHSA-gghm-c696-f4j4 <path_to_url`_ * CVE-2023-4260 `Zephyr project bug tracker GHSA-gj27-862r-55wh <path_to_url`_ * CVE-2023-4263 `Zephyr project bug tracker GHSA-rf6q-rhhp-pqhf <path_to_url`_ * CVE-2023-4264 `Zephyr project bug tracker GHSA-rgx6-3w4j-gf5j <path_to_url`_ * CVE-2023-4424: Under embargo until 2023-11-01 * CVE-2023-5055: Under embargo until 2023-11-01 * CVE-2023-5139: Under embargo until 2023-10-25 * CVE-2023-5184 `Zephyr project bug tracker GHSA-8x3p-q3r5-xh9g <path_to_url`_ * CVE-2023-5563 `Zephyr project bug tracker GHSA-98mc-rj7w-7rpv <path_to_url`_ * CVE-2023-5753 `Zephyr project bug tracker GHSA-hmpr-px56-rvww <path_to_url`_ Kernel ****** * Added support for dynamic thread stack allocation via :c:func:`k_thread_stack_alloc` * Added support for :c:func:`k_spin_trylock` * Added :c:func:`k_object_is_valid` to check if a kernel object is valid. This replaces code that has been duplicated throughout the tree. Architectures ************* * ARC * Introduced the scalar port for ARC VPX processors * Introduced support for ARCv3 HS (both 32 and 64 bit) SMP platforms with up to 12 CPU cores * Reworked GNU helper tools usage for ARC MWDT toolchain. Now helper tools can be used from Zephyr SDK (if SDK is installed) * Fixed dynamic thread stack allocation * Fixed STR assembly macro offset calculation issue which may cause build error for ARCv3 64bit * Cleaned-up and made more user friendly handling of the ARC MWDT toolchain path (ARCMWDT_TOOLCHAIN_PATH) * ARM * Architectural support for Arm Cortex-M has been separated from Arm Cortex-A and Cortex-R. This includes separate source modules to handle tasks like IRQ management, exception handling, thread handling and swap. For implementation details see :github:`60031`. * ARM64 * RISC-V * Added support for detecting null pointer exception using PMP. * Added the :kconfig:option:`CONFIG_RISCV_RESERVED_IRQ_ISR_TABLES_OFFSET` option to allow IRQ vector at a specified offset to meet the requirements set by the Core-Local Interrupt Controller RISC-V specification. * Added the :kconfig:option:`CONFIG_RISCV_SOC_HAS_CUSTOM_SYS_IO` option to allow the use of custom system input/output functions. * Introduced the :kconfig:option:`CONFIG_RISCV_TRAP_HANDLER_ALIGNMENT` option to set the correct alignment of the trap handling code which is dependent on the ``MTVEC.BASE`` field size and is platform or application-specific. * Xtensa * Added basic MMU v2 Support. * x86 * Added support for Intel Alder Lake boards * Added support for Intel Sensor Hub (ISH) * POSIX * Has been reworked to use the native simulator. * New boards have been added. * For the new boards, embedded C libraries can be used, and conflicts with the host symbols and libraries avoided. * The :ref:`POSIX OS abstraction<posix_support>` is supported in these new boards. * AMP targets are now supported. * Added support for LLVM source profiling/coverage. Bluetooth ********* * Audio Improved memory usage of codec configurations and codec capabilities. Fixed several bugs in BAP and the BAP-related services (ASCS, PACS, BASS), as well as missing features such as proper notification handling. * Added BAP ``bt_bap_stream_get_tx_sync`` * Added CAP stream send and tx sync * Added ``bt_audio_codec_cap_get`` helper functions * Added support for long read/write in CAP * Fixed ASCS Source ASE link loss state transition * Fixed ASCS possible ASE leak * Fixed ASCS to drop ISO PDUs if ASE is not in streaming state * Fixed BAP ``bt_bap_scan_delegator_find_state`` implementation * Fixed BAP issue with PA sync and ID in ``broadcast_sink_create`` * Fixed TMAS characteristic permissions * Fixed ``tbs_client`` missing discovery complete event * Fixed audio stack to accept empty CCID list in audio metadata * Fixed bad size of metadata_backup in ASCS * Fixed possible ASCS ASE stuck in releasing state * Refactored ``bt_audio_codec_cap`` to flat arrays * Refactored ``bt_audio_codec_cfg`` to flat arrays * Removed ``CONFIG_BT_PACS_{SNK,SRC}_CONTEXT`` * Removed scanning and PA sync from broadcast sink * Renamed ``bt_codec`` to ``bt_audio_codec_{cap, conf, data}`` * Renamed codec qos framing * Replaced ``BT_AUDIO_CODEC_LC3_ID`` -> ``BT_HCI_CODING_FORMAT_LC3`` * Replaced ``BT_AUDIO_CODEC_PARSE_ERR_`` values with errno values. * Reworked PACS notify system * Updated ASCS ISO QOS based on BAP QOS * Updated BAP to filter PA data duplicates by default * Updated CSIP to unlock Non-bonded devices immediately. * Updated PACS to notify bonded clients on reconnect * Updated ``bt_cap_stream_ops_register`` to always register BAP callbacks * Updated the ASCS ACL disconnect behavior * Updated to split ``bt_audio_codec_meta_get`` to ``cfg`` and ``cap`` * Direction Finding * Host * Added SMP bondable flag overlay per connection * Added USE_NRPA advertising option * Added ``BT_CONN_PARAM_ANY`` to allow setting any value to connection parameters * Added advanced broadcast ISO parameters * Added advanced unicast ISO parameters * Added new API to manage Bluetooth settings storage * Fixed HCI ISO Data packets fragmentation * Fixed HCI ISO SDU length sent to controller * Fixed OTS ``bt_ots_init`` parameter struct naming * Fixed OTS memory leak while procedure is not finished * Fixed a connection reference leak * Fixed forced pairing request handling * Fixed host to invalidate the Resolvable Private Address when starting legacy advertising * Fixed issue with ``bt_iso_cig_reconfigure`` * Fixed possible buffer overflow in ``bt_conn_le_start_encryption`` * Fixed some SMP issues * Fixed to abort pairing if connection disconnected * Updated L2CAP accept callbacks * Updated LE L2CAP connected callback to be after connection response * Updated PAwR implementation to use RPA as responder address if BT_PRIVACY=y * Mesh * Added TF-M support. * Added support to use both tinycrypt and PSA based crypto * Added full virtual addresses support with the collisions resolution. The :kconfig:option:`CONFIG_BT_MESH_LABEL_NO_RECOVER` Kconfig option is introduced to restore the addresses for the subscription list and model publication. * Added statistic module. * Fixed an issue where a node acting as a LPN was triggering Friend Poll messages when sending a segmented message over the loopback interface. * Fixed an issue where provisioning completes successfully on a node when the identical Public Key is used by a provisioner. * Fixed an issue where the :c:func:`settings_load` function called from a cooperative thread other than the system workqueue caused the GATT Mesh Proxy Service registration to fail. * Fixed an issue where a node could enter IV Update in Progress state if an old SNB with the current IV Index and IV Update flag set to 1 was resent. * Mesh Protocol v1.1 changes * Added storing Private GATT Proxy state persistently. * Added support for Firmware Distribution Upload OOB Start message in the Firwmware Distribution Server model. The message support can be enabled with the :kconfig:option:`CONFIG_BT_MESH_DFD_SRV_OOB_UPLOAD` Kconfig option. * Added extended provisioning protocol timeout when OOB methods are used in the provisioning. * Added support for Composition Data Pages 2, 129 and 130. * Added documentation for Composition Data Pages 0, 1, 2, 128, 129 and 130. * Added documentation for the Segmentation and Reassembly in the Transport layer. * Added documentation for the SAR Configuration models * Fixed an issue where the Opcode Aggregator Server model did not compile without the Opcode Aggregator Client model. * Fixed an issue where the identity address was used in Private GATT Proxy advertisements instead of Non-Resolvable Private Addresses. * Fixed the Proxy Privacy parameter support. * Fixed an issue where the Composition Data Page 128 was not present on a node that has instantiated the Remote Provisioning Server model. * Fixed an issue where the Large Composition Data Server model did not support Composition Data Pages other then 0. * Fixed an issue where the Remote Provisioning Client model instanted on a node together with the Remote Provisioning Server model could not reprovision itself. * Fixed an issue where the acknowledgment timer in the Segmentation and Reassembly was not restarted when the incoming Segment Acknowledgment message did not contain at least one segment newly marked as acknowledged. * Fixed an issue where the On-Demand Private Proxy Server and Client models had interdependency that did not allow to compile them separately. * Controller Improved support for Broadcast and Connected Isochronous channels in the Controller, enabling LE audio application development. The Controller is experimental, is missing implementations for interleaved packing in Isochronous channels' lower link layer. * Added Checks for minimum sizes of Adv PDUs * Added Kconfig Option to ignore Tx HCI ISO Data Packet Seq Num * Added Kconfig for avoiding ISO SDU fragmentation * Added Kconfig to maximize BIG event length and preempt PTO & CTRL subevents * Added ``BT_CTLR_EVENT_OVERHEAD_RESERVE_MAX`` Kconfig * Added memory barrier to ticker transactions * Added missing nRF53x Tx Power Kconfig * Added support for Flush Timeout in Connected ISO * Fixed BIS payload sliding window overrun check * Fixed CIS Central FT calculation * Fixed CIS Central error handling * Fixed CIS asymmetric PHY usage * Fixed CIS encryption when DF support enabled * Fixed ISO-AL for quality tests and time stamps * Fixed PHY value in HCI LE CIS Established Event * Fixed ULL stuck in semaphore under rare conditions * Fixed assertion due to late PER CIS active set * Fixed compiler instruction re-ordering that caused assertions * Fixed connected ISO dynamic tx power * Fixed failing advertising conformance tests * Fixed handling received Auxiliary PDUs when Coded PHY not supported * Fixed leak in scheduled ticker node when rescheduling ticker nodes * Fixed missing host feature reset * Fixed nRF53 SoC back-to-back PDU chaining * Fixed nRF53 SoC back-to-back Tx Rx implementation * Fixed regression in Adv PDU overflow calculation * Fixed regression in observer that caused assertions and scheduling stall * Fixed use of pre-programmed PPI on nRF SoCs * Removed HCI ISO data with invalid status in preparation for FT support * Updated Extended Advertising Report to not be generated when ``AUX_ADV_IND`` not received * Updated to have ``EVENT_OVERHEAD_START_US`` verbose assertion in each state/role LLL * Updated to stop following ``aux_ptr`` if ``DATA_LEN_MAX`` is reached during extended scanning Boards & SoC Support ******************** * Added support for these SoC series: * Nuvoton NuMaker M46x series * Added support for STM32F072X8 SoC variants * Added support for STM32L051X6 SoC variants * Added support for STM32L451XX SoC variants * Added support for STM32L4Q5XX SoC variants * Added support for STM32WBA SoC series * Removed support for these SoC series: * Made these changes in other SoC series: * i.MX RT SOCs no longer enable CONFIG_DEVICE_CONFIGURATION_DATA by default. boards using external SDRAM should set CONFIG_DEVICE_CONFIGURATION_DATA and CONFIG_NXP_IMX_EXTERNAL_SDRAM to enabled. * i.MX RT SOCs no longer support CONFIG_OCRAM_NOCACHE, as this functionality can be achieved using devicetree memory regions * Refactored ESP32 SoC folders. So now these are a proper SoC series. * RP2040: Changed to reset the I2C device on initializing * Added support for these ARC boards: * Added support for nsim_vpx5 - simulation (nSIM) platform with ARCv2 VPX5 core, close to vpx5_integer_full template * Added support for nsim_hs5x_smp_12cores - simulation (nSIM) platform with 12 cores SMP 32-bit ARCv3 HS * Added support for nsim_hs6x_smp_12cores - simulation (nSIM) platform with 12 cores SMP 64-bit ARCv3 HS * Added support for these ARM boards: * Nuvoton NuMaker Platform M467 * ST Nucleo U5A5ZJ Q * ST Nucleo WBA52CG * Added support for these ARM64 boards: * Added support for these RISC-V boards: * Added support for these X86 boards: * Added support for these Xtensa boards: * Added ``esp32_devkitc_wroom`` and ``esp32_devkitc_wrover``. * Added ``esp32s3_luatos_core``. * Added ``m5stack_core2``. * Added ``qemu_xtensa_mmu`` utilizing Diamond DC233c SoC to support testing Xtensa MMU. * Added ``xiao_esp32s3``. * Added ``yd_esp32``. * Added support for these POSIX boards: * :ref:`native_sim(_64) <native_sim>` * nrf5340bsim_nrf5340_cpu(net\|app). A simulated nrf5340 SOC, which uses Babblesim for its radio traffic. * Made these changes for ARC boards: * Turned off unsupported stack checking option for hsdk4xd platform * Changed vendor prefix for ARC QEMU platforms from "qemu" to "snps" * Made these changes for ARM boards: * ST morpho connector description was added on ST nucleo boards. * rpi_pico: * The default adapter when debugging with openocd has been changed to cmsis-dap. * Made these changes for ARM64 boards: * Made these changes for RISC-V boards: * Made these changes for X86 boards: * Made these changes for Xtensa boards: * esp32s3_devkitm: * Added USB-CDC support. * Added CAN support. * Made these changes for POSIX boards: * nrf52_bsim: * Has been reworked to use the native simulator as its runner. * Multiple HW models improvements and fixes. GPIO & GPIOTE peripherals added. * Removed support for these ARC boards: * Removed support for these ARM boards: * Removed support for these ARM64 boards: * Removed support for these RISC-V boards: * Removed support for these X86 boards: * Removed support for these Xtensa boards: * Removed ``esp32``. Use ``esp32_devkitc_`` instead. Made these changes in other boards: * Added support for these following shields: * Adafruit PiCowbell CAN Bus Shield for Pico * Arduino UNO click shield * G1120B0MIPI MIPI Display * MikroElektronika MCP2518FD Click shield (CAN-FD) * RK055HDMIPI4M MIPI Display * RK055HDMIPI4MA0 MIPI Display * Semtech SX1276MB1MAS LoRa Shield Build system and infrastructure ******************************* * SCA (Static Code Analysis) * Added support for CodeChecker * Twister now supports ``required_snippets`` in testsuite .yml files, this can be used to include a snippet when a test is ran (and exclude any boards from running that the snippet cannot be applied to). * Interrupts * Added support for shared interrupts * Added support for setting MCUboot encryption key in sysbuild which is then propagated to the bootloader and target images to automatically create encrypted updates. * Build time priority checking: enable build time priority checking by default. This fails the build if the initialization sequence in the final ELF file does not match the devicetree hierarchy. It can be turned off by disabling the :kconfig:option:`CONFIG_CHECK_INIT_PRIORITIES` option. * Added a new ``initlevels`` target for printing the final device and :c:macro:`SYS_INIT` initialization sequence from the final ELF file. * Reworked syscall code generations so that not all marshalling functions will be included in the final binary. Syscalls associated with disabled subsystems no longer have their marshalling functions generated. * Partially enabled compiler warning about shadow variables for subset of in-tree code. Out-of-tree code needs to be patched before we can fully enable shadow variable warnings. Drivers and Sensors ******************* * ADC * Added support for STM32F0 HSI14 clock (dedicated ADC clock) * Added support for STM32 ADC source clock and prescaler. On STM32F1 and STM32F3 series, ADC prescaler can be configured using dedicated RCC Clock Controller option. * Added support for the ADC sequencer for all STM32 series (except F1) * Fixed STM32F4 ADC temperature and Vbat measurement. * Added driver for TI ADS1112. * Added driver for TI TLA2021. * Added driver for Gecko ADC. * Added driver for NXP S32 ADC SAR. * Added driver for MAX1125x family. * Added driver for MAX11102-MAX1117. * CAN * Added support for TI TCAN4x5x CAN-FD controller with integrated transceiver (:dtcompatible:`ti,tcan4x5x`). * Added support for Microchip MCP251xFD CAN-FD controller (:dtcompatible:`microchip,mcp251xfd`). * Added support for CAN statistics to the Bosch M_CAN controller driver backend. * Switched the NXP S32 CANXL driver to use clock control for the CAN clock instead of hard-coding a CAN clock frequency in the devicetree. * Clock control * Added support for Nuvoton NuMaker M46x * Counter * Added :kconfig:option:`CONFIG_COUNTER_RTC_STM32_SUBSECONDS` to enable subsecond as the basic time tick on STM32 RTC based counter driver. * Added support for Raspberry Pi Pico Timer * DAC * Added support for Analog Devices AD56xx * Added support for NXP lpcxpresso55s36 (LPDAC) * Disk * Ramdisk driver is now configured using devicetree, and supports multiple instances * Display * Added support for ST7735S (in ST7735R driver) * DMA * Added support for NXP S32K to the eDMA driver * Added support for NXP SMARTDMA * Added support for NXP Pixel Pipeline (PXP) for display acceleration * Added support for DMA get_status() to the SAM XDMAC driver * Fixes for Intel HDA driver for L1 entry/exit, explicit SCS (sample container) settings * Fixes for STM32U5 enables error interrupts, fixes block size and data size configuration * Better Kconfig options for tuning static memory usage in NXP LPC driver * EEPROM * Added support for Fujitsu MB85RCxx series I2C FRAM (:dtcompatible:`fujitsu,mb85rcxx`). * Entropy * Added a requirement for ``entropy_get_entropy()`` to be thread-safe because of random subsystem needs. * Ethernet * Added :kconfig:option:`CONFIG_ETH_NATIVE_POSIX_RX_TIMEOUT` to set rx timeout for native posix. * Added support for adin2111. * Added support for NXP S32 GMAC. * Added support for promiscuous mode in eth_smsc91x. * Added support for STM32H5X SOC series. * Added support for MDIO Clause 45 APIs. * Added support for YD-ESP32 board Ethernet. * Fixed stm32 to generate more unique MAC address by using device id as a base for the MAC. * Fixed mcux to increase the PTP timestamp accuracy from 20us to 200ns. * Fixed Ethernet max header size when using VLAN. * Removed the ``mdio`` DT property. Please use :c:macro:`DT_INST_BUS()` in the driver instead. * Reworked the device node hierarchy in smsc91x. * Renamed the phy-dev property with phy-handle to match the Linux ethernet-controller binding and move it up to ethernet.yaml so that it can be used by other drivers. * Updated Ethernet PHY to use ``reg`` property in DT bindings. * Updated driver DT bindings to use ``ethernet-phy`` devicetree node name consistently. * Updated esp32 and sam-gmac DT so that the phy is pointed by a phandle rather than a child node, this makes the phy device a child of mdio. * Flash * Introduce npcx flash driver that supports two or more spi nor flashes via a single Flash Interface Unit (FIU) module and Direct Read Access (DRA) mode for better performance. * Added support for Nuvoton NuMaker M46x embedded flash * STM32 QSPI driver now supports Jedec SFDP parameter reading. * STM32 OSPI driver now supports both Low and High ports of IO manager. * GPIO * Added support for Nuvoton NuMaker M46x * I2C * STM32 V1 driver now supports large transactions (more than 256 bytes chunks) * STM32 V2 driver now supports 10-bit addressing. * I2C devices can now be used as wakeup source from STOP modes on STM32. * Fix long ISR execution in Silicon Labs I2C target callback * Fail gracefully on DMA max size for nRF52 devices in the TWIM driver * Added support for Intel LPSS DMA usage in the DesignWare driver * Added filtering of dumped messages for debugging using DeviceTree * Added target mode to Silicon Labs Gecko driver * Added Intel SEDI driver * Added Infineon XMC4 driver * Added Microchip PolarFire SoC driver * Added Ambiq driver for Apollo4 SoCs * I2S * Fixed handling of the PCM data format in the NXP MCUX driver. * I3C * ``i3c_cdns``: * Fixed build error when :kconfig:option:`CONFIG_I3C_USE_IBI` is disabled. * Fixed transfer issue when controller is busy. Now wait for controller to idle before proceeding with another transfer. * IEEE 802.15.4 * A new mandatory method attr_get() was introduced into ieee802154_radio_api. Drivers need to implement at least IEEE802154_ATTR_PHY_SUPPORTED_CHANNEL_PAGES and IEEE802154_ATTR_PHY_SUPPORTED_CHANNEL_RANGES. * The hardware capabilities IEEE802154_HW_2_4_GHZ and IEEE802154_HW_SUB_GHZ were removed as they were not aligned with the standard and some already existing drivers couldn't properly express their channel page and channel range (notably SUN FSK and HRP UWB drivers). The capabilities were replaced by the standard conforming new driver attribute IEEE802154_ATTR_PHY_SUPPORTED_CHANNEL_PAGES that fits all in-tree drivers. * The method get_subg_channel_count() was removed from ieee802154_radio_api. This method could not properly express the channel range of existing drivers (notably SUN FSK drivers that implement channel pages > 0 and may not have zero-based channel ranges or UWB drivers that could not be represented at all). The method was replaced by the new driver attribute IEEE802154_ATTR_PHY_SUPPORTED_CHANNEL_RANGES that fits all in-tree drivers. * Interrupt Controller * GIC: Architecture version selection is now based on the device tree * Input * New drivers: :dtcompatible:`gpio-qdec`, :dtcompatible:`st,stmpe811`. * Drivers converted from Kscan to Input: :dtcompatible:`goodix,gt911` :dtcompatible:`xptek,xpt2046` :dtcompatible:`hynitron,cst816s` :dtcompatible:`microchip,cap1203`. * Added a Kconfig option for dumping all events to the console :kconfig:option:`CONFIG_INPUT_EVENT_DUMP` and new shell commands :kconfig:option:`CONFIG_INPUT_SHELL`. * Merged ``zephyr,gpio-keys`` into :dtcompatible:`gpio-keys` and added ``zephyr,code`` codes to all in-tree board ``gpio-keys`` nodes. * Renamed the callback definition macro from ``INPUT_LISTENER_CB_DEFINE`` to :c:macro:`INPUT_CALLBACK_DEFINE`. * PCIE * Added support in shell to display PCIe capabilities. * Added virtual channel support. * Added kconfig :kconfig:option:`CONFIG_PCIE_INIT_PRIORITY` to specify initialization priority for host controller. * Added support to get IRQ from ACPI PCI Routing Table (PRT). * ACPI * Adopted the ACPICA library as a new module to further enhance ACPI support. * Pin control * Added support for Nuvoton NuMaker M46x * PWM * Added 4 channels capture on STM32 PWM driver. * Added driver for Intel Blinky PWM. * Added driver for MAX31790. * Added driver for Infineon XMC4XXX CCU4. * Added driver for Infineon XMC4XXX CCU8. * Added MCUX CTimer based PWM driver. * Added PWM driver based on TI CC13xx/CC26xx GPT timer. * Reworked the pwm_nrf5_sw driver so that it can be used also on nRF53 and nRF91 Series. Consequently, the driver was renamed to pwm_nrf_sw. * Added driver for Nuvoton NuMaker family. * Added PWM driver based on NXP S32 EMIOS peripheral. * Regulators * Added support for GPIO-controlled voltage regulator * Added support for AXP192 PMIC * Added support for NXP VREF regulator * Fixed regulators can now specify their operating voltage * PFM mode is now support for nPM1300 * Added new API to configure "ship" mode * Regulator shell allows to configure DVS modes * Reset * Added support for Nuvoton NuMaker M46x * Retained memory * Added support for allowing mutex support to be forcibly disabled with :kconfig:option:`CONFIG_RETAINED_MEM_MUTEX_FORCE_DISABLE`. * Fixed issue with user mode support not working. * RTC * Added support for STM32 RTC API driver. This driver is not compatible with the use of RTC based implementation of COUNTER API. * SDHC * Added driver for EMMC Host controller present on Alder lake platforms * Added driver for Atmel HSMCI controller present on SAM4E MCU series * Sensor * Reworked the :dtcompatible:`ti,bq274xx` to add ``BQ27427`` support, fixed units for capacity and power channels. * Added ADC current sense amplifier and voltage sensor drivers. * Added ADI LTC2990 voltage, current, and temperature sensor driver. * Added AMS TSL2540 ambient light sensor driver. * Added Bosch BMI08x accelerometer/gyroscope driver. * Added DFRobot A01NYUB distance sensor driver. * Added Fintek F75303 temperature sensor driver. * Added Isentek IST8310 magnetometer driver. * Added Microchip TCN75A temperature sensor driver. * Added NXP TEMPMON driver. * Added Seeed HM330X dust sensor driver. * Added TI TMAG5170 3D Hall sensor driver. * Added power management support to BMM150, LM75, and Microchip tachometer drivers. * Added trigger support to the BMM150 magnetometer driver. * Added tap trigger support to the LIS2DH accelerometer driver. * Updated ST sensor drivers to use STMEMSC HAL i/f v2.3 * Updated the decoder APIs to vertically decode raw sensor data. * Various fixes and enhancements in the NTC thermistor and INA23x drivers. * Serial * Added support for Nuvoton NuMaker M46x * NS16550: Reworked how device initialization macros. * ``CONFIG_UART_NS16550_ACCESS_IOPORT`` and ``CONFIG_UART_NS16550_SIMULT_ACCESS`` are removed. For UART using IO port access, add ``io-mapped`` property to device tree node. * Added async support for ESP32S3. * Added support for serial TTY under ``native_posix``. * Added support for UART on Efinix Sapphire SoCs. * Added Intel SEDI UART driver. * Added support for UART on BCM2711. * ``uart_stm32``: * Added RS485 support. * Added wide data support. * ``uart_pl011``: added support for Ambiq SoCs. * ``serial_test``: added support for interrupt and async APIs. * ``uart_emul``: added support for interrupt API. * ``uart_rpi_pico``: fixed handling Modbus DE-RE signal * SPI * Remove npcx spi driver implemented by Flash Interface Unit (FIU) module. * Added support for Raspberry Pi Pico PIO based SPI. * Timer * The TI CC13xx/26xx system clock timer compatible was changed from :dtcompatible:`ti,cc13xx-cc26xx-rtc` to :dtcompatible:`ti,cc13xx-cc26xx-rtc-timer` and the corresponding Kconfig option from :kconfig:option:`CC13X2_CC26X2_RTC_TIMER` to :kconfig:option:`CC13XX_CC26XX_RTC_TIMER` for improved consistency and extensibility. No action is required unless the internal timer was modified. * USB * Added UDC driver for STM32 based MCU, relying on HAL/PCD. This driver is compatible with UDC API (experimental). * Added support for STM32H5 series on USB driver. * WiFi * Increased esp32 default network (TCP workq, RX and mgmt event) stack sizes to 2048 bytes. * Reduced the RAM usage for esp32s2_saola in Wi-Fi samples. * Fixed undefined declarations in winc1500. * Fixed SPI buffer length in eswifi. * Fixed esp32 data sending and channel selection in AP mode. * Fixed esp_at driver init and network interface dormant state setting. Networking ********** * CoAP: * Optimized CoAP client library to use only a single thread internally. * Converted CoAP client library to use ``zsock_`` API internally. Fixed a bug in CoAP client library, which resulted in an incorrect retransmission timeout calculation. * Use 64 bit timer values for calculating transmission timeouts. This fixes potential problems for devices that stay on for more than 49 days when the 32 bit uptime counter might roll over and cause CoAP packets to not timeout at all on this event. * API documentation improvements. * Added new API functions: * :c:func:`coap_has_descriptive_block_option` * :c:func:`coap_remove_descriptive_block_option` * :c:func:`coap_packet_remove_option` * :c:func:`coap_packet_set_path` * Connection Manager: * Added support for auto-connect and auto-down behaviors (controlled by :c:enum:`CONN_MGR_IF_NO_AUTO_CONNECT` and :c:enum:`CONN_MGR_IF_NO_AUTO_DOWN` flags). * Split Connection Manager APIs into separate header files. * Extended Connection Manager documentation to cover new functionalities. * DHCP: * Added support for DHCPv4 unicast replies processing. * Added support for DHCPv6 protocol. * Ethernet: * Fixed ARP queueing so that the queued network packet is sent immediately instead of queued 2nd time in the core network stack. * gPTP: * Added support for detecting gPTP packets that use the default multicast destination address. * Fixed Announce and Follow Up message handling. * ICMP: * Fixed ICMPv6 error message type check. * Reworked ICMP callback registration and handling, which allows to register multiple handlers for the same ICMP message. * Introduced an API to send ICMP Echo Request (ping). * Added possibility to register offloaded ICMP ping handlers. * Added support for setting packet priority for ping. * IPv6: * Made sure that ongoing DAD procedure is cancelled when IPv6 address is removed. * Fixed a bug, where Solicited-Node multicast address could be removed while still in use. * LwM2M: * Added support for tickless mode. This removes the 500 ms timeout from the socket loop so the engine does not constantly wake up the CPU. This can be enabled by :kconfig:option:`CONFIG_LWM2M_TICKLESS`. * Added new :c:macro:`LWM2M_RD_CLIENT_EVENT_DEREGISTER` event. * Block-wise sending now supports LwM2M read and composite-read operations as well. When :kconfig:option:`CONFIG_LWM2M_COAP_BLOCK_TRANSFER` is enabled, any content that is larger than :kconfig:option:`CONFIG_LWM2M_COAP_MAX_MSG_SIZE` is split into a block-wise transfer. * Block-wise transfers don't require tokens to match anymore as this was not in line with CoAP specification (CoAP doesn't require tokens reuse). * Various fixes to bootstrap. Now client ensures that Bootstrap-Finish command is sent, before closing the DTLS pipe. Also allows Bootstrap server to close the DTLS pipe. Added timeout when waiting for bootstrap commands. * Added support for X509 certificates. * Various fixes to string handling. Allow setting string to zero length. Ensure string termination when using string operations on opaque resources. * Added support for Connection Monitoring object version 1.3. * Added protection for Security object to prevent read/writes by the server. * Fixed a possible notification stall in case of observation token change. * Added new shell command, ``lwm2m create``, which allows to create LwM2M object instances. * Added LwM2M interoperability test-suite against Leshan server. * API documentation improvements. * Several other minor fixes and improvements. * Misc: * Time and timestamps in the network subsystem, PTP and IEEE 802.15.4 were more precisely specified and all in-tree call sites updated accordingly. Fields for timed TX and TX/RX timestamps have been consolidated. See :c:type:`net_time_t`, :c:struct:`net_ptp_time`, :c:struct:`ieee802154_config`, :c:struct:`ieee802154_radio_api` and :c:struct:`net_pkt` for extensive documentation. As this is largely an internal API, existing applications will most probably continue to work unchanged. * Added support for additional net_pkt filter hooks: * :kconfig:option:`CONFIG_NET_PKT_FILTER_IPV4_HOOK` * :kconfig:option:`CONFIG_NET_PKT_FILTER_IPV6_HOOK` * :kconfig:option:`CONFIG_NET_PKT_FILTER_LOCAL_IN_HOOK` * Reworked several networking components to use timepoint API. * Added API functions facilitate going through all IPv4/IPv6 registered on an interface (:c:func:`net_if_ipv4_addr_foreach`, :c:func:`net_if_ipv6_addr_foreach`). * ``NET_EVENT_IPV6_PREFIX_ADD`` and ``NET_EVENT_IPV6_PREFIX_DEL`` events now provide more detailed information about the prefix (:c:struct:`net_event_ipv6_prefix`). * General cleanup of the shadowed variables across the networking subsystem. * Added ``qemu_cortex_a53`` networking support. * Introduced new modem subsystem. * Added new :zephyr:code-sample:`cellular-modem` sample. * Added support for network interface names (instead of reusing underlying device name). * Removed support for Google Cloud IoT sample due to service retirement. * Fixed a bug where packets passed in promiscuous mode could have been modified by L2 in certain cases. * Added support for setting syslog server (used for networking log backend) IP address at runtime. * Removed no longer used ``queued`` and ``sent`` net_pkt flags. * Added support for binding zperf TCP/UDP server to a specific IP address. * MQTT-SN: * Improved thread safety of internal buffers allocation. * API documentation improvements. * OpenThread: * Reworked :c:func:`otPlatEntropyGet` to use :c:func:`sys_csrand_get` internally. * Introduced ``ieee802154_radio_openthread.h`` radio driver extension interface specific for OpenThread. Added new transmit mode, specific to OpenThread, :c:enum:`IEEE802154_OPENTHREAD_TX_MODE_TXTIME_MULTIPLE_CCA`. * PPP: * Fixed PPP L2 usage of the network interface carrier state. * Made PPP L2 thread priority configurable (:kconfig:option:`CONFIG_NET_L2_PPP_THREAD_PRIO`). * Moved PPP L2 out of experimental stage. * Prevent PPP connection reestablish when carrier is down. * Sockets: * Added support for statically allocated socketpairs (in case no heap is available). * Made send timeout configurable (:kconfig:option:`CONFIG_NET_SOCKET_MAX_SEND_WAIT`). * Added support for ``FIONREAD`` and ``FIONBIO`` :c:func:`ioctl` commands. * Fixed input filtering for connected datagram sockets. * Fixed :c:func:`getsockname` operation on unconnected sockets. * Added new secure socket options for DTLS Connection ID support: * :c:macro:`TLS_DTLS_CID` * :c:macro:`TLS_DTLS_CID_VALUE` * :c:macro:`TLS_DTLS_PEER_CID_VALUE` * :c:macro:`TLS_DTLS_CID_STATUS` * Added support for :c:macro:`SO_REUSEADDR` and :c:macro:`SO_REUSEPORT` socket options. * TCP: * Fixed potential stall in data retransmission, when data was only partially acknowledged. * Made TCP work queue priority configurable (:kconfig:option:`CONFIG_NET_TCP_WORKER_PRIO`). * Added support for TCP new Reno collision avoidance algorithm. * Fixed source address selection on bound sockets. * Fixed possible memory leak in case listening socket was closed during active handshake. * Fixed RST packet handling during handshake. * Refactored the code responsible for connection teardown to fix found bugs and simplify future maintenance. * TFTP: * Added new :zephyr:code-sample:`tftp-client` sample. * API documentation improvements. * WebSocket * WebSocket library no longer closes underlying TCP socket automatically on disconnect. This aligns with the connect behavior, where the WebSocket library expects an already connected TCP socket. * Wi-Fi: * Added Passive scan support. * The Wi-Fi scan API updated with Wi-Fi scan parameter to allow scan mode selection. * Updated TWT handling. * Added support for generic network manager API. * Added support for Wi-Fi mode setting and selection. * Added user input validation for SSID and PSK in Wi-Fi shell. * Added scan extension for specifying channels, limiting scan results, filtering SSIDs, setting active and passive channel dwell times and frequency bands. USB *** * USB device HID * Kconfig option USB_HID_PROTOCOL_CODE, deprecated in v2.6, is finally removed. Devicetree ********** API === New general-purpose macros: - :c:macro:`DT_REG_ADDR_U64` - :c:macro:`DT_REG_ADDR_BY_NAME_U64` - :c:macro:`DT_INST_REG_ADDR_BY_NAME_U64` - :c:macro:`DT_INST_REG_ADDR_U64` - :c:macro:`DT_FOREACH_STATUS_OKAY_NODE_VARGS` - :c:macro:`DT_FOREACH_NODE_VARGS` - :c:macro:`DT_HAS_COMPAT_ON_BUS_STATUS_OKAY` New special-purpose macros introduced for dependency ordinals: - :c:macro:`DT_DEP_ORD_STR_SORTABLE` New general purpose macros introduced for fixed flash partitions: - :c:macro:`DT_MEM_FROM_FIXED_PARTITION` - :c:macro:`DT_FIXED_PARTITION_ADDR` Bindings ======== * Generic or vendor-independent: * New bindings: * :dtcompatible:`current-sense-amplifier` * :dtcompatible:`current-sense-shunt` * :dtcompatible:`gpio-qdec` * :dtcompatible:`regulator-gpio` * :dtcompatible:`usb-audio-feature-volume` * Modified bindings: * CAN (Controller Area Network) controller bindings: * property ``phase-seg1-data`` deprecation status changed from False to True * property ``phase-seg1`` deprecation status changed from False to True * property ``phase-seg2-data`` deprecation status changed from False to True * property ``phase-seg2`` deprecation status changed from False to True * property ``prop-seg-data`` deprecation status changed from False to True * property ``prop-seg`` deprecation status changed from False to True * property ``sjw-data`` default value changed from None to 1 * property ``sjw-data`` deprecation status changed from False to True * property ``sjw`` default value changed from None to 1 * property ``sjw`` deprecation status changed from False to True * Ethernet controller bindings: new ``phy-handle`` property (in some bindings, this was renamed from ``phy-dev``), matching the Linux ethernet-controller binding. * The ``riscv,isa`` property used by RISC-V CPU bindings no longer has an ``enum`` value. * :dtcompatible:`neorv32-cpu`: * new property: ``mmu-type`` * new property: ``riscv,isa`` * :dtcompatible:`regulator-fixed`: * new property: ``regulator-min-microvolt`` * new property: ``regulator-max-microvolt`` * property ``enable-gpios`` is no longer required * :dtcompatible:`ethernet-phy`: * removed property: ``address`` * removed property: ``mdio`` * property ``reg`` is now required * :dtcompatible:`usb-audio-hs` and :dtcompatible:`usb-audio-hp`: * new property: ``volume-max`` * new property: ``volume-min`` * new property: ``volume-res`` * new property: ``status`` * new property: ``compatible`` * new property: ``reg`` * new property: ``reg-names`` * new property: ``interrupts`` * new property: ``interrupts-extended`` * new property: ``interrupt-names`` * new property: ``interrupt-parent`` * new property: ``label`` * new property: ``clocks`` * new property: ``clock-names`` * new property: ``#address-cells`` * new property: ``#size-cells`` * new property: ``dmas`` * new property: ``dma-names`` * new property: ``io-channels`` * new property: ``io-channel-names`` * new property: ``mboxes`` * new property: ``mbox-names`` * new property: ``wakeup-source`` * new property: ``power-domain`` * new property: ``zephyr,pm-device-runtime-auto`` * :dtcompatible:`ntc-thermistor-generic`: * removed property: ``r25-ohm`` * :dtcompatible:`ns16550`: * new property: ``resets`` * new property: ``reset-names`` * :dtcompatible:`fixed-clock`: * removed property: ``clocks`` * All CPU bindings got a new ``enable-method`` property. `pull request 60210 <path_to_url`_ for details. * Analog Devices, Inc. (adi): * New bindings: * :dtcompatible:`adi,ad5628` * :dtcompatible:`adi,ad5648` * :dtcompatible:`adi,ad5668` * :dtcompatible:`adi,ad5672` * :dtcompatible:`adi,ad5674` * :dtcompatible:`adi,ad5676` * :dtcompatible:`adi,ad5679` * :dtcompatible:`adi,ad5684` * :dtcompatible:`adi,ad5686` * :dtcompatible:`adi,ad5687` * :dtcompatible:`adi,ad5689` * :dtcompatible:`adi,adin1110` * :dtcompatible:`adi,adltc2990` * Modified bindings: * :dtcompatible:`adi,adin2111-mdio` (on adin2111 bus): * removed property: ``protocol`` * Altera Corp. (altr): * New bindings: * :dtcompatible:`altr,pio-1.0` * Ambiq Micro, Inc. (ambiq): * New bindings: * :dtcompatible:`ambiq,am1805` * :dtcompatible:`ambiq,apollo4-pinctrl` * :dtcompatible:`ambiq,counter` * :dtcompatible:`ambiq,i2c` * :dtcompatible:`ambiq,mspi` * :dtcompatible:`ambiq,pwrctrl` * :dtcompatible:`ambiq,spi` * :dtcompatible:`ambiq,stimer` * :dtcompatible:`ambiq,uart` * :dtcompatible:`ambiq,watchdog` * AMS AG (ams): * New bindings: * :dtcompatible:`ams,tsl2540` * Andes Technology Corporation (andestech): * New bindings: * :dtcompatible:`andestech,atcwdt200` * :dtcompatible:`andestech,plic-sw` * :dtcompatible:`andestech,qspi-nor` * ARM Ltd. (arm): * New bindings: * :dtcompatible:`arm,cortex-a76` * :dtcompatible:`arm,gic-v1` * :dtcompatible:`arm,gic-v2` * :dtcompatible:`arm,gic-v3` * :dtcompatible:`arm,psci-1.1` * ASPEED Technology Inc. (aspeed): * Modified bindings: * :dtcompatible:`aspeed,ast10x0-reset`: * specifier cells for space "reset" are now named: ['id'] (old value: None) * specifier cells for space "clock" are now named: None (old value: ['reset_id']) * Atmel Corporation (atmel): * New bindings: * :dtcompatible:`atmel,sam-hsmci` * Modified bindings: * :dtcompatible:`atmel,sam-mdio`: * removed property: ``protocol`` * property ``#address-cells`` const value changed from None to 1 * property ``#size-cells`` const value changed from None to 0 * property ``#address-cells`` is now required * property ``#size-cells`` is now required * Bosch Sensortec GmbH (bosch): * New bindings: * :dtcompatible:`bosch,bmi08x-accel` * :dtcompatible:`bosch,bmi08x-accel` * :dtcompatible:`bosch,bmi08x-gyro` * :dtcompatible:`bosch,bmi08x-gyro` * Modified bindings: * :dtcompatible:`bosch,bmm150`: * new property: ``drdy-gpios`` * :dtcompatible:`bosch,bmi270`: * new property: ``irq-gpios`` * Broadcom Corporation (brcm): * New bindings: * :dtcompatible:`brcm,bcm2711-aux-uart` * Cadence Design Systems Inc. (cdns): * New bindings: * :dtcompatible:`cdns,tensilica-xtensa-lx3` * DFRobot (dfrobot): * New bindings: * :dtcompatible:`dfrobot,a01nyub` * Efinix Inc (efinix): * New bindings: * :dtcompatible:`efinix,sapphire-gpio` * :dtcompatible:`efinix,sapphire-timer0` * :dtcompatible:`efinix,sapphire-uart0` * EPCOS AG (epcos): * Modified bindings: * :dtcompatible:`epcos,b57861s0103a039`: * removed property: ``r25-ohm`` * Espressif Systems (espressif): * Modified bindings: * :dtcompatible:`espressif,esp-at` (on uart bus): * new property: ``external-reset`` * :dtcompatible:`espressif,esp32-mdio`: * removed property: ``protocol`` * property ``#address-cells`` const value changed from None to 1 * property ``#size-cells`` const value changed from None to 0 * property ``#address-cells`` is now required * property ``#size-cells`` is now required * :dtcompatible:`espressif,riscv`: * new property: ``mmu-type`` * new property: ``riscv,isa`` * :dtcompatible:`espressif,esp32-spi`: * new property: ``line-idle-low`` * Feature Integration Technology Inc. (fintek): * New bindings: * :dtcompatible:`fintek,f75303` * FocalTech Systems Co.,Ltd (focaltech): * Modified bindings: * :dtcompatible:`focaltech,ft5336` (on i2c bus): * new property: ``reset-gpios`` * Fujitsu Ltd. (fujitsu): * New bindings: * :dtcompatible:`fujitsu,mb85rcxx` * Shenzhen Huiding Technology Co., Ltd. (goodix): * Modified bindings: * :dtcompatible:`goodix,gt911` (on i2c bus): * bus list changed from ['kscan'] to [] * new property: ``alt-addr`` * Himax Technologies, Inc. (himax): * New bindings: * :dtcompatible:`himax,hx8394` * Infineon Technologies (infineon): * New bindings: * :dtcompatible:`infineon,cat1-counter` * :dtcompatible:`infineon,cat1-spi` * :dtcompatible:`infineon,xmc4xxx-ccu4-pwm` * :dtcompatible:`infineon,xmc4xxx-ccu8-pwm` * :dtcompatible:`infineon,xmc4xxx-i2c` * Intel Corporation (intel): * New bindings: * :dtcompatible:`intel,agilex5-clock` * :dtcompatible:`intel,alder-lake` * :dtcompatible:`intel,apollo-lake` * :dtcompatible:`intel,blinky-pwm` * :dtcompatible:`intel,elkhart-lake` * :dtcompatible:`intel,emmc-host` * :dtcompatible:`intel,ish` * :dtcompatible:`intel,loapic` * :dtcompatible:`intel,sedi-gpio` * :dtcompatible:`intel,sedi-i2c` * :dtcompatible:`intel,sedi-ipm` * :dtcompatible:`intel,sedi-uart` * :dtcompatible:`intel,socfpga-agilex-sip-smc` * :dtcompatible:`intel,socfpga-reset` * :dtcompatible:`intel,timeaware-gpio` * Removed bindings: * ``intel,agilex-socfpga-sip-smc`` * ``intel,apollo_lake`` * ``intel,elkhart_lake`` * ``intel,gna`` * Modified bindings: * :dtcompatible:`intel,niosv`: * new property: ``mmu-type`` * new property: ``riscv,isa`` * :dtcompatible:`intel,adsp-imr`: * new property: ``zephyr,memory-attr`` * property ``zephyr,memory-region-mpu`` enum value changed from ['RAM', 'RAM_NOCACHE', 'FLASH', 'PPB', 'IO', 'EXTMEM'] to None * property ``zephyr,memory-region-mpu`` deprecation status changed from False to True * :dtcompatible:`intel,lpss`: * new property: ``dma-parent`` * :dtcompatible:`intel,adsp-shim-clkctl`: * new property: ``adsp-clkctl-clk-ipll`` * Isentek Inc. (isentek): * New bindings: * :dtcompatible:`isentek,ist8310` * Integrated Silicon Solutions Inc. (issi): * New bindings: * :dtcompatible:`issi,is31fl3216a` * :dtcompatible:`issi,is31fl3733` * ITE Tech. Inc. (ite): * New bindings: * :dtcompatible:`ite,it8xxx2-sha` * Modified bindings: * :dtcompatible:`ite,it8xxx2-pinctrl-func`: * new property: ``func3-ext`` * new property: ``func3-ext-mask`` * :dtcompatible:`ite,riscv-ite`: * new property: ``mmu-type`` * new property: ``riscv,isa`` * :dtcompatible:`ite,enhance-i2c`: * new property: ``target-enable`` * new property: ``target-pio-mode`` * Linaro Limited (linaro): * New bindings: * :dtcompatible:`linaro,ivshmem-ipm` * Maxim Integrated Products (maxim): * New bindings: * :dtcompatible:`maxim,max11102` * :dtcompatible:`maxim,max11103` * :dtcompatible:`maxim,max11105` * :dtcompatible:`maxim,max11106` * :dtcompatible:`maxim,max11110` * :dtcompatible:`maxim,max11111` * :dtcompatible:`maxim,max11115` * :dtcompatible:`maxim,max11116` * :dtcompatible:`maxim,max11117` * :dtcompatible:`maxim,max11253` * :dtcompatible:`maxim,max11254` * :dtcompatible:`maxim,max31790` * Microchip Technology Inc. (microchip): * New bindings: * :dtcompatible:`microchip,mcp251xfd` * :dtcompatible:`microchip,mpfs-i2c` * :dtcompatible:`microchip,tcn75a` * Modified bindings: * :dtcompatible:`microchip,xec-pwmbbled`: * new property: ``enable-low-power-32k`` * :dtcompatible:`microchip,cap1203` (on i2c bus): * bus list changed from ['kscan'] to [] * new property: ``input-codes`` * :dtcompatible:`microchip,xec-ps2`: * new property: ``wakerx-gpios`` * Motorola, Inc. (motorola): * Modified bindings: * :dtcompatible:`motorola,mc146818`: * new property: ``clock-frequency`` * Murata Manufacturing Co., Ltd. (murata): * New bindings: * :dtcompatible:`murata,ncp15wb473` * Nordic Semiconductor (nordic): * New bindings: * :dtcompatible:`nordic,npm1300-led` * :dtcompatible:`nordic,npm1300-wdt` * Removed bindings: * ``nordic,nrf-cc310`` * ``nordic,nrf-cc312`` * Modified bindings: * :dtcompatible:`nordic,nrf-ccm`: * new property: ``headermask-supported`` * :dtcompatible:`nordic,nrf-twi`: * new property: ``easydma-maxcnt-bits`` * :dtcompatible:`nordic,nrf-twim` and :dtcompatible:`nordic,nrf-twis`: * new property: ``easydma-maxcnt-bits`` * new property: ``memory-regions`` * new property: ``memory-region-names`` * :dtcompatible:`nordic,nrf-spi`, :dtcompatible:`nordic,nrf-spis`, and :dtcompatible:`nordic,nrf-spim`: * new property: ``wake-gpios`` * :dtcompatible:`nordic,npm1300-charger`: * new property: ``thermistor-cold-millidegrees`` * new property: ``thermistor-cool-millidegrees`` * new property: ``thermistor-warm-millidegrees`` * new property: ``thermistor-hot-millidegrees`` * new property: ``trickle-microvolt`` * new property: ``term-current-percent`` * new property: ``vbatlow-charge-enable`` * new property: ``disable-recharge`` * :dtcompatible:`nordic,nrf-uicr`: * new property: ``nfct-pins-as-gpios`` * new property: ``gpio-as-nreset`` * :dtcompatible:`nordic,npm1300` (on i2c bus): * new property: ``host-int-gpios`` * new property: ``pmic-int-pin`` * Nuclei System Technology (nuclei): * Modified bindings: * :dtcompatible:`nuclei,bumblebee`: * new property: ``mmu-type`` * new property: ``riscv,isa`` * Nuvoton Technology Corporation (nuvoton): * New bindings: * :dtcompatible:`nuvoton,nct38xx` * :dtcompatible:`nuvoton,nct38xx-gpio` * :dtcompatible:`nuvoton,npcx-fiu-nor` * :dtcompatible:`nuvoton,npcx-fiu-qspi` * :dtcompatible:`nuvoton,numaker-fmc` * :dtcompatible:`nuvoton,numaker-gpio` * :dtcompatible:`nuvoton,numaker-pcc` * :dtcompatible:`nuvoton,numaker-pinctrl` * :dtcompatible:`nuvoton,numaker-pwm` * :dtcompatible:`nuvoton,numaker-rst` * :dtcompatible:`nuvoton,numaker-scc` * :dtcompatible:`nuvoton,numaker-spi` * :dtcompatible:`nuvoton,numaker-uart` * Removed bindings: * ``nuvoton,nct38xx-gpio`` * ``nuvoton,npcx-spi-fiu`` * Modified bindings: * :dtcompatible:`nuvoton,npcx-sha`: * new property: ``context-buffer-size`` * :dtcompatible:`nuvoton,npcx-adc`: * new property: ``vref-mv`` * removed property: ``threshold-reg-offset`` * :dtcompatible:`nuvoton,adc-cmp`: * new property: ``thr-sel`` * :dtcompatible:`nuvoton,npcx-pcc`: * new property: ``pwdwn-ctl-val`` * property ``clock-frequency`` enum value changed from [100000000, 96000000, 90000000, 80000000, 66000000, 50000000, 48000000, 40000000, 33000000] to [120000000, 100000000, 96000000, 90000000, 80000000, 66000000, 50000000, 48000000] * property ``ram-pd-depth`` enum value changed from [12, 15] to [8, 12, 15] * NXP Semiconductors (nxp): * New bindings: * :dtcompatible:`nxp,ctimer-pwm` * :dtcompatible:`nxp,fs26-wdog` * :dtcompatible:`nxp,imx-flexspi-w956a8mbya` * :dtcompatible:`nxp,irqsteer-intc` * :dtcompatible:`nxp,lpdac` * :dtcompatible:`nxp,mbox-imx-mu` * :dtcompatible:`nxp,mcux-dcp` * :dtcompatible:`nxp,mcux-edma-v3` * :dtcompatible:`nxp,pcf8563` * :dtcompatible:`nxp,pxp` * :dtcompatible:`nxp,s32-adc-sar` * :dtcompatible:`nxp,s32-clock` * :dtcompatible:`nxp,s32-emios` * :dtcompatible:`nxp,s32-emios-pwm` * :dtcompatible:`nxp,s32-gmac` * :dtcompatible:`nxp,s32-qspi` * :dtcompatible:`nxp,s32-qspi-device` * :dtcompatible:`nxp,s32-qspi-nor` * :dtcompatible:`nxp,s32k3-pinctrl` * :dtcompatible:`nxp,smartdma` * :dtcompatible:`nxp,tempmon` * :dtcompatible:`nxp,vref` * Modified bindings: * :dtcompatible:`nxp,s32-netc-emdio`: * removed property: ``protocol`` * property ``#address-cells`` const value changed from None to 1 * property ``#size-cells`` const value changed from None to 0 * property ``#address-cells`` is now required * property ``#size-cells`` is now required * :dtcompatible:`nxp,mipi-dsi-2l`: * property ``nxp,lcdif`` is no longer required * :dtcompatible:`nxp,imx-mipi-dsi`: * property ``nxp,lcdif`` is no longer required * :dtcompatible:`nxp,pca9633` (on i2c bus): * new property: ``disable-allcall`` * :dtcompatible:`nxp,s32-sys-timer`: * removed property: ``clock-frequency`` * property ``clocks`` is now required * :dtcompatible:`nxp,imx-lpspi`: * new property: ``data-pin-config`` * :dtcompatible:`nxp,s32-spi`: * property ``clock-frequency`` is no longer required * property ``clocks`` is now required * :dtcompatible:`nxp,imx-wdog`: * pinctrl support * :dtcompatible:`nxp,s32-swt`: * removed property: ``clock-frequency`` * property ``clocks`` is now required * :dtcompatible:`nxp,lpc-lpadc`: * new property: ``nxp,reference-supply`` * :dtcompatible:`nxp,kinetis-pit`: * new property: ``max-load-value`` * property ``clocks`` is now required * :dtcompatible:`nxp,mcux-edma`: * new property: ``dmamux-reg-offset`` * new property: ``channel-gap`` * new property: ``irq-shared-offset`` * :dtcompatible:`nxp,imx-elcdif`: * new property: ``nxp,pxp`` * ON Semiconductor Corp. (onnn): * New bindings: * :dtcompatible:`onnn,ncp5623` * Princeton Technology Corp. (ptc): * New bindings: * :dtcompatible:`ptc,pt6314` * Quectel Wireless Solutions Co., Ltd. (quectel): * New bindings: * :dtcompatible:`quectel,bg95` * QuickLogic Corp. (quicklogic): * New bindings: * :dtcompatible:`quicklogic,eos-s3-pinctrl` * Modified bindings: * :dtcompatible:`quicklogic,usbserialport-s3b`: * pinctrl support * Raspberry Pi Foundation (raspberrypi): * New bindings: * :dtcompatible:`raspberrypi,pico-header` * :dtcompatible:`raspberrypi,pico-i2c` * :dtcompatible:`raspberrypi,pico-spi-pio` * :dtcompatible:`raspberrypi,pico-timer` * Raydium Semiconductor Corp. (raydium): * New bindings: * :dtcompatible:`raydium,rm67162` * Renesas Electronics Corporation (renesas): * New bindings: * :dtcompatible:`renesas,smartbond-lp-osc` * :dtcompatible:`renesas,smartbond-timer` * Modified bindings: * :dtcompatible:`renesas,smartbond-flash-controller`: * new property: ``read-cs-idle-delay`` * new property: ``erase-cs-idle-delay`` * Smart Battery System (sbs): * New bindings: * :dtcompatible:`sbs,default-sbs-gauge` * :dtcompatible:`sbs,sbs-charger` * Seeed Technology Co., Ltd (seeed): * New bindings: * :dtcompatible:`seeed,hm330x` * SiFive, Inc. (sifive): * Modified bindings: * :dtcompatible:`sifive,i2c0`: * pinctrl support * Silicon Laboratories (silabs): * New bindings: * :dtcompatible:`silabs,gecko-adc` * Sino Wealth Electronic Ltd (sinowealth): * New bindings: * :dtcompatible:`sinowealth,sh1106` * :dtcompatible:`sinowealth,sh1106` * Sitronix Technology Corporation (sitronix): * Modified bindings: * :dtcompatible:`sitronix,st7735r` (on spi bus): * property ``reset-gpios`` is no longer required * Standard Microsystems Corporation (smsc): * Modified bindings: * :dtcompatible:`smsc,lan91c111-mdio`: * removed property: ``protocol`` * property ``#address-cells`` const value changed from None to 1 * property ``#size-cells`` const value changed from None to 0 * property ``#address-cells`` is now required * property ``#size-cells`` is now required * :dtcompatible:`smsc,lan91c111`: * new property: ``local-mac-address`` * new property: ``zephyr,random-mac-address`` * property ``reg`` is no longer required * Synopsys, Inc. (snps): * New bindings: * :dtcompatible:`snps,dw-timers` * Solomon Systech Limited (solomon): * Modified bindings: * :dtcompatible:`solomon,ssd1306fb` * new property: ``inversion-on`` * new property: ``ready-time-ms`` * Sequans Communications (sqn): * New bindings: * :dtcompatible:`sqn,hwspinlock` * STMicroelectronics (st): * New bindings: * :dtcompatible:`st,stm32-bxcan` * :dtcompatible:`st,stm32-spi-host-cmd` * :dtcompatible:`st,stm32f1-rcc` * :dtcompatible:`st,stm32f3-rcc` * :dtcompatible:`st,stm32wba-flash-controller` * :dtcompatible:`st,stm32wba-hse-clock` * :dtcompatible:`st,stm32wba-pll-clock` * :dtcompatible:`st,stm32wba-rcc` * :dtcompatible:`st,stmpe811` * Removed bindings: * ``st,stm32-can`` * Modified bindings: * :dtcompatible:`st,stm32-pwm`: * new property: ``four-channel-capture-support`` * :dtcompatible:`st,stm32f4-adc`: * new property: ``st,adc-clock-source`` * new property: ``st,adc-prescaler`` * new property: ``st,adc-sequencer`` * removed property: ``temp-channel`` * removed property: ``vref-channel`` * removed property: ``vbat-channel`` * :dtcompatible:`st,stm32-adc`: * new property: ``st,adc-clock-source`` * new property: ``st,adc-prescaler`` * new property: ``st,adc-sequencer`` * removed property: ``temp-channel`` * removed property: ``vref-channel`` * removed property: ``vbat-channel`` * :dtcompatible:`st,stm32f1-adc`: * new property: ``st,adc-sequencer`` * removed property: ``temp-channel`` * removed property: ``vref-channel`` * removed property: ``vbat-channel`` * :dtcompatible:`st,stm32-ospi`: * new property: ``io-low-port`` * new property: ``io-high-port`` * :dtcompatible:`st,stm32c0-hsi-clock`: * removed property: ``clocks`` * :dtcompatible:`st,stm32-hse-clock`: * removed property: ``clocks`` * :dtcompatible:`st,stm32wl-hse-clock`: * removed property: ``clocks`` * :dtcompatible:`st,stm32g0-hsi-clock`: * removed property: ``clocks`` * :dtcompatible:`st,stm32h7-hsi-clock`: * removed property: ``clocks`` * :dtcompatible:`st,stm32-lse-clock`: * removed property: ``clocks`` * :dtcompatible:`st,stm32u5-pll-clock`: * new property: ``fracn`` * Telink Semiconductor (telink): * Modified bindings: * :dtcompatible:`telink,b91-pwm`: * pinctrl support * :dtcompatible:`telink,b91`: * new property: ``mmu-type`` * new property: ``riscv,isa`` * :dtcompatible:`telink,b91-i2c`: * pinctrl support * :dtcompatible:`telink,b91-spi`: * pinctrl support * :dtcompatible:`telink,b91-uart`: * pinctrl support * Texas Instruments (ti): * New bindings: * :dtcompatible:`ti,ads1112` * :dtcompatible:`ti,bq27z746` * :dtcompatible:`ti,cc13xx-cc26xx-rtc-timer` * :dtcompatible:`ti,cc13xx-cc26xx-timer` * :dtcompatible:`ti,cc13xx-cc26xx-timer-pwm` * :dtcompatible:`ti,cc32xx-pinctrl` * :dtcompatible:`ti,davinci-gpio` * :dtcompatible:`ti,davinci-gpio-nexus` * :dtcompatible:`ti,lp5009` * :dtcompatible:`ti,lp5012` * :dtcompatible:`ti,lp5018` * :dtcompatible:`ti,lp5024` * :dtcompatible:`ti,lp5030` * :dtcompatible:`ti,lp5036` * :dtcompatible:`ti,lp5569` * :dtcompatible:`ti,tas6422dac` * :dtcompatible:`ti,tcan4x5x` * :dtcompatible:`ti,tla2021` * :dtcompatible:`ti,tmag5170` * :dtcompatible:`ti,vim` * Removed bindings: * ``ti,cc13xx-cc26xx-rtc`` * ``ti,lp503x`` * Modified bindings: * :dtcompatible:`ti,cc32xx-i2c`: * pinctrl support * :dtcompatible:`ti,ina230` (on i2c bus): * new property: ``alert-config`` * new property: ``adc-mode`` * new property: ``vbus-conversion-time-us`` * new property: ``vshunt-conversion-time-us`` * new property: ``avg-count`` * new property: ``rshunt-micro-ohms`` * removed property: ``rshunt-milliohms`` * property ``config`` default value changed from None to 0 * property ``config`` deprecation status changed from False to True * property ``config`` is no longer required * :dtcompatible:`ti,ina237` (on i2c bus): * new property: ``adc-mode`` * new property: ``vbus-conversion-time-us`` * new property: ``vshunt-conversion-time-us`` * new property: ``temp-conversion-time-us`` * new property: ``avg-count`` * new property: ``high-precision`` * new property: ``rshunt-micro-ohms`` * removed property: ``rshunt-milliohms`` * property ``adc-config`` default value changed from None to 0 * property ``config`` default value changed from None to 0 * property ``adc-config`` deprecation status changed from False to True * property ``config`` deprecation status changed from False to True * property ``adc-config`` is no longer required * property ``config`` is no longer required * :dtcompatible:`ti,cc32xx-uart`: * pinctrl support * A stand-in for a real vendor which can be used in examples and tests (vnd): * New bindings: * :dtcompatible:`vnd,memory-attr` * :dtcompatible:`vnd,reg-holder-64` * :dtcompatible:`vnd,reserved-compat` * Modified bindings: * :dtcompatible:`vnd,serial`: * property ``reg`` is no longer required * X-Powers (x-powers): * New bindings: * :dtcompatible:`x-powers,axp192` * :dtcompatible:`x-powers,axp192-gpio` * :dtcompatible:`x-powers,axp192-regulator` * Xen Hypervisor (xen): * New bindings: * :dtcompatible:`xen,xen` * Removed bindings: * ``xen,xen-4.15`` * Xilinx (xlnx): * New bindings: * :dtcompatible:`xlnx,zynqmp-ipi-mailbox` * Shenzhen Xptek Technology Co., Ltd (xptek): * Modified bindings: * :dtcompatible:`xptek,xpt2046` (on spi bus): * bus list changed from ['kscan'] to [] * Zephyr-specific binding (zephyr): * New bindings: * :dtcompatible:`zephyr,fake-rtc` * :dtcompatible:`zephyr,i2c-dump-allowlist` * :dtcompatible:`zephyr,lvgl-button-input` * :dtcompatible:`zephyr,lvgl-encoder-input` * :dtcompatible:`zephyr,lvgl-pointer-input` * :dtcompatible:`zephyr,mdio-gpio` * :dtcompatible:`zephyr,native-tty-uart` * :dtcompatible:`zephyr,ram-disk` * :dtcompatible:`zephyr,sensing` * :dtcompatible:`zephyr,sensing-phy-3d-sensor` * Removed bindings: * ``zephyr,gpio-keys`` * Modified bindings: * :dtcompatible:`zephyr,mmc-disk` (on sd bus): * new property: ``bus-width`` * :dtcompatible:`zephyr,bt-hci-spi` (on spi bus): * new property: ``controller-data-delay-us`` * :dtcompatible:`zephyr,sdhc-spi-slot` (on spi bus): * new property: ``pwr-gpios`` * :dtcompatible:`zephyr,memory-region`: * new property: ``zephyr,memory-attr`` * property ``zephyr,memory-region-mpu`` enum value changed from ['RAM', 'RAM_NOCACHE', 'FLASH', 'PPB', 'IO', 'EXTMEM'] to None * property ``zephyr,memory-region-mpu`` deprecation status changed from False to True * property ``reg`` is now required Libraries / Subsystems ********************** * Management * Introduced MCUmgr client support with handlers for img_mgmt and os_mgmt. * Added response checking to MCUmgr's :c:enumerator:`MGMT_EVT_OP_CMD_RECV` notification callback to allow applications to reject MCUmgr commands. * MCUmgr SMP version 2 error translation (to legacy MCUmgr error code) is now supported in function handlers by setting ``mg_translate_error`` of :c:struct:`mgmt_group` when registering a group. See :c:type:`smp_translate_error_fn` for function details. * Fixed an issue with MCUmgr img_mgmt group whereby the size of the upload in the initial packet was not checked. * Fixed an issue with MCUmgr fs_mgmt group whereby some status codes were not checked properly, this meant that the error returned might not be the correct error, but would only occur in situations where an error was already present. * Fixed an issue whereby the SMP response function did not check to see if the initial zcbor map was created successfully. * Fixes an issue with MCUmgr shell_mgmt group whereby the length of a received command was not properly checked. * Added optional mutex locking support to MCUmgr img_mgmt group, which can be enabled with :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_MUTEX`. * Added MCUmgr settings management group, which allows for manipulation of zephyr settings from a remote device, see :ref:`mcumgr_smp_group_3` for details. * Added :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_ALLOW_CONFIRM_NON_ACTIVE_IMAGE_SECONDARY` and :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_ALLOW_CONFIRM_NON_ACTIVE_IMAGE_ANY` that allow to control whether MCUmgr client will be allowed to confirm non-active images. * Added :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_ALLOW_ERASE_PENDING` that allows to erase slots pending for next boot, that are not revert slots. * Added ``user_data`` as an optional field to :c:struct:`mgmt_handler` when :kconfig:option:`CONFIG_MCUMGR_MGMT_HANDLER_USER_DATA` is enabled. * Added optional ``force`` parameter to os mgmt reset command, this can be checked in the :c:enumerator:`MGMT_EVT_OP_OS_MGMT_RESET` notification callback whose data structure is :c:struct:`os_mgmt_reset_data`. * Added configurable number of SMP encoding levels via :kconfig:option:`CONFIG_MCUMGR_SMP_CBOR_MIN_ENCODING_LEVELS`, which automatically increments minimum encoding levels for in-tree groups if :kconfig:option:`CONFIG_ZCBOR_CANONICAL` is enabled. * Added STM32 SPI backend for EC Host command protocol. * Fixed settings_mgmt returning unknown error instead of invalid key specified error. * Fixed fs_mgmt returning parameter too large error instead of file is empty error when attempting to hash/checksum a file which is empty. * File systems * Added support for ext2 file system. * Added support of mounting littlefs on the block device from the shell/fs. * Added alignment parameter to FS_LITTLEFS_DECLARE_CUSTOM_CONFIG macro, it can speed up read/write operation for SDMMC devices in case when we align buffers on CONFIG_SDHC_BUFFER_ALIGNMENT, because we can avoid extra copy of data from card buffer to read/prog buffer. * Random * ``CONFIG_XOROSHIRO_RANDOM_GENERATOR``, deprecated a long time ago, is finally removed. * Retention * Added the :ref:`blinfo_api` subsystem. * Added support for allowing mutex support to be forcibly disabled with :kconfig:option:`CONFIG_RETENTION_MUTEX_FORCE_DISABLE`. * Binary descriptors * Added the :ref:`binary_descriptors` (``bindesc``) subsystem. * POSIX API * Added dynamic thread stack support for :c:func:`pthread_create` * Fixed :c:func:`stat` so that it returns file stats instead of filesystem stats * Implemented :c:func:`pthread_barrierattr_destroy`, :c:func:`pthread_barrierattr_getpshared`, :c:func:`pthread_barrierattr_init`, :c:func:`pthread_barrierattr_setpshared`, :c:func:`pthread_condattr_destroy`, :c:func:`pthread_condattr_init`, :c:func:`pthread_mutexattr_destroy`, :c:func:`pthread_mutexattr_init`, :c:func:`uname`, :c:func:`sigaddset`, :c:func:`sigdelset`, :c:func:`sigemptyset`, :c:func:`sigfillset`, :c:func:`sigismember`, :c:func:`strsignal`, :c:func:`pthread_spin_destroy`, :c:func:`pthread_spin_init`, :c:func:`pthread_spin_lock`, :c:func:`pthread_spin_trylock`, :c:func:`pthread_spin_unlock`, :c:func:`timer_getoverrun`, :c:func:`pthread_condattr_getclock`, :c:func:`pthread_condattr_setclock`, :c:func:`clock_nanosleep` * Added support for querying the number of bytes available to read via the :c:macro:`FIONREAD` request to :c:func:`ioctl` * Added :kconfig:option:`CONFIG_FDTABLE` to conditionally compile file descriptor table * Added logging to POSIX threads, mutexes, and condition variables * Fixed :c:func:`poll` issue with event file descriptors * LoRa/LoRaWAN * Updated ``loramac-node`` from v4.6.0 to v4.7.0 * CAN ISO-TP * Added support for CAN FD. * RTIO * Added atomic completion counter fixing a race caught by unit tests * Added a :c:macro:`RTIO_SQE_NO_RESPONSE` flag for submissions when no completion notification is needed * Removed unused Kconfig options for different executors * ZBus * Changed channels' and observers' metadata to comply with the data/config approach. ZBus stores immutable config in iterable sections in Flash and the mutable portion of data in the RAM. * The relationship between channels and observers is mapped using a new entity called observation. The observation enables us to increase the granularity of masking observation. Developers can mask individual observations, disable the observer, or use runtime observers. * Added API :c:macro:`ZBUS_CHAN_ADD_OBS` macro for adding post-definition static observers of a channel. That can replace the runtime observer feature, enabling developers to add static observers after the channel definition in different files. It increases the composability of the system using ZBus, making post-definition channel observation rely on the stack instead of the heap. * Added a new type of observer called Message Subscriber. ZBus' VDED will send a copy of the message during the publication/notification process. * Changed the VDED delivery sequence. Check the ref:`documentation<zbus delivery sequence>`. * ZBus runtime observers now rely on the heap instead of a memory pool. * Added new iterable section iterators APIs (for channels and observers) can now receive a ``user_data`` pointer to keep context between the function calls. * Added APIs :c:macro:`ZBUS_LISTENER_DEFINE_WITH_ENABLE` and :c:macro:`ZBUS_SUBSCRIBER_DEFINE_WITH_ENABLE` that allows developers to define observers' statuses (enabled/disabled) programmatically. With the API, developers can create observers initially disabled and enable them in runtime. * Power management * Added :kconfig:option:`CONFIG_PM_NEED_ALL_DEVICES_IDLE`. When this option is set the power management will keep the system active if there is any device busy. * :c:func:`pm_device_runtime_get` can be called from ISR now. * Power states can be disabled directly in devicetree doing ``status = "disabled";`` * Added the helper function, :c:func:`pm_device_driver_init`, for initializing devices into a specific power state. * Modem modules * Added the :ref:`modem` subsystem. HALs **** * Nordic * Updated nrfx to version 3.1.0. * Nuvoton * Added Nuvoton NuMaker M46x MCUboot ******* * Added :kconfig:option:`CONFIG_MCUBOOT_BOOTLOADER_NO_DOWNGRADE` that allows to inform application that the on-board MCUboot has been configured with downgrade prevention enabled. This option is automatically selected for DirectXIP mode and is available for both swap modes. * Added :kconfig:option:`CONFIG_MCUBOOT_BOOTLOADER_MODE_OVERWRITE_ONLY` that allows to inform application that the on-board MCUboot will overwrite the primary slot with secondary slot contents, without saving the original image in primary slot. * Fixed issue with serial recovery not showing image details for decrypted images. * Fixed issue with serial recovery in single slot mode wrongly iterating over 2 image slots. * Fixed an issue with boot_serial repeats not being processed when output was sent, this would lead to a divergence of commands whereby later commands being sent would have the previous command output sent instead. * Fixed an issue with the boot_serial zcbor setup encoder function wrongly including the buffer address in the size which caused serial recovery to fail on some platforms. * Fixed wrongly building in optimize for debug mode by default, this saves a significant amount of flash space. * Fixed issue with serial recovery use of MBEDTLS having undefined operations which led to usage faults when the secondary slot image was encrypted. * Fixed issue with bootutil asserting on maximum alignment in non-swap modes. * Added error output when flash device fails to open and asserts are disabled, which will now panic the bootloader. * Added currently running slot ID and maximum application size to shared data function definition. * Added P384 and SHA384 support to imgtool. * Added optional serial recovery image state and image set state commands. * Added ``dumpinfo`` command for signed image parsing in imgtool. * Added ``getpubhash`` command to dump the sha256 hash of the public key in imgtool. * Added support for ``getpub`` to print the output to a file in imgtool. * Added support for dumping the raw versions of the public keys in imgtool. * Added support for sharing boot information with application via retention subsystem. * Added support for serial recovery to read and handle encrypted seondary slot partitions. * Removed ECDSA P224 support. * Removed custom image list boot serial extension support. * Reworked boot serial extensions so that they can be used by modules or from user repositories by switching to iterable sections. * Reworked image encryption support for Zephyr, static dummy key files are no longer in the code, a pem file must be supplied to extract the private and public keys. The Kconfig menu has changed to only show a single option for enabling encryption and selecting the key file. * Reworked the ECDSA256 TLV curve agnostic and renamed it to ``ECDSA_SIG``. * CDDL auto-generated function code has been replaced with zcbor function calls, this now allows the parameters to be supplied in any order. * The MCUboot version in this release is version ``2.0.0+0-rc1``. Nanopb ****** * Changed project status to maintained. * Added a separate nanopb.cmake file to be included by applications. * Added helper cmake function ``zephyr_nanopb_sources`` to simplify ``.proto`` file inclusion. LVGL **** * Changed project status to maintained. * Library has been updated to release v8.3.7. * Added ``zephyr,lvgl-{pointer,button,encoder}-input`` pseudo device bindings. :kconfig:option:`CONFIG_LV_Z_KSCAN_POINTER` is still supported but touch controllers need a :dtcompatible:`zephyr,kscan-input` child node to emit input events. * LVGL shell allows for monkey testing (requires :kconfig:option:`CONFIG_LV_USE_MONKEY`) and inspecting memory usage. Trusted Firmware-A ****************** * Updated to TF-A 2.9.0. Documentation ************* * Upgraded Sphinx to 6.2 Tests and Samples ***************** * Created common sample for file systems (`fs_sample`). It originates from sample for FAT (`fat_fs`) and supports both FAT and ext2 file systems. * Created the zbus confirmed channel sample to demonstrate how to implement a delivery-guaranteed channel using subscribers. * Created the zbus message subscriber sample to demonstrate how to use message subscribers. ```	/content/code_sandbox/doc/releases/release-notes-3.5.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	20,608
```restructuredtext .. _safety_overview: Zephyr Safety Overview ######################## Introduction ********** This document is the safety documentation providing an overview over the safety-relevant activities and what the Zephyr Project and the Zephyr Safety Working Group / Committee try to achieve. This overview is provided for people who are interested in the functional safety development part of the Zephyr RTOS and project members who want to contribute to the safety aspects of the project. Overview **** In this section we give the reader an overview of what the general goal of the safety certification is, what standard we aim to achieve and what quality standards and processes need to be implemented to reach such a safety certification. Safety Document update ****************** This document is a living document and may evolve over time as new requirements, guidelines, or processes are introduced. #. Changes will be submitted from the interested party(ies) via pull requests to the Zephyr documentation repository. #. The Zephyr Safety Committee will review these changes and provide feedback or acceptance of the changes. #. Once accepted, these changes will become part of the document. General safety scope ****************** The general scope of the Safety Committee is to achieve a certification for the `IEC 61508 <path_to_url`__ standard and the Safety Integrity Level (SIL) 3 / Systematic Capability (SC) 3 for a limited source scope (see certification scope TBD). Since the code base is pre-existing, we use the route 3s/1s approach defined by the IEC 61508 standard. Route 3s Assessment of non-compliant development. Which is basically the route 1s with existing sources. Route 1s Compliant development. Compliance with the requirements of this standard for the avoidance and control of systematic faults in software. Summarization IEC 61508 standard ================================ The IEC 61508 standard is a widely recognized international standard for functional safety of electrical, electronic, and programmable electronic safety-related systems. Here's an overview of some of the key safety aspects of the standard: #. Hazard and Risk Analysis: The IEC 61508 standard requires a thorough analysis of potential hazards and risks associated with a system in order to determine the appropriate level of safety measures needed to reduce those risks to acceptable levels. #. Safety Integrity Level (SIL): The standard introduces the concept of Safety Integrity Level (SIL) to classify the level of risk reduction required for each safety function. The higher the SIL, the greater the level of risk reduction required. #. System Design: The IEC 61508 standard requires a systematic approach to system design that includes the identification of safety requirements, the development of a safety plan, and the use of appropriate safety techniques and measures to ensure that the system meets the required SIL. #. Verification and Validation: The standard requires rigorous testing and evaluation of the safety-related system to ensure that it meets the specified SIL and other safety requirements. This includes verification of the system design, validation of the system's functionality, and ongoing monitoring and maintenance of the system. #. Documentation and Traceability: The IEC 61508 standard requires a comprehensive documentation process to ensure that all aspects of the safety-related system are fully documented and that there is full traceability from the safety requirements to the final system design and implementation. Overall, the IEC 61508 standard provides a framework for the design, development, and implementation of safety-related systems that aims to reduce the risk of accidents and improve overall safety. By following the standard, organizations can ensure that their safety-related systems are designed and implemented to the highest level of safety integrity. Quality ***** Quality is a mandatory expectation for software across the industry. The code base of the project must achieve various software quality goals in order to be considered an auditable code base from a safety perspective and to be usable for certification purposes. But software quality is not an additional requirement caused by functional safety standards. Functional safety considers quality as an existing pre-condition and therefore the "quality managed" status should be pursued for any project regardless of the functional safety goals. The following list describes the quality goals which need to be reached to achieve an auditable code base: 1. Basic software quality standards a. :ref:`coding_guidelines` (including: static code analysis, coding style, etc.) b. :ref:`safety_requirements` and requirements tracing c. Test coverage 2. Software architecture design principles a. Layered architecture model b. Encapsulated components c. Encapsulated single functionality (if not fitable and manageable in safety) Basic software quality standards - Safety view ============================================== In this chapter the Safety Committee describes why they need the above listed quality goals as pre-condition and what needs to be done to achieve an auditable code base from the safety perspective. Generally speaking, it can be said that all of these quality measures regarding safety are used to minimize the error rate during code development. Coding Guidelines ----------------- The coding guidelines are the basis to a common understanding and a unified ruleset and development style for industrial software products. For safety the coding guidelines are essential and have another purpose beside the fact of a unified ruleset. It is also necessary to prove that the developers follow a unified development style to prevent systematic errors in the process of developing software and thus to minimize the overall error rate of the complete software system. Also the IEC 61508 standard** sets a pre-condition and recommendation towards the use of coding standards / guidelines to reduce likelihood of errors. Requirements and requirements tracing ------------------------------------- Requirements and requirement management are not only important for software development, but also very important in terms of safety. On the one hand, this specifies and describes in detail and on a technical level what the software should do, and on the other hand, it is an important and necessary tool to verify whether the described functionality is implemented as expected. For this purpose, tracing the requirements down to the code level is used. With the requirements management and tracing in hand, it can now be verified whether the functionality has been tested and implemented correctly, thus minimizing the systematic error rate. Also the IEC 61508 standard highly recommends (which is like a must-have for the certification) requirements and requirements tracing. Test coverage ------------- A high test coverage, in turn, is evidence of safety that the code conforms precisely to what it was developed for and does not execute any unforeseen instructions. If the entire code is tested and has a high (ideally 100%) test coverage, it has the additional advantage of quickly detecting faulty changes and further minimizing the error rate. However, it must be noted that different requirements apply to safety for test coverage, and various metrics must be considered, which are prescribed by the IEC 61508 standard for the SIL 3 / SC3 target. The following must be fulfilled, among other things: * Structural test coverage (entry points) 100% * Structural test coverage (statements) 100% * Structural test coverage (branches) 100% If the 100% cannot be reached (e.g. statement coverage of defensive code) that part needs to be described and justified in the documentation. Software architecture design principles ======================================= To create and maintain a structured software product it is also necessary to consider individual software architecture designs and implement them in accordance with safety standards because some designs and implementations are not reasonable in safety, so that the overall software and code base can be used as auditable code. However, most of these software architecture designs have already been implemented in the Zephyr project and need to be verified by the Safety Committee / Safety Working Group and the safety architect. Layered architecture model -------------------------- The IEC 61508 standard strongly recommends a modular approach to software architecture. This approach has been pursued in the Zephyr project from the beginning with its layered architecture. The idea behind this architecture is to organize modules or components with similar functionality into layers. As a result, each layer can be assigned a specific role in the system. This model has the advantage in safety that interfaces between different components and layers can be shown at a very high level, and thus it can be determined which functionalities are safety-relevant and can be limited. Furthermore, various analyses and documentations can be built on top of this architecture, which are important for certification and the responsible certification body. Encapsulated components ----------------------- Encapsulated components are an essential part of the architecture design for safety at this point. The most important aspect is the separation of safety-relevant components from non-safety-relevant components, including their associated interfaces. This ensures that the components have no repercussions on other components. Encapsulated single functionality (if not reasonable and manageable in safety) your_sha256_hash-------------- Another requirement for the overall system and software environment is that individual functionalities can be disabled within components. This is because if a function is absolutely unacceptable for safety (e.g. complete dynamic memory management), then these individual functionalities should be able to be turned off. The Zephyr Project already offers such a possibility through the use of Kconfig and its flexible configurability. Processes and workflow ******************** .. figure:: images/zephyr-safety-process.svg :align: center :alt: Safety process and workflow overview :figclass: align-center Safety process and workflow overview The diagram describes the rough process defined by the Safety Committee to ensure safety in the development of the Zephyr project. To ensure understanding, a few points need to be highlighted and some details explained regarding the role of the safety architect and the role of the safety committee in the whole process. The diagram only describes the paths that are possible when a change is related to safety. #. On the main branch, the safety scope of the project should be identified, which typically represents a small subset of the entire code base. This subset should then be made auditable during normal development on main, which means that special attention is paid to quality goals (`Quality`_) and safety processes within this scope. The Safety Architect works alongside the Technical Steering Committee (TSC) in this area, monitoring the development process to ensure that the architecture meets the safety requirements. #. At this point, the safety architect plays an increasingly important role. For PRs/issues that fall within the safety scope, the safety architect should ideally be involved in the discussions and decisions of minor changes in the safety scope to be able to react to safety-relevant changes that are not conformant. If a pull request or issue introduces a significant and influential change or improvement that requires extended discussion or decision-making, the safety architect should bring it to the attention of the Safety Committee or the Technical Steering Committee (TSC) as appropriate, so that they can make a decision on the best course of action. #. This section describes the certification side. At this point, the code base has to be in an "auditable" state, and ideally no further changes should be necessary or made to the code base. There is still a path from the main branch to this area. This is needed in case a serious bug or important change is found or implemented on the main branch in the safety scope, after the LTS and the auditable branch were created. In this case, the Safety Committee, together with the safety architect, must decide whether this bug fix or change should be integrated into the LTS so that the bug fix or change could also be integrated into the auditable branch. This integration can take three forms: First either as only a code change or second as only an update to the safety documentation or third as both. #. This describes the necessary safety process required for certification itself. Here, the final analyses, tests, and documents are created and conducted which must be created and conducted during the certification, and which are prescribed by the certifying authority and the standard being certified. If the certification body approves everything at this stage and the safety process is completed, a safety release can be created and published. #. This transition from the auditable branch to the main branch should only occur in exceptional circumstances, specifically when something has been identified during the certification process that needs to be quickly adapted on the auditable branch in order to obtain certification. In order to prevent this issue from arising again during the next certification, there needs to be a path to merge these changes back into the main branch so that they are not lost, and to have them ready for the next certification if necessary. .. important:: Safety should not block the project and minimize the room to grow in any way. .. important:: TODO:** Find and define ways, guidelines and processes which minimally impact the daily work of the maintainers, reviewers and contributors and also the safety architect itself. But which are also suitable for safety. ```	/content/code_sandbox/doc/safety/safety_overview.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,781
```restructuredtext .. _safety_section: Safety ######## These documents describe the processes, developer guidelines and requirements for ensuring safety is addressed within the Zephyr project. .. toctree:: :maxdepth: 1 :glob: safety_overview.rst safety_requirements.rst ```	/content/code_sandbox/doc/safety/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	64
```restructuredtext .. _zephyr_1.6: Zephyr Kernel 1.6.0 #################### We are pleased to announce the release of Zephyr kernel version 1.6.0. This release introduces the unified Kernel replacing the separate nano- and micro-kernels and simplifying the overall Zephyr architecture and programming interfaces. Support for the ARM Cortex-M0/M0+ family was added and board support for Cortex-M was expanded. Additionally, this release adds many improvements for documentation, build infrastructure, and testing. Major enhancements included with the release: * Introduced the Unified Kernel; the nano and micro kernel were removed. * The legacy API is still supported but deprecated. * Legacy tests and samples were moved to tests/legacy and samples/legacy. * Unified kernel documentation was added and legacy nanokernel/microkernel documentation was removed. * Added support for several ARM Cortex-M boards * Added support for USB mass storage and access to the filesystem. * Added native Bluetooth Controller support. Currently nRF51 & nRF52 are supported. A detailed list of changes since v1.5.0 by component follows: Kernel ****** * Introduced the unified kernel. * Removed deprecated Tasks IRQs. * Removed deprecated dynamic interrupt API. * Added DLIST to operate in all elements of a doubly-linked list. * SLIST: Added sys_slist_get() to fetch and remove the head, also Added append_list and merge_slist. * Added nano_work_pending to check if it is pending execution. * Unified: Added support for k_malloc and k_free. * Renamed kernel objects event to alert and memory map to memory slab. * Changed memory pool, memory maps, message queues and event handling APIs. Architectures ************* * ARC: Removed CONFIG_TIMER0_CLOCK_FREQ. * ARC: Unified linker scripts. * ARC: Removed dynamic interrupts. * ARM: Added choice to use floating point ABI. * ARM: Added NXP Kinetis kconfig options to configure clocks. * ARM: Removed dynamic interrupts and exceptions. * ARM: Atmel: Added constants and structures for watchdog registers. * ARM: Added support for ARM Cortex-M0/M0+. * x86: Removed dynamic interrupts and exceptions. * x86: Declared internal API for interrupt controllers. * x86: Changed IRQ controller to return -1 if cannot determine source vector. * x86: Grouped Quark SoC's under intel_quark family. * x86: Optimized and simplified IRQ and exception stubs. Boards ****** * Renamed board Quark SE devboard to Quark SE C1000 devboard. * Renamed board Quark SE SSS devboard to Quark SE C1000 SS devboard. * Quark SE C1000: Disabled IPM and enabled UART0 on the Sensor Subsystem. * Removed basic_cortex_m3 and basic_minuteia boards. * Arduino 101: Removed backup/restore scripts. To restore original bootloader use flashpack utility instead. * Renamed nRF52 Nitrogen to 96Boards Nitrogen. * Added ARM LTD Beetle SoC and V2M Beetle board. * Added Texas Instruments CC3200 LaunchXL support. * Added support for Nordic Semiconductor nRF51822. * Added support for NXP Hexiwear board. Drivers and Sensors ******************* * SPI: Fixed typos in SPI port numbers. * Pinmux: Removed Quark dev unused file. * I2C: Added KSDK shim driver. * Ethernet: Added KSDK shim driver. * Flash: Added KSDK shim driver * I2C: Changed config parameters to SoC specific. * QMSI: Implemented suspend and resume functions QMSI shim drivers * Added HP206C sensor. * Changed config_info pointers to const. * Added support for SoCWatch driver. * Added FXOS8700 accelerometer / magnetometer sensor driver. Networking ********** * Minor fixes to uIP networking stack (This will be deprecated in 1.7) Bluetooth ********* * Added native Bluetooth Controller support. Currently nRF51 & nRF52 are supported. * New location for Controller & Host implementations: subsys/bluetooth/ * Added raw HCI API to enable physical HCI transport for a Controller-only build. * Added sample raw HCI apps for USB and UART. * Added cross-transport pairing support for the Security Manager Protocol. * Added RFCOMM support (for Bluetooth Classic) * Added basic persistent storage support (filesystem-backed) * Renamed bt_driver API to bt_hci_driver, in anticipation of Bluetooth radio drivers. Build Infrastructure ******************** * Makefile: Changed outdir into board-specific directory to avoid build collisions. * Makefile: Changed to use HOST_OS environment variable. * Makefile: Added support for third party build systems. * Sanity: Added support to filter using environment variables. * Sanity: Added support for multiple toolchains. * Sanity: Added ISSM and ARM GCC embedded toolchains to the supported toolchains. * Sanity: Added extra arguments to be passed to the build. * Sanity: Removed linker VMA/LMA offset check. * Sysgen: Added --kernel_type argument. * Modified build infrastructure to support unified kernel. * SDK: Zephyr: Added check for minimum required version. * Imported get_maintainer.pl from Linux kernel. Libraries ********* * libc: Added subset of standard types in inttypes.h. * libc: Added support for 'z' length specifier. * libc: Removed stddef.h which is provided by the compiler. * libc: printf: Improved code for printing. * printk: Added support for modifiers. * Added CoAP implementation for Zephyr. * File system: Added API to grow or shrink a file. * File system: Added API to get volume statistics. * File system: Added API to flush cache of an opened file. HALs **** * QMSI: Updated to version 1.3.1. * HAL: Imported CC3200 SDK. * Imported Nordic MDK nRF51 files. * Imported Kinetis SDK Ethernet phy driver. * Imported SDK RNGA driver. Documentation ************* * Drivers: Improved Zephyr Driver model. * Updated device power management API. * Unified Kernel primer. * Moved supported board information to the wiki.zephyrproject.org site. * Revised documentation for Kernel Event logger and Timing. Test and Samples **************** * Fixed incorrect printk usage. * Removed test for dynamic exceptions. * Added USB sample. * Added tests and samples for CoAP client and server. * Added philosophers unified sample. * Removed printf/printk wrappers. * Added Unified kernel API samples. * Imported TinyCrypt test cases for CTR, ECC DSA and ECC DH algorithm. Deprecations ************ * Deprecated microkernel and nanokernel APIs. * Removed dynamic IRQs and exceptions. * Removed Tasks IRQs. JIRA Related Items ****************** * ``ZEP-308`` - Build System cleanup and Kernel / Application build separation * ``ZEP-334`` - Unified Kernel * ``ZEP-766`` - USB Mass Storage access to internal filesystem * ``ZEP-1090`` - CPU x86 save/restore using new QMSI bootloader flow * ``ZEP-1173`` - Add support for bonding remove * ``ZEP-48`` - define API for interrupt controllers * ``ZEP-181`` - Persistent storage APIs * ``ZEP-233`` - Support USB mass storage device class * ``ZEP-237`` - Support pre-built host tools * ``ZEP-240`` - printk/printf usage in samples * ``ZEP-248`` - Add a BOARD/SOC porting guide * ``ZEP-342`` - USB DFU * ``ZEP-451`` - Quark SE output by default redirected to IPM * ``ZEP-521`` - ARM - add choice to floating point ABI selection * ``ZEP-546`` - UART interrupts not triggered on ARC * ``ZEP-584`` - warn user if SDK is out of date * ``ZEP-592`` - Sanitycheck support for multiple toolchains * ``ZEP-605`` - SMP over BR/EDR * ``ZEP-614`` - Port TinyCrypt 2.0 test cases to Zephyr * ``ZEP-622`` - Add FS API to truncate/shrink a file * ``ZEP-627`` - Port Trickle support from Contiki into current stack * ``ZEP-635`` - Add FS API to grow a file * ``ZEP-636`` - Add FS API to get volume total and free space * ``ZEP-640`` - Remove dynamic IRQs/exceptions from Zephyr * ``ZEP-653`` - QMSI shim driver: Watchdog: Implement suspend and resume callbacks * ``ZEP-654`` - QMSI shim driver: I2C: Implement suspend and resume callbacks * ``ZEP-657`` - QMSI shim driver: AONPT: Implement suspend and resume callbacks * ``ZEP-661`` - QMSI shim driver: SPI: Implement suspend and resume callbacks * ``ZEP-688`` - unify duplicated sections of arch linker scripts * ``ZEP-715`` - Add K64F clock configurations * ``ZEP-716`` - Add Hexiwear board support * ``ZEP-717`` - Add ksdk I2C shim driver * ``ZEP-718`` - Add ksdk ethernet shim driver * ``ZEP-721`` - Add FXOS8700 accelerometer/magnetometer sensor driver * ``ZEP-737`` - Update host tools from upstream: fixdep.c * ``ZEP-740`` - PWM API: Check if 'flags' argument is really required * ``ZEP-745`` - Revisit design of PWM Driver API * ``ZEP-750`` - Arduino 101 board should support one configuration using original bootloader * ``ZEP-758`` - Rename Quark SE Devboard to its official name: Quark SE C1000 * ``ZEP-767`` - Add FS API to flush cache of an open file * ``ZEP-775`` - Enable USB CDC by default on Arduino 101 and redirect serial to USB * ``ZEP-783`` - ARM Cortex-M0/M0+ support * ``ZEP-784`` - Add support for Nordic Semiconductor nRF51822 SoC * ``ZEP-850`` - remove obsolete boards basic_minuteia and basic_cortex_m3 * ``ZEP-906`` - [unified] Add scheduler time slicing support * ``ZEP-907`` - Test memory pool support (with mailboxes) * ``ZEP-908`` - Add task offload to fiber support * ``ZEP-909`` - Adapt tickless idle + power management for ARM * ``ZEP-910`` - Adapt tickless idle for x86 * ``ZEP-912`` - Finish renaming kernel object types * ``ZEP-916`` - Eliminate kernel object API anomalies * ``ZEP-920`` - Investigate malloc/free support * ``ZEP-921`` - Miscellaneous documentation work * ``ZEP-922`` - Revise documentation for Kernel Event Logger * ``ZEP-923`` - Revise documentation for Timing * ``ZEP-924`` - Revise documentation for Interrupts * ``ZEP-925`` - API changes to message queues * ``ZEP-926`` - API changes to memory pools * ``ZEP-927`` - API changes to memory maps * ``ZEP-928`` - API changes to event handling * ``ZEP-930`` - Cut over to unified kernel * ``ZEP-933`` - Unified kernel ARC port * ``ZEP-934`` - NIOS_II port * ``ZEP-935`` - Kernel logger support (validation) * ``ZEP-954`` - Update device PM API to allow setting additional power states * ``ZEP-957`` - Create example sample for new unified kernel API usage * ``ZEP-959`` - sync checkpatch.pl with upstream Linux * ``ZEP-966`` - need support for EM7D SOC on em_starterkit * ``ZEP-975`` - DNS client port to new IP stack * ``ZEP-981`` - Add doxygen documentation to both include/kernel.h and include/legacy.h * ``ZEP-989`` - Cache next ready thread instead of finding out the long way * ``ZEP-993`` - Quark SE (x86): Refactor save/restore execution context feature * ``ZEP-994`` - Quark SE (ARC): Add PMA sample * ``ZEP-996`` - Refactor save/restore feature from i2c_qmsi driver * ``ZEP-997`` - Refactor save/restore feature from spi_qmsi driver * ``ZEP-998`` - Refactor save/restore feature from uart_qmsi driver * ``ZEP-999`` - Refactor save/restore feature from gpio_qmsi driver * ``ZEP-1000`` - Refactor save/restore feature from rtc_qmsi driver * ``ZEP-1001`` - Refactor save/restore feature from wdt_qmsi driver * ``ZEP-1002`` - Refactor save/restore feature from counter_qmsi_aonpt driver * ``ZEP-1004`` - Extend counter_qmsi_aon driver to support save/restore peripheral context * ``ZEP-1005`` - Extend dma_qmsi driver to support save/restore peripheral context * ``ZEP-1006`` - Extend soc_flash_qmsi driver to support save/restore peripheral context * ``ZEP-1008`` - Extend pwm_qmsi driver to support save/restore peripheral context * ``ZEP-1023`` - workq in Kernel primer for unified kernel * ``ZEP-1030`` - Enable QMSI shim drivers of SoC peripherals on the sensor subsystem * ``ZEP-1043`` - Update QMSI to 1.2 * ``ZEP-1045`` - Add/Enhance shim layer to wrap SOC specific PM implementations * ``ZEP-1046`` - Implement RAM sharing between bootloader and Zephyr * ``ZEP-1047`` - Adapt to new PM related boot flow changes in QMSI boot loader * ``ZEP-1106`` - Fix all test failures from TCF * ``ZEP-1107`` - Update QMSI to 1.3 * ``ZEP-1109`` - Texas Instruments CC3200 LaunchXL Support * ``ZEP-1119`` - move top level usb/ to sys/usb * ``ZEP-1120`` - move top level fs/ to sys/fs * ``ZEP-1121`` - Add config support for enabling SoCWatch in Zephyr * ``ZEP-1140`` - Add a unified kernel version of power_mgr sample app for testing PM code with the new kernel * ``ZEP-1188`` - Add an API to retrieve pending interrupts for wake events * ``ZEP-1191`` - Create wiki page for Hexiwear board * ``ZEP-1235`` - Basic shell support for file system browsing * ``ZEP-1245`` - ARM LTD V2M Beetle Support * ``ZEP-1313`` - porting and user guides must include a security section * ``ZEP-1386`` - Revise power management document to reflect latest changes * ``ZEP-199`` - Zephyr driver model is undocumented * ``ZEP-436`` - Test case tests/kernel/test_mem_safe fails on ARM hardware * ``ZEP-471`` - Ethernet packet with multicast address is not working * ``ZEP-472`` - Ethernet packets are getting missed if sent in quick succession. * ``ZEP-517`` - build on windows failed "zephyr/Makefile:869: \\\* multiple target patterns" * ``ZEP-528`` - ARC has 2 almost identical copies of the linker script * ``ZEP-577`` - Sample application source does not compile on Windows * ``ZEP-601`` - enable CONFIG_DEBUG_INFO * ``ZEP-602`` - unhandled CPU exceptions/interrupts report wrong faulting vector if triggered by CPU * ``ZEP-615`` - Un-supported flash erase size listed in SPI flash w25qxxdv driver header file * ``ZEP-639`` - device_pm_ops structure should be defined as static * ``ZEP-686`` - docs: Info in "Application Development Primer" and "Developing an Application and the Build System" is largely duplicated * ``ZEP-698`` - samples/task_profiler issues * ``ZEP-707`` - mem_safe test stomps on top of .data and bottom of .noinit * ``ZEP-724`` - build on windows failed: 'make: execvp: uname: File or path name too long' * ``ZEP-733`` - Minimal libc shouldn't be providing stddef.h * ``ZEP-762`` - unexpected "abspath" and "notdir" from mingw make system * ``ZEP-777`` - samples/driver/i2c_stts751: kconfig build warning from "select DMA_QMSI" * ``ZEP-778`` - Samples/drivers/i2c_lsm9ds0: kconfig build warning from "select DMA_QMSI" * ``ZEP-779`` - Using current MinGW gcc version 5.3.0 breaks Zephyr build on Windows * ``ZEP-845`` - UART for ARC on Arduino 101 behaves unexpectedly * ``ZEP-905`` - hello_world compilation for arduino_due target fails when using CROSS_COMPILE * ``ZEP-940`` - Fail to get ATT response * ``ZEP-950`` - USB: Device is not listed by USB20CV test suite * ``ZEP-961`` - samples: other cases cannot execute after run aon_counter case * ``ZEP-967`` - Sanity doesn't build 'samples/usb/dfu' with assertions (-R) * ``ZEP-970`` - Sanity doesn't build 'tests/kernel/test_build' with assertions (-R) * ``ZEP-982`` - Minimal libc has EWOULDBLOCK != EAGAIN * ``ZEP-1014`` - [TCF] tests/bluetooth/init build fail * ``ZEP-1025`` - Unified kernel build sometimes breaks on a missing .d dependency file. * ``ZEP-1027`` - Documentation for GCC ARM is not accurate * ``ZEP-1031`` - qmsi: dma: driver test fails with LLVM * ``ZEP-1048`` - grove_lcd sample: sample does not work if you disable serial * ``ZEP-1051`` - mpool allocation failed after defrag twice... * ``ZEP-1062`` - Unified kernel isn't compatible with CONFIG_NEWLIB_LIBC * ``ZEP-1074`` - ATT retrying misbehaves when ATT insufficient Authentication is received * ``ZEP-1076`` - "samples/philosophers/unified" build failed with dynamic stack * ``ZEP-1077`` - "samples/philosophers/unified" build warnings with NUM_PHIL<6 * ``ZEP-1079`` - Licensing not clear for imported components * ``ZEP-1097`` - ENC28J60 driver fails on concurrent tx and rx * ``ZEP-1098`` - ENC28J60 fails to receive big data frames * ``ZEP-1100`` - Current master still identifies itself as 1.5.0 * ``ZEP-1101`` - SYS_KERNEL_VER_PATCHLEVEL() and friends artificially limit version numbers to 4 bits * ``ZEP-1124`` - tests/kernel/test_sprintf/microkernel/testcase.ini#test failure on frdm_k64f * ``ZEP-1130`` - region 'RAM' overflowed occurs while building test_hmac_prng * ``ZEP-1138`` - Received packets not being passed to upper layer from IP stack when using ENC28J60 driver * ``ZEP-1139`` - Fix build error when power management is built with unified kernel * ``ZEP-1141`` - TinyCrypt SHA256 test fails with system crash using unified kernel type * ``ZEP-1144`` - TinyCrypt AES128 fixed-key with variable-text test fails using unified kernel type * ``ZEP-1145`` - system hang after TinyCrypt HMAC test * ``ZEP-1146`` - zephyrproject.org home page needs technical scrub for 1.6 release * ``ZEP-1149`` - port ztest framework to unified kernel * ``ZEP-1154`` - tests/samples failing with unified kernel * ``ZEP-1155`` - Fix filesystem API namespace * ``ZEP-1163`` - LIB_INCLUDE_DIR is clobbered in Makefile second pass * ``ZEP-1164`` - ztest skip waiting the test case to finish its execution * ``ZEP-1179`` - Build issues when compiling with LLVM from ISSM (icx) * ``ZEP-1182`` - kernel.h doxygen show unexpected "asm" blocks * ``ZEP-1183`` - btshell return "panic: errcode -1" when init bt * ``ZEP-1195`` - Wrong ATT error code passed to the application * ``ZEP-1199`` - [L2CAP] No credits to receive packet * ``ZEP-1219`` - [L2CAP] Data sent exceeds maximum PDU size * ``ZEP-1221`` - Connection Timeout during pairing * ``ZEP-1226`` - cortex M7 port assembler error * ``ZEP-1227`` - ztest native testing not working in unified kernel * ``ZEP-1232`` - Daily build is failing asserts * ``ZEP-1234`` - Removal of fiber* APIs due to unified migration breaks USB mass storage patchset * ``ZEP-1247`` - Test tests/legacy/benchmark/latency_measure is broken for daily sanitycheck * ``ZEP-1252`` - Test test_chan_blen_transfer does not build for quark_d2000_crb * ``ZEP-1277`` - Flash driver (w25qxxdv) erase function is not checking for offset alignment * ``ZEP-1278`` - Incorrect boundary check in flash driver (w25qxxdv) for erase offset * ``ZEP-1287`` - ARC SPI 1 Port is not working * ``ZEP-1289`` - Race condition with k_sem_take * ``ZEP-1291`` - libzephyr.a dependency on phony "gcc" target * ``ZEP-1293`` - ENC28J60 driver doesn't work on Arduino 101 * ``ZEP-1295`` - incorrect doxygen comment in kernel.h:k_work_pending() * ``ZEP-1297`` - test/legacy/kernel/test_mail: failure on ARC platforms * ``ZEP-1299`` - System can't resume completely with DMA suspend and resume operation * ``ZEP-1302`` - ENC28J60 fails with rx/tx of long frames * ``ZEP-1303`` - Configuration talks about >32 thread prios, but the kernel does not support it * ``ZEP-1309`` - ARM uses the end of memory for its init stack * ``ZEP-1310`` - ARC uses the end of memory for its init stack * ``ZEP-1312`` - ARC: software crashed at k_mbox_get() with async sending a message * ``ZEP-1319`` - Zephyr is unable to compile when CONFIG_RUNTIME_NMI is enabled on ARM platforms * ``ZEP-1341`` - power_states test app passes wrong value as power state to post_ops functions * ``ZEP-1343`` - tests/drivers/pci_enum: failing on QEMU ARM and X86 due to missing commit * ``ZEP-1345`` - cpu context save and restore could corrupt stack * ``ZEP-1349`` - ARC sleep needs to pass interrupt priority threshold when interrupts are enabled * ``ZEP-1353`` - FDRM k64f Console output broken on normal flash mode Known Issues ************ * ``ZEP-1405`` - function l2cap_br_conn_req in /subsys/bluetooth/host/l2cap_br.c references uninitialized pointer ```	/content/code_sandbox/doc/releases/release-notes-1.6.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	5,300
```restructuredtext .. _safety_requirements: Safety Requirements ################### Introduction ********** The safety committee leads the effort to gather requirements that reflect the actual state of the implementation, following the `route 3s <path_to_url#general-safety-scope>`_ approach of the project's safety effort. The goal is NOT to create new requirements to request additional features for the project. The requirements are gathered in the separate repository: `Requirement repository <path_to_url`__ Guidelines ******** Below are the guidelines for the requirements repository and the expectations of the safety committee when adding requirements to the repository. Scope ===== The scope of the requirements covers the KERNEL functionalities. Consistency =========== Maintain consistency across all requirements. The language and choice of words shall be consistent. (See: `Syntax`_) Levels of requirements in the repository ======================================== System Requirements System requirements describe the behaviour of the Zephyr RTOS (= the system here). They describe the functionality of the Zephyr RTOS from a very high-level perspective, without going into details of the functionality itself. The purpose of the system requirements is to get an overview of the currently implemented features of the Zephyr RTOS. In other words a person writing these requirements usually has some knowledge of the Zephyr RTOS Project as the requirements are specific to an RTOS. Software Requirements Software requirements refine the system-level requirements at a more granular level so that each requirement can be tested. These requirements define the specific actions the feature shall be able to execute and the behavior of the feature. Requirement UID (Unique identifier) Handling ============================================ The tool used to manage requirements, `strictDoc <path_to_url`_, is responsible for handling the Unique Identifier (UID) associated with each requirement. To manage UIDs, follow these steps: #. Don't add a requirement UID and UID field for new requirements #. After completing work on the new requirements execute: ``strictDoc manage auto-uid .`` #. Establish links between the requirements with the new attributed UIDs if needed After doing this, the requirements are ready and a pull request can be created. The CI in the PR will check if the requirements UIDs are valid or if there are duplicates in it. If there are duplicates in the PR, these need to be resolved by rebasing and re-executing the steps above. Requirement Types ================= * Functional * Non-Functional Requirement title convention ============================ Use short and succinct requirement titles. Pull Request requirement repository =================================== * Adhere to the :ref:`contribute_guidelines` of the Zephyr Project. * As long as they are applicable to the requirements repository. * Avoid creating large commits that contain both trivial and non-trivial changes. * Avoid moving and changing requirements in the same commit. Characteristics of a good requirement ===================================== * Unambiguous * Verifiable (e.g. testable for functional requirements) * Clear (concise, succinct, simple, precise) * Correct * Understandable * Feasible (realistic, possible) * Independent * Atomic * Necessary * Implementation-free (abstract) Characteristics of a set of requirements ======================================== * Complete * Consistent * Non redundant Syntax ====== * Use of a recognized Requirements Syntax is recommended. * `EARS <path_to_url`_ is a good reference. Particularly if you are unfamiliar with requirements writing. * Other formats are accepted as long as the characteristics of a requirement from above are met. ```	/content/code_sandbox/doc/safety/safety_requirements.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	757
```css /** * * Custom stylesheet for Google Programmable Search Engine results. / .gs-webResult .gs-snippet, .gs-fileFormatType, .gs-spelling, .gsc-refinementHeader, .gsc-result-info, .gsc-orderby-label { color: var(--body-color) !important; } .gsc-control-cse { width: 100%; padding: 0 !important; font-family: inherit !important; font-size: inherit !important; background-color: inherit !important; border: none !important; font-size: inherit !important; } .gsc-completion-container { font-family: inherit !important; } .gs-result .gs-title, .gs-result .gs-title { color: var(--link-color) !important; background-color: var(--content-background-color) !important; } .gs-result .gs-title:visited, .gs-result .gs-title:visited * { color: var(--link-color-visited) !important; } .gsc-results .gsc-cursor-box .gsc-cursor-page, .gsc-results .gsc-cursor-box .gsc-cursor-current-page { background-color: var(--content-background-color) !important; color: var(--link-color) !important; } .gs-result .gs-image, .gs-result .gs-promotion-image { border: none !important; padding-right: .5em; } .gsc-table-result { font-family: inherit !important; padding-top: .5em !important; font-size: inherit !important; } .gsc-tabHeader.gsc-tabhActive, .gsc-refinementHeader.gsc-refinementhActive, .gsc-tabHeader.gsc-tabhInactive, .gsc-refinementHeader.gsc-refinementhInactive { background-color: inherit !important; } .gs-no-results-result .gs-snippet, .gs-error-result .gs-snippet { color: var(--admonition-attention-title-color) !important; background-color: var(--admonition-attention-title-background-color) !important; } .gsc-webResult .gsc-result { background-color: inherit !important; margin: 0; padding: .5em 0; border: none !important; border-bottom: 1px solid var(--hr-color) !important; } .gs-webResult div.gs-per-result-labels { margin-top: 1.3em; margin-bottom: 0.3em; font-size:0.8em; } .gs-webResult div.gs-per-result-labels span { display: none; } .gs-webResult div.gs-per-result-labels a.gs-label { text-decoration: none !important; cursor: pointer; padding: 0.4em 0.6em; margin-left: .5em; color: var(--admonition-tip-title-color) !important; background-color: var(--admonition-tip-title-background-color) !important; border-radius: 50px; } .gcsc-find-more-on-google { color: var(--link-color) !important; } .gcsc-find-more-on-google-magnifier { fill: var(--link-color) !important; } ```	/content/code_sandbox/doc/_static/css/gcs.css	css	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	679
```css /** * * Dark theme colors / :root { --body-color: rgba(255, 255, 255, 0.85); --content-wrap-background-color: #202326; --content-background-color: #2e3236; / Decrease the logo opacity when using the dark theme to be less distracting / --logo-opacity: 0.85; --navbar-background-color: #25282b; --navbar-background-color-hover: #333639; --navbar-background-color-active: #111417; --navbar-current-background-color: #333639; --navbar-current-background-color-hover: #44474a; --navbar-current-background-color-active: #222528; --navbar-level-1-color: #ddd; --navbar-level-2-color: #ccc; --navbar-level-3-color: #bbb; --navbar-heading-color: #af7fe4; --navbar-scrollbar-color: #af7fe4; --navbar-scrollbar-hover-color: #9454db; --navbar-scrollbar-active-color: #7929d2; --navbar-scrollbar-background: #1c1e21; --link-color: #8cf; --link-color-hover: #9df; --link-color-active: #6ad; --link-color-visited: #cb99f6; --external-reference-icon: url("data:image/svg+xml;base64,your_sha256_hashLm9yZy8yMDAwL3N2ZyI+your_sha256_hashLjRoLTZ2LTZoMy40Ii8+your_sha256_hashyour_sha256_hasheiIvPjwvZz48L3N2Zz4K"); --classref-badge-text-color: hsl(0, 0%, 70%); --hr-color: #555; --table-row-odd-background-color: #3b3e41; --code-background-color: #434649; --code-border-color: #505356; --code-literal-color: #faa; --input-background-color: #333537; --input-focus-border-color: #5f8cff; --search-input-background-color: #43464a; / derived from --input-background-color / --search-match-color: #52b4ff; / derived from --link-color / --search-match-background-color: #414c56; / derived from --link-color / --search-active-color: #202326; --search-credits-background-color: #202123; / derived from --navbar-background-color / --search-credits-color: #6b6b6b; / derived from --footer-color / --search-credits-link-color: #628fb1; / derived from --link-color / / Colors taken from the Godot script editor with the Adaptive theme */ --highlight-background-color: #202531; --highlight-background-emph-color: #2d3444; --highlight-default-color: rgba(255, 255, 255, 0.85); --highlight-comment-color: rgba(204, 206, 211, 0.5); --highlight-keyword-color: #ff7085; --highlight-keyword2-color: #42ffc2; --highlight-number-color: #a1ffe0; --highlight-decorator-color: #abc8ff; --highlight-type-color: #8effda; --highlight-type2-color: #c6ffed; --highlight-function-color: #57b3ff; --highlight-operator-color: #abc8ff; --highlight-string-color: #ffeca1; --admonition-note-background-color: #303d4f; --admonition-note-color: #bfeeff; --admonition-note-title-background-color: #305070; --admonition-note-title-color: #bfefff; --admonition-attention-background-color: #444033; --admonition-attention-color: #ffeeaf; --admonition-attention-title-background-color: #665022; --admonition-attention-title-color: #ffeeaf; --admonition-danger-background-color: #433; --admonition-danger-color: #fcc; --admonition-danger-title-background-color: #633; --admonition-danger-title-color: #fcc; --admonition-tip-background-color: #28382d; --admonition-tip-color: #dfd; --admonition-tip-title-background-color: #336648; --admonition-tip-title-color: #dfd; --kbd-background-color: #595b5d; --kbd-outline-color: #3d4144; --kbd-shadow-color: #1e2023; --kbd-text-color: #e2f2ff; --guiitems-background-color: #303d4f; --guiitems-border-color: #7fbbe3; --btn-neutral-background-color: #404040; --btn-neutral-hover-background-color: #505050; --footer-color: #aaa; } ```	/content/code_sandbox/doc/_static/css/dark.css	css	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,106
```css /** * * Light theme colors / :root { --body-color: #404040; --content-wrap-background-color: #efefef; --content-background-color: #fcfcfc; --logo-opacity: 1.0; --navbar-background-color: #333f67; --navbar-background-color-hover: #29355c; --navbar-background-color-active: #212d51; --navbar-current-background-color: #212d51; --navbar-current-background-color-hover: #182343; --navbar-current-background-color-active: #131e3b; --navbar-level-1-color: #c3e3ff; --navbar-level-2-color: #b8d6f0; --navbar-level-3-color: #a3c4e1; --navbar-heading-color: #af7fe4; --navbar-scrollbar-color: #af7fe4; --navbar-scrollbar-hover-color: #9454db; --navbar-scrollbar-active-color: #7929d2; --navbar-scrollbar-background: #131e2b; --link-color: #2980b9; --link-color-hover: #3091d1; --link-color-active: #105078; --link-color-visited: #9b59b6; --external-reference-icon: url("data:image/svg+xml;base64,your_sha256_hashLm9yZy8yMDAwL3N2ZyI+your_sha256_hashMXYzLjRoLTZ2LTZoMy40Ii8+your_sha256_hashyour_sha256_hasheiIvPjwvZz48L3N2Zz4K"); --classref-badge-text-color: hsl(0, 0%, 45%); --hr-color: #e1e4e5; --table-row-odd-background-color: #f3f6f6; --code-background-color: #fff; --code-border-color: #e1e4e5; --code-literal-color: #d04c60; --input-background-color: #fcfcfc; --input-focus-border-color: #5f8cff; --search-input-background-color: #e6eef3; / derived from --input-background-color / --search-match-color: #2c6b96; / derived from --link-color / --search-match-background-color: #e3f2fd; / derived from --link-color / --search-active-color: #efefef; --search-credits-background-color: #333f67; / derived from --navbar-background-color / --search-credits-color: #b3b3b3; / derived from --footer-color / --search-credits-link-color: #4392c5; / derived from --link-color */ --highlight-background-color: #f0f2f4; --highlight-background-emph-color: #dbe6c3; --highlight-default-color: #404040; --highlight-comment-color: #408090; --highlight-keyword-color: #007020; --highlight-keyword2-color: #902000; --highlight-number-color: #208050; --highlight-decorator-color: #4070a0; --highlight-type-color: #007020; --highlight-type2-color: #0e84b5; --highlight-function-color: #06287e; --highlight-operator-color: #666666; --highlight-string-color: #4070a0; --admonition-note-background-color: #e7f2fa; --admonition-note-color: #404040; --admonition-note-title-background-color: #6ab0de; --admonition-note-title-color: #fff; --admonition-attention-background-color: #ffedcc; --admonition-attention-color: #404040; --admonition-attention-title-background-color: #f0b37e; --admonition-attention-title-color: #fff; --admonition-danger-background-color: #fcf3f2; --admonition-danger-color: #404040; --admonition-danger-title-background-color: #e9a499; --admonition-danger-title-color: #fff; --admonition-tip-background-color: #dbfaf4; --admonition-tip-color: #404040; --admonition-tip-title-background-color: #1abc9c; --admonition-tip-title-color: #fff; --kbd-background-color: #fafbfc; --kbd-outline-color: #d1d5da; --kbd-shadow-color: #b0b7bf; --kbd-text-color: #444d56; --guiitems-background-color: #e7f2fa; --guiitems-border-color: #7fbbe3; --btn-neutral-background-color: #f3f6f6; --btn-neutral-hover-background-color: #e5ebeb; --footer-color: #808080; } ```	/content/code_sandbox/doc/_static/css/light.css	css	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,107
```javascript /** * Simple search result scoring code. * */ var Scorer = { // Implement the following function to further tweak the score for // each result The function takes a result array [filename, title, // anchor, descr, score] and returns the new score. // For Zephyr search results, push display down for kconfig, boards, // and samples so "regular" docs will show up before them score: function(result) { if (result[0].search("reference/kconfig/")>=0) { return -5; } else if (result[0].search("boards/")>=0) { return -5; } else if (result[0].search("samples/")>=0) { return -5; } else { return result[4]; } }, // query matches the full name of an object objNameMatch: 11, // or matches in the last dotted part of the object name objPartialMatch: 6, // Additive scores depending on the priority of the object objPrio: {0: 15, // used to be importantResults 1: 5, // used to be objectResults 2: -5}, // used to be unimportantResults // Used when the priority is not in the mapping. objPrioDefault: 0, // query found in title title: 15, // query found in terms term: 5 }; ```	/content/code_sandbox/doc/_static/js/scorer.js	javascript	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	336
```javascript /** / // Handle page scroll and adjust sidebar accordingly. // Each page has two scrolls: the main scroll, which is moving the content of the page; // and the sidebar scroll, which is moving the navigation in the sidebar. // We want the logo to gradually disappear as the main content is scrolled, giving // more room to the navigation on the left. This means adjusting the height // available to the navigation on the fly. const registerOnScrollEvent = (function(){ // Configuration. // The number of pixels the user must scroll by before the logo is completely hidden. const scrollTopPixels = 156; // The target margin to be applied to the navigation bar when the logo is hidden. const menuTopMargin = 54; // The max-height offset when the logo is completely visible. const menuHeightOffset_default = 210; // The max-height offset when the logo is completely hidden. const menuHeightOffset_fixed = 63; // The distance between the two max-height offset values above; used for intermediate values. const menuHeightOffset_diff = (menuHeightOffset_default - menuHeightOffset_fixed); // Media query handler. return function(mediaQuery) { // We only apply this logic to the "desktop" resolution (defined by a media query at the bottom). // This handler is executed when the result of the query evaluation changes, which means that // the page has moved between "desktop" and "mobile" states. // When entering the "desktop" state, we register scroll events and adjust elements on the page. // When entering the "mobile" state, we clean up any registered events and restore elements on the page // to their initial state. const $window = $(window); const $sidebar = $('.wy-side-scroll'); const $search = $sidebar.children('.wy-side-nav-search'); const $menu = $sidebar.children('.wy-menu-vertical'); if (mediaQuery.matches) { // Entering the "desktop" state. // The main scroll event handler. // Executed as the page is scrolled and once immediately as the page enters this state. const handleMainScroll = (currentScroll) => { if (currentScroll >= scrollTopPixels) { // After the page is scrolled below the threshold, we fix everything in place. $search.css('margin-top', `-${scrollTopPixels}px`); $menu.css('margin-top', `${menuTopMargin}px`); $menu.css('max-height', `calc(100% - ${menuHeightOffset_fixed}px)`); } else { // Between the top of the page and the threshold we calculate intermediate values // to guarantee a smooth transition. $search.css('margin-top', `-${currentScroll}px`); $menu.css('margin-top', `${menuTopMargin + (scrollTopPixels - currentScroll)}px`); if (currentScroll > 0) { const scrolledPercent = (scrollTopPixels - currentScroll) / scrollTopPixels; const offsetValue = menuHeightOffset_fixed + menuHeightOffset_diff scrolledPercent; $menu.css('max-height', `calc(100% - ${offsetValue}px)`); } else { $menu.css('max-height', `calc(100% - ${menuHeightOffset_default}px)`); } } }; // The sidebar scroll event handler. // Executed as the sidebar is scrolled as well as after the main scroll. This is needed // because the main scroll can affect the scrollable area of the sidebar. const handleSidebarScroll = () => { const menuElement = $menu.get(0); const menuScrollTop = $menu.scrollTop(); const menuScrollBottom = menuElement.scrollHeight - (menuScrollTop + menuElement.offsetHeight); // As the navigation is scrolled we add a shadow to the top bar hanging over it. if (menuScrollTop > 0) { $search.addClass('fixed-and-scrolled'); } else { $search.removeClass('fixed-and-scrolled'); } }; $search.addClass('fixed'); $window.scroll(function() { handleMainScroll(window.scrollY); handleSidebarScroll(); }); $menu.scroll(function() { handleSidebarScroll(); }); handleMainScroll(window.scrollY); handleSidebarScroll(); } else { // Entering the "mobile" state. $window.unbind('scroll'); $menu.unbind('scroll'); $search.removeClass('fixed'); $search.css('margin-top', `0px`); $menu.css('margin-top', `0px`); $menu.css('max-height', 'initial'); } }; })(); $(document).ready(() => { // Initialize handlers for page scrolling and our custom sidebar. const mediaQuery = window.matchMedia('only screen and (min-width: 769px)'); registerOnScrollEvent(mediaQuery); mediaQuery.addListener(registerOnScrollEvent); }); ```	/content/code_sandbox/doc/_static/js/custom.js	javascript	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,044
```css /** * * Various tweaks to the Read the Docs theme to better conform with Zephyr's * visual identity. Many colors are also overridden to use CSS variables. / body, h1, h2, h3, h4, h5, h6, input[type="text"], input[type="button"], input[type="reset"], input[type="submit"], textarea, legend, .btn, .rst-content .toctree-wrapper p.caption, .rst-versions { / Use a system font stack for better performance (no Web fonts required) / font-family: system-ui, -apple-system, "Segoe UI", Roboto, "Helvetica Neue", Arial, "Noto Sans", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji"; } h1, h2, h3, h4, h5, h6, legend, .rst-content .toctree-wrapper p.caption { / Use a lighter font for headers (Medium instead of Bold) / font-weight: 500; } .rst-content div.figure p.caption { / Tweak caption styling to be closer to typical captions / text-align: center; margin-top: 8px; opacity: 0.75; } .rst-content div.figure.figure-w480 { max-width: 480px; } p, article ul, article ol, .wy-plain-list-disc, .wy-plain-list-decimal, .rst-content ol.arabic, .rst-content .section ul, .rst-content .toctree-wrapper ul, .rst-content .section ol { / Increase the line height slightly to account for the different font / line-height: 25px; } body, .rst-content table.docutils thead { color: var(--body-color); } a { color: var(--link-color); } a:hover { color: var(--link-color-hover); text-decoration: underline; } a:active { / Add visual feedback when clicking on a link / color: var(--link-color-active); } a:visited { color: var(--link-color-visited); } a.btn:hover { text-decoration: none; } .sphinx-tabs .sphinx-menu a.item { / Original definition has `!important` / color: var(--link-color) !important; } .rst-content .toc-backref { color: var(--link-color); } / Style external links differently to make them easier to distinguish from internal links. / .reference.external { background-position: center right; background-repeat: no-repeat; background-image: var(--external-reference-icon); padding-right: 13px; } hr, #search-results .search li:first-child, #search-results .search li { border-color: var(--hr-color); } / JavaScript documentation directives / .rst-content dl:not(.docutils) dt { background-color: var(--admonition-note-background-color) !important; border-color: var(--admonition-note-title-background-color) !important; color: var(--admonition-note-color) !important; } .rst-content dl:not(.docutils) dl dt { background-color: var(--admonition-attention-background-color) !important; border-color: var(--admonition-attention-title-background-color) !important; color: var(--admonition-attention-color) !important; } .rst-content dt.sig .k { color: var(--highlight-keyword2-color) !important; font-style: normal !important; } .rst-content dt.sig .kt { color: var(--highlight-keyword-color) !important; font-style: normal !important; } .rst-content dt.sig .sig-name .n { color: var(--highlight-function-color) !important; } .rst-content dt.sig .k, .rst-content dt.sig .kt, .rst-content dt.sig .n { font-weight: normal !important; } .rst-content dl:not(.docutils) dt a.headerlink { color: var(--link-color) !important; } .rst-content dl:not(.docutils) dt a.headerlink:visited { color: var(--link-color-visited) !important; } footer, #search-results .context { color: var(--footer-color); } / Icon tweaks / a.icon-home, a.icon-home:visited { color: var(--navbar-level-1-color); } / Main sections / .wy-nav-content-wrap { background-color: var(--content-wrap-background-color); } .wy-nav-content { background-color: var(--content-background-color); } .wy-body-for-nav { background-color: var(--content-wrap-background-color); } @media only screen and (min-width: 769px) { .wy-nav-content { max-width: 915px; } } / Table display tweaks / .rst-content table.docutils, .wy-table-bordered-all td, .rst-content table.docutils td, .wy-table thead th, .rst-content table.docutils thead th, .rst-content table.field-list thead th { border-color: var(--code-border-color); } .rst-content table.docutils caption, .rst-content table.field-list caption, .wy-table caption { color: var(--body-color); } .wy-table-odd td, .wy-table-striped tr:nth-child(2n-1) td, .rst-content table.docutils:not(.field-list) tr:nth-child(2n-1) td { background-color: var(--table-row-odd-background-color); } / Override table no-wrap / / The first column cells are not verbose, no need to wrap them / .wy-table-responsive table td:not(:nth-child(1)), .wy-table-responsive table th:not(:nth-child(1)) { white-space: normal; } / Allow to control wrapping behavior per table / .wy-table-responsive table.wrap-normal td, .wy-table-responsive table.wrap-normal th { white-space: normal; } / Make sure not to wrap keyboard shortcuts / .wy-table-responsive table td kbd { white-space: nowrap; } / Force table content font-size in responsive tables to be 100% * fixing larger font size for paragraphs in the kconfig tables / .wy-table-responsive td p { font-size: 100%; } / Code display tweaks / code, .rst-content tt, .rst-content code { font-size: 14px; background-color: var(--code-background-color); border: 1px solid var(--code-border-color); } .rst-content tt.literal, .rst-content code.literal { color: var(--code-literal-color); } .rst-content div[class^="highlight"] { border-color: none; border: none; } .rst-content pre.literal-block, .rst-content div[class^="highlight"] pre, .rst-content .linenodiv pre { / Increase the font size and line height in code blocks / font-size: 14px; line-height: 1.5; } .rst-content pre.literal-block { border: none; border-radius: 0.25rem; background-color: var(--code-background-color); } / Code tab display tweaks / .ui.tabular.menu .active.item, .ui.segment, .sphinx-tabs-panel { background-color: var(--code-background-color) !important; } .sphinx-tabs-tab { color: var(--link-color) !important; } .sphinx-tabs-tab[aria-selected="true"] { background-color: var(--code-background-color) !important; border-bottom: 1px solid var(--code-background-color) !important; } / Code literals / a.internal code.literal { color: var(--link-color); } a.internal:visited code.literal { color: var(--link-color-visited); } / Syntax highlighting / .tab div[class^='highlight']:last-child { margin-bottom: 1em; } .rst-content tt.literal, .rst-content code.literal, .highlight { border-radius: 0.25rem; } .highlight { background-color: var(--highlight-background-color); } / Emphasized lines / .highlight .hll { background-color: var(--highlight-background-emph-color); } .highlight .gh / Generic.Heading /, .highlight .gu / Generic.Subheading /, .highlight .go / Generic.Output /, .highlight .gt / Generic.Traceback / { color: var(--highlight-default-color); } .highlight .c / Comment /, .highlight .c1 / Comment.Single /, .highlight .cm / Comment.Multiline /, .highlight .cs / Comment.Special / { color: var(--highlight-comment-color); } .highlight .bp / Name.Builtin.Pseudo /, .highlight .k / Keyword /, .highlight .kc / Keyword.Constant /, .highlight .kd / Keyword.Declaration /, .highlight .kn / Keyword.Namespace /, .highlight .kp / Keyword.Pseudo /, .highlight .kr / Keyword.Reserved /, .highlight .kt / Keyword.Type /, .highlight .ow / Operator.Word / { color: var(--highlight-keyword-color); } .highlight .ch / Comment.Hashbang /, .highlight .cp / Comment.Preproc / { color: var(--highlight-keyword2-color); } .highlight .m / Literal.Number /, .highlight .mf / Literal.Number.Float /, .highlight .mi / Literal.Number.Integer /, .highlight .il / Literal.Number.Integer.Long /, .highlight .mb / Literal.Number.Bin /, .highlight .mh / Literal.Number.Hex /, .highlight .mo / Literal.Number.Oct / { color: var(--highlight-number-color); } .highlight .na / Name.Attribute /, .highlight .nd / Name.Decorator /, .highlight .ni / Name.Entity /, .highlight .nl / Name.Label / { color: var(--highlight-decorator-color); } .highlight .nb / Name.Builtin /, .highlight .ne / Name.Exception / { color: var(--highlight-type-color); } .highlight .nc / Name.Class /, .highlight .nn / Name.Namespace /, .highlight .no / Name.Constant /, .highlight .nv / Name.Variable /, .highlight .vc / Name.Variable.Class /, .highlight .vg / Name.Variable.Global /, .highlight .vi / Name.Variable.Instance /, .highlight .vm / Name.Variable.Magic / { color: var(--highlight-type2-color); } .highlight .nf / Name.Function /, .highlight .fm / Name.Function.Magic /, .highlight .nt / Name.Tag / { color: var(--highlight-function-color); } .highlight .o / Operator /, .highlight .si / Literal.String.Interpol /, .highlight .sx / Literal.String.Other /, .highlight .sr / Literal.String.Regex /, .highlight .ss / Literal.String.Symbol / { color: var(--highlight-operator-color); } .highlight .cpf/ Comment.PreprocFile /, .highlight .s / Literal.String /, .highlight .s1 / Literal.String.Single /, .highlight .s2 / Literal.String.Double /, .highlight .sc / Literal.String.Char /, .highlight .se / Literal.String.Escape /, .highlight .sa / Literal.String.Affix /, .highlight .sb / Literal.String.Backtick /, .highlight .dl / Literal.String.Delimiter /, .highlight .sd / Literal.String.Doc /, .highlight .sh / Literal.String.Heredoc / { color: var(--highlight-string-color); } / Admonition tweaks / .rst-content .admonition, .rst-content .admonition.note, .rst-content .admonition.seealso { background-color: var(--admonition-note-background-color); color: var(--admonition-note-color); overflow: auto; } .rst-content .admonition .admonition-title, .rst-content .admonition.note .admonition-title, .rst-content .admonition.seealso .admonition-title { background-color: var(--admonition-note-title-background-color); color: var(--admonition-note-title-color); } .rst-content .admonition.attention, .rst-content .admonition.caution, .rst-content .admonition.warning { background-color: var(--admonition-attention-background-color); color: var(--admonition-attention-color); overflow: auto; } .rst-content .admonition.attention .admonition-title, .rst-content .admonition.caution .admonition-title, .rst-content .admonition.warning .admonition-title { background-color: var(--admonition-attention-title-background-color); color: var(--admonition-attention-title-color); } .rst-content .admonition.danger { background-color: var(--admonition-danger-background-color); color: var(--admonition-danger-color); overflow: auto; } .rst-content .admonition.danger .admonition-title { background-color: var(--admonition-danger-title-background-color); color: var(--admonition-danger-title-color); } .rst-content .admonition.tip, .rst-content .admonition.important { background-color: var(--admonition-tip-background-color); color: var(--admonition-tip-color); overflow: auto; } .rst-content .admonition.tip .admonition-title, .rst-content .admonition.important .admonition-title { background-color: var(--admonition-tip-title-background-color); color: var(--admonition-tip-title-color); } / Admonition tweaks - sphinx_togglebutton / .rst-content .admonition.toggle { overflow: visible; } .rst-content .admonition.toggle button { display: inline-flex; color: var(--admonition-note-title-color); } .rst-content .admonition.toggle .tb-icon { height: 1em; width: 1em; } / Keyboard shortcuts tweaks / kbd, .kbd, .rst-content :not(dl.option-list) > :not(dt):not(kbd):not(.kbd) > kbd, .rst-content :not(dl.option-list) > :not(dt):not(kbd):not(.kbd) > .kbd { background-color: var(--kbd-background-color); border: 1px solid var(--kbd-outline-color); border-radius: 3px; box-shadow: inset 0 -1px 0 var(--kbd-shadow-color); color: var(--kbd-text-color); display: inline-block; font-size: 12px; line-height: 11px; padding: 4px 5px; vertical-align: middle; } / guilabel and menuselection tweaks / .rst-content .guilabel, .rst-content .menuselection { color: var(--body-color); background-color: var(--guiitems-background-color); border-color: var(--guiitems-border-color); } / Buttons / .btn-neutral { background-color: var(--btn-neutral-background-color) !important; color: var(--body-color) !important; } .btn-neutral:hover { background-color: var(--btn-neutral-hover-background-color) !important; } .btn-neutral:visited { color: var(--body-color) !important; } / Navigation bar logo and search / .logo { opacity: var(--logo-opacity); } .wy-side-nav-search > a img.logo { / Fixed size to prevent reflows and support hiDPI displays / / A 5 pixel margin is added on each side. The logo itself displays at 200100 at 100% scaling. / width: 210px; height: 105px; } .wy-side-nav-search { background-color: var(--navbar-background-color); } .wy-side-nav-search.fixed { position: fixed; } @media only screen and (min-width: 769px) { / Simulate a drop shadow that only affects the bottom edge / / This is used to indicate the search bar is fixed / .wy-side-nav-search.fixed-and-scrolled::after { content: ''; position: absolute; left: 0; bottom: -8px; width: 300px; height: 8px; pointer-events: none; background: linear-gradient(hsla(0, 0%, 0%, 0.2), transparent); } } .wy-side-nav-search > a:hover, .wy-side-nav-search .wy-dropdown > a:hover { background-color: var(--navbar-background-color-hover); } .wy-side-nav-search > a:active, .wy-side-nav-search .wy-dropdown > a:active { background-color: var(--navbar-background-color-active); } .wy-side-nav-search input[type=search] { width: 100%; border-radius: 50px; padding: 6px 12px; background-color: var(--input-background-color); color: var(--body-color); / Avoid reflowing when toggling the focus state / border: 2px solid transparent; box-shadow: none; / Make visual feedback instant / transition: none; font-size: 14px; } .wy-side-nav-search input[type="search"]:focus { border: 2px solid var(--input-focus-border-color); } .wy-side-nav-search input[type="search"]::placeholder { color: var(--body-color); opacity: 0.55; } / Navigation bar / .wy-nav-side { background-color: var(--navbar-background-color); } .wy-menu-vertical header, .wy-menu-vertical p.caption { color: var(--navbar-heading-color); / Improves the appearance of uppercase text / letter-spacing: 0.75px; } / Mobile navigation / .wy-nav-top, .wy-nav-top a { background-color: var(--navbar-background-color); color: var(--navbar-level-1-color); } / Version branch label below the logo / .wy-side-nav-search > div.version { color: var(--navbar-level-3-color); opacity: 0.9; } / First level of navigation items / .wy-menu-vertical a { color: var(--navbar-level-1-color); } .wy-menu-vertical a:hover { background-color: var(--navbar-background-color-hover); color: var(--navbar-level-1-color); } .wy-menu-vertical a:active { background-color: var(--navbar-background-color-active); } .wy-menu-vertical li.toctree-l1.current > a { border: none; } .wy-side-nav-search, .wy-menu-vertical a, .wy-menu-vertical a span.toctree-expand, .wy-menu-vertical li.toctree-l2 a span.toctree-expand { color: var(--navbar-level-3-color); opacity: 0.9; margin-right: 8px; } .wy-side-nav-search, .wy-menu-vertical a, .wy-menu-vertical a:hover span.toctree-expand, .wy-menu-vertical li.toctree-l2 a:hover span.toctree-expand { color: var(--navbar-level-2-color); opacity: 1; } .wy-side-nav-search, .wy-menu-vertical a, .wy-menu-vertical a:active span.toctree-expand, .wy-menu-vertical li.toctree-l2 a:active span.toctree-expand { color: var(--navbar-level-1-color); opacity: 1; } / Second (and higher) levels of navigation items / .wy-menu-vertical li.current a { / Make long words always display on a single line, keep wrapping for multiple words / / This fixes the class reference titles' display with very long class names / display: flex; } .wy-menu-vertical li.current a, .wy-menu-vertical li.toctree-l2.current > a, .wy-menu-vertical li.toctree-l2.current li.toctree-l3 > a, .wy-menu-vertical li.toctree-l2.current li.toctree-l4 > a { background-color: var(--navbar-current-background-color); color: var(--navbar-level-2-color); border-color: var(--navbar-current-background-color); } .wy-menu-vertical li.current a:hover, .wy-menu-vertical li.toctree-l2.current > a:hover, .wy-menu-vertical li.toctree-l2.current li.toctree-l3 > a:hover, .wy-menu-vertical li.toctree-l3.current li.toctree-l4 > a:hover { background-color: var(--navbar-current-background-color-hover); } .wy-menu-vertical li.current a:active, .wy-menu-vertical li.toctree-l2.current > a:active, .wy-menu-vertical li.toctree-l2.current li.toctree-l3 > a:active, .wy-menu-vertical li.toctree-l3.current li.toctree-l4 > a:active { background-color: var(--navbar-current-background-color-active); } .wy-menu-vertical a { / This overrides 8px margin added in other multi-selector rules / margin-right: 0; } / Banner panel in sidebar / .wy-nav-side .ethical-rtd.fixed { position: fixed; } / Version selector (only visible on Read the Docs) / .rst-versions { background-color: var(--navbar-current-background-color); } .rst-versions a, .rst-versions .rst-current-version, .rst-versions .rst-current-version .fa, .rst-versions .rst-other-versions dd a { color: var(--navbar-level-1-color); } .rst-versions .rst-other-versions small { color: var(--navbar-level-3-color); } .rst-versions .rst-other-versions dd a:hover { text-decoration: underline; } .rst-versions .rst-other-versions { color: var(--navbar-heading-color); } .rst-versions .rst-current-version { background-color: var(--navbar-current-background-color); } .rst-versions .rst-current-version:hover { background-color: var(--navbar-current-background-color-hover); } .rst-versions .rst-current-version:active { background-color: var(--navbar-current-background-color-active); } .rst-versions.shift-up { overflow-y: auto; } / Hide the obnoxious automatic highlight in search results / .rst-content .highlighted { background-color: transparent; font-weight: inherit; padding: 0; } / Allows the scrollbar to be shown in the sidebar / @media only screen and (min-width: 769px) { .wy-side-scroll { overflow: hidden; } .wy-nav-side .wy-side-scroll .ethical-rtd { width: calc(300px - 1.25em); padding: 0 0 0 1em; } } .wy-menu.wy-menu-vertical { overflow-y: auto; overflow-x: hidden; max-height: calc(100% - 243px); } @media screen and (max-width: 768px) { .wy-nav-side { padding-bottom: 44px; } .wy-menu.wy-menu-vertical { overflow-y: initial; max-height: initial; } } / Scrollbar styling / .wy-menu.wy-menu-vertical { scrollbar-color: var(--navbar-scrollbar-color) var(--navbar-scrollbar-background); } .wy-menu.wy-menu-vertical::-webkit-scrollbar { width: .75rem; } .wy-menu.wy-menu-vertical::-webkit-scrollbar-track { background-color: var(--navbar-scrollbar-background); } .wy-menu.wy-menu-vertical::-webkit-scrollbar-thumb { background-color: var(--navbar-scrollbar-color); } / Firefox does the dimming on hover automatically. We emulate it for Webkit-based browsers. / .wy-menu.wy-menu-vertical::-webkit-scrollbar-thumb:hover { background-color: var(--navbar-scrollbar-hover-color); } .wy-menu.wy-menu-vertical::-webkit-scrollbar-thumb:active { background-color: var(--navbar-scrollbar-active-color); } / Breathe tweaks / .rst-content .section > dl > dd { margin-left: 0; } .rst-content p.breathe-sectiondef-title { font-size: 115%; color: var(--link-color); } .rst-content dl:not(.docutils) dl:not(.rst-other-versions) dt { background: var(--admonition-note-background-color) !important; border-top: none !important; border-left: none !important; } / Misc tweaks / .rst-columns { column-width: 18em; } .rst-content div.figure, .rst-content figure { text-align: center; } .wy-alert.wy-alert-danger { background-color: var(--admonition-danger-background-color); } dark-mode-toggle::part(fieldset) { padding-inline: 0.75rem; padding-block: 0; } dark-mode-toggle::part(darkLabel), dark-mode-toggle::part(lightLabel), dark-mode-toggle::part(toggleLabel){ font-size: unset; } / Home page grid display / .grid { list-style-type: none !important; display: -webkit-box; display: -ms-flexbox; display: flex; -ms-flex-wrap: wrap; flex-wrap: wrap; -webkit-box-pack: center; -ms-flex-pack: center; justify-content: center; margin: 1rem auto; max-width: calc((160px + 2rem) 4); } .grid-item { list-style-type: none !important; -webkit-box-flex: 0; -ms-flex: 0 0 auto; flex: 0 0 auto; width: 150px; text-align: center; margin: 1rem; } .grid-item a { display: block; width: 150px; height: 150px; padding: 20px; display: -webkit-box; display: -ms-flexbox; display: flex; -webkit-box-orient: vertical; -webkit-box-direction: normal; -ms-flex-direction: column; flex-direction: column; -webkit-box-pack: center; -ms-flex-pack: center; justify-content: center; -webkit-box-align: center; -ms-flex-align: center; align-items: center; border-radius: 0.5rem; background: linear-gradient(135deg, #0070c5 0%, #5c13a5 100%); color: white; } .grid-item h2 { font-size: 1rem; } .grid-item img { margin-bottom: 1rem; max-width: 75%; } .grid-item a:hover { text-decoration: none; } .grid-item p { font-size: 0.9rem; margin-top: 0.5rem; color: var(--body-color); } .grid-icon { line-height: 1.5; font-size: 3rem; color: white; } /* Custom search box, including search engine selection */ .search-container { position: relative; } #search-se-settings-icon { position: absolute; color: var(--body-color); right: 10px; top: 50%; transform: translateY(-50%); cursor: pointer; opacity: 0.8; } #search-se-menu { display: none; position: absolute; font-size: 11px; background-color: var(--input-background-color); color: var(--body-color); right: 0px; top: 36px; border: solid 1px var(--body-color); border-radius: 10px; z-index: 1000; } #search-se-menu ul { list-style: none; margin: 0; padding: 2px; } #search-se-menu ul li { padding: 8px 12px; cursor: pointer; display: flex; justify-content: space-between; align-items: center; gap: 1em; } #search-se-menu [role="menuitemradio"]:focus { background-color: var(--navbar-current-background-color-hover); color: var(--navbar-level-1-color); border-radius: 10px; } #search-se-menu ul li .fa-check { display: none; } #search-se-menu ul li.selected .fa-check { display: inline; } .doxygroup::after { content: 'Doxygen'; display: inline-block; background-color: var(--admonition-note-title-background-color); color: var(--admonition-note-title-color); padding: 2px 8px; border-radius: 12px; margin-left: 8px; font-size: 0.875em; font-weight: bold; } ```	/content/code_sandbox/doc/_static/css/custom.css	css	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	6,049
```unknown const e=document;const t=localStorage;const i="prefers-color-scheme";const a="media";const s="light";const r="dark";const o=`(${i}:${r})`;const n=`(${i}:${s})`;const l="link[rel=stylesheet]";const h="remember";const c="legend";const d="toggle";const b="switch";const p="appearance";const g="permanent";const m="mode";const u="colorschemechange";const f="permanentcolorscheme";const k="all";const v="not all";const $="dark-mode-toggle";const L="path_to_url";const y=(e,t,i=t)=>{Object.defineProperty(e,i,{enumerable:true,get(){const e=this.getAttribute(t);return e===null?"":e},set(e){this.setAttribute(t,e)}})};const x=(e,t,i=t)=>{Object.defineProperty(e,i,{enumerable:true,get(){return this.hasAttribute(t)},set(e){if(e){this.setAttribute(t,"")}else{this.removeAttribute(t)}}})};const w=e.createElement("template");w.innerHTML=`<style>,::after,::before{box-sizing:border-box}:host{contain:content;display:block}:host([hidden]){display:none}form{background-color:var(--${$}-background-color,transparent);color:var(--${$}-color,inherit);padding:0}fieldset{border:none;margin:0;padding-block:.25rem;padding-inline:.25rem}legend{font:var(--${$}-legend-font,inherit);padding:0}input,label{cursor:pointer}label{white-space:nowrap}input{opacity:0;position:absolute;pointer-events:none}input:focus-visible+label{outline:#e59700 auto 2px;outline:-webkit-focus-ring-color auto 5px}label:not(:empty)::before{margin-inline-end:.5rem;}label::before{content:"";display:inline-block;background-size:var(--${$}-icon-size,1rem);background-repeat:no-repeat;height:var(--${$}-icon-size,1rem);width:var(--${$}-icon-size,1rem);vertical-align:middle;}[part=lightLabel]::before{background-image:var(--${$}-light-icon, url("${L}sun.png"))}[part=darkLabel]::before{filter:var(--${$}-icon-filter, none);background-image:var(--${$}-dark-icon, url("${L}moon.png"))}[part=toggleLabel]::before{background-image:var(--${$}-checkbox-icon,none)}[part=permanentLabel]::before{background-image:var(--${$}-remember-icon-unchecked, url("${L}unchecked.svg"))}[part=darkLabel],[part=lightLabel],[part=toggleLabel]{font:var(--${$}-label-font,inherit)}[part=darkLabel]:empty,[part=lightLabel]:empty,[part=toggleLabel]:empty{font-size:0;padding:0}[part=permanentLabel]{font:var(--${$}-remember-font,inherit)}input:checked+[part=permanentLabel]::before{background-image:var(--${$}-remember-icon-checked, url("${L}checked.svg"))}input:checked+[part=darkLabel],input:checked+[part=lightLabel]{background-color:var(--${$}-active-mode-background-color,transparent)}input:checked+[part=darkLabel]::before,input:checked+[part=lightLabel]::before{background-color:var(--${$}-active-mode-background-color,transparent)}input:checked+[part=toggleLabel]::before{filter:var(--${$}-icon-filter, none)}input:checked+[part=toggleLabel]+aside [part=permanentLabel]::before{filter:var(--${$}-remember-filter, invert(100%))}aside{visibility:hidden;margin-block-start:.15rem}[part=darkLabel]:focus-visible~aside,[part=lightLabel]:focus-visible~aside,[part=toggleLabel]:focus-visible~aside{visibility:visible;transition:visibility 0s}aside [part=permanentLabel]:empty{display:none}@media (hover:hover){aside{transition:visibility 3s}aside:hover{visibility:visible}[part=darkLabel]:hover~aside,[part=lightLabel]:hover~aside,[part=toggleLabel]:hover~aside{visibility:visible;transition:visibility 0s}}</style><form part=form><fieldset part=fieldset><legend part=legend></legend><input part=lightRadio id=l name=mode type=radio><label part=lightLabel for=l></label><input part=darkRadio id=d name=mode type=radio><label part=darkLabel for=d></label><input part=toggleCheckbox id=t type=checkbox><label part=toggleLabel for=t></label><aside part=aside><input part=permanentCheckbox id=p type=checkbox><label part=permanentLabel for=p></label></aside></fieldset></form>`;export class DarkModeToggle extends HTMLElement{static get observedAttributes(){return[m,p,g,c,s,r,h]}constructor(){super();y(this,m);y(this,p);y(this,c);y(this,s);y(this,r);y(this,h);x(this,g);this.t=null;this.i=null;e.addEventListener(u,(e=>{this.mode=e.detail.colorScheme;this.o();this.l()}));e.addEventListener(f,(e=>{this.permanent=e.detail.permanent;this.h.checked=this.permanent}));this.p()}p(){const h=this.attachShadow({mode:"open"});h.appendChild(w.content.cloneNode(true));this.t=e.querySelectorAll(`${l}[${a}=${i}][${a}="${r}"]`);this.i=e.querySelectorAll(`${l}[${a}=${i}][${a}*="${s}"]`);this.g=h.querySelector("[part=lightRadio]");this.m=h.querySelector("[part=lightLabel]");this.u=h.querySelector("[part=darkRadio]");this.k=h.querySelector("[part=darkLabel]");this.v=h.querySelector("[part=toggleCheckbox]");this.$=h.querySelector("[part=toggleLabel]");this.L=h.querySelector("legend");this.M=h.querySelector("aside");this.h=h.querySelector("[part=permanentCheckbox]");this.C=h.querySelector("[part=permanentLabel]");const c=matchMedia(o).media!==v;if(c){matchMedia(o).addListener((({matches:e})=>{this.mode=e?r:s;this.R(u,{colorScheme:this.mode})}))}const b=t.getItem($);if(b&&[r,s].includes(b)){this.mode=b;this.h.checked=true;this.permanent=true}else if(c){this.mode=matchMedia(n).matches?s:r}if(!this.mode){this.mode=s}if(this.permanent&&!b){t.setItem($,this.mode)}if(!this.appearance){this.appearance=d}this._();this.o();this.l();[this.g,this.u].forEach((e=>{e.addEventListener("change",(()=>{this.mode=this.g.checked?s:r;this.l();this.R(u,{colorScheme:this.mode})}))}));this.v.addEventListener("change",(()=>{this.mode=this.v.checked?r:s;this.o();this.R(u,{colorScheme:this.mode})}));this.h.addEventListener("change",(()=>{this.permanent=this.h.checked;this.R(f,{permanent:this.permanent})}));this.A();this.R(u,{colorScheme:this.mode});this.R(f,{permanent:this.permanent})}attributeChangedCallback(e,i,a){if(e===m){if(![s,r].includes(a)){throw new RangeError(`Allowed values: "${s}" and "${r}".`)}if(matchMedia("(hover:none)").matches&&this.remember){this.S()}if(this.permanent){t.setItem($,this.mode)}this.o();this.l();this.A()}else if(e===p){if(![d,b].includes(a)){throw new RangeError(`Allowed values: "${d}" and "${b}".`)}this._()}else if(e===g){if(this.permanent){t.setItem($,this.mode)}else{t.removeItem($)}this.h.checked=this.permanent}else if(e===c){this.L.textContent=a}else if(e===h){this.C.textContent=a}else if(e===s){this.m.textContent=a;if(this.mode===s){this.$.textContent=a}}else if(e===r){this.k.textContent=a;if(this.mode===r){this.$.textContent=a}}}R(e,t){this.dispatchEvent(new CustomEvent(e,{bubbles:true,composed:true,detail:t}))}_(){const e=this.appearance===d;this.g.hidden=e;this.m.hidden=e;this.u.hidden=e;this.k.hidden=e;this.v.hidden=!e;this.$.hidden=!e}o(){if(this.mode===s){this.g.checked=true}else{this.u.checked=true}}l(){if(this.mode===s){this.$.style.setProperty(`--${$}-checkbox-icon`,`var(--${$}-light-icon,url("${L}moon.png"))`);this.$.textContent=this.light;this.v.checked=false}else{this.$.style.setProperty(`--${$}-checkbox-icon`,`var(--${$}-dark-icon,url("${L}sun.png"))`);this.$.textContent=this.dark;this.v.checked=true}}A(){if(this.mode===s){this.i.forEach((e=>{e.media=k;e.disabled=false}));this.t.forEach((e=>{e.media=v;e.disabled=true}))}else{this.t.forEach((e=>{e.media=k;e.disabled=false}));this.i.forEach((e=>{e.media=v;e.disabled=true}))}}S(){this.M.style.visibility="visible";setTimeout((()=>{this.M.style.visibility="hidden"}),3e3)}}customElements.define($,DarkModeToggle); ```	/content/code_sandbox/doc/_static/js/dark-mode-toggle.min.mjs	unknown	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,064
```tex % LaTeX documentation preamble % \usepackage[some]{background} \usepackage{sectsty} \usepackage{pdflscape} \definecolor{bg-color}{HTML}{333f67} \setcounter{tocdepth}{2} \addto\captionsenglish{\renewcommand{\contentsname}{Table of contents}} \allsectionsfont{\color{bg-color}} ```	/content/code_sandbox/doc/_static/latex/preamble.tex	tex	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	81
```tex % LaTeX documentation title page % \makeatletter \newgeometry{top=3cm,left=0cm,right=0cm,bottom=2.5cm} \backgroundsetup{ scale=2.3, contents={\sphinxlogo}, opacity=0.2, angle=0, position={0.25\textwidth,-0.4\textheight} } \BgThispage \begin{minipage}{2cm} \color{bg-color} \rule{2cm}{1.7cm} \end{minipage} \hspace{0.2cm} \begin{minipage}{3cm} \sphinxlogo \end{minipage} \hspace{0.2cm} \begin{minipage}{15cm} \Huge \textbf{\@title}\\ \LARGE \py@release\releaseinfo \end{minipage} \vspace{21cm} \begin{flushright} \begin{minipage}{7cm} \large \@author\\\@date \end{minipage} \begin{minipage}{1.5cm} \color{bg-color} \rule{1.5cm}{1.3cm} \end{minipage} \end{flushright} \restoregeometry \makeatother ```	/content/code_sandbox/doc/_static/latex/title.tex	tex	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	304
```python """ Helper functions used by gen_kconfig_rest.py and gen_devicetree_rest.py. """ import errno def write_if_updated(path, s): """ Writes 's' as the contents of <out_dir>/<filename>, but only if it differs from the current contents of the file. This avoids unnecessary timestamp updates, which trigger documentation rebuilds. Returns True if the file was updated, False otherwise. """ try: with open(path, "r", encoding="utf-8") as f: if s == f.read(): return False except OSError as e: if e.errno != errno.ENOENT: raise with open(path, "w", encoding="utf-8") as f: f.write(s) return True ```	/content/code_sandbox/doc/_scripts/gen_helpers.py	python	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	170
```python """ This module contains a variable with a list of tuples (old_url, new_url) for pages to redirect. This list allows redirecting old URLs (caused by reorganizing doc directories) Notes: - Please keep this list sorted alphabetically. - URLs must be relative to document root (with NO leading slash), and without the html extension). """ REDIRECTS = [ # zephyr-keep-sorted-start ('application/index', 'develop/application/index'), ('boards/arduino/uno_r4_minima/doc/index', 'boards/arduino/uno_r4/doc/index'), ('boards/x86/ehl_crb/doc/index', 'boards/x86/intel_ehl/doc/index'), ('boards/x86/rpl_crb/doc/index', 'boards/x86/intel_rpl/doc/index'), ('connectivity/bluetooth/audio', 'connectivity/bluetooth/api/audio/audio'), ('connectivity/bluetooth/bap', 'connectivity/bluetooth/api/audio/bap'), ('connectivity/bluetooth/bluetooth-audio-arch', 'connectivity/bluetooth/bluetooth-le-audio-arch'), ('connectivity/bluetooth/bluetooth-le-audio-arch', 'connectivity/bluetooth/api/audio/bluetooth-le-audio-arch'), ('connectivity/bluetooth/cap', 'connectivity/bluetooth/api/audio/cap'), ('connectivity/bluetooth/coordinated_sets', 'connectivity/bluetooth/api/audio/coordinated_sets'), ('connectivity/bluetooth/dis-pics', 'connectivity/bluetooth/ics/dis'), ('connectivity/bluetooth/gap-pics', 'connectivity/bluetooth/ics/gap'), ('connectivity/bluetooth/gatt-pics', 'connectivity/bluetooth/ics/gatt'), ('connectivity/bluetooth/l2cap-pics', 'connectivity/bluetooth/ics/l2cap'), ('connectivity/bluetooth/media', 'connectivity/bluetooth/api/audio/media'), ('connectivity/bluetooth/mesh-pics', 'connectivity/bluetooth/ics/mesh'), ('connectivity/bluetooth/microphone', 'connectivity/bluetooth/api/audio/microphone'), ('connectivity/bluetooth/overview', 'connectivity/bluetooth/features'), ('connectivity/bluetooth/rfcomm-pics', 'connectivity/bluetooth/ics/rfcomm'), ('connectivity/bluetooth/shell/bap', 'connectivity/bluetooth/api/audio/shell/bap'), ('connectivity/bluetooth/shell/bap_broadcast_assistant', 'connectivity/bluetooth/api/audio/shell/bap_broadcast_assistant'), ('connectivity/bluetooth/shell/bap_scan_delegator', 'connectivity/bluetooth/api/audio/shell/bap_scan_delegator'), ('connectivity/bluetooth/shell/cap', 'connectivity/bluetooth/api/audio/shell/cap'), ('connectivity/bluetooth/shell/ccp', 'connectivity/bluetooth/api/audio/shell/ccp'), ('connectivity/bluetooth/shell/csip', 'connectivity/bluetooth/api/audio/shell/csip'), ('connectivity/bluetooth/shell/gmap', 'connectivity/bluetooth/api/audio/shell/gmap'), ('connectivity/bluetooth/shell/mcp', 'connectivity/bluetooth/api/audio/shell/mcp'), ('connectivity/bluetooth/shell/pbp', 'connectivity/bluetooth/api/audio/shell/pbp'), ('connectivity/bluetooth/shell/tmap', 'connectivity/bluetooth/api/audio/shell/tmap'), ('connectivity/bluetooth/sm-pics', 'connectivity/bluetooth/ics/sm'), ('connectivity/bluetooth/volume', 'connectivity/bluetooth/api/audio/volume'), ('connectivity/networking/networking-api-usage', 'connectivity/networking/api/index'), ('development_process/code_flow', 'project/code_flow'), ('development_process/index', 'project/index'), ('development_process/issues', 'project/issues'), ('development_process/proposals', 'project/proposals'), ('getting_started/index', 'develop/getting_started/index'), ('getting_started/toolchain_3rd_party_x_compilers', 'develop/toolchains/index'), ('getting_started/toolchain_custom_cmake', 'develop/toolchains/custom_cmake'), ('getting_started/toolchain_other_x_compilers', 'develop/toolchains/other_x_compilers'), ('guides/arch/arm_cortex_m', 'hardware/arch/arm_cortex_m'), ('guides/arch/index', 'hardware/arch/index'), ('guides/arch/x86', 'hardware/arch/x86'), ('guides/beyond-GSG', 'develop/beyond-GSG'), ('guides/bluetooth/index', 'connectivity/bluetooth/index'), ('guides/bluetooth/sm-pics', 'connectivity/bluetooth/sm-pics'), ('guides/build/index', 'build/cmake/index'), ('guides/build/kconfig/extensions', 'build/kconfig/extensions'), ('guides/build/kconfig/menuconfig', 'build/kconfig/menuconfig'), ('guides/build/kconfig/preprocessor-functions', 'build/kconfig/preprocessor-functions'), ('guides/build/kconfig/setting', 'build/kconfig/setting'), ('guides/build/kconfig/tips', 'build/kconfig/tips'), ('guides/coccinelle', 'develop/tools/coccinelle'), ('guides/code-relocation', 'kernel/code-relocation'), ('guides/crypto/index', 'services/crypto/index'), ('guides/crypto/tinycrypt', 'services/crypto/tinycrypt'), ('guides/device_mgmt/dfu', 'services/device_mgmt/dfu'), ('guides/device_mgmt/index', 'services/device_mgmt/index'), ('guides/device_mgmt/mcumgr', 'services/device_mgmt/mcumgr'), ('guides/device_mgmt/ota', 'services/device_mgmt/ota'), ('guides/dts/api-usage', 'build/dts/api-usage'), ('guides/dts/bindings', 'build/dts/bindings'), ('guides/dts/design', 'build/dts/design'), ('guides/dts/dt-vs-kconfig', 'build/dts/dt-vs-kconfig'), ('guides/dts/howtos', 'build/dts/howtos'), ('guides/dts/index', 'build/dts/index'), ('guides/dts/intro', 'build/dts/intro'), ('guides/dts/macros.bnf', 'build/dts/macros.bnf'), ('guides/dts/main-example.dts', 'build/dts/main-example.dts'), ('guides/dts/troubleshooting', 'build/dts/troubleshooting'), ('guides/emulator/index', 'hardware/emulator/index'), ('guides/env_vars', 'develop/env_vars'), ('guides/flash_debug/host-tools', 'develop/flash_debug/host-tools'), ('guides/flash_debug/index', 'develop/flash_debug/index'), ('guides/flash_debug/probes', 'develop/flash_debug/probes'), ('guides/kconfig/extensions', 'build/kconfig/extensions'), ('guides/kconfig/index', 'build/kconfig/index'), ('guides/kconfig/menuconfig', 'build/kconfig/menuconfig'), ('guides/kconfig/preprocessor-functions', 'build/kconfig/preprocessor-functions'), ('guides/kconfig/setting', 'build/kconfig/setting'), ('guides/kconfig/tips', 'build/kconfig/tips'), ('guides/modules', 'develop/modules'), ('guides/networking/index', 'connectivity/networking/index'), ('guides/optimizations/index', 'develop/optimizations/index'), ('guides/optimizations/tools', 'develop/optimizations/tools'), ('guides/pinctrl/index', 'hardware/pinctrl/index'), ('guides/platformio/index', 'develop/tools/platformio/index'), ('guides/pm/device', 'services/pm/device'), ('guides/pm/device_runtime', 'services/pm/device_runtime'), ('guides/pm/index', 'services/pm/index'), ('guides/pm/overview', 'services/pm/overview'), ('guides/pm/power_domain', 'services/pm/power_domain'), ('guides/pm/system', 'services/pm/system'), ('guides/portability/index', 'services/portability/index'), ('guides/porting/arch', 'hardware/porting/arch'), ('guides/porting/board_porting', 'hardware/porting/board_porting'), ('guides/porting/index', 'hardware/porting/index'), ('guides/porting/shields', 'hardware/porting/shields'), ('guides/smf/index', 'services/smf/index'), ('guides/test/coverage', 'develop/test/coverage'), ('guides/test/index', 'develop/test/index'), ('guides/test/mocking.c', 'develop/test/mocking.c'), ('guides/test/twister', 'develop/test/twister'), ('guides/test/ztest', 'develop/test/ztest'), ('guides/tfm/build', 'services/tfm/build'), ('guides/tfm/index', 'services/tfm/index'), ('guides/tfm/integration', 'services/tfm/integration'), ('guides/tfm/overview', 'services/tfm/overview'), ('guides/tfm/requirements', 'services/tfm/requirements'), ('guides/tfm/testsuites', 'services/tfm/testsuites'), ('guides/west/basics', 'develop/west/basics'), ('guides/west/build-flash-debug', 'develop/west/build-flash-debug'), ('guides/west/built-in', 'develop/west/built-in'), ('guides/west/config', 'develop/west/config'), ('guides/west/extensions', 'develop/west/extensions'), ('guides/west/index', 'develop/west/index'), ('guides/west/install', 'develop/west/install'), ('guides/west/manifest', 'develop/west/manifest'), ('guides/west/moving-to-west', 'develop/west/moving-to-west'), ('guides/west/release-notes', 'develop/west/release-notes'), ('guides/west/sign', 'develop/west/sign'), ('guides/west/troubleshooting', 'develop/west/troubleshooting'), ('guides/west/west-apis', 'develop/west/west-apis'), ('guides/west/west-not-found', 'develop/west/west-not-found'), ('guides/west/why', 'develop/west/why'), ('guides/west/without-west', 'develop/west/without-west'), ('guides/west/workspaces', 'develop/west/workspaces'), ('guides/west/zephyr-cmds', 'develop/west/zephyr-cmds'), ('guides/zephyr_cmake_package', 'build/zephyr_cmake_package'), ('hardware/peripherals/eeprom', 'hardware/peripherals/eeprom/index'), ('hardware/peripherals/sensor', 'hardware/peripherals/sensor/index'), ('reference/api/api_lifecycle', 'develop/api/api_lifecycle'), ('reference/api/index', 'develop/api/index'), ('reference/api/overview', 'develop/api/overview'), ('reference/api/terminology', 'develop/api/terminology'), ('reference/drivers/index', 'kernel/drivers/index'), ('reference/file_system/index', 'services/file_system/index'), ('reference/libc/index', 'kernel/libc/index'), ('reference/logging/index', 'services/logging/index'), ('reference/misc/notify', 'services/notify'), ('reference/misc/timeutil', 'kernel/timeutil'), ('reference/modbus/index', 'services/modbus/index'), ('reference/networking/sockets', 'connectivity/networking/api/sockets'), ('reference/peripherals/adc', 'hardware/peripherals/adc'), ('reference/peripherals/dac', 'hardware/peripherals/dac'), ('reference/peripherals/dma', 'hardware/peripherals/dma'), ('reference/peripherals/eeprom', 'hardware/peripherals/eeprom'), ('reference/peripherals/espi', 'hardware/peripherals/espi'), ('reference/peripherals/flash', 'hardware/peripherals/flash'), ('reference/peripherals/gna', 'hardware/peripherals/gna'), ('reference/peripherals/gpio', 'hardware/peripherals/gpio'), ('reference/peripherals/hwinfo', 'hardware/peripherals/hwinfo'), ('reference/peripherals/i2c', 'hardware/peripherals/i2c'), ('reference/peripherals/index', 'hardware/peripherals/index'), ('reference/peripherals/ipm', 'hardware/peripherals/ipm'), ('reference/peripherals/kscan', 'hardware/peripherals/kscan'), ('reference/peripherals/led', 'hardware/peripherals/led'), ('reference/peripherals/mbox', 'hardware/peripherals/mbox'), ('reference/peripherals/mdio', 'hardware/peripherals/mdio'), ('reference/peripherals/mspi', 'hardware/peripherals/mspi'), ('reference/peripherals/peci', 'hardware/peripherals/peci'), ('reference/peripherals/pinmux', 'hardware/peripherals/pinmux'), ('reference/peripherals/ps2', 'hardware/peripherals/ps2'), ('reference/peripherals/pwm', 'hardware/peripherals/pwm'), ('reference/peripherals/reset', 'hardware/peripherals/reset'), ('reference/peripherals/rtc', 'hardware/peripherals/rtc'), ('reference/peripherals/sensor', 'hardware/peripherals/sensor'), ('reference/peripherals/spi', 'hardware/peripherals/spi'), ('reference/peripherals/tcpc', 'hardware/peripherals/tcpc'), ('reference/peripherals/uart', 'hardware/peripherals/uart'), ('reference/peripherals/video', 'hardware/peripherals/video'), ('reference/pm/index', 'services/pm/api/index'), ('reference/settings/index', 'services/settings/index'), ('reference/shell/index', 'services/shell/index'), ('reference/storage/fcb/fcb', 'services/storage/fcb/fcb'), ('reference/storage/index', 'services/storage/index'), ('reference/storage/nvs/nvs', 'services/storage/nvs/nvs'), ('reference/task_wdt/index', 'services/task_wdt/index'), ('reference/usb/hid', 'services/usb/hid'), ('reference/usb/index', 'services/usb/index'), ('reference/usb/udc', 'services/usb/udc'), ('reference/usb/uds', 'services/usb/uds'), ('reference/usb/uds_cdc_acm', 'services/usb/uds_cdc_acm'), ('reference/usb/uds_testing', 'services/usb/uds_testing'), ('reference/usermode/index', 'kernel/usermode/index'), ('reference/usermode/overview', 'kernel/usermode/overview'), ('reference/usermode/syscalls', 'kernel/usermode/syscalls'), ('reference/util/index', 'kernel/util/index'), ('samples/application_development/with_mcuboot/README', 'samples/sysbuild/with_mcuboot/README'), ('samples/bluetooth/broadcast_audio_assistant/README', 'samples/bluetooth/bap_broadcast_assistant/README'), ('samples/bluetooth/broadcast_audio_sink/README', 'samples/bluetooth/bap_broadcast_sink/README'), ('samples/bluetooth/broadcast_audio_source/README', 'samples/bluetooth/bap_broadcast_source/README'), ('samples/bluetooth/public_broadcast_sink/README', 'samples/bluetooth/pbp_public_broadcast_sink/README'), ('samples/bluetooth/public_broadcast_source/README', 'samples/bluetooth/pbp_public_broadcast_source/README'), ('samples/bluetooth/unicast_audio_client/README', 'samples/bluetooth/bap_unicast_client/README'), ('samples/bluetooth/unicast_audio_server/README', 'samples/bluetooth/bap_unicast_server/README'), ('samples/drivers/adc/README', 'samples/drivers/adc/adc_dt/README'), ('samples/drivers/kscan_touch', 'samples/subsys/input/input'), ('samples/drivers/led_apa102/README', 'samples/drivers/led_strip/README'), ('samples/drivers/led_lpd8806/README', 'samples/drivers/led_strip/README'), ('samples/drivers/led_ws2812/README', 'samples/drivers/led_strip/README'), ('samples/net/cloud/google_iot_mqtt/README', 'samples/net/cloud/cloud'), ('samples/sensor/wsen_hids/README', 'samples/sensor/sensor'), ('samples/sensor/wsen_itds/README', 'samples/sensor/sensor'), ('samples/subsys/video/capture/README', 'samples/drivers/video/capture/README'), ('samples/subsys/video/tcpserversink/README', 'samples/drivers/video/tcpserversink/README'), ('samples/subsys/video/video', 'samples/drivers/video/video'), ('services/portability/posix', 'services/portability/posix/index'), # zephyr-keep-sorted-stop ] ```	/content/code_sandbox/doc/_scripts/redirects.py	python	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	3,622
```python """ Like gen_kconfig_rest.py, but for generating an index of existing devicetree bindings. """ import argparse from collections import defaultdict import glob import io import logging import os from pathlib import Path import pprint import re import sys import textwrap from devicetree import edtlib import gen_helpers ZEPHYR_BASE = Path(__file__).parents[2] GENERIC_OR_VENDOR_INDEPENDENT = 'Generic or vendor-independent' UNKNOWN_VENDOR = 'Unknown vendor' ZEPHYR_BASE = Path(__file__).parents[2] # Base properties that have documentation in 'dt-important-props'. DETAILS_IN_IMPORTANT_PROPS = set('compatible label reg status interrupts'.split()) logger = logging.getLogger('gen_devicetree_rest') class VndLookup: """ A convenience class for looking up information based on a devicetree compatible's vendor prefix 'vnd'. """ def __init__(self, vendor_prefixes, bindings): self.vnd2vendor = self.load_vnd2vendor(vendor_prefixes) self.vnd2bindings = self.init_vnd2bindings(bindings) self.vnd2ref_target = self.init_vnd2ref_target() def vendor(self, vnd): return self.vnd2vendor.get(vnd, UNKNOWN_VENDOR) def bindings(self, vnd, default=None): return self.vnd2bindings.get(vnd, default) def target(self, vnd): return self.vnd2ref_target.get( vnd, self.vnd2ref_target[(UNKNOWN_VENDOR,)]) @staticmethod def load_vnd2vendor(vendor_prefixes): # Load the vendor-prefixes.txt file. Return a dict mapping 'vnd' # vendor prefixes as they are found in compatible properties to # each vendor's full name. # # For example, this line: # # vnd A stand-in for a real vendor # # Gets split into a key 'vnd' and a value 'A stand-in for a real # vendor' in the return value. # # The 'None' key maps to GENERIC_OR_VENDOR_INDEPENDENT. vnd2vendor = { None: GENERIC_OR_VENDOR_INDEPENDENT, } vnd2vendor.update(edtlib.load_vendor_prefixes_txt(vendor_prefixes)) logger.info('found %d vendor prefixes in %s', len(vnd2vendor) - 1, vendor_prefixes) if logger.isEnabledFor(logging.DEBUG): logger.debug('vnd2vendor=%s', pprint.pformat(vnd2vendor)) return vnd2vendor def init_vnd2bindings(self, bindings): # Take a 'vnd2vendor' map and a list of bindings and return a dict # mapping 'vnd' vendor prefixes prefixes to lists of bindings. The # bindings in each list are sorted by compatible. The keys in the # return value are sorted by vendor name. # # Special cases: # # - The 'None' key maps to bindings with no vendor prefix # in their compatibles, like 'gpio-keys'. This is the first key. # - The (UNKNOWN_VENDOR,) key maps to bindings whose compatible # has a vendor prefix that exists, but is not known, # like 'somethingrandom,device'. This is the last key. # Get an unsorted dict mapping vendor prefixes to lists of bindings. unsorted = defaultdict(list) generic_bindings = [] unknown_vendor_bindings = [] for binding in bindings: vnd = compatible_vnd(binding.compatible) if vnd is None: generic_bindings.append(binding) elif vnd in self.vnd2vendor: unsorted[vnd].append(binding) else: unknown_vendor_bindings.append(binding) # Key functions for sorting. def vnd_key(vnd): return self.vnd2vendor[vnd].casefold() def binding_key(binding): return binding.compatible # Sort the bindings for each vendor by compatible. # Plain dicts are sorted in CPython 3.6+, which is what we # support, so the return dict's keys are in the same # order as vnd2vendor. # # The unknown-vendor bindings being inserted as a 1-tuple key is a # hack for convenience that ensures they won't collide with a # known vendor. The code that consumes the dict below handles # this. vnd2bindings = { None: sorted(generic_bindings, key=binding_key) } for vnd in sorted(unsorted, key=vnd_key): vnd2bindings[vnd] = sorted(unsorted[vnd], key=binding_key) vnd2bindings[(UNKNOWN_VENDOR,)] = sorted(unknown_vendor_bindings, key=binding_key) if logger.isEnabledFor(logging.DEBUG): logger.debug('vnd2bindings: %s', pprint.pformat(vnd2bindings)) return vnd2bindings def init_vnd2ref_target(self): # The return value, vnd2ref_target, is a dict mapping vendor # prefixes to ref targets for their relevant sections in this # file, with these special cases: # # - The None key maps to the ref target for bindings with no # vendor prefix in their compatibles, like 'gpio-keys' # - The (UNKNOWN_VENDOR,) key maps to the ref target for bindings # whose compatible has a vendor prefix that is not recognized. vnd2ref_target = {} for vnd in self.vnd2bindings: if vnd is None: vnd2ref_target[vnd] = 'dt_no_vendor' elif isinstance(vnd, str): vnd2ref_target[vnd] = f'dt_vendor_{vnd}' else: assert vnd == (UNKNOWN_VENDOR,), vnd vnd2ref_target[vnd] = 'dt_unknown_vendor' return vnd2ref_target def main(): args = parse_args() setup_logging(args.verbose) bindings = load_bindings(args.dts_roots, args.dts_folders) base_binding = load_base_binding() vnd_lookup = VndLookup(args.vendor_prefixes, bindings) dump_content(bindings, base_binding, vnd_lookup, args.out_dir, args.turbo_mode) def parse_args(): # Parse command line arguments from sys.argv. parser = argparse.ArgumentParser(allow_abbrev=False) parser.add_argument('-v', '--verbose', default=0, action='count', help='increase verbosity; may be given multiple times') parser.add_argument('--vendor-prefixes', required=True, help='vendor-prefixes.txt file path') parser.add_argument('--dts-root', dest='dts_roots', action='append', help='''additional DTS root directory as it would be set in DTS_ROOTS''') parser.add_argument('--dts-folder', dest='dts_folders', action='append', default=[], help='additional DTS folders containing binding files') parser.add_argument('--turbo-mode', action='store_true', help='Enable turbo mode (dummy references)') parser.add_argument('out_dir', help='output files are generated here') return parser.parse_args() def setup_logging(verbose): if verbose >= 2: log_level = logging.DEBUG elif verbose == 1: log_level = logging.INFO else: log_level = logging.ERROR logging.basicConfig(format='%(filename)s:%(levelname)s: %(message)s', level=log_level) def load_bindings(dts_roots, dts_folders): # Get a list of edtlib.Binding objects from searching 'dts_roots'. if not dts_roots: sys.exit('no DTS roots; use --dts-root to specify at least one') binding_files = [] for dts_root in dts_roots: binding_files.extend(glob.glob(f'{dts_root}/dts/bindings/*/.yml', recursive=True)) binding_files.extend(glob.glob(f'{dts_root}/dts/bindings/*/.yaml', recursive=True)) for folders in dts_folders: binding_files.extend(glob.glob(f'{folders}/.yml', recursive=False)) binding_files.extend(glob.glob(f'{folders}/.yaml', recursive=False)) bindings = edtlib.bindings_from_paths(binding_files, ignore_errors=True) num_total = len(bindings) # Remove bindings from the 'vnd' vendor, which is not a real vendor, # but rather a stand-in we use for examples and tests when a real # vendor would be inappropriate. bindings = [binding for binding in bindings if compatible_vnd(binding.compatible) != 'vnd'] logger.info('found %d bindings (ignored %d) in this dts_roots list: %s', len(bindings), num_total - len(bindings), dts_roots) return bindings def load_base_binding(): # Make a Binding object for base.yaml. # # This helps separate presentation for properties common to all # nodes from node-specific properties. base_yaml = ZEPHYR_BASE / 'dts' / 'bindings' / 'base' / 'base.yaml' base_includes = {"pm.yaml": os.fspath(ZEPHYR_BASE / 'dts' / 'bindings' / 'base'/ 'pm.yaml')} if not base_yaml.is_file(): sys.exit(f'Expected to find base.yaml at {base_yaml}') return edtlib.Binding(os.fspath(base_yaml), base_includes, require_compatible=False, require_description=False) def dump_content(bindings, base_binding, vnd_lookup, out_dir, turbo_mode): # Dump the generated .rst files for a vnd2bindings dict. # Files are only written if they are changed. Existing .rst # files which would not be written by the 'vnd2bindings' # dict are removed. out_dir = Path(out_dir) setup_bindings_dir(bindings, out_dir) if turbo_mode: write_dummy_index(bindings, out_dir) else: write_bindings_rst(vnd_lookup, out_dir) write_orphans(bindings, base_binding, vnd_lookup, out_dir) def setup_bindings_dir(bindings, out_dir): # Make a set of all the Path objects we will be creating for # out_dir / bindings / {binding_path}.rst. Delete all the ones that # shouldn't be there. Make sure the bindings output directory # exists. paths = set() bindings_dir = out_dir / 'bindings' logger.info('making output subdirectory %s', bindings_dir) bindings_dir.mkdir(parents=True, exist_ok=True) for binding in bindings: paths.add(bindings_dir / binding_filename(binding)) for dirpath, _, filenames in os.walk(bindings_dir): for filename in filenames: path = Path(dirpath) / filename if path not in paths: logger.info('removing unexpected file %s', path) path.unlink() def write_dummy_index(bindings, out_dir): # Write out_dir / bindings.rst, with dummy anchors # header content = '\n'.join(( '.. _devicetree_binding_index:', '.. _dt_vendor_zephyr:', '', 'Dummy bindings index', '####################', '', )) # build compatibles set and dump it compatibles = {binding.compatible for binding in bindings} content += '\n'.join(( f'.. dtcompatible:: {compatible}' for compatible in compatibles )) write_if_updated(out_dir / 'bindings.rst', content) def write_bindings_rst(vnd_lookup, out_dir): # Write out_dir / bindings.rst, the top level index of bindings. string_io = io.StringIO() print_block(f'''\ .. _devicetree_binding_index: Bindings index ############## This page documents the available devicetree bindings. See {zref('dt-bindings')} for an introduction to the Zephyr bindings file format. Vendor index ********** This section contains an index of hardware vendors. Click on a vendor's name to go to the list of bindings for that vendor. .. rst-class:: rst-columns ''', string_io) for vnd, bindings in vnd_lookup.vnd2bindings.items(): if len(bindings) == 0: continue print(f'- :ref:`{vnd_lookup.target(vnd)}`', file=string_io) print_block('''\ Bindings by vendor ************** This section contains available bindings, grouped by vendor. Within each group, bindings are listed by the "compatible" property they apply to, like this: Vendor name (vendor prefix)** .. rst-class:: rst-columns - <compatible-A> - <compatible-B> (on <bus-name> bus) - <compatible-C> - ... The text "(on <bus-name> bus)" appears when bindings may behave differently depending on the bus the node appears on. For example, this applies to some sensor device nodes, which may appear as children of either I2C or SPI bus nodes. ''', string_io) for vnd, bindings in vnd_lookup.vnd2bindings.items(): if isinstance(vnd, tuple): title = vnd[0] else: title = vnd_lookup.vendor(vnd).strip() if isinstance(vnd, str): title += f' ({vnd})' underline = '=' * len(title) if len(bindings) == 0: continue print_block(f'''\ .. _{vnd_lookup.target(vnd)}: {title} {underline} .. rst-class:: rst-columns ''', string_io) for binding in bindings: print(f'- :ref:`{binding_ref_target(binding)}`', file=string_io) print(file=string_io) write_if_updated(out_dir / 'bindings.rst', string_io.getvalue()) def write_orphans(bindings, base_binding, vnd_lookup, out_dir): # Write out_dir / bindings / foo / binding_page.rst for each binding # in 'bindings', along with any "disambiguation" pages needed when a # single compatible string can be handled by multiple bindings. # # These files are 'orphans' in the Sphinx sense: they are not in # any toctree. logging.info('updating :orphan: files for %d bindings', len(bindings)) num_written = 0 # First, figure out which compatibles map to multiple bindings. We # need this information to decide which of the generated files for # a compatible are "disambiguation" pages that point to per-bus # binding pages, and which ones aren't. compat2bindings = defaultdict(list) for binding in bindings: compat2bindings[binding.compatible].append(binding) dup_compat2bindings = {compatible: bindings for compatible, bindings in compat2bindings.items() if len(bindings) > 1} # Next, write the per-binding pages. These contain the # per-compatible targets for compatibles not in 'dup_compats'. # We'll finish up by writing per-compatible "disambiguation" pages # for compatibles in 'dup_compats'. # Names of properties in base.yaml. base_names = set(base_binding.prop2specs.keys()) for binding in bindings: string_io = io.StringIO() print_binding_page(binding, base_names, vnd_lookup, dup_compat2bindings, string_io) written = write_if_updated(out_dir / 'bindings' / binding_filename(binding), string_io.getvalue()) if written: num_written += 1 # Generate disambiguation pages for dup_compats. compatibles_dir = out_dir / 'compatibles' setup_compatibles_dir(dup_compat2bindings.keys(), compatibles_dir) for compatible in dup_compat2bindings: string_io = io.StringIO() print_compatible_disambiguation_page( compatible, dup_compat2bindings[compatible], string_io) written = write_if_updated(compatibles_dir / compatible_filename(compatible), string_io.getvalue()) if written: num_written += 1 logging.info('done writing :orphan: files; %d files needed updates', num_written) def print_binding_page(binding, base_names, vnd_lookup, dup_compats, string_io): # Print the rst content for 'binding' to 'string_io'. The # 'dup_compats' argument should support membership testing for # compatibles which have multiple associated bindings; if # 'binding.compatible' is not in it, then the ref target for the # entire compatible is generated in this page as well. # :orphan: # # .. ref_target: # # Title [(on <bus> bus)] # ###################### if binding.on_bus: on_bus_title = f' (on {binding.on_bus} bus)' else: on_bus_title = '' compatible = binding.compatible title = f'{compatible}{on_bus_title}' underline = '#' * len(title) if compatible not in dup_compats: # If this binding is the only one that handles this # compatible, point the ".. dtcompatible:" directive straight # to this page. There's no need for disambiguation. dtcompatible = f'.. dtcompatible:: {binding.compatible}' else: # This compatible is handled by multiple bindings; # its ".. dtcompatible::" should be in a disambiguation page # instead. dtcompatible = '' print_block(f'''\ :orphan: .. raw:: html <!-- FIXME: do not limit page width until content uses another representation format other than tables --> <style>.wy-nav-content {{ max-width: none; !important }}</style> {dtcompatible} .. _{binding_ref_target(binding)}: {title} {underline} ''', string_io) # Vendor: <link-to-vendor-section> vnd = compatible_vnd(compatible) print('Vendor: ' f':ref:`{vnd_lookup.vendor(vnd)} <{vnd_lookup.target(vnd)}>`\n', file=string_io) # Binding description. if binding.bus: bus_help = f'These nodes are "{binding.bus}" bus nodes.' else: bus_help = '' print_block(f'''\ Description ********* {bus_help} ''', string_io) print(to_code_block(binding.description.strip()), file=string_io) # Properties. print_block('''\ Properties ****** ''', string_io) print_top_level_properties(binding, base_names, string_io) print_child_binding_properties(binding, string_io) # Specifier cells. # # This presentation isn't particularly nice. Perhaps something # better can be done for future work. if binding.specifier2cells: print_block('''\ Specifier cell names ****************** ''', string_io) for specifier, cells in binding.specifier2cells.items(): print(f'- {specifier} cells: {", ".join(cells)}', file=string_io) def print_top_level_properties(binding, base_names, string_io): # Print the RST for top level properties for 'binding' to 'string_io'. # # The 'base_names' set contains all the base.yaml properties. def prop_table(filter_fn, deprecated): # Get a properly formatted and indented table of properties. specs = [prop_spec for prop_spec in binding.prop2specs.values() if filter_fn(prop_spec)] indent = ' ' * 14 if specs: temp_io = io.StringIO() print_property_table(specs, temp_io, deprecated=deprecated) return textwrap.indent(temp_io.getvalue(), indent) return indent + '(None)' def node_props_filter(prop_spec): return prop_spec.name not in base_names and not prop_spec.deprecated def deprecated_node_props_filter(prop_spec): return prop_spec.name not in base_names and prop_spec.deprecated def base_props_filter(prop_spec): return prop_spec.name in base_names if binding.child_binding: print_block('''\ Top level properties ==================== ''', string_io) if binding.prop2specs: if binding.child_binding: print_block(f''' These property descriptions apply to "{binding.compatible}" nodes themselves. This page also describes child node properties in the following sections. ''', string_io) print_block(f'''\ .. tabs:: .. group-tab:: Node specific properties Properties not inherited from the base binding file. {prop_table(node_props_filter, False)} .. group-tab:: Deprecated node specific properties Deprecated properties not inherited from the base binding file. {prop_table(deprecated_node_props_filter, False)} .. group-tab:: Base properties Properties inherited from the base binding file, which defines common properties that may be set on many nodes. Not all of these may apply to the "{binding.compatible}" compatible. {prop_table(base_props_filter, True)} ''', string_io) else: print('No top-level properties.\n', file=string_io) def print_child_binding_properties(binding, string_io): # Prints property tables for all levels of nesting of child # bindings. level = 1 child = binding.child_binding while child is not None: if level == 1: level_string = 'Child' elif level == 2: level_string = 'Grandchild' else: level_string = f'Level {level} child' if child.prop2specs: title = f'{level_string} node properties' underline = '=' * len(title) print(f'{title}\n{underline}\n', file=string_io) print_property_table(child.prop2specs.values(), string_io, deprecated=True) child = child.child_binding level += 1 def print_property_table(prop_specs, string_io, deprecated=False): # Writes a table of properties based on 'prop_specs', an iterable # of edtlib.PropertySpec objects, to 'string_io'. # # If 'deprecated' is true and the property is deprecated, an extra # line is printed mentioning that fact. We allow this to be turned # off for tables where all properties are deprecated, so it's # clear from context. # Table header. print_block('''\ .. list-table:: :widths: 1 1 4 :header-rows: 1 * - Name - Type - Details ''', string_io) def to_prop_table_row(prop_spec): # Get a multiline string for a PropertySpec table row. # The description column combines the description field, # along with things like the default value or enum values. # # The property 'description' field from the binding may span # one or multiple lines. We try to come up with a nice # presentation for each. details = '' raw_prop_descr = prop_spec.description if raw_prop_descr: details += to_code_block(raw_prop_descr) if prop_spec.required: details += '\n\nThis property is required.' if prop_spec.default: details += f'\n\nDefault value: ``{prop_spec.default}``' if prop_spec.const: details += f'\n\nConstant value: ``{prop_spec.const}``' elif prop_spec.enum: details += ('\n\nLegal values: ' + ', '.join(f'``{repr(val)}``' for val in prop_spec.enum)) if prop_spec.name in DETAILS_IN_IMPORTANT_PROPS: details += (f'\n\nSee {zref("dt-important-props")} for more ' 'information.') if deprecated and prop_spec.deprecated: details += '\n\nThis property is deprecated.' return f"""\ * - ``{prop_spec.name}`` - ``{prop_spec.type}`` - {textwrap.indent(details, ' ' * 7).lstrip()} """ # Print each row. for prop_spec in prop_specs: print(to_prop_table_row(prop_spec), file=string_io) def setup_compatibles_dir(compatibles, compatibles_dir): # Make a set of all the Path objects we will be creating for # out_dir / compatibles / {compatible_path}.rst. Delete all the ones that # shouldn't be there. Make sure the compatibles output directory # exists. logger.info('making output subdirectory %s', compatibles_dir) compatibles_dir.mkdir(parents=True, exist_ok=True) paths = set(compatibles_dir / compatible_filename(compatible) for compatible in compatibles) for path in compatibles_dir.iterdir(): if path not in paths: logger.info('removing unexpected file %s', path) path.unlink() def print_compatible_disambiguation_page(compatible, bindings, string_io): # Print the disambiguation page for 'compatible', which can be # handled by any of the bindings in 'bindings', to 'string_io'. assert len(bindings) > 1, (compatible, bindings) underline = '#' * len(compatible) output_list = '\n '.join(f'- :ref:`{binding_ref_target(binding)}`' for binding in bindings) print_block(f'''\ :orphan: .. dtcompatible:: {compatible} {compatible} {underline} The devicetree compatible ``{compatible}`` may be handled by any of the following bindings: {output_list} ''', string_io) def print_block(block, string_io): # Helper for dedenting and printing a triple-quoted RST block. # (Just a block of text, not necessarily just a 'code-block' # directive.) print(textwrap.dedent(block), file=string_io) def to_code_block(s, indent=0): # Converts 's', a string, to an indented rst .. code-block::. The # 'indent' argument is a leading indent for each line in the code # block, in spaces. indent = indent * ' ' return ('.. code-block:: none\n\n' + textwrap.indent(s, indent + ' ') + '\n') def compatible_vnd(compatible): # Get the vendor prefix for a compatible string 'compatible'. # # For example, compatible_vnd('foo,device') is 'foo'. # # If 'compatible' has no comma (','), None is returned. if ',' not in compatible: return None return compatible.split(',', 1)[0] def compatible_filename(compatible): # Name of the per-compatible disambiguation page within the # out_dir / compatibles directory. return f'{compatible}.rst' def zref(target, text=None): # Make an appropriate RST :ref:`text <target>` or :ref:`target` # string to a zephyr documentation ref target 'target', and return # it. # # By default, the bindings docs are in the main Zephyr # documentation, but this script supports putting them in a # separate Sphinx doc set. Since we also link to Zephyr # documentation from the generated content, we have an environment # variable based escape hatch for putting the target in the zephyr # doc set. # # This relies on intersphinx: # path_to_url docset = os.environ.get('GEN_DEVICETREE_REST_ZEPHYR_DOCSET', '') if docset.strip(): target = f'{docset}:{target}' if text: return f':ref:`{text} <{target}>`' return f':ref:`{target}`' def binding_filename(binding): # Returns the output file name for a binding relative to the # directory containing documentation for all bindings. It does # this by stripping off the '.../dts/bindings/' prefix common to # all bindings files in a DTS_ROOT directory. # # For example, for .../zephyr/dts/bindings/base/base.yaml, this # would return 'base/base.yaml'. # # Hopefully that's unique across roots. If not, we'll need to # update this function. as_posix = Path(binding.path).as_posix() dts_bindings = 'dts/bindings/' idx = as_posix.rfind(dts_bindings) if idx == -1: raise ValueError(f'binding path has no {dts_bindings}: {binding.path}') # Cut past dts/bindings, strip off the extension (.yaml or .yml), and # replace with .rst. return os.path.splitext(as_posix[idx + len(dts_bindings):])[0] + '.rst' def binding_ref_target(binding): # Return the sphinx ':ref:' target name for a binding. stem = Path(binding.path).stem return 'dtbinding_' + re.sub('[/,-]', '_', stem) def write_if_updated(path, s): # gen_helpers.write_if_updated() wrapper that handles logging and # creating missing parents, as needed. if not path.parent.is_dir(): path.parent.mkdir(parents=True) written = gen_helpers.write_if_updated(path, s) logger.debug('%s %s', 'wrote' if written else 'did NOT write', path) return written if __name__ == '__main__': main() sys.exit(0) ```	/content/code_sandbox/doc/_scripts/gen_devicetree_rest.py	python	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	6,532
```restructuredtext .. _developing_with_zephyr: Developing with Zephyr ###################### .. toctree:: :maxdepth: 1 getting_started/index.rst beyond-GSG.rst env_vars.rst application/index.rst debug/index.rst api/index.rst languages/index.rst optimizations/index flash_debug/index modules.rst west/index test/index sca/index toolchains/index tools/index ```	/content/code_sandbox/doc/develop/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	112
```restructuredtext .. _beyond-gsg: Beyond the Getting Started Guide ################################ The :ref:`getting_started` gives a straight-forward path to set up your Linux, macOS, or Windows environment for Zephyr development. In this document, we delve deeper into Zephyr development setup issues and alternatives. .. _python-pip: Python and pip ************ Python 3 and its package manager, pip\ [#pip]_, are used extensively by Zephyr to install and run scripts required to compile and run Zephyr applications, set up and maintain the Zephyr development environment, and build project documentation. Depending on your operating system, you may need to provide the ``--user`` flag to the ``pip3`` command when installing new packages. This is documented throughout the instructions. See `Installing Packages`_ in the Python Packaging User Guide for more information about pip\ [#pip]_, including `information on -\\-user`_. - On Linux, make sure ``~/.local/bin`` is at the front of your :envvar:`PATH` :ref:`environment variable <env_vars>`, or programs installed with ``--user`` won't be found. Installing with ``--user`` avoids conflicts between pip and the system package manager, and is the default on Debian-based distributions. - On macOS, `Homebrew disables -\\-user`_. - On Windows, see the `Installing Packages`_ information on ``--user`` if you require using this option. On all operating systems, pip's ``-U`` flag installs or updates the package if the package is already installed locally but a more recent version is available. It is good practice to use this flag if the latest version of a package is required. (Check the :zephyr_file:`scripts/requirements.txt` file to see if a specific Python package version is expected.) Advanced Platform Setup ******************* Here are some alternative instructions for more advanced platform setup configurations for supported development platforms: .. toctree:: :maxdepth: 1 Linux setup alternatives <getting_started/installation_linux.rst> macOS setup alternatives <getting_started/installation_mac.rst> Windows setup alternatives <getting_started/installation_win.rst> .. _gs_toolchain: Install a Toolchain ***************** Zephyr binaries are compiled and linked by a toolchain comprised of a cross-compiler and related tools which are different from the compiler and tools used for developing software that runs natively on your host operating system. You can install the :ref:`Zephyr SDK <toolchain_zephyr_sdk>` to get toolchains for all supported architectures, or install an :ref:`alternate toolchain <toolchains>` recommended by the SoC vendor or a specific board (check your specific :ref:`board-level documentation <boards>`). You can configure the Zephyr build system to use a specific toolchain by setting :ref:`environment variables <env_vars>` such as :envvar:`ZEPHYR_TOOLCHAIN_VARIANT <{TOOLCHAIN}_TOOLCHAIN_PATH>` to a supported value, along with additional variable(s) specific to the toolchain variant. .. _gs_toolchain_update: Updating the Zephyr SDK toolchain ********************************* When updating Zephyr SDK, check whether the :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` or :envvar:`ZEPHYR_SDK_INSTALL_DIR` environment variables are already set. * If the variables are not set, the latest compatible version of Zephyr SDK will be selected by default. Proceed to next step without making any changes. * If :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` is set, the corresponding toolchain will be selected at build time. Zephyr SDK is identified by the value ``zephyr``. If the :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` environment variable is not ``zephyr``, then either unset it or change its value to ``zephyr`` to make sure Zephyr SDK is selected. * If the :envvar:`ZEPHYR_SDK_INSTALL_DIR` environment variable is set, it will override the default lookup location for Zephyr SDK. If you install Zephyr SDK to one of the :ref:`recommended locations <toolchain_zephyr_sdk_bundle_variables>`, you can unset this variable. Otherwise, set it to your chosen install location. For more information about these environment variables in Zephyr, see :ref:`env_vars_important`. Cloning the Zephyr Repositories ***************************** The Zephyr project source is maintained in the `GitHub zephyr repo <path_to_url`_. External modules used by Zephyr are found in the parent `GitHub Zephyr project <path_to_url`_. Because of these dependencies, it's convenient to use the Zephyr-created :ref:`west <west>` tool to fetch and manage the Zephyr and external module source code. See :ref:`west-basics` for more details. Once your development tools are installed, use :ref:`west` to create, initialize, and download sources from the zephyr and external module repos. We'll use the name ``zephyrproject``, but you can choose any name that does not contain a space anywhere in the path. .. code-block:: console west init zephyrproject cd zephyrproject west update The ``west update`` command fetches and keeps :ref:`modules` in the :file:`zephyrproject` folder in sync with the code in the local zephyr repo. .. warning:: You must run ``west update`` any time the :file:`zephyr/west.yml` changes, caused, for example, when you pull the :file:`zephyr` repository, switch branches in it, or perform a ``git bisect`` inside of it. Keeping Zephyr updated ====================== To update the Zephyr project source code, you need to get the latest changes via ``git``. Afterwards, run ``west update`` as mentioned in the previous paragraph. .. code-block:: console # replace zephyrproject with the path you gave west init cd zephyrproject/zephyr git pull west update Export Zephyr CMake package *********************** The :ref:`cmake_pkg` can be exported to CMake's user package registry if it has not already been done as part of :ref:`getting_started`. .. _gs-board-aliases: Board Aliases ********* Developers who work with multiple boards may find explicit board names cumbersome and want to use aliases for common targets. This is supported by a CMake file with content like this: .. code-block:: cmake # Variable foo_BOARD_ALIAS=bar replaces BOARD=foo with BOARD=bar and # sets BOARD_ALIAS=foo in the CMake cache. set(pca10028_BOARD_ALIAS nrf51dk/nrf51822) set(pca10056_BOARD_ALIAS nrf52840dk/nrf52840) set(k64f_BOARD_ALIAS frdm_k64f) set(sltb004a_BOARD_ALIAS efr32mg_sltb004a) and specifying its location in :envvar:`ZEPHYR_BOARD_ALIASES`. This enables use of aliases ``pca10028`` in contexts like ``cmake -DBOARD=pca10028`` and ``west -b pca10028``. Build and Run an Application ************************** You can build, flash, and run Zephyr applications on real hardware using a supported host system. Depending on your operating system, you can also run it in emulation with QEMU, or as a native application with :ref:`native_sim <native_sim>`. Additional information about building applications can be found in the :ref:`build_an_application` section. Build Blinky ============ Let's build the :zephyr:code-sample:`blinky` sample application. Zephyr applications are built to run on specific hardware, called a "board"\ [#board_misnomer]_. We'll use the Phytec :ref:`reel_board <reel_board>` here, but you can change the ``reel_board`` build target to another value if you have a different board. See :ref:`boards` or run ``west boards`` from anywhere inside the ``zephyrproject`` directory for a list of supported boards. #. Go to the zephyr repository: .. code-block:: console cd zephyrproject/zephyr #. Build the blinky sample for the ``reel_board``: .. zephyr-app-commands:: :app: samples/basic/blinky :board: reel_board :goals: build The main build products will be in :file:`build/zephyr`; :file:`build/zephyr/zephyr.elf` is the blinky application binary in ELF format. Other binary formats, disassembly, and map files may be present depending on your board. The other sample applications in the :zephyr_file:`samples` folder are documented in :ref:`samples-and-demos`. .. note:: If you want to reuse an existing build directory for another board or application, you need to add the parameter ``-p=auto`` to ``west build`` to clean out settings and artifacts from the previous build. Run the Application by Flashing to a Board ========================================== Most hardware boards supported by Zephyr can be flashed by running ``west flash``. This may require board-specific tool installation and configuration to work properly. See :ref:`application_run` and your specific board's documentation in :ref:`boards` for additional details. .. _setting-udev-rules: Setting udev rules =================== Flashing a board requires permission to directly access the board hardware, usually managed by installation of the flashing tools. On Linux systems, if the ``west flash`` command fails, you likely need to define udev rules to grant the needed access permission. Udev is a device manager for the Linux kernel and the udev daemon handles all user space events raised when a hardware device is added (or removed) from the system. We can add a rules file to grant access permission by non-root users to certain USB-connected devices. The OpenOCD (On-Chip Debugger) project conveniently provides a rules file that defined board-specific rules for most Zephyr-supported arm-based boards, so we recommend installing this rules file by downloading it from their sourceforge repo, or if you've installed the Zephyr SDK there is a copy of this rules file in the SDK folder: * Either download the OpenOCD rules file and copy it to the right location:: wget -O 60-openocd.rules path_to_url sudo cp 60-openocd.rules /etc/udev/rules.d * or copy the rules file from the Zephyr SDK folder:: sudo cp ${ZEPHYR_SDK_INSTALL_DIR}/sysroots/x86_64-pokysdk-linux/usr/share/openocd/contrib/60-openocd.rules /etc/udev/rules.d Then, in either case, ask the udev daemon to reload these rules:: sudo udevadm control --reload Unplug and plug in the USB connection to your board, and you should have permission to access the board hardware for flashing. Check your board-specific documentation (:ref:`boards`) for further information if needed. Run the Application in QEMU =========================== On Linux and macOS, you can run Zephyr applications via emulation on your host system using `QEMU <path_to_url`_ when targeting either the x86 or ARM Cortex-M3 architectures. (QEMU is included with the Zephyr SDK installation.) On Windows, you need to install QEMU manually from `Download QEMU <path_to_url#windows>`_. After installation, add path to QEMU installation folder to PATH environment variable. To enable QEMU in Test Runner (Twister) on Windows, :ref:`set the environment variable <env_vars>` ``QEMU_BIN_PATH`` to the path of QEMU installation folder. For example, you can build and run the :ref:`hello_world` sample using the x86 emulation board configuration (``qemu_x86``), with: .. zephyr-app-commands:: :zephyr-app: samples/hello_world :host-os: unix :board: qemu_x86 :goals: build run To exit QEMU, type :kbd:`Ctrl-a`, then :kbd:`x`. Use ``qemu_cortex_m3`` to target an emulated Arm Cortex-M3 sample. .. _gs_native: Run a Sample Application natively (Linux) ========================================= You can compile some samples to run as host programs on Linux. See :ref:`native_sim` for more information. On 64-bit host operating systems, you need to install a 32-bit C library, or build targeting :ref:`native_sim/native/64<native_sim32_64>`. First, build Hello World for ``native_sim``. .. zephyr-app-commands:: :zephyr-app: samples/hello_world :host-os: unix :board: native_sim :goals: build Next, run the application. .. code-block:: console west build -t run # or just run zephyr.exe directly: ./build/zephyr/zephyr.exe Press :kbd:`Ctrl-C` to exit. You can run ``./build/zephyr/zephyr.exe --help`` to get a list of available options. This executable can be instrumented using standard tools, such as gdb or valgrind. .. rubric:: Footnotes .. [#pip] pip is Python's package installer. Its ``install`` command first tries to reuse packages and package dependencies already installed on your computer. If that is not possible, ``pip install`` downloads them from the Python Package Index (PyPI) on the Internet. The package versions requested by Zephyr's :file:`requirements.txt` may conflict with other requirements on your system, in which case you may want to set up a virtualenv for Zephyr development. .. [#board_misnomer] This has become something of a misnomer over time. While the target can be, and often is, a microprocessor running on its own dedicated hardware board, Zephyr also supports using QEMU to run targets built for other architectures in emulation, targets which produce native host system binaries that implement Zephyr's driver interfaces with POSIX APIs, and even running different Zephyr-based binaries on CPU cores of differing architectures on the same physical chip. Each of these hardware configurations is called a "board," even though that doesn't always make perfect sense in context. .. _information on -\\-user: path_to_url#installing-to-the-user-site .. _Homebrew disables -\\-user: path_to_url#note-on-pip-install---user .. _Installing Packages: path_to_url ```	/content/code_sandbox/doc/develop/beyond-GSG.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	3,285
```restructuredtext .. _env_vars: Environment Variables ===================== Various pages in this documentation refer to setting Zephyr-specific environment variables. This page describes how. Setting Variables *************** Option 1: Just Once ------------------- To set the environment variable ``MY_VARIABLE`` to ``foo`` for the lifetime of your current terminal window: .. tabs:: .. group-tab:: Linux/macOS .. code-block:: console export MY_VARIABLE=foo .. group-tab:: Windows .. code-block:: console set MY_VARIABLE=foo .. warning:: This is best for experimentation. If you close your terminal window, use another terminal window or tab, restart your computer, etc., this setting will be lost forever. Using options 2 or 3 is recommended if you want to keep using the setting. Option 2: In all Terminals -------------------------- .. tabs:: .. group-tab:: Linux/macOS Add the ``export MY_VARIABLE=foo`` line to your shell's startup script in your home directory. For Bash, this is usually :file:`~/.bashrc` on Linux or :file:`~/.bash_profile` on macOS. Changes in these startup scripts don't affect shell instances already started; try opening a new terminal window to get the new settings. .. group-tab:: Windows You can use the ``setx`` program in ``cmd.exe`` or the third-party RapidEE program. To use ``setx``, type this command, then close the terminal window. Any new ``cmd.exe`` windows will have ``MY_VARIABLE`` set to ``foo``. .. code-block:: console setx MY_VARIABLE foo To install RapidEE, a freeware graphical environment variable editor, `using Chocolatey`_ in an Administrator command prompt: .. code-block:: console choco install rapidee You can then run ``rapidee`` from your terminal to launch the program and set environment variables. Make sure to use the "User" environment variables area -- otherwise, you have to run RapidEE as administrator. Also make sure to save your changes by clicking the Save button at top left before exiting. Settings you make in RapidEE will be available whenever you open a new terminal window. .. _env_vars_zephyrrc: Option 3: Using ``zephyrrc`` files ---------------------------------- Choose this option if you don't want to make the variable's setting available to all of your terminals, but still want to save the value for loading into your environment when you are using Zephyr. .. tabs:: .. group-tab:: Linux/macOS Create a file named :file:`~/.zephyrrc` if it doesn't exist, then add this line to it: .. code-block:: console export MY_VARIABLE=foo To get this value back into your current terminal environment, you must run ``source zephyr-env.sh`` from the main ``zephyr`` repository. Among other things, this script sources :file:`~/.zephyrrc`. The value will be lost if you close the window, etc.; run ``source zephyr-env.sh`` again to get it back. .. group-tab:: Windows Add the line ``set MY_VARIABLE=foo`` to the file :file:`%userprofile%\\zephyrrc.cmd` using a text editor such as Notepad to save the value. To get this value back into your current terminal environment, you must run ``zephyr-env.cmd`` in a ``cmd.exe`` window after changing directory to the main ``zephyr`` repository. Among other things, this script runs :file:`%userprofile%\\zephyrrc.cmd`. The value will be lost if you close the window, etc.; run ``zephyr-env.cmd`` again to get it back. These scripts: - set :envvar:`ZEPHYR_BASE` to the location of the zephyr repository - adds some Zephyr-specific locations (such as zephyr's :file:`scripts` directory) to your :envvar:`PATH` environment variable - loads any settings from the ``zephyrrc`` files described above in :ref:`env_vars_zephyrrc`. You can thus use them any time you need any of these settings. .. _zephyr-env: Zephyr Environment Scripts ********************** You can use the zephyr repository scripts ``zephyr-env.sh`` (for macOS and Linux) and ``zephyr-env.cmd`` (for Windows) to load Zephyr-specific settings into your current terminal's environment. To do so, run this command from the zephyr repository: .. tabs:: .. group-tab:: Linux/macOS .. code-block:: console source zephyr-env.sh .. group-tab:: Windows .. code-block:: console zephyr-env.cmd These scripts: - set :envvar:`ZEPHYR_BASE` to the location of the zephyr repository - adds some Zephyr-specific locations (such as zephyr's :file:`scripts` directory) to your ``PATH`` environment variable - loads any settings from the ``zephyrrc`` files described above in :ref:`env_vars_zephyrrc`. You can thus use them any time you need any of these settings. .. _env_vars_important: Important Environment Variables ***************************** Some :ref:`important-build-vars` can also be set in the environment. Here is a description of some of these important environment variables. This is not a comprehensive list. .. envvar:: BOARD See :ref:`important-build-vars`. .. envvar:: CONF_FILE See :ref:`important-build-vars`. .. envvar:: SHIELD See :ref:`shields`. .. envvar:: ZEPHYR_BASE See :ref:`important-build-vars`. .. envvar:: EXTRA_ZEPHYR_MODULES See :ref:`important-build-vars`. .. envvar:: ZEPHYR_MODULES See :ref:`important-build-vars`. .. envvar:: ZEPHYR_BOARD_ALIASES See :ref:`gs-board-aliases` The following additional environment variables are significant when configuring the :ref:`toolchain <gs_toolchain>` used to build Zephyr applications. .. envvar:: ZEPHYR_SDK_INSTALL_DIR Path where Zephyr SDK is installed. .. envvar:: ZEPHYR_TOOLCHAIN_VARIANT The name of the toolchain to use. .. envvar:: {TOOLCHAIN}_TOOLCHAIN_PATH Path to the toolchain specified by :envvar:`ZEPHYR_TOOLCHAIN_VARIANT`. For example, if ``ZEPHYR_TOOLCHAIN_VARIANT=llvm``, use ``LLVM_TOOLCHAIN_PATH``. (Note the capitalization when forming the environment variable name.) You might need to update some of these variables when you :ref:`update the Zephyr SDK toolchain <gs_toolchain_update>`. Emulators and boards may also depend on additional programs. The build system will try to locate those programs automatically, but may rely on additional CMake or environment variables to do so. Please consult your emulator's or board's documentation for more information. The following environment variables may be useful in such situations: .. envvar:: PATH ``PATH`` is an environment variable used on Unix-like or Microsoft Windows operating systems to specify a set of directories where executable programs are located. .. _using Chocolatey: path_to_url ```	/content/code_sandbox/doc/develop/env_vars.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,660
```restructuredtext .. _modules: Modules (External projects) ############################ Zephyr relies on the source code of several externally maintained projects in order to avoid reinventing the wheel and to reuse as much well-established, mature code as possible when it makes sense. In the context of Zephyr's build system those are called modules. These modules must be integrated with the Zephyr build system, as described in more detail in other sections on this page. To be classified as a candidate for being included in the default list of modules, an external project is required to have its own life-cycle outside the Zephyr Project, that is, reside in its own repository, and have its own contribution and maintenance workflow and release process. Zephyr modules should not contain code that is written exclusively for Zephyr. Instead, such code should be contributed to the main zephyr tree. Modules to be included in the default manifest of the Zephyr project need to provide functionality or features endorsed and approved by the project Technical Steering Committee and should comply with the :ref:`module licensing requirements<modules_licensing>` and :ref:`contribution guidelines<modules_contributing>`. They should also have a Zephyr developer that is committed to maintain the module codebase. Zephyr depends on several categories of modules, including but not limited to: - Debugger integration - Silicon vendor Hardware Abstraction Layers (HALs) - Cryptography libraries - File Systems - Inter-Process Communication (IPC) libraries Additionally, in some cases modules (particularly vendor HALs) can contain references to optional :ref:`binary blobs <bin-blobs>`. This page summarizes a list of policies and best practices which aim at better organizing the workflow in Zephyr modules. .. _modules-vs-projects: Modules vs west projects ********************** Zephyr modules, described in this page, are not the same as :ref:`west projects <west-workspace>`. In fact, modules :ref:`do not require west <modules_without_west>` at all. However, when using modules :ref:`with west <modules_using_west>`, then the build system uses west in order to find modules. In summary: Modules are repositories that contain a :file:`zephyr/module.yml` file, so that the Zephyr build system can pull in the source code from the repository. :ref:`West projects <west-manifests-projects>` are entries in the `projects:` section in the :file:`west.yml` manifest file. West projects are often also modules, but not always. There are west projects that are not included in the final firmware image (eg. tools) and thus do not need to be modules. Modules are found by the Zephyr build system either via :ref:`west itself <modules_using_west>`, or via the :ref:`ZEPHYR_MODULES CMake variable <modules_without_west>`. The contents of this page only apply to modules, and not to west projects in general (unless they are a module themselves). Module Repositories ***************** * All modules included in the default manifest shall be hosted in repositories under the zephyrproject-rtos GitHub organization. * The module repository codebase shall include a module.yml file in a :file:`zephyr/` folder at the root of the repository. * Module repository names should follow the convention of using lowercase letters and dashes instead of underscores. This rule will apply to all new module repositories, except for repositories that are directly tracking external projects (hosted in Git repositories); such modules may be named as their external project counterparts. .. note:: Existing module repositories that do not conform to the above convention do not need to be renamed to comply with the above convention. * Module repositories names should be explicitly set in the :file:`zephyr/module.yml` file. * Modules should use "zephyr" as the default name for the repository main branch. Branches for specific purposes, for example, a module branch for an LTS Zephyr version, shall have names starting with the 'zephyr\_' prefix. * If the module has an external (upstream) project repository, the module repository should preserve the upstream repository folder structure. .. note:: It is not required in module repositories to maintain a 'master' branch mirroring the master branch of the external repository. It is not recommended as this may generate confusion around the module's main branch, which should be 'zephyr'. * Modules should expose all provided header files with an include pathname beginning with the module-name. (E.g., mcuboot should expose its ``bootutil/bootutil.h`` as "mcuboot/bootutil/bootutil.h".) .. _modules_synchronization: Synchronizing with upstream =========================== It is preferred to synchronize a module repository with the latest stable release of the corresponding external project. It is permitted, however, to update a Zephyr module repository with the latest development branch tip, if this is required to get important updates in the module codebase. When synchronizing a module with upstream it is mandatory to document the rationale for performing the particular update. Requirements for allowed practices ---------------------------------- Changes to the main branch of a module repository, including synchronization with upstream code base, may only be applied via pull requests. These pull requests shall be verifiable by Zephyr CI and mergeable (e.g. with the Rebase and merge, or Create a merge commit option using Github UI). This ensures that the incoming changes are always reviewable, and the downstream module repository history is incremental (that is, existing commits, tags, etc. are always preserved). This policy also allows to run Zephyr CI, git lint, identity, and license checks directly on the set of changes that are to be brought into the module repository. .. note:: Force-pushing to a module's main branch is not allowed. Allowed practices ----------------- The following practices conform to the above requirements and should be followed in all modules repositories. It is up to the module code owner to select the preferred synchronization practice, however, it is required that the selected practice is consistently followed in the respective module repository. Updating modules with a diff from upstream: Upstream changes brought as a single snapshot commit (manual diff) in a pull request against the module's main branch, which may be merged using the Rebase & merge operation. This approach is simple and should be applicable to all modules with the downside of suppressing the upstream history in the module repository. .. note:: The above practice is the only allowed practice in modules where the external project is not hosted in an upstream Git repository. The commit message is expected to identify the upstream project URL, the version to which the module is updated (upstream version, tag, commit SHA, if applicable, etc.), and the reason for the doing the update. Updating modules by merging the upstream branch: Upstream changes brought in by performing a Git merge of the intended upstream branch (e.g. main branch, latest release branch, etc.) submitting the result in pull request against the module main branch, and merging the pull request using the Create a merge commit operation. This approach is applicable to modules with an upstream project Git repository. The main advantages of this approach is that the upstream repository history (that is, the original commit SHAs) is preserved in the module repository. The downside of this approach is that two additional merge commits are generated in the downstream main branch. Contributing to Zephyr modules **************************** .. _modules_contributing: Individual Roles & Responsibilities =================================== To facilitate management of Zephyr module repositories, the following individual roles are defined. Administrator: Each Zephyr module shall have an administrator who is responsible for managing access to the module repository, for example, for adding individuals as Collaborators in the repository at the request of the module owner. Module administrators are members of the Administrators team, that is a group of project members with admin rights to module GitHub repositories. Module owner:** Each module shall have a module code owner. Module owners will have the overall responsibility of the contents of a Zephyr module repository. In particular, a module owner will: * coordinate code reviewing in the module repository * be the default assignee in pull-requests against the repository's main branch * request additional collaborators to be added to the repository, as they see fit * regularly synchronize the module repository with its upstream counterpart following the policies described in :ref:`modules_synchronization` * be aware of security vulnerability issues in the external project and update the module repository to include security fixes, as soon as the fixes are available in the upstream code base * list any known security vulnerability issues, present in the module codebase, in Zephyr release notes. .. note:: Module owners are not required to be Zephyr :ref:`Maintainers <project_roles>`. Merger: The Zephyr Release Engineering team has the right and the responsibility to merge approved pull requests in the main branch of a module repository. Maintaining the module codebase =============================== Updates in the zephyr main tree, for example, in public Zephyr APIs, may require patching a module's codebase. The responsibility for keeping the module codebase up to date is shared between the contributor of such updates in Zephyr and the module owner. In particular: * the contributor of the original changes in Zephyr is required to submit the corresponding changes that are required in module repositories, to ensure that Zephyr CI on the pull request with the original changes, as well as the module integration testing are successful. * the module owner has the overall responsibility for synchronizing and testing the module codebase with the zephyr main tree. This includes occasional advanced testing of the module's codebase in addition to the testing performed by Zephyr's CI. The module owner is required to fix issues in the module's codebase that have not been caught by Zephyr pull request CI runs. .. _modules_changes: Contributing changes to modules =============================== Submitting and merging changes directly to a module's codebase, that is, before they have been merged in the corresponding external project repository, should be limited to: * changes required due to updates in the zephyr main tree * urgent changes that should not wait to be merged in the external project first, such as fixes to security vulnerabilities. Non-trivial changes to a module's codebase, including changes in the module design or functionality should be discouraged, if the module has an upstream project repository. In that case, such changes shall be submitted to the upstream project, directly. :ref:`Submitting changes to modules <submitting_new_modules>` describes in detail the process of contributing changes to module repositories. Contribution guidelines ----------------------- Contributing to Zephyr modules shall follow the generic project :ref:`Contribution guidelines <contribute_guidelines>`. Pull Requests: may be merged with minimum of 2 approvals, including an approval by the PR assignee. In addition to this, pull requests in module repositories may only be merged if the introduced changes are verified with Zephyr CI tools, as described in more detail in other sections on this page. The merging of pull requests in the main branch of a module repository must be coupled with the corresponding manifest file update in the zephyr main tree. Issue Reporting: `GitHub issues`_ are intentionally disabled in module repositories, in favor of a centralized policy for issue reporting. Tickets concerning, for example, bugs or enhancements in modules shall be opened in the main zephyr repository. Issues should be appropriately labeled using GitHub labels corresponding to each module, where applicable. .. note:: It is allowed to file bug reports for zephyr modules to track the corresponding upstream project bugs in Zephyr. These bug reports shall not affect the :ref:`Release Quality Criteria<release_quality_criteria>`. .. _modules_licensing: Licensing requirements and policies ********************************* All source files in a module's codebase shall include a license header, unless the module repository has main license file** that covers source files that do not include license headers. Main license files shall be added in the module's codebase by Zephyr developers, only if they exist as part of the external project, and they contain a permissive OSI-compliant license. Main license files should preferably contain the full license text instead of including an SPDX license identifier. If multiple main license files are present it shall be made clear which license applies to each source file in a module's codebase. Individual license headers in module source files supersede the main license. Any new content to be added in a module repository will require to have license coverage. .. note:: Zephyr recommends conveying module licensing via individual license headers and main license files. This not a hard requirement; should an external project have its own practice of conveying how licensing applies in the module's codebase (for example, by having a single or multiple main license files), this practice may be accepted by and be referred to in the Zephyr module, as long as licensing requirements, for example OSI compliance, are satisfied. ================ When creating a module repository a developer shall: * import the main license files, if they exist in the external project, and * document (for example in the module README or .yml file) the default license that covers the module's codebase. -------------- adds new content in module repositories. Documentation requirements ************************** All Zephyr module repositories shall include an .rst file documenting: * the scope and the purpose of the module * how the module integrates with Zephyr * the owner of the module repository * synchronization information with the external project (commit, SHA, version etc.) * licensing information as described in :ref:`modules_licensing`. The file shall be required for the inclusion of the module and the contained information should be kept up to date. Testing requirements ****************** All Zephyr modules should provide some level of integration** testing, ensuring that the integration with Zephyr works correctly. Integration tests: * may be in the form of a minimal set of samples and tests that reside in the zephyr main tree * should verify basic usage of the module (configuration, functional APIs, etc.) that is integrated with Zephyr. * shall be built and executed (for example in QEMU) as part of twister runs in pull requests that introduce changes in module repositories. .. note:: New modules, that are candidates for being included in the Zephyr default manifest, shall provide some level of integration testing. .. note:: Vendor HALs are implicitly tested via Zephyr tests built or executed on target platforms, so they do not need to provide integration tests. The purpose of integration testing is not to provide functional verification of the module; this should be part of the testing framework of the external project. Certain external projects provide test suites that reside in the upstream testing infrastructure but are written explicitly for Zephyr. These tests may (but are not required to) be part of the Zephyr test framework. Deprecating and removing modules ********************************* Modules may be deprecated for reasons including, but not limited to: * Lack of maintainership in the module * Licensing changes in the external project * Codebase becoming obsolete The module information shall indicate whether a module is deprecated and the build system shall issue a warning when trying to build Zephyr using a deprecated module. Deprecated modules may be removed from the Zephyr default manifest after 2 Zephyr releases. .. note:: Repositories of removed modules shall remain accessible via their original URL, as they are required by older Zephyr versions. Integrate modules in Zephyr build system ************************************** The build system variable :makevar:`ZEPHYR_MODULES` is a `CMake list`_ of absolute paths to the directories containing Zephyr modules. These modules contain :file:`CMakeLists.txt` and :file:`Kconfig` files describing how to build and configure them, respectively. Module :file:`CMakeLists.txt` files are added to the build using CMake's `add_subdirectory()`_ command, and the :file:`Kconfig` files are included in the build's Kconfig menu tree. If you have :ref:`west <west>` installed, you don't need to worry about how this variable is defined unless you are adding a new module. The build system knows how to use west to set :makevar:`ZEPHYR_MODULES`. You can add additional modules to this list by setting the :makevar:`EXTRA_ZEPHYR_MODULES` CMake variable or by adding a :makevar:`EXTRA_ZEPHYR_MODULES` line to ``.zephyrrc`` (See the section on :ref:`env_vars` for more details). This can be useful if you want to keep the list of modules found with west and also add your own. .. note:: If the module ``FOO`` is provided by :ref:`west <west>` but also given with ``-DEXTRA_ZEPHYR_MODULES=/<path>/foo`` then the module given by the command line variable :makevar:`EXTRA_ZEPHYR_MODULES` will take precedence. This allows you to use a custom version of ``FOO`` when building and still use other Zephyr modules provided by :ref:`west <west>`. This can for example be useful for special test purposes. If you want to permanently add modules to the zephyr workspace and you are using zephyr as your manifest repository, you can also add a west manifest file into the :zephyr_file:`submanifests` directory. See :zephyr_file:`submanifests/README.txt` for more details. See :ref:`west-basics` for more on west workspaces. Finally, you can also specify the list of modules yourself in various ways, or not use modules at all if your application doesn't need them. .. _module-yml: Module yaml file description ************************** A module can be described using a file named :file:`zephyr/module.yml`. The format of :file:`zephyr/module.yml` is described in the following: Module name =========== Each Zephyr module is given a name by which it can be referred to in the build system. The name should be specified in the :file:`zephyr/module.yml` file. This will ensure the module name is not changeable through user-defined directory names or ``west`` manifest files: .. code-block:: yaml name: <name> In CMake the location of the Zephyr module can then be referred to using the CMake variable ``ZEPHYR_<MODULE_NAME>_MODULE_DIR`` and the variable ``ZEPHYR_<MODULE_NAME>_CMAKE_DIR`` holds the location of the directory containing the module's :file:`CMakeLists.txt` file. .. note:: When used for CMake and Kconfig variables, all letters in module names are converted to uppercase and all non-alphanumeric characters are converted to underscores (_). As example, the module ``foo-bar`` must be referred to as ``ZEPHYR_FOO_BAR_MODULE_DIR`` in CMake and Kconfig. Here is an example for the Zephyr module ``foo``: .. code-block:: yaml name: foo .. note:: If the ``name`` field is not specified then the Zephyr module name will be set to the name of the module folder. As example, the Zephyr module located in :file:`<workspace>/modules/bar` will use ``bar`` as its module name if nothing is specified in :file:`zephyr/module.yml`. Module integration files (in-module) ==================================== Inclusion of build files, :file:`CMakeLists.txt` and :file:`Kconfig`, can be described as: .. code-block:: yaml build: cmake: <cmake-directory> kconfig: <directory>/Kconfig The ``cmake: <cmake-directory>`` part specifies that :file:`<cmake-directory>` contains the :file:`CMakeLists.txt` to use. The ``kconfig: <directory>/Kconfig`` part specifies the Kconfig file to use. Neither is required: ``cmake`` defaults to ``zephyr``, and ``kconfig`` defaults to ``zephyr/Kconfig``. Here is an example :file:`module.yml` file referring to :file:`CMakeLists.txt` and :file:`Kconfig` files in the root directory of the module: .. code-block:: yaml build: cmake: . kconfig: Kconfig .. _sysbuild_module_integration: Sysbuild integration ==================== :ref:`Sysbuild<sysbuild>` is the Zephyr build system that allows for building multiple images as part of a single application, the sysbuild build process can be extended externally with modules as needed, for example to add custom build steps or add additional targets to a build. Inclusion of sysbuild-specific build files, :file:`CMakeLists.txt` and :file:`Kconfig`, can be described as: .. code-block:: yaml build: sysbuild-cmake: <cmake-directory> sysbuild-kconfig: <directory>/Kconfig The ``sysbuild-cmake: <cmake-directory>`` part specifies that :file:`<cmake-directory>` contains the :file:`CMakeLists.txt` to use. The ``sysbuild-kconfig: <directory>/Kconfig`` part specifies the Kconfig file to use. Here is an example :file:`module.yml` file referring to :file:`CMakeLists.txt` and :file:`Kconfig` files in the `sysbuild` directory of the module: .. code-block:: yaml build: sysbuild-cmake: sysbuild sysbuild-kconfig: sysbuild/Kconfig The module description file :file:`zephyr/module.yml` can also be used to specify that the build files, :file:`CMakeLists.txt` and :file:`Kconfig`, are located in a :ref:`modules_module_ext_root`. Build files located in a ``MODULE_EXT_ROOT`` can be described as: .. code-block:: yaml build: sysbuild-cmake-ext: True sysbuild-kconfig-ext: True This allows control of the build inclusion to be described externally to the Zephyr module. .. _modules-vulnerability-monitoring: Vulnerability monitoring ======================== The module description file :file:`zephyr/module.yml` can be used to improve vulnerability monitoring. If your module needs to track vulnerabilities using an external reference (e.g your module is forked from another repository), you can use the ``security`` section. It contains the field ``external-references`` that contains a list of references that needs to be monitored for your module. The supported formats are: - CPE (Common Platform Enumeration) - PURL (Package URL) .. code-block:: yaml security: external-references: - <module-related-cpe> - <an-other-module-related-cpe> - <module-related-purl> A real life example for `mbedTLS` module could look like this: .. code-block:: yaml security: external-references: - cpe:2.3:a:arm:mbed_tls:3.5.2:::::::* - pkg:github/Mbed-TLS/mbedtls@V3.5.2 .. note:: CPE field must follow the CPE 2.3 schema provided by `NVD <path_to_url`_. PURL field must follow the PURL specification provided by `Github <path_to_url`_. Build system integration ======================== When a module has a :file:`module.yml` file, it will automatically be included into the Zephyr build system. The path to the module is then accessible through Kconfig and CMake variables. Zephyr modules -------------- In both Kconfig and CMake, the variable ``ZEPHYR_<MODULE_NAME>_MODULE_DIR`` contains the absolute path to the module. In CMake, ``ZEPHYR_<MODULE_NAME>_CMAKE_DIR`` contains the absolute path to the directory containing the :file:`CMakeLists.txt` file that is included into CMake build system. This variable's value is empty if the module.yml file does not specify a CMakeLists.txt. To read these variables for a Zephyr module named ``foo``: - In CMake: use ``${ZEPHYR_FOO_MODULE_DIR}`` for the module's top level directory, and ``${ZEPHYR_FOO_CMAKE_DIR}`` for the directory containing its :file:`CMakeLists.txt` - In Kconfig: use ``$(ZEPHYR_FOO_MODULE_DIR)`` for the module's top level directory Notice how a lowercase module name ``foo`` is capitalized to ``FOO`` in both CMake and Kconfig. These variables can also be used to test whether a given module exists. For example, to verify that ``foo`` is the name of a Zephyr module: .. code-block:: cmake if(ZEPHYR_FOO_MODULE_DIR) # Do something if FOO exists. endif() In Kconfig, the variable may be used to find additional files to include. For example, to include the file :file:`some/Kconfig` in module ``foo``: .. code-block:: kconfig source "$(ZEPHYR_FOO_MODULE_DIR)/some/Kconfig" During CMake processing of each Zephyr module, the following variables are also available: - the current module's name: ``${ZEPHYR_CURRENT_MODULE_NAME}`` - the current module's top level directory: ``${ZEPHYR_CURRENT_MODULE_DIR}`` - the current module's :file:`CMakeLists.txt` directory: ``${ZEPHYR_CURRENT_CMAKE_DIR}`` This removes the need for a Zephyr module to know its own name during CMake processing. The module can source additional CMake files using these ``CURRENT`` variables. For example: .. code-block:: cmake include(${ZEPHYR_CURRENT_MODULE_DIR}/cmake/code.cmake) It is possible to append values to a Zephyr `CMake list`_ variable from the module's first CMakeLists.txt file. To do so, append the value to the list and then set the list in the PARENT_SCOPE of the CMakeLists.txt file. For example, to append ``bar`` to the ``FOO_LIST`` variable in the Zephyr CMakeLists.txt scope: .. code-block:: cmake list(APPEND FOO_LIST bar) set(FOO_LIST ${FOO_LIST} PARENT_SCOPE) An example of a Zephyr list where this is useful is when adding additional directories to the ``SYSCALL_INCLUDE_DIRS`` list. Sysbuild modules ---------------- In both Kconfig and CMake, the variable ``SYSBUILD_CURRENT_MODULE_DIR`` contains the absolute path to the sysbuild module. In CMake, ``SYSBUILD_CURRENT_CMAKE_DIR`` contains the absolute path to the directory containing the :file:`CMakeLists.txt` file that is included into CMake build system. This variable's value is empty if the module.yml file does not specify a CMakeLists.txt. To read these variables for a sysbuild module: - In CMake: use ``${SYSBUILD_CURRENT_MODULE_DIR}`` for the module's top level directory, and ``${SYSBUILD_CURRENT_CMAKE_DIR}`` for the directory containing its :file:`CMakeLists.txt` - In Kconfig: use ``$(SYSBUILD_CURRENT_MODULE_DIR)`` for the module's top level directory In Kconfig, the variable may be used to find additional files to include. For example, to include the file :file:`some/Kconfig`: .. code-block:: kconfig source "$(SYSBUILD_CURRENT_MODULE_DIR)/some/Kconfig" The module can source additional CMake files using these variables. For example: .. code-block:: cmake include(${SYSBUILD_CURRENT_MODULE_DIR}/cmake/code.cmake) It is possible to append values to a Zephyr `CMake list`_ variable from the module's first CMakeLists.txt file. To do so, append the value to the list and then set the list in the PARENT_SCOPE of the CMakeLists.txt file. For example, to append ``bar`` to the ``FOO_LIST`` variable in the Zephyr CMakeLists.txt scope: .. code-block:: cmake list(APPEND FOO_LIST bar) set(FOO_LIST ${FOO_LIST} PARENT_SCOPE) Sysbuild modules hooks ---------------------- Sysbuild provides an infrastructure which allows a sysbuild module to define a function which will be invoked by sysbuild at a pre-defined point in the CMake flow. Functions invoked by sysbuild: - ``<module-name>_pre_cmake(IMAGES <images>)``: This function is called for each sysbuild module before CMake configure is invoked for all images. - ``<module-name>_post_cmake(IMAGES <images>)``: This function is called for each sysbuild module after CMake configure has completed for all images. - ``<module-name>_pre_domains(IMAGES <images>)``: This function is called for each sysbuild module before domains yaml is created by sysbuild. - ``<module-name>_post_domains(IMAGES <images>)``: This function is called for each sysbuild module after domains yaml has been created by sysbuild. arguments passed from sysbuild to the function defined by a module: - ``<images>`` is the list of Zephyr images that will be created by the build system. If a module ``foo`` want to provide a post CMake configure function, then the module's sysbuild :file:`CMakeLists.txt` file must define function ``foo_post_cmake()``. To facilitate naming of functions, the module name is provided by sysbuild CMake through the ``SYSBUILD_CURRENT_MODULE_NAME`` CMake variable when loading the module's sysbuild :file:`CMakeLists.txt` file. Example of how the ``foo`` sysbuild module can define ``foo_post_cmake()``: .. code-block:: cmake function(${SYSBUILD_CURRENT_MODULE_NAME}_post_cmake) cmake_parse_arguments(POST_CMAKE "" "" "IMAGES" ${ARGN}) message("Invoking ${CMAKE_CURRENT_FUNCTION}. Images: ${POST_CMAKE_IMAGES}") endfunction() Zephyr module dependencies ========================== A Zephyr module may be dependent on other Zephyr modules to be present in order to function correctly. Or it might be that a given Zephyr module must be processed after another Zephyr module, due to dependencies of certain CMake targets. Such a dependency can be described using the ``depends`` field. .. code-block:: yaml build: depends: - <module> Here is an example for the Zephyr module ``foo`` that is dependent on the Zephyr module ``bar`` to be present in the build system: .. code-block:: yaml name: foo build: depends: - bar This example will ensure that ``bar`` is present when ``foo`` is included into the build system, and it will also ensure that ``bar`` is processed before ``foo``. .. _modules_module_ext_root: Module integration files (external) =================================== Module integration files can be located externally to the Zephyr module itself. The ``MODULE_EXT_ROOT`` variable holds a list of roots containing integration files located externally to Zephyr modules. Module integration files in Zephyr ---------------------------------- The Zephyr repository contain :file:`CMakeLists.txt` and :file:`Kconfig` build files for certain known Zephyr modules. Those files are located under .. code-block:: none <ZEPHYR_BASE> modules <module_name> CMakeLists.txt Kconfig Module integration files in a custom location --------------------------------------------- You can create a similar ``MODULE_EXT_ROOT`` for additional modules, and make those modules known to Zephyr build system. Create a ``MODULE_EXT_ROOT`` with the following structure .. code-block:: none <MODULE_EXT_ROOT> modules modules.cmake <module_name> CMakeLists.txt Kconfig and then build your application by specifying ``-DMODULE_EXT_ROOT`` parameter to the CMake build system. The ``MODULE_EXT_ROOT`` accepts a `CMake list`_ of roots as argument. A Zephyr module can automatically be added to the ``MODULE_EXT_ROOT`` list using the module description file :file:`zephyr/module.yml`, see :ref:`modules_build_settings`. .. note:: ``ZEPHYR_BASE`` is always added as a ``MODULE_EXT_ROOT`` with the lowest priority. This allows you to overrule any integration files under ``<ZEPHYR_BASE>/modules/<module_name>`` with your own implementation your own ``MODULE_EXT_ROOT``. The :file:`modules.cmake` file must contain the logic that specifies the integration files for Zephyr modules via specifically named CMake variables. To include a module's CMake file, set the variable ``ZEPHYR_<MODULE_NAME>_CMAKE_DIR`` to the path containing the CMake file. To include a module's Kconfig file, set the variable ``ZEPHYR_<MODULE_NAME>_KCONFIG`` to the path to the Kconfig file. The following is an example on how to add support the ``FOO`` module. Create the following structure .. code-block:: none <MODULE_EXT_ROOT> modules modules.cmake foo CMakeLists.txt Kconfig and inside the :file:`modules.cmake` file, add the following content .. code-block:: cmake set(ZEPHYR_FOO_CMAKE_DIR ${CMAKE_CURRENT_LIST_DIR}/foo) set(ZEPHYR_FOO_KCONFIG ${CMAKE_CURRENT_LIST_DIR}/foo/Kconfig) Module integration files (zephyr/module.yml) -------------------------------------------- The module description file :file:`zephyr/module.yml` can be used to specify that the build files, :file:`CMakeLists.txt` and :file:`Kconfig`, are located in a :ref:`modules_module_ext_root`. Build files located in a ``MODULE_EXT_ROOT`` can be described as: .. code-block:: yaml build: cmake-ext: True kconfig-ext: True This allows control of the build inclusion to be described externally to the Zephyr module. The Zephyr repository itself is always added as a Zephyr module ext root. .. _modules_build_settings: Build settings ============== It is possible to specify additional build settings that must be used when including the module into the build system. All ``root`` settings are relative to the root of the module. Build settings supported in the :file:`module.yml` file are: - ``board_root``: Contains additional boards that are available to the build system. Additional boards must be located in a :file:`<board_root>/boards` folder. - ``dts_root``: Contains additional dts files related to the architecture/soc families. Additional dts files must be located in a :file:`<dts_root>/dts` folder. - ``snippet_root``: Contains additional snippets that are available for use. These snippets must be defined in :file:`snippet.yml` files underneath the :file:`<snippet_root>/snippets` folder. For example, if you have ``snippet_root: foo``, then you should place your module's :file:`snippet.yml` files in :file:`<your-module>/foo/snippets` or any nested subdirectory. - ``soc_root``: Contains additional SoCs that are available to the build system. Additional SoCs must be located in a :file:`<soc_root>/soc` folder. - ``arch_root``: Contains additional architectures that are available to the build system. Additional architectures must be located in a :file:`<arch_root>/arch` folder. - ``module_ext_root``: Contains :file:`CMakeLists.txt` and :file:`Kconfig` files for Zephyr modules, see also :ref:`modules_module_ext_root`. - ``sca_root``: Contains additional :ref:`SCA <sca>` tool implementations available to the build system. Each tool must be located in :file:`<sca_root>/sca/<tool>` folder. The folder must contain a :file:`sca.cmake`. Example of a :file:`module.yaml` file containing additional roots, and the corresponding file system layout. .. code-block:: yaml build: settings: board_root: . dts_root: . soc_root: . arch_root: . module_ext_root: . requires the following folder structure: .. code-block:: none <zephyr-module-root> arch boards dts modules soc Twister (Test Runner) ===================== To execute both tests and samples available in modules, the Zephyr test runner (twister) should be pointed to the directories containing those samples and tests. This can be done by specifying the path to both samples and tests in the :file:`zephyr/module.yml` file. Additionally, if a module defines out of tree boards, the module file can point twister to the path where those files are maintained in the module. For example: .. code-block:: yaml build: cmake: . samples: - samples tests: - tests boards: - boards .. _modules-bin-blobs: Binary Blobs ============ Zephyr supports fetching and using :ref:`binary blobs <bin-blobs>`, and their metadata is contained entirely in :file:`zephyr/module.yml`. This is because a binary blob must always be associated with a Zephyr module, and thus the blob metadata belongs in the module's description itself. Binary blobs are fetched using :ref:`west blobs <west-blobs>`. If ``west`` is :ref:`not used <modules_without_west>`, they must be downloaded and verified manually. The ``blobs`` section in :file:`zephyr/module.yml` consists of a sequence of maps, each of which has the following entries: - ``path``: The path to the binary blob, relative to the :file:`zephyr/blobs/` folder in the module repository - ``sha256``: `SHA-256 <path_to_url`_ checksum of the binary blob file - ``type``: The :ref:`type of binary blob <bin-blobs-types>`. Currently limited to ``img`` or ``lib`` - ``version``: A version string - ``license-path``: Path to the license file for this blob, relative to the root of the module repository - ``url``: URL that identifies the location the blob will be fetched from, as well as the fetching scheme to use - ``description``: Human-readable description of the binary blob - ``doc-url``: A URL pointing to the location of the official documentation for this blob Module Inclusion ================ .. _modules_using_west: Using West ---------- If west is installed and :makevar:`ZEPHYR_MODULES` is not already set, the build system finds all the modules in your :term:`west installation` and uses those. It does this by running :ref:`west list <west-built-in-misc>` to get the paths of all the projects in the installation, then filters the results to just those projects which have the necessary module metadata files. Each project in the ``west list`` output is tested like this: - If the project contains a file named :file:`zephyr/module.yml`, then the content of that file will be used to determine which files should be added to the build, as described in the previous section. - Otherwise (i.e. if the project has no :file:`zephyr/module.yml`), the build system looks for :file:`zephyr/CMakeLists.txt` and :file:`zephyr/Kconfig` files in the project. If both are present, the project is considered a module, and those files will be added to the build. - If neither of those checks succeed, the project is not considered a module, and is not added to :makevar:`ZEPHYR_MODULES`. .. _modules_without_west: Without West ------------ If you don't have west installed or don't want the build system to use it to find Zephyr modules, you can set :makevar:`ZEPHYR_MODULES` yourself using one of the following options. Each of the directories in the list must contain either a :file:`zephyr/module.yml` file or the files :file:`zephyr/CMakeLists.txt` and :file:`Kconfig`, as described in the previous section. #. At the CMake command line, like this: .. code-block:: console cmake -DZEPHYR_MODULES=<path-to-module1>[;<path-to-module2>[...]] ... #. At the top of your application's top level :file:`CMakeLists.txt`, like this: .. code-block:: cmake set(ZEPHYR_MODULES <path-to-module1> <path-to-module2> [...]) find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE}) If you choose this option, make sure to set the variable before calling ``find_package(Zephyr ...)``, as shown above. #. In a separate CMake script which is pre-loaded to populate the CMake cache, like this: .. code-block:: cmake # Put this in a file with a name like "zephyr-modules.cmake" set(ZEPHYR_MODULES <path-to-module1> <path-to-module2> CACHE STRING "pre-cached modules") You can tell the build system to use this file by adding ``-C zephyr-modules.cmake`` to your CMake command line. Not using modules ----------------- If you don't have west installed and don't specify :makevar:`ZEPHYR_MODULES` yourself, then no additional modules are added to the build. You will still be able to build any applications that don't require code or Kconfig options defined in an external repository. Submitting changes to modules ****************************** When submitting new or making changes to existing modules the main repository Zephyr needs a reference to the changes to be able to verify the changes. In the main tree this is done using revisions. For code that is already merged and part of the tree we use the commit hash, a tag, or a branch name. For pull requests however, we require specifying the pull request number in the revision field to allow building the zephyr main tree with the changes submitted to the module. To avoid merging changes to master with pull request information, the pull request should be marked as ``DNM`` (Do Not Merge) or preferably a draft pull request to make sure it is not merged by mistake and to allow for the module to be merged first and be assigned a permanent commit hash. Drafts reduce noise by not automatically notifying anyone until marked as "Ready for review". Once the module is merged, the revision will need to be changed either by the submitter or by the maintainer to the commit hash of the module which reflects the changes. Note that multiple and dependent changes to different modules can be submitted using exactly the same process. In this case you will change multiple entries of all modules that have a pull request against them. .. _submitting_new_modules: Process for submitting a new module =================================== Please follow the process in :ref:`external-src-process` and obtain the TSC approval to integrate the external source code as a module If the request is approved, a new repository will created by the project team and initialized with basic information that would allow submitting code to the module project following the project contribution guidelines. If a module is maintained as a fork of another project on Github, the Zephyr module related files and changes in relation to upstream need to be maintained in a special branch named ``zephyr``. Maintainers from the Zephyr project will create the repository and initialize it. You will be added as a collaborator in the new repository. Submit the module content (code) to the new repository following the guidelines described :ref:`here <modules_using_west>`, and then add a new entry to the :zephyr_file:`west.yml` with the following information: .. code-block:: console - name: <name of repository> path: <path to where the repository should be cloned> revision: <ref pointer to module pull request> For example, to add my_module to the manifest: .. code-block:: console - name: my_module path: modules/lib/my_module revision: pull/23/head Where 23 in the example above indicated the pull request number submitted to the my_module repository. Once the module changes are reviewed and merged, the revision needs to be changed to the commit hash from the module repository. .. _changes_to_existing_module: Process for submitting changes to existing modules ================================================== #. Submit the changes using a pull request to an existing repository following the :ref:`contribution guidelines <contribute_guidelines>` and :ref:`expectations <contributor-expectations>`. #. Submit a pull request changing the entry referencing the module into the :zephyr_file:`west.yml` of the main Zephyr tree with the following information: .. code-block:: console - name: <name of repository> path: <path to where the repository should be cloned> revision: <ref pointer to module pull request> For example, to add my_module to the manifest: .. code-block:: console - name: my_module path: modules/lib/my_module revision: pull/23/head Where 23 in the example above indicated the pull request number submitted to the my_module repository. Once the module changes are reviewed and merged, the revision needs to be changed to the commit hash from the module repository. .. _CMake list: path_to_url#lists .. _add_subdirectory(): path_to_url .. _GitHub issues: path_to_url ```	/content/code_sandbox/doc/develop/modules.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	10,200
```unknown mainmenu "Your Application Name" # Your application configuration options go here # Sources Kconfig.zephyr in the Zephyr root directory. # # Note: All 'source' statements work relative to the Zephyr root directory (due # to the $srctree environment variable being set to $ZEPHYR_BASE). If you want # to 'source' relative to the current Kconfig file instead, use 'rsource' (or a # path relative to the Zephyr root). source "Kconfig.zephyr" ```	/content/code_sandbox/doc/develop/application/application-kconfig.include	unknown	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	117
```restructuredtext .. _application: Application Development ####################### .. note:: In this document, we'll assume: - your application directory, :file:`<app>`, is something like :file:`<home>/zephyrproject/app` - its build directory is :file:`<app>/build` These terms are defined below. On Linux/macOS, <home> is equivalent to ``~``. On Windows, it's ``%userprofile%``. Keeping your application inside the workspace (:file:`<home>/zephyrproject`) makes it easier to use ``west build`` and other commands with it. (You can put your application anywhere as long as :ref:`ZEPHYR_BASE <important-build-vars>` is set appropriately, though.) Overview ****** Zephyr's build system is based on `CMake`_. The build system is application-centric, and requires Zephyr-based applications to initiate building the Zephyr source code. The application build controls the configuration and build process of both the application and Zephyr itself, compiling them into a single binary. The main zephyr repository contains Zephyr's source code, configuration files, and build system. You also likely have installed various :ref:`modules` alongside the zephyr repository, which provide third party source code integration. The files in the application directory** link Zephyr and any modules with the application. This directory contains all application-specific files, such as application-specific configuration files and source code. Here are the files in a simple Zephyr application: .. code-block:: none <app> CMakeLists.txt app.overlay prj.conf VERSION src main.c These contents are: * CMakeLists.txt: This file tells the build system where to find the other application files, and links the application directory with Zephyr's CMake build system. This link provides features supported by Zephyr's build system, such as board-specific configuration files, the ability to run and debug compiled binaries on real or emulated hardware, and more. * app.overlay: This is a devicetree overlay file that specifies application-specific changes which should be applied to the base devicetree for any board you build for. The purpose of devicetree overlays is usually to configure something about the hardware used by the application. The build system looks for :file:`app.overlay` by default, but you can add more devicetree overlays, and other default files are also searched for. See :ref:`devicetree` for more information about devicetree. * prj.conf: This is a Kconfig fragment that specifies application-specific values for one or more Kconfig options. These application settings are merged with other settings to produce the final configuration. The purpose of Kconfig fragments is usually to configure the software features used by the application. The build system looks for :file:`prj.conf` by default, but you can add more Kconfig fragments, and other default files are also searched for. See :ref:`application-kconfig` below for more information. * VERSION: A text file that contains several version information fields. These fields let you manage the lifecycle of the application and automate providing the application version when signing application images. See :ref:`app-version-details` for more information about this file and how to use it. * main.c: A source code file. Applications typically contain source files written in C, C++, or assembly language. The Zephyr convention is to place them in a subdirectory of :file:`<app>` named :file:`src`. Once an application has been defined, you will use CMake to generate a build directory, which contains the files you need to build the application and Zephyr, then link them together into a final binary you can run on your board. The easiest way to do this is with :ref:`west build <west-building>`, but you can use CMake directly also. Application build artifacts are always generated in a separate build directory: Zephyr does not support "in-tree" builds. The following sections describe how to create, build, and run Zephyr applications, followed by more detailed reference material. .. _zephyr-app-types: Application types *************** We distinguish three basic types of Zephyr application based on where :file:`<app>` is located: .. table:: +------------------------------+--------------------------------+ \| Application type \| :file:`<app>` location \| +------------------------------+--------------------------------+ \| :ref:`repository \| zephyr repository \| \| <zephyr-repo-app>` \| \| +------------------------------+--------------------------------+ \| :ref:`workspace \| west workspace where Zephyr is \| \| <zephyr-workspace-app>` \| installed \| +------------------------------+--------------------------------+ \| :ref:`freestanding \| other locations \| \| <zephyr-freestanding-app>` \| \| +------------------------------+--------------------------------+ We'll discuss these more below. To learn how the build system supports each type, see :ref:`cmake_pkg`. .. _zephyr-repo-app: Zephyr repository application ============================= An application located within the ``zephyr`` source code repository in a Zephyr :ref:`west workspace <west-workspaces>` is referred to as a Zephyr repository application. In the following example, the :ref:`hello_world sample <hello_world>` is a Zephyr repository application: .. code-block:: none zephyrproject/ .west/ config zephyr/ arch/ boards/ cmake/ samples/ hello_world/ ... tests/ ... .. _zephyr-workspace-app: Zephyr workspace application ============================ An application located within a :ref:`workspace <west-workspaces>`, but outside the zephyr repository itself, is referred to as a Zephyr workspace application. In the following example, ``app`` is a Zephyr workspace application: .. code-block:: none zephyrproject/ .west/ config zephyr/ bootloader/ modules/ tools/ <vendor/private-repositories>/ applications/ app/ .. _zephyr-freestanding-app: Zephyr freestanding application =============================== A Zephyr application located outside of a Zephyr :ref:`workspace <west-workspaces>` is referred to as a Zephyr freestanding application. In the following example, ``app`` is a Zephyr freestanding application: .. code-block:: none <home>/ zephyrproject/ .west/ config zephyr/ bootloader/ modules/ ... app/ CMakeLists.txt prj.conf src/ main.c .. _zephyr-creating-app: Creating an Application ******************* In Zephyr, you can either use a reference workspace application or create your application by hand. .. _zephyr-creating-app-from-example: Using a Reference Workspace Application ======================================= The `example-application`_ Git repository contains a reference :ref:`workspace application <zephyr-workspace-app>`. It is recommended to use it as a reference when creating your own application as described in the following sections. The example-application repository demonstrates how to use several commonly-used features, such as: - Custom :ref:`board ports <board_porting_guide>` - Custom :ref:`devicetree bindings <dt-bindings>` - Custom :ref:`device drivers <device_model_api>` - Continuous Integration (CI) setup, including using :ref:`twister <twister_script>` - A custom west :ref:`extension command <west-extensions>` Basic example-application Usage ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The easiest way to get started with the example-application repository within an existing Zephyr workspace is to follow these steps: .. code-block:: console cd <home>/zephyrproject git clone path_to_url my-app The directory name :file:`my-app` above is arbitrary: change it as needed. You can now go into this directory and adapt its contents to suit your needs. Since you are using an existing Zephyr workspace, you can use ``west build`` or any other west commands to build, flash, and debug. Advanced example-application Usage ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You can also use the example-application repository as a starting point for building your own customized Zephyr-based software distribution. This lets you do things like: - remove Zephyr modules you don't need - add additional custom repositories of your own - override repositories provided by Zephyr with your own versions - share the results with others and collaborate further The example-application repository contains a :file:`west.yml` file and is therefore also a west :ref:`manifest repository <west-workspace>`. Use this to create a new, customized workspace by following these steps: .. code-block:: console cd <home> mkdir my-workspace cd my-workspace git clone path_to_url my-manifest-repo west init -l my-manifest-repo This will create a new workspace with the :ref:`T2 topology <west-t2>`, with :file:`my-manifest-repo` as the manifest repository. The :file:`my-workspace` and :file:`my-manifest-repo` names are arbitrary: change them as needed. Next, customize the manifest repository. The initial contents of this repository will match the example-application's contents when you clone it. You can then edit :file:`my-manifest-repo/west.yml` to your liking, changing the set of repositories in it as you wish. See :ref:`west-manifest-import` for many examples of how to add or remove different repositories from your workspace as needed. Make any other changes you need to other files. When you are satisfied, you can run: .. code-block:: west update and your workspace will be ready for use. If you push the resulting :file:`my-manifest-repo` repository somewhere else, you can share your work with others. For example, let's say you push the repository to ``path_to_url``. Other people can then set up a matching workspace by running: .. code-block:: west init -m path_to_url my-workspace cd my-workspace west update From now on, you can collaborate on the shared software by pushing changes to the repositories you are using and updating :file:`my-manifest-repo/west.yml` as needed to add and remove repositories, or change their contents. .. _zephyr-creating-app-by-hand: Creating an Application by Hand =============================== You can follow these steps to create a basic application directory from scratch. However, using the `example-application`_ repository or one of Zephyr's :ref:`samples-and-demos` as a starting point is likely to be easier. #. Create an application directory. For example, in a Unix shell or Windows ``cmd.exe`` prompt: .. code-block:: console mkdir app .. warning:: Building Zephyr or creating an application in a directory with spaces anywhere on the path is not supported. So the Windows path :file:`C:\\Users\\YourName\\app` will work, but :file:`C:\\Users\\Your Name\\app` will not. #. Create your source code files. It's recommended to place all application source code in a subdirectory named :file:`src`. This makes it easier to distinguish between project files and sources. Continuing the previous example, enter: .. code-block:: console cd app mkdir src #. Place your application source code in the :file:`src` sub-directory. For this example, we'll assume you created a file named :file:`src/main.c`. #. Create a file named :file:`CMakeLists.txt` in the ``app`` directory with the following contents: .. code-block:: cmake cmake_minimum_required(VERSION 3.20.0) find_package(Zephyr) project(my_zephyr_app) target_sources(app PRIVATE src/main.c) Notes: - The ``cmake_minimum_required()`` call is required by CMake. It is also invoked by the Zephyr package on the next line. CMake will error out if its version is older than either the version in your :file:`CMakeLists.txt` or the version number in the Zephyr package. - ``find_package(Zephyr)`` pulls in the Zephyr build system, which creates a CMake target named ``app`` (see :ref:`cmake_pkg`). Adding sources to this target is how you include them in the build. The Zephyr package will define ``Zephyr-Kernel`` as a CMake project and enable support for the ``C``, ``CXX``, ``ASM`` languages. - ``project(my_zephyr_app)`` defines your application's CMake project. This must be called after ``find_package(Zephyr)`` to avoid interference with Zephyr's ``project(Zephyr-Kernel)``. - ``target_sources(app PRIVATE src/main.c)`` is to add your source file to the ``app`` target. This must come after ``find_package(Zephyr)`` which defines the target. You can add as many files as you want with ``target_sources()``. #. Create at least one Kconfig fragment for your application (usually named :file:`prj.conf`) and set Kconfig option values needed by your application there. See :ref:`application-kconfig`. If no Kconfig options need to be set, create an empty file. #. Configure any devicetree overlays needed by your application, usually in a file named :file:`app.overlay`. See :ref:`set-devicetree-overlays`. #. Set up any other files you may need, such as :ref:`twister <twister_script>` configuration files, continuous integration files, documentation, etc. .. _important-build-vars: Important Build System Variables ****************************** You can control the Zephyr build system using many variables. This section describes the most important ones that every Zephyr developer should know about. .. note:: The variables :makevar:`BOARD`, :makevar:`CONF_FILE`, and :makevar:`DTC_OVERLAY_FILE` can be supplied to the build system in 3 ways (in order of precedence): * As a parameter to the ``west build`` or ``cmake`` invocation via the ``-D`` command-line switch. If you have multiple overlay files, you should use quotations, ``"file1.overlay;file2.overlay"`` * As :ref:`env_vars`. * As a ``set(<VARIABLE> <VALUE>)`` statement in your :file:`CMakeLists.txt` * :makevar:`ZEPHYR_BASE`: Zephyr base variable used by the build system. ``find_package(Zephyr)`` will automatically set this as a cached CMake variable. But ``ZEPHYR_BASE`` can also be set as an environment variable in order to force CMake to use a specific Zephyr installation. * :makevar:`BOARD`: Selects the board that the application's build will use for the default configuration. See :ref:`boards` for built-in boards, and :ref:`board_porting_guide` for information on adding board support. * :makevar:`CONF_FILE`: Indicates the name of one or more Kconfig configuration fragment files. Multiple filenames can be separated with either spaces or semicolons. Each file includes Kconfig configuration values that override the default configuration values. See :ref:`initial-conf` for more information. * :makevar:`EXTRA_CONF_FILE`: Additional Kconfig configuration fragment files. Multiple filenames can be separated with either spaces or semicolons. This can be useful in order to leave :makevar:`CONF_FILE` at its default value, but "mix in" some additional configuration options. * :makevar:`DTC_OVERLAY_FILE`: One or more devicetree overlay files to use. Multiple files can be separated with semicolons. See :ref:`set-devicetree-overlays` for examples and :ref:`devicetree-intro` for information about devicetree and Zephyr. * :makevar:`EXTRA_DTC_OVERLAY_FILE`: Additional devicetree overlay files to use. Multiple files can be separated with semicolons. This can be useful to leave :makevar:`DTC_OVERLAY_FILE` at its default value, but "mix in" some additional overlay files. * :makevar:`SHIELD`: see :ref:`shields` * :makevar:`ZEPHYR_MODULES`: A `CMake list`_ containing absolute paths of additional directories with source code, Kconfig, etc. that should be used in the application build. See :ref:`modules` for details. If you set this variable, it must be a complete list of all modules to use, as the build system will not automatically pick up any modules from west. * :makevar:`EXTRA_ZEPHYR_MODULES`: Like :makevar:`ZEPHYR_MODULES`, except these will be added to the list of modules found via west, instead of replacing it. * :makevar:`FILE_SUFFIX`: Optional suffix for filenames that will be added to Kconfig fragments and devicetree overlays (if these files exists, otherwise will fallback to the name without the prefix). See :ref:`application-file-suffixes` for details. .. note:: You can use a :ref:`cmake_build_config_package` to share common settings for these variables. .. _zephyr-app-cmakelists: Application CMakeLists.txt ************************ Every application must have a :file:`CMakeLists.txt` file. This file is the entry point, or top level, of the build system. The final :file:`zephyr.elf` image contains both the application and the kernel libraries. This section describes some of what you can do in your :file:`CMakeLists.txt`. Make sure to follow these steps in order. #. If you only want to build for one board, add the name of the board configuration for your application on a new line. For example: .. code-block:: cmake set(BOARD qemu_x86) Refer to :ref:`boards` for more information on available boards. The Zephyr build system determines a value for :makevar:`BOARD` by checking the following, in order (when a BOARD value is found, CMake stops looking further down the list): - Any previously used value as determined by the CMake cache takes highest precedence. This ensures you don't try to run a build with a different :makevar:`BOARD` value than you set during the build configuration step. - Any value given on the CMake command line (directly or indirectly via ``west build``) using ``-DBOARD=YOUR_BOARD`` will be checked for and used next. - If an :ref:`environment variable <env_vars>` ``BOARD`` is set, its value will then be used. - Finally, if you set ``BOARD`` in your application :file:`CMakeLists.txt` as described in this step, this value will be used. #. If your application uses a configuration file or files other than the usual :file:`prj.conf`, add lines setting the :makevar:`CONF_FILE` variable to these files appropriately. If multiple filenames are given, separate them by a single space or semicolon. CMake lists can be used to build up configuration fragment files in a modular way when you want to avoid setting :makevar:`CONF_FILE` in a single place. For example: .. code-block:: cmake set(CONF_FILE "fragment_file1.conf") list(APPEND CONF_FILE "fragment_file2.conf") See :ref:`initial-conf` for more information. #. If your application uses devicetree overlays, you may need to set :ref:`DTC_OVERLAY_FILE <important-build-vars>`. See :ref:`set-devicetree-overlays`. #. If your application has its own kernel configuration options, create a :file:`Kconfig` file in the same directory as your application's :file:`CMakeLists.txt`. See :ref:`the Kconfig section of the manual <kconfig>` for detailed Kconfig documentation. An (unlikely) advanced use case would be if your application has its own unique configuration options that are set differently depending on the build configuration. If you just want to set application specific values for existing Zephyr configuration options, refer to the :makevar:`CONF_FILE` description above. Structure your :file:`Kconfig` file like this: .. literalinclude:: application-kconfig.include :language: kconfig .. note:: Environment variables in ``source`` statements are expanded directly, so you do not need to define an ``option env="ZEPHYR_BASE"`` Kconfig "bounce" symbol. If you use such a symbol, it must have the same name as the environment variable. See :ref:`kconfig_extensions` for more information. The :file:`Kconfig` file is automatically detected when placed in the application directory, but it is also possible for it to be found elsewhere if the CMake variable :makevar:`KCONFIG_ROOT` is set with an absolute path. #. Specify that the application requires Zephyr on a new line, after any lines added from the steps above: .. code-block:: cmake find_package(Zephyr) project(my_zephyr_app) .. note:: ``find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})`` can be used if enforcing a specific Zephyr installation by explicitly setting the ``ZEPHYR_BASE`` environment variable should be supported. All samples in Zephyr supports the ``ZEPHYR_BASE`` environment variable. #. Now add any application source files to the 'app' target library, each on their own line, like so: .. code-block:: cmake target_sources(app PRIVATE src/main.c) Below is a simple example :file:`CMakeList.txt`: .. code-block:: cmake set(BOARD qemu_x86) find_package(Zephyr) project(my_zephyr_app) target_sources(app PRIVATE src/main.c) The Cmake property ``HEX_FILES_TO_MERGE`` leverages the application configuration provided by Kconfig and CMake to let you merge externally built hex files with the hex file generated when building the Zephyr application. For example: .. code-block:: cmake set_property(GLOBAL APPEND PROPERTY HEX_FILES_TO_MERGE ${app_bootloader_hex} ${PROJECT_BINARY_DIR}/${KERNEL_HEX_NAME} ${app_provision_hex}) .. _zephyr-app-cmakecache: CMakeCache.txt ********** CMake uses a CMakeCache.txt file as persistent key/value string storage used to cache values between runs, including compile and build options and paths to library dependencies. This cache file is created when CMake is run in an empty build folder. For more details about the CMakeCache.txt file see the official CMake documentation `runningcmake`_ . .. _runningcmake: path_to_url Application Configuration *********************** .. _application-configuration-directory: Application Configuration Directory =================================== Zephyr will use configuration files from the application's configuration directory except for files with an absolute path provided by the arguments described earlier, for example ``CONF_FILE``, ``EXTRA_CONF_FILE``, ``DTC_OVERLAY_FILE``, and ``EXTRA_DTC_OVERLAY_FILE``. The application configuration directory is defined by the ``APPLICATION_CONFIG_DIR`` variable. ``APPLICATION_CONFIG_DIR`` will be set by one of the sources below with the highest priority listed first. 1. If ``APPLICATION_CONFIG_DIR`` is specified by the user with ``-DAPPLICATION_CONFIG_DIR=<path>`` or in a CMake file before ``find_package(Zephyr)`` then this folder is used a the application's configuration directory. 2. The application's source directory. .. _application-kconfig: Kconfig Configuration ===================== Application configuration options are usually set in :file:`prj.conf` in the application directory. For example, C++ support could be enabled with this assignment: .. code-block:: cfg CONFIG_CPP=y Looking at :ref:`existing samples <samples-and-demos>` is a good way to get started. See :ref:`setting_configuration_values` for detailed documentation on setting Kconfig configuration values. The :ref:`initial-conf` section on the same page explains how the initial configuration is derived. See :ref:`kconfig-search` for a complete list of configuration options. See :ref:`hardening` for security information related with Kconfig options. The other pages in the :ref:`Kconfig section of the manual <kconfig>` are also worth going through, especially if you planning to add new configuration options. Experimental features ~~~~~~~~~~~~~~~~~~~~~ Zephyr is a project under constant development and thus there are features that are still in early stages of their development cycle. Such features will be marked ``[EXPERIMENTAL]`` in their Kconfig title. The :kconfig:option:`CONFIG_WARN_EXPERIMENTAL` setting can be used to enable warnings at CMake configure time if any experimental feature is enabled. .. code-block:: cfg CONFIG_WARN_EXPERIMENTAL=y For example, if option ``CONFIG_FOO`` is experimental, then enabling it and :kconfig:option:`CONFIG_WARN_EXPERIMENTAL` will print the following warning at CMake configure time when you build an application: .. code-block:: none warning: Experimental symbol FOO is enabled. Devicetree Overlays =================== See :ref:`set-devicetree-overlays`. .. _application-file-suffixes: File Suffixes ============= Zephyr applications might want to have a single code base with multiple configurations for different build/product variants which would necessitate different Kconfig options and devicetree configuration. In order to better configure this, Zephyr provides a :makevar:`FILE_SUFFIX` option when configuring applications that can be automatically appended to filenames. This is applied to Kconfig fragments and board overlays but with a fallback so that if such files do not exist, the files without these suffixes will be used instead. Given the following example project layout: .. code-block:: none <app> CMakeLists.txt prj.conf prj_mouse.conf boards native_sim.overlay qemu_cortex_m3_mouse.overlay src main.c * If this is built normally without ``FILE_SUFFIX`` being defined for ``native_sim`` then ``prj.conf`` and ``boards/native_sim.overlay`` will be used. * If this is build normally without ``FILE_SUFFIX`` being defined for ``qemu_cortex_m3`` then ``prj.conf`` will be used, no application devicetree overlay will be used. * If this is built with ``FILE_SUFFIX`` set to ``mouse`` for ``native_sim`` then ``prj_mouse.conf`` and ``boards/native_sim.overlay`` will be used (there is no ``native_sim_mouse.overlay`` file so it falls back to ``native_sim.overlay``). * If this is build with ``FILE_SUFFIX`` set to ``mouse`` for ``qemu_cortex_m3`` then ``prj_mouse.conf`` will be used and ``boards/qemu_cortex_m3_mouse.overlay`` will be used. .. note:: When ``CONF_FILE`` is set in the form of ``prj_X.conf`` then the ``X`` will be used as the build type. If this is combined with ``FILE_SUFFIX`` then the file suffix option will take priority over the build type. Application-Specific Code ************************* Application-specific source code files are normally added to the application's :file:`src` directory. If the application adds a large number of files the developer can group them into sub-directories under :file:`src`, to whatever depth is needed. Application-specific source code should not use symbol name prefixes that have been reserved by the kernel for its own use. For more information, see `Naming Conventions <path_to_url`_. Third-party Library Code ======================== It is possible to build library code outside the application's :file:`src` directory but it is important that both application and library code targets the same Application Binary Interface (ABI). On most architectures there are compiler flags that control the ABI targeted, making it important that both libraries and applications have certain compiler flags in common. It may also be useful for glue code to have access to Zephyr kernel header files. To make it easier to integrate third-party components, the Zephyr build system has defined CMake functions that give application build scripts access to the zephyr compiler options. The functions are documented and defined in :zephyr_file:`cmake/modules/extensions.cmake` and follow the naming convention ``zephyr_get_<type>_<format>``. The following variables will often need to be exported to the third-party build system. * ``CMAKE_C_COMPILER``, ``CMAKE_AR``. * ``ARCH`` and ``BOARD``, together with several variables that identify the Zephyr kernel version. :zephyr_file:`samples/application_development/external_lib` is a sample project that demonstrates some of these features. .. _build_an_application: Building an Application *********************** The Zephyr build system compiles and links all components of an application into a single application image that can be run on simulated hardware or real hardware. Like any other CMake-based system, the build process takes place :ref:`in two stages <cmake-details>`. First, build files (also known as a buildsystem) are generated using the ``cmake`` command-line tool while specifying a generator. This generator determines the native build tool the buildsystem will use in the second stage. The second stage runs the native build tool to actually build the source files and generate an image. To learn more about these concepts refer to the `CMake introduction`_ in the official CMake documentation. Although the default build tool in Zephyr is :std:ref:`west <west>`, Zephyr's meta-tool, which invokes ``cmake`` and the underlying build tool (``ninja`` or ``make``) behind the scenes, you can also choose to invoke ``cmake`` directly if you prefer. On Linux and macOS you can choose between the ``make`` and ``ninja`` generators (i.e. build tools), whereas on Windows you need to use ``ninja``, since ``make`` is not supported on this platform. For simplicity we will use ``ninja`` throughout this guide, and if you choose to use ``west build`` to build your application know that it will default to ``ninja`` under the hood. As an example, let's build the Hello World sample for the ``reel_board``: .. zephyr-app-commands:: :tool: all :app: samples/hello_world :board: reel_board :goals: build On Linux and macOS, you can also build with ``make`` instead of ``ninja``: Using west: - to use ``make`` just once, add ``-- -G"Unix Makefiles"`` to the west build command line; see the :ref:`west build <west-building-generator>` documentation for an example. - to use ``make`` by default from now on, run ``west config build.generator "Unix Makefiles"``. Using CMake directly: .. zephyr-app-commands:: :tool: cmake :app: samples/hello_world :generator: make :host-os: unix :board: reel_board :goals: build Basics ====== #. Navigate to the application directory :file:`<app>`. #. Enter the following commands to build the application's :file:`zephyr.elf` image for the board specified in the command-line parameters: .. zephyr-app-commands:: :tool: all :cd-into: :board: <board> :goals: build If desired, you can build the application using the configuration settings specified in an alternate :file:`.conf` file using the :code:`CONF_FILE` parameter. These settings will override the settings in the application's :file:`.config` file or its default :file:`.conf` file. For example: .. zephyr-app-commands:: :tool: all :cd-into: :board: <board> :gen-args: -DCONF_FILE=prj.alternate.conf :goals: build :compact: As described in the previous section, you can instead choose to permanently set the board and configuration settings by either exporting :makevar:`BOARD` and :makevar:`CONF_FILE` environment variables or by setting their values in your :file:`CMakeLists.txt` using ``set()`` statements. Additionally, ``west`` allows you to :ref:`set a default board <west-building-config>`. .. _build-directory-contents: Build Directory Contents ======================== When using the Ninja generator a build directory looks like this: .. code-block:: none <app>/build build.ninja CMakeCache.txt CMakeFiles cmake_install.cmake rules.ninja zephyr The most notable files in the build directory are: * :file:`build.ninja`, which can be invoked to build the application. * A :file:`zephyr` directory, which is the working directory of the generated build system, and where most generated files are created and stored. After running ``ninja``, the following build output files will be written to the :file:`zephyr` sub-directory of the build directory. (This is not the Zephyr base directory, which contains the Zephyr source code etc. and is described above.) * :file:`.config`, which contains the configuration settings used to build the application. .. note:: The previous version of :file:`.config` is saved to :file:`.config.old` whenever the configuration is updated. This is for convenience, as comparing the old and new versions can be handy. * Various object files (:file:`.o` files and :file:`.a` files) containing compiled kernel and application code. * :file:`zephyr.elf`, which contains the final combined application and kernel binary. Other binary output formats, such as :file:`.hex` and :file:`.bin`, are also supported. .. _application_rebuild: Rebuilding an Application ========================= Application development is usually fastest when changes are continually tested. Frequently rebuilding your application makes debugging less painful as the application becomes more complex. It's usually a good idea to rebuild and test after any major changes to the application's source files, CMakeLists.txt files, or configuration settings. .. important:: The Zephyr build system rebuilds only the parts of the application image potentially affected by the changes. Consequently, rebuilding an application is often significantly faster than building it the first time. Sometimes the build system doesn't rebuild the application correctly because it fails to recompile one or more necessary files. You can force the build system to rebuild the entire application from scratch with the following procedure: #. Open a terminal console on your host computer, and navigate to the build directory :file:`<app>/build`. #. Enter one of the following commands, depending on whether you want to use ``west`` or ``cmake`` directly to delete the application's generated files, except for the :file:`.config` file that contains the application's current configuration information. .. code-block:: console west build -t clean or .. code-block:: console ninja clean Alternatively, enter one of the following commands to delete all generated files, including the :file:`.config` files that contain the application's current configuration information for those board types. .. code-block:: console west build -t pristine or .. code-block:: console ninja pristine If you use west, you can take advantage of its capability to automatically :ref:`make the build folder pristine <west-building-config>` whenever it is required. #. Rebuild the application normally following the steps specified in :ref:`build_an_application` above. .. _application_board_version: Building for a board revision ============================= The Zephyr build system has support for specifying multiple hardware revisions of a single board with small variations. Using revisions allows the board support files to make minor adjustments to a board configuration without duplicating all the files described in :ref:`create-your-board-directory` for each revision. To build for a particular revision, use ``<board>@<revision>`` instead of plain ``<board>``. For example: .. zephyr-app-commands:: :tool: all :cd-into: :board: <board>@<revision> :goals: build :compact: Check your board's documentation for details on whether it has multiple revisions, and what revisions are supported. When targeting a board revision, the active revision will be printed at CMake configure time, like this: .. code-block:: console -- Board: plank, Revision: 1.5.0 .. _application_run: Run an Application **************** An application image can be run on a real board or emulated hardware. .. _application_run_board: Running on a Board ================== Most boards supported by Zephyr let you flash a compiled binary using the ``flash`` target to copy the binary to the board and run it. Follow these instructions to flash and run an application on real hardware: #. Build your application, as described in :ref:`build_an_application`. #. Make sure your board is attached to your host computer. Usually, you'll do this via USB. #. Run one of these console commands from the build directory, :file:`<app>/build`, to flash the compiled Zephyr image and run it on your board: .. code-block:: console west flash or .. code-block:: console ninja flash The Zephyr build system integrates with the board support files to use hardware-specific tools to flash the Zephyr binary to your hardware, then run it. Each time you run the flash command, your application is rebuilt and flashed again. In cases where board support is incomplete, flashing via the Zephyr build system may not be supported. If you receive an error message about flash support being unavailable, consult :ref:`your board's documentation <boards>` for additional information on how to flash your board. .. note:: When developing on Linux, it's common to need to install board-specific udev rules to enable USB device access to your board as a non-root user. If flashing fails, consult your board's documentation to see if this is necessary. .. _application_run_qemu: Running in an Emulator ====================== Zephyr has built-in emulator support for QEMU. It allows you to run and test an application virtually, before (or in lieu of) loading and running it on actual target hardware. Check out :ref:`beyond-GSG` for additional steps needed on Windows. Follow these instructions to run an application via QEMU: #. Build your application for one of the QEMU boards, as described in :ref:`build_an_application`. For example, you could set ``BOARD`` to: - ``qemu_x86`` to emulate running on an x86-based board - ``qemu_cortex_m3`` to emulate running on an ARM Cortex M3-based board #. Run one of these console commands from the build directory, :file:`<app>/build`, to run the Zephyr binary in QEMU: .. code-block:: console west build -t run or .. code-block:: console ninja run #. Press :kbd:`Ctrl A, X` to stop the application from running in QEMU. The application stops running and the terminal console prompt redisplays. Each time you execute the run command, your application is rebuilt and run again. .. note:: If the (Linux only) :ref:`Zephyr SDK <toolchain_zephyr_sdk>` is installed, the ``run`` target will use the SDK's QEMU binary by default. To use another version of QEMU, :ref:`set the environment variable <env_vars>` ``QEMU_BIN_PATH`` to the path of the QEMU binary you want to use instead. .. note:: You can choose a specific emulator by appending ``_<emulator>`` to your target name, for example ``west build -t run_qemu`` or ``ninja run_qemu`` for QEMU. .. _custom_board_definition: Custom Board, Devicetree and SOC Definitions **************************************** In cases where the board or platform you are developing for is not yet supported by Zephyr, you can add board, Devicetree and SOC definitions to your application without having to add them to the Zephyr tree. The structure needed to support out-of-tree board and SOC development is similar to how boards and SOCs are maintained in the Zephyr tree. By using this structure, it will be much easier to upstream your platform related work into the Zephyr tree after your initial development is done. Add the custom board to your application or a dedicated repository using the following structure: .. code-block:: console boards/ soc/ CMakeLists.txt prj.conf README.rst src/ where the ``boards`` directory hosts the board you are building for: .. code-block:: console . boards vendor my_custom_board doc img support src and the ``soc`` directory hosts any SOC code. You can also have boards that are supported by a SOC that is available in the Zephyr tree. Boards ====== Use the vendor name as the folder name (which must match the vendor prefix in :zephyr_file:`dts/bindings/vendor-prefixes.txt` if submitting upstream to Zephyr, or be ``others`` if it is not a vendor board) under ``boards`` for ``my_custom_board``. Documentation (under ``doc/``) and support files (under ``support/``) are optional, but will be needed when submitting to Zephyr. The contents of ``my_custom_board`` should follow the same guidelines for any Zephyr board, and provide the following files:: my_custom_board_defconfig my_custom_board.dts my_custom_board.yaml board.cmake board.h CMakeLists.txt doc/ Kconfig.my_custom_board Kconfig.defconfig support/ Once the board structure is in place, you can build your application targeting this board by specifying the location of your custom board information with the ``-DBOARD_ROOT`` parameter to the CMake build system: .. zephyr-app-commands:: :tool: all :board: <board name> :gen-args: -DBOARD_ROOT=<path to boards> :goals: build :compact: This will use your custom board configuration and will generate the Zephyr binary into your application directory. You can also define the ``BOARD_ROOT`` variable in the application :file:`CMakeLists.txt` file. Make sure to do so before** pulling in the Zephyr boilerplate with ``find_package(Zephyr ...)``. .. note:: When specifying ``BOARD_ROOT`` in a CMakeLists.txt, then an absolute path must be provided, for example ``list(APPEND BOARD_ROOT ${CMAKE_CURRENT_SOURCE_DIR}/<extra-board-root>)``. When using ``-DBOARD_ROOT=<board-root>`` both absolute and relative paths can be used. Relative paths are treated relatively to the application directory. SOC Definitions =============== Similar to board support, the structure is similar to how SOCs are maintained in the Zephyr tree, for example: .. code-block:: none soc st stm32 common stm32l0x The file :zephyr_file:`soc/Kconfig` will create the top-level ``SoC/CPU/Configuration Selection`` menu in Kconfig. Out of tree SoC definitions can be added to this menu using the ``SOC_ROOT`` CMake variable. This variable contains a semicolon-separated list of directories which contain SoC support files. Following the structure above, the following files can be added to load more SoCs into the menu. .. code-block:: none soc st stm32 stm32l0x Kconfig Kconfig.soc Kconfig.defconfig The Kconfig files above may describe the SoC or load additional SoC Kconfig files. An example of loading ``stm31l0`` specific Kconfig files in this structure: .. code-block:: none soc st stm32 Kconfig.soc stm32l0x Kconfig.soc can be done with the following content in ``st/stm32/Kconfig.soc``: .. code-block:: kconfig rsource "/Kconfig.soc" Once the SOC structure is in place, you can build your application targeting this platform by specifying the location of your custom platform information with the ``-DSOC_ROOT`` parameter to the CMake build system: .. zephyr-app-commands:: :tool: all :board: <board name> :gen-args: -DSOC_ROOT=<path to soc> -DBOARD_ROOT=<path to boards> :goals: build :compact: This will use your custom platform configurations and will generate the Zephyr binary into your application directory. See :ref:`modules_build_settings` for information on setting SOC_ROOT in a module's :file:`zephyr/module.yml` file. Or you can define the ``SOC_ROOT`` variable in the application :file:`CMakeLists.txt` file. Make sure to do so before* pulling in the Zephyr boilerplate with ``find_package(Zephyr ...)``. .. note:: When specifying ``SOC_ROOT`` in a CMakeLists.txt, then an absolute path must be provided, for example ``list(APPEND SOC_ROOT ${CMAKE_CURRENT_SOURCE_DIR}/<extra-soc-root>``. When using ``-DSOC_ROOT=<soc-root>`` both absolute and relative paths can be used. Relative paths are treated relatively to the application directory. .. _dts_root: Devicetree Definitions ====================== Devicetree directory trees are found in ``APPLICATION_SOURCE_DIR``, ``BOARD_DIR``, and ``ZEPHYR_BASE``, but additional trees, or DTS_ROOTs, can be added by creating this directory tree:: include/ dts/common/ dts/arm/ dts/ dts/bindings/ Where 'arm' is changed to the appropriate architecture. Each directory is optional. The binding directory contains bindings and the other directories contain files that can be included from DT sources. Once the directory structure is in place, you can use it by specifying its location through the ``DTS_ROOT`` CMake Cache variable: .. zephyr-app-commands:: :tool: all :board: <board name> :gen-args: -DDTS_ROOT=<path to dts root> :goals: build :compact: You can also define the variable in the application :file:`CMakeLists.txt` file. Make sure to do so before pulling in the Zephyr boilerplate with ``find_package(Zephyr ...)``. .. note:: When specifying ``DTS_ROOT`` in a CMakeLists.txt, then an absolute path must be provided, for example ``list(APPEND DTS_ROOT ${CMAKE_CURRENT_SOURCE_DIR}/<extra-dts-root>``. When using ``-DDTS_ROOT=<dts-root>`` both absolute and relative paths can be used. Relative paths are treated relatively to the application directory. Devicetree source are passed through the C preprocessor, so you can include files that can be located in a ``DTS_ROOT`` directory. By convention devicetree include files have a ``.dtsi`` extension. You can also use the preprocessor to control the content of a devicetree file, by specifying directives through the ``DTS_EXTRA_CPPFLAGS`` CMake Cache variable: .. zephyr-app-commands:: :tool: all :board: <board name> :gen-args: -DDTS_EXTRA_CPPFLAGS=-DTEST_ENABLE_FEATURE :goals: build :compact: .. _CMake: path_to_url .. _CMake introduction: path_to_url#description .. _CMake list: path_to_url#lists .. _example-application: path_to_url ```	/content/code_sandbox/doc/develop/application/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	10,883
```restructuredtext .. _flashing_and_debugging: Flashing and Hardware Debugging ############################### .. toctree:: :maxdepth: 1 host-tools.rst probes.rst ```	/content/code_sandbox/doc/develop/flash_debug/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	42
```restructuredtext .. _debug-probes: Debug Probes ############ A debug probe is special hardware which allows you to control execution of a Zephyr application running on a separate board. Debug probes usually allow reading and writing registers and memory, and support breakpoint debugging of the Zephyr application on your host workstation using tools like GDB. They may also support other debug software and more advanced features such as :ref:`tracing program execution <tracing>`. For details on the related host software supported by Zephyr, see :ref:`flash-debug-host-tools`. Debug probes are usually connected to your host workstation via USB; they are sometimes also accessible via an IP network or other means. They usually connect to the device running Zephyr using the JTAG or SWD protocols. Debug probes are either separate hardware devices or circuitry integrated into the same board which runs Zephyr. Many supported boards in Zephyr include a second microcontroller that serves as an onboard debug probe, usb-to-serial adapter, and sometimes a drag-and-drop flash programmer. This eliminates the need to purchase an external debug probe and provides a variety of debug host tool options. Several hardware vendors have their own branded onboard debug probe implementations: NXP boards may use `OpenSDA <#opensda-onboard-debug-probe>`_, `LPC-Link2 <#lpc-link2-onboard-debug-probe>`_, or `MCU-Link <#mcu-link-onboard-debug-probe>`_, probes depending on the microcontroller the debug probe firmware runs on. ST boards have the `ST-LINK probe <#stlink-v21-onboard-debug-probe>`_. Each onboard debug probe microcontroller can support one or more types of firmware that communicate with their respective debug host tools. For example, an OpenSDA microcontroller can be programmed with DAPLink firmware to communicate with pyOCD or OpenOCD debug host tools, or with J-Link firmware to communicate with J-Link debug host tools. +------------------------------------------+your_sha256_hash-----------------------------------------+ \|\| Debug Probes & Host Tools \| Host Tools \| +\| Compatibility Chart +--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| J-Link Debug \| OpenOCD \| pyOCD \| NXP S32DS \| NXP LinkServer \| +----------------+-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| J-Link External \| \| \| \| \| \| \| +-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| LPC-Link2 CMSIS-DAP \| \| \| \| \| \| \| +-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| LPC-Link2 J-Link \| \| \| \| \| \| \| +-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| MCU-Link CMSIS-DAP \| \| \| \| \| \| \| Debug Probes +-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| MCU-Link J-Link \| \| \| \| \| \| \| +-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| NXP S32 Debug Probe \| \| \| \| \| \| \| +-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| OpenSDA DAPLink \| \| \| \| \| \| \| +-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| OpenSDA J-Link \| \| \| \| \| \| \| +-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ \| \| ST-LINK/V2-1 \| \| \| some STM32 boards \| \| \| +----------------+-------------------------+--------------------+--------------------+---------------------+--------------------+--------------------+ Some supported boards in Zephyr do not include an onboard debug probe and therefore require an external debug probe. In addition, boards that do include an onboard debug probe often also have an SWD or JTAG header to enable the use of an external debug probe instead. One reason this may be useful is that the onboard debug probe may have limitations, such as lack of support for advanced debuggers or high-speed tracing. You may need to adjust jumpers to prevent the onboard debug probe from interfering with the external debug probe. .. _nxp-onboard-debug-probes: NXP Onboard Debug Probes ********************** NXP boards may have one of several onboard debug probes. These probes include the :ref:`mcu-link-onboard-debug-probe`, :ref:`lpc-link2-onboard-debug-probe` and :ref:`opensda-onboard-debug-probe`. Each of these probes is implemented as a secondary microcontroller present on the evaluation board. The specific debug probe type present on a given board can be determined based on the debug microcontroller SOC: - LPC55S69: :ref:`mcu-link-onboard-debug-probe` - LPC4322: :ref:`lpc-link2-onboard-debug-probe` - MK20: :ref:`opensda-onboard-debug-probe` For example, the :ref:`frdm_k64f` board has an MK20 debug microcontroller, so this board uses the :ref:`opensda-onboard-debug-probe`. .. _mcu-link-onboard-debug-probe: MCU-Link Onboard Debug Probe ************************ The MCU-Link onboard debug probe uses an LPC55S69 SOC. This probe supports the following firmwares: - :ref:`mcu-link-cmsis-onboard-debug-probe` (default firmware) - :ref:`mcu-link-jlink-onboard-debug-probe` This probe is programmed using the MCU-Link host tools, which are installed with the :ref:`linkserver-debug-host-tools`. NXP recommends using NXP's `MCUXpresso Installer`_ to install the Linkserver tools. .. _mcu-link-cmsis-onboard-debug-probe: MCU-Link CMSIS-DAP Onboard Debug Probe ====================================== This is the default firmware installed on MCU-Link debug probes. The CMSIS-DAP debug probes allow debugging from any compatible toolchain, including IAR EWARM, Keil MDK, NXPs MCUXpresso IDE and MCUXpresso extension for VS Code. In addition to debug probe functionality, the MCU-Link probes may also provide: 1. SWO trace end point: this virtual device is used by MCUXpresso to retrieve SWO trace data. See the MCUXpresso IDE documentation for more information. #. Virtual COM (VCOM) port / UART bridge connected to the target processor #. USB to UART, SPI and/or I2C interfaces (depending on MCU-Link type/implementation) #. Energy measurements of the target MCU This debug probe is compatible with the following debug host tools: - :ref:`linkserver-debug-host-tools` Once the MCU-Link host tools are installed, the following steps are required to program the CMSIS-DAP firmware: 1. Make sure the MCU-Link utility is present on your host machine. This can be done by installing :ref:`linkserver-debug-host-tools`. #. Put the MCU-Link microcontroller into DFU boot mode by attaching the DFU jumper then connecting to the USB debug port on the board. This jumper may also be referred to as the ISP jumper, and will be connected to ``PIO0_5`` on the LPC55S69. #. Run the ``program_CMSIS`` script, found in the installed MCU-Link ``scripts`` folder. #. Remove the DFU jumper and power cycle the board. .. _mcu-link-jlink-onboard-debug-probe: MCU-Link JLink Onboard Debug Probe ================================== This debug probe firmware provides a JLink compatible debug interface, as well as a USB-Serial adapter. It is compatible with the following debug host tools: - :ref:`jlink-debug-host-tools` These probes do not have JLink firmware installed by default, and must be updated. Once the MCU-Link host tools are installed, the following steps are required to program the JLink firmware: 1. Make sure the MCU-Link utility is present on your host machine. This can be done by installing :ref:`linkserver-debug-host-tools`. #. Put the MCU-Link microcontroller into DFU boot mode by attaching the DFU jumper then connecting to the USB debug port on the board. This jumper may also be referred to as the ISP jumper, and will be connected to ``PIO0_5`` on the LPC55S69. #. Run the ``program_JLINK`` script, found in the installed MCU-Link ``scripts`` folder. #. Remove the DFU jumper and power cycle the board. .. _lpc-link2-onboard-debug-probe: LPC-LINK2 Onboard Debug Probe ************************* The LPC-LINK2 onboard debug probe uses an LPC4322 SOC. This probe supports the following firmwares: - :ref:`lpclink2-cmsis-onboard-debug-probe` - :ref:`lpclink2-jlink-onboard-debug-probe` - :ref:`lpclink2-daplink-onboard-debug-probe` (default firmware) This probe is programmed using the LPCScrypt host tools, which are installed with the :ref:`linkserver-debug-host-tools`. NXP recommends using NXP's `MCUXpresso Installer`_ to install the Linkserver tools. .. _lpclink2-cmsis-onboard-debug-probe: LPC-LINK2 CMSIS DAP Onboard Debug Probe ======================================= The CMSIS-DAP debug probes allow debugging from any compatible toolchain, including IAR EWARM, Keil MDK, as well as NXPs MCUXpresso IDE and MCUXpresso extension for VS Code. As well as providing debug probe functionality, the LPC-Link2 probes also provide: 1. SWO trace end point: this virtual device is used by MCUXpresso to retrieve SWO trace data. See the MCUXpresso IDE documentation for more information. 2. Virtual COM (VCOM) port / UART bridge connected to the target processor 3. LPCSIO bridge that provides communication to I2C and SPI slave devices This debug probe firmware is compatible with the following debug host tools: - :ref:`linkserver-debug-host-tools` The probe may be updated to use CMSIS-DAP firmware with the following steps: 1. Make sure the LPCScrypt utility is present on your host machine. This can be done by installing :ref:`linkserver-debug-host-tools`. #. Put the LPC-Link2 microcontroller into DFU boot mode by attaching the DFU jumper, then connecting to the USB debug port on the board. This jumper is connected to ``P2_6`` on the LPC4322 SOC. #. Run the ``program_CMSIS`` script, found in the installed LPCScrypt ``scripts`` folder. #. Remove the DFU jumper and power cycle the board. .. _lpclink2-jlink-onboard-debug-probe: LPC-Link2 J-Link Onboard Debug Probe ==================================== .. note:: On some boards, the J-Link probe firmware will no longer power the board via the USB debug port. On these boards, an alternative method of powering the board must be used when this firmware is programmed. This debug probe firmware provides a JLink compatible debug interface, as well as a USB-Serial adapter. It is compatible with the following debug host tools: - :ref:`jlink-debug-host-tools` The probe may be updated to use the J-Link firmware with the following steps: .. note:: Verify the firmware supports your board by visiting `Firmware for LPCXpresso`_ 1. Make sure the LPCScrypt utility is present on your host machine. This can be done by installing :ref:`linkserver-debug-host-tools`. #. Put the LPC-Link2 microcontroller into DFU boot mode by attaching the DFU jumper, then connecting to the USB debug port on the board. This jumper is connected to ``P2_6`` on the LPC4322 SOC. #. Run the ``program_JLINK`` script, found in the installed LPCScrypt ``scripts`` folder. #. Remove the DFU jumper and power cycle the board. .. _lpclink2-daplink-onboard-debug-probe: LPC-Link2 DAPLink Onboard Debug Probe ===================================== The LPC-Link2 DAPLink firmware is the default firmware shipped on LPC-Link2 based boards, but is not the recommended firmware. Users should update to the :ref:`lpclink2-cmsis-onboard-debug-probe` firmware following the instructions provided above. For details on programming the DAPLink firmware, see `NXP AN13206`_. .. _opensda-onboard-debug-probe: OpenSDA Onboard Debug Probe *********************** The OpenSDA onboard debug probe is based on the NXP MK20 SOC. It features drag and drop programming supports, and supports the following debug firmwares: - :ref:`opensda-daplink-onboard-debug-probe` (default firmware) - :ref:`opensda-jlink-onboard-debug-probe` .. _opensda-daplink-onboard-debug-probe: OpenSDA DAPLink Onboard Debug Probe =================================== This debug probe firmware is compatible with the following debug host tools: - :ref:`pyocd-debug-host-tools` - :ref:`openocd-debug-host-tools` - :ref:`linkserver-debug-host-tools` This probe is realized by programming the OpenSDA microcontroller with DAPLink OpenSDA firmware. NXP provides `OpenSDA DAPLink Board-Specific Firmwares`_. Install the debug host tools before you program the firmware. As with all OpenSDA debug probes, the steps for programming the firmware are: 1. Put the OpenSDA microcontroller into bootloader mode by holding the reset button while you power on the board. Note that "bootloader mode" in this context applies to the OpenSDA microcontroller itself, not the target microcontroller of your Zephyr application. #. After you power on the board, release the reset button. A USB mass storage device called BOOTLOADER or MAINTENANCE will enumerate. If the enumerated device is named BOOTLOADER, please first update the bootloader to the latest revision by following the instructions for a `DAPLink Bootloader Update`_. #. Copy the OpenSDA firmware binary to the USB mass storage device. #. Power cycle the board, this time without holding the reset button. You should see three USB devices enumerate: a CDC device (serial port), a HID device (debug port), and a mass storage device (drag-and-drop flash programming). .. _opensda-jlink-onboard-debug-probe: OpenSDA J-Link Onboard Debug Probe ================================== This debug probe is compatible with the following debug host tools: - :ref:`jlink-debug-host-tools` This probe is realized by programming the OpenSDA microcontroller with J-Link OpenSDA firmware. Segger provides `OpenSDA J-Link Generic Firmwares`_ and `OpenSDA J-Link Board-Specific Firmwares`_, where the latter is generally recommended when available. Board-specific firmwares are required for i.MX RT boards to support their external flash memories, whereas generic firmwares are compatible with all Kinetis boards. Install the debug host tools before you program the firmware. As with all OpenSDA debug probes, the steps for programming the firmware are: 1. Put the OpenSDA microcontroller into bootloader mode by holding the reset button while you plug a USB into the board's USB debug port. Note that "bootloader mode" in this context applies to the OpenSDA microcontroller itself, not the target microcontroller of your Zephyr application. #. After you power on the board, release the reset button. A USB mass storage device called BOOTLOADER or MAINTENANCE will enumerate. If the enumerated device is named BOOTLOADER, please first update the bootloader to the latest revision by following the instructions for a `DAPLink Bootloader Update`_. #. Copy the OpenSDA firmware binary to the USB mass storage device. #. Power cycle the board, this time without holding the reset button. You should see two USB devices enumerate: a CDC device (serial port) and a vendor-specific device (debug port). .. _jlink-external-debug-probe: J-Link External Debug Probe *********************** `Segger J-Link`_ is a family of external debug probes, including J-Link EDU, J-Link PLUS, J-Link ULTRA+, and J-Link PRO, that support a large number of devices from different hardware architectures and vendors. This debug probe is compatible with the following debug host tools: - :ref:`jlink-debug-host-tools` - :ref:`openocd-debug-host-tools` Install the debug host tools before you program the firmware. .. _stlink-v21-onboard-debug-probe: ST-LINK/V2-1 Onboard Debug Probe **************************** ST-LINK/V2-1 is a serial and debug adapter built into all Nucleo and Discovery boards. It provides a bridge between your computer (or other USB host) and the embedded target processor, which can be used for debugging, flash programming, and serial communication, all over a simple USB cable. It is compatible with the following host debug tools: - :ref:`openocd-debug-host-tools` - :ref:`jlink-debug-host-tools` For some STM32 based boards, it is also compatible with: - :ref:`pyocd-debug-host-tools` While it works out of the box with OpenOCD, it requires some flashing to work with J-Link. To do this, SEGGER offers a firmware upgrading the ST-LINK/V2-1 on board on the Nucleo and Discovery boards. This firmware makes the ST-LINK/V2-1 compatible with J-LinkOB, allowing users to take advantage of most J-Link features like the ultra fast flash download and debugging speed or the free-to-use GDBServer. More information about upgrading ST-LINK/V2-1 to JLink or restore ST-Link/V2-1 firmware please visit: `Segger over ST-Link`_ Flash and debug with ST-Link ============================ .. tabs:: .. tab:: Using OpenOCD OpenOCD is available by default on ST-Link and configured as the default flash and debug tool. Flash and debug can be done as follows: .. zephyr-app-commands:: :zephyr-app: samples/hello_world :goals: flash .. zephyr-app-commands:: :zephyr-app: samples/hello_world :goals: debug .. tab:: _`Using Segger J-Link` Once STLink is flashed with SEGGER FW and J-Link GDB server is installed on your host computer, you can flash and debug as follows: Use CMake with ``-DBOARD_FLASH_RUNNER=jlink`` to change the default OpenOCD runner to J-Link. Alternatively, you might add the following line to your application ``CMakeList.txt`` file. .. code-block:: cmake set(BOARD_FLASH_RUNNER jlink) If you use West (Zephyr's meta-tool) you can modify the default runner using the ``--runner`` (or ``-r``) option. .. code-block:: console west flash --runner jlink To attach a debugger to your board and open up a debug console with ``jlink``. .. code-block:: console west debug --runner jlink For more information about West and available options, see :ref:`west`. If you configured your Zephyr application to use `Segger RTT`_ console instead, open telnet: .. code-block:: console $ telnet localhost 19021 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. SEGGER J-Link V6.30f - Real time terminal output J-Link STLink V21 compiled Jun 26 2017 10:35:16 V1.0, SN=773895351 Process: JLinkGDBServerCLExe Zephyr Shell, Zephyr version: 1.12.99 Type 'help' for a list of available commands shell> If you get no RTT output you might need to disable other consoles which conflict with the RTT one if they are enabled by default in the particular sample or application you are running, such as disable UART_CONSOLE in menuconfig Updating or restoring ST-Link firmware ====================================== ST-Link firmware can be updated using `STM32CubeProgrammer Tool`_. It is usually useful when facing flashing issues, for instance when using twister's device-testing option. Once installed, you can update attached board ST-Link firmware with the following command .. code-block:: console s java -jar ~/your_sha512_hash.jar -sn <board_uid> Where board_uid can be obtained using twister's generate-hardware-map option. For more information about twister and available options, see :ref:`twister_script`. .. _nxp-s32-debug-probe: NXP S32 Debug Probe ***************** `NXP S32 Debug Probe`_ enables NXP S32 target system debugging via a standard debug port while connected to a developer's workstation via USB or remotely via Ethernet. NXP S32 Debug Probe is designed to work in conjunction with NXP S32 Design Studio (S32DS) and NXP Automotive microcontrollers and processors. Install the debug host tools as in indicated in :ref:`nxp-s32-debug-host-tools` before you program the firmware. .. _LPCScrypt: path_to_url .. _Firmware for LPCXpresso: path_to_url .. _OpenSDA DAPLink Board-Specific Firmwares: path_to_url .. _OpenSDA J-Link Generic Firmwares: path_to_url#JLinkOpenSDAGenericFirmwares .. _OpenSDA J-Link Board-Specific Firmwares: path_to_url#JLinkOpenSDABoardSpecificFirmwares .. _Segger J-Link: path_to_url .. _Segger over ST-Link: path_to_url .. _Segger RTT: path_to_url .. _STM32CubeProgrammer Tool: path_to_url .. _MCUXpresso Installer: path_to_url .. _NXP S32 Debug Probe: path_to_url .. _NXP AN13206: path_to_url .. _DAPLink Bootloader Update: path_to_url ```	/content/code_sandbox/doc/develop/flash_debug/probes.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	5,071
```restructuredtext .. _flash-debug-host-tools: Flash & Debug Host Tools ######################## This guide describes the software tools you can run on your host workstation to flash and debug Zephyr applications. Zephyr's west tool has built-in support for all of these in its ``flash``, ``debug``, ``debugserver``, and ``attach`` commands, provided your board hardware supports them and your Zephyr board directory's :file:`board.cmake` file declares that support properly. See :ref:`west-build-flash-debug` for more information on these commands. .. _atmel_sam_ba_bootloader: SAM Boot Assistant (SAM-BA) *************************** Atmel SAM Boot Assistant (Atmel SAM-BA) allows In-System Programming (ISP) from USB or UART host without any external programming interface. Zephyr allows users to develop and program boards with SAM-BA support using :ref:`west <west-flashing>`. Zephyr supports devices with/without ROM bootloader and both extensions from Arduino and Adafruit. Full support was introduced in Zephyr SDK 0.12.0. The typical command to flash the board is: .. code-block:: console west flash [ -r bossac ] [ -p /dev/ttyX ] Flash configuration for devices: .. tabs:: .. tab:: With ROM bootloader These devices don't need any special configuration. After building your application, just run ``west flash`` to flash the board. .. tab:: Without ROM bootloader For these devices, the user should: 1. Define flash partitions required to accommodate the bootloader and application image; see :ref:`flash_map_api` for details. 2. Have board :file:`.defconfig` file with the :kconfig:option:`CONFIG_USE_DT_CODE_PARTITION` Kconfig option set to ``y`` to instruct the build system to use these partitions for code relocation. This option can also be set in ``prj.conf`` or any other Kconfig fragment. 3. Build and flash the SAM-BA bootloader on the device. .. tab:: With compatible SAM-BA bootloader For these devices, the user should: 1. Define flash partitions required to accommodate the bootloader and application image; see :ref:`flash_map_api` for details. 2. Have board :file:`.defconfig` file with the :kconfig:option:`CONFIG_BOOTLOADER_BOSSA` Kconfig option set to ``y``. This will automatically select the :kconfig:option:`CONFIG_USE_DT_CODE_PARTITION` Kconfig option which instruct the build system to use these partitions for code relocation. The board :file:`.defconfig` file should have :kconfig:option:`CONFIG_BOOTLOADER_BOSSA_ARDUINO` , :kconfig:option:`CONFIG_BOOTLOADER_BOSSA_ADAFRUIT_UF2` or the :kconfig:option:`CONFIG_BOOTLOADER_BOSSA_LEGACY` Kconfig option set to ``y`` to select the right compatible SAM-BA bootloader mode. These options can also be set in ``prj.conf`` or any other Kconfig fragment. 3. Build and flash the SAM-BA bootloader on the device. .. note:: The :kconfig:option:`CONFIG_BOOTLOADER_BOSSA_LEGACY` Kconfig option should be used as last resource. Try configure first with Devices without ROM bootloader. Typical flash layout and configuration -------------------------------------- For bootloaders that reside on flash, the devicetree partition layout is mandatory. For devices that have a ROM bootloader, they are mandatory when the application uses a storage or other non-application partition. In this special case, the boot partition should be omitted and code_partition should start from offset 0. It is necessary to define the partitions with sizes that avoid overlaps, always. A typical flash layout for devices without a ROM bootloader is: .. code-block:: devicetree / { chosen { zephyr,code-partition = &code_partition; }; }; &flash0 { partitions { compatible = "fixed-partitions"; #address-cells = <1>; #size-cells = <1>; boot_partition: partition@0 { label = "sam-ba"; reg = <0x00000000 0x2000>; read-only; }; code_partition: partition@2000 { label = "code"; reg = <0x2000 0x3a000>; read-only; }; /* * The final 16 KiB is reserved for the application. * Storage partition will be used by FCB/LittleFS/NVS * if enabled. / storage_partition: partition@3c000 { label = "storage"; reg = <0x0003c000 0x00004000>; }; }; }; A typical flash layout for devices with a ROM bootloader and storage partition is: .. code-block:: devicetree / { chosen { zephyr,code-partition = &code_partition; }; }; &flash0 { partitions { compatible = "fixed-partitions"; #address-cells = <1>; #size-cells = <1>; code_partition: partition@0 { label = "code"; reg = <0x0 0xF0000>; read-only; }; / * The final 64 KiB is reserved for the application. * Storage partition will be used by FCB/LittleFS/NVS * if enabled. / storage_partition: partition@F0000 { label = "storage"; reg = <0x000F0000 0x00100000>; }; }; }; Enabling SAM-BA runner ---------------------- In order to instruct Zephyr west tool to use the SAM-BA bootloader the :file:`board.cmake` file must have ``include(${ZEPHYR_BASE}/boards/common/bossac.board.cmake)`` entry. Note that Zephyr tool accept more entries to define multiple runners. By default, the first one will be selected when using ``west flash`` command. The remaining options are available passing the runner option, for instance ``west flash -r bossac``. More implementation details can be found in the :ref:`boards` documentation. As a quick reference, see these three board documentation pages: - :ref:`sam4e_xpro` (ROM bootloader) - :ref:`adafruit_feather_m0_basic_proto` (Adafruit UF2 bootloader) - :ref:`arduino_nano_33_iot` (Arduino bootloader) - :ref:`arduino_nano_33_ble` (Arduino legacy bootloader) Enabling BOSSAC on Windows Native [Experimental] ------------------------------------------------ Zephyr SDKs bossac is currently supported on Linux and macOS only. Windows support can be achieved by using the bossac version from `BOSSA official releases`_. After installing using default options, the :file:`bossac.exe` must be added to Windows PATH. A specific bossac executable can be used by passing the ``--bossac`` option, as follows: .. code-block:: console west flash -r bossac --bossac="C:\Program Files (x86)\BOSSA\bossac.exe" --bossac-port="COMx" .. note:: WSL is not currently supported. .. _linkserver-debug-host-tools: LinkServer Debug Host Tools ************************* Linkserver is a utility for launching and managing GDB servers for NXP debug probes, which also provides a command-line target flash programming capabilities. Linkserver can be used with the `NXP MCUXpresso for Visual Studio Code`_ implementation, with custom debug configurations based on GNU tools or as part of a headless solution for continuous integration and test. LinkServer can be used with MCU-Link, LPC-Link2, LPC11U35-based and OpenSDA based standalone or on-board debug probes from NXP. NXP recommends installing LinkServer by using NXP's `MCUXpresso Installer`_. This method will also install the tools supporting the debug probes below, including NXP's MCU-Link and LPCScrypt tools. LinkServer is compatible with the following debug probes: - :ref:`lpclink2-cmsis-onboard-debug-probe` - :ref:`mcu-link-cmsis-onboard-debug-probe` - :ref:`opensda-daplink-onboard-debug-probe` To use LinkServer with West commands, the install folder should be added to the :envvar:`PATH` :ref:`environment variable <env_vars>`. The default installation path to add is: .. tabs:: .. group-tab:: Linux .. code-block:: console /usr/local/LinkServer .. group-tab:: Windows .. code-block:: console c:\nxp\LinkServer_<version> Supported west commands: 1. flash #. debug #. debugserver #. attach Notes: 1. Probes can be listed with LinkServer: .. code-block:: console LinkServer probes 2. With multiple debug probes attached to the host, use the LinkServer west runner ``--probe`` option to pass the probe index. .. code-block:: console west flash --runner=linkserver --probe=3 3. Device-specific settings can be overridden with the west runner for LinkServer with the option '--override'. May be used multiple times. The format is dictated by LinkServer, e.g.: .. code-block:: console west flash --runner=linkserver --override /device/memory/5/flash-driver=MIMXRT500_SFDP_MXIC_OSPI_S.cfx 4. LinkServer does not install an implicit breakpoint at the reset handler. If you would like to single step from the start of their application, you will need to add a breakpoint at ``main`` or the reset handler manually. .. _jlink-debug-host-tools: J-Link Debug Host Tools ******************* Segger provides a suite of debug host tools for Linux, macOS, and Windows operating systems: - J-Link GDB Server: GDB remote debugging - J-Link Commander: Command-line control and flash programming - RTT Viewer: RTT terminal input and output - SystemView: Real-time event visualization and recording These debug host tools are compatible with the following debug probes: - :ref:`lpclink2-jlink-onboard-debug-probe` - :ref:`opensda-jlink-onboard-debug-probe` - :ref:`mcu-link-jlink-onboard-debug-probe` - :ref:`jlink-external-debug-probe` - :ref:`stlink-v21-onboard-debug-probe` Check if your SoC is listed in `J-Link Supported Devices`_. Download and install the `J-Link Software and Documentation Pack`_ to get the J-Link GDB Server and Commander, and to install the associated USB device drivers. RTT Viewer and SystemView can be downloaded separately, but are not required. Note that the J-Link GDB server does not yet support Zephyr RTOS-awareness. .. _openocd-debug-host-tools: OpenOCD Debug Host Tools ******************** OpenOCD is a community open source project that provides GDB remote debugging and flash programming support for a wide range of SoCs. A fork that adds Zephyr RTOS-awareness is included in the Zephyr SDK; otherwise see `Getting OpenOCD`_ for options to download OpenOCD from official repositories. These debug host tools are compatible with the following debug probes: - :ref:`opensda-daplink-onboard-debug-probe` - :ref:`jlink-external-debug-probe` - :ref:`stlink-v21-onboard-debug-probe` Check if your SoC is listed in `OpenOCD Supported Devices`_. .. note:: On Linux, openocd is available though the `Zephyr SDK <path_to_url`_. Windows users should use the following steps to install openocd: - Download openocd for Windows from here: `OpenOCD Windows`_ - Copy bin and share dirs to ``C:\Program Files\OpenOCD\`` - Add ``C:\Program Files\OpenOCD\bin`` to 'PATH' environment variable .. _pyocd-debug-host-tools: pyOCD Debug Host Tools ****************** pyOCD is an open source project from Arm that provides GDB remote debugging and flash programming support for Arm Cortex-M SoCs. It is distributed on PyPi and installed when you complete the :ref:`gs_python_deps` step in the Getting Started Guide. pyOCD includes support for Zephyr RTOS-awareness. These debug host tools are compatible with the following debug probes: - :ref:`lpclink2-cmsis-onboard-debug-probe` - :ref:`mcu-link-cmsis-onboard-debug-probe` - :ref:`opensda-daplink-onboard-debug-probe` - :ref:`stlink-v21-onboard-debug-probe` Check if your SoC is listed in `pyOCD Supported Devices`_. .. _lauterbach-trace32-debug-host-tools: Lauterbach TRACE32 Debug Host Tools ******************************* `Lauterbach TRACE32`_ is a product line of microprocessor development tools, debuggers and real-time tracer with support for JTAG, SWD, NEXUS or ETM over multiple core architectures, including Arm Cortex-A/-R/-M, RISC-V, Xtensa, etc. Zephyr allows users to develop and program boards with Lauterbach TRACE32 support using :ref:`west <west-flashing>`. The runner consists of a wrapper around TRACE32 software, and allows a Zephyr board to execute a custom start-up script (Practice Script) for the different commands supported, including the ability to pass extra arguments from CMake. Is up to the board using this runner to define the actions performed on each command. Install Lauterbach TRACE32 Software ----------------------------------- Download Lauterbach TRACE32 software from the `Lauterbach TRACE32 download website`_ (registration required) and follow the installation steps described in `Lauterbach TRACE32 Installation Guide`_. Flashing and Debugging ---------------------- Set the :ref:`environment variable <env_vars>` :envvar:`T32_DIR` to the TRACE32 system directory. Then execute ``west flash`` or ``west debug`` commands to flash or debug the Zephyr application as detailed in :ref:`west-build-flash-debug`. The ``debug`` command launches TRACE32 GUI to allow debug the Zephyr application, while the ``flash`` command hides the GUI and perform all operations in the background. By default, the ``t32`` runner will launch TRACE32 using the default configuration file named ``config.t32`` located in the TRACE32 system directory. To use a different configuration file, supply the argument ``--config CONFIG`` to the runner, for example: .. code-block:: console west flash --config myconfig.t32 For more options, run ``west flash --context -r t32`` to print the usage. Zephyr RTOS Awareness --------------------- To enable Zephyr RTOS awareness follow the steps described in `Lauterbach TRACE32 Zephyr OS Awareness Manual`_. .. _nxp-s32-debug-host-tools: NXP S32 Debug Probe Host Tools ************************** :ref:`nxp-s32-debug-probe` is designed to work in conjunction with `NXP S32 Design Studio for S32 Platform`_. Download (registration required) NXP S32 Design Studio for S32 Platform and follow the `S32 Design Studio for S32 Platform Installation User Guide`_ to get the necessary debug host tools and associated USB device drivers. Note that Zephyr RTOS-awareness support for the NXP S32 GDB server depends on the target device. Consult the product release notes for more information. Supported west commands: 1. debug #. debugserver #. attach Basic usage ----------- Before starting, add NXP S32 Design Studio installation directory to the system :ref:`PATH environment variable <env_vars>`. Alternatively, it can be passed to the runner on each invocation via ``--s32ds-path`` as shown below: .. tabs:: .. group-tab:: Linux .. code-block:: console west debug --s32ds-path=/opt/NXP/S32DS.3.5 .. group-tab:: Windows .. code-block:: console west debug --s32ds-path=C:\NXP\S32DS.3.5 If multiple S32 debug probes are connected to the host via USB, the runner will ask the user to select one via command line prompt before continuing. The connection string for the probe can be also specified when invoking the runner via ``--dev-id=<connection-string>``. Consult NXP S32 debug probe user manual for details on how to construct the connection string. For example, if using a probe with serial ID ``00:04:9f:00:ca:fe``: .. code-block:: console west debug --dev-id='s32dbg:00:04:9f:00:ca:fe' It is possible to pass extra options to the debug host tools via ``--tool-opt``. When executing ``debug`` or ``attach`` commands, the tool options will be passed to the GDB client only. When executing ``debugserver``, the tool options will be passed to the GDB server. For example, to load a Zephyr application to SRAM and afterwards detach the debug session: .. code-block:: console west debug --tool-opt='--batch' probe-rs Debug Host Tools *********************** probe-rs is an open-source embedded toolkit written in Rust. It provides out-of-the-box support for a variety of debug probes, including CMSIS-DAP, ST-Link, SEGGER J-Link, FTDI and built-in USB-JTAG interface on ESP32 devices. Check `probe-rs Installation`_ for more setup details. Check if your SoC is listed in `probe-rs Supported Devices`_. .. _J-Link Software and Documentation Pack: path_to_url#J-LinkSoftwareAndDocumentationPack .. _J-Link Supported Devices: path_to_url .. _Getting OpenOCD: path_to_url .. _OpenOCD Supported Devices: path_to_url .. _pyOCD Supported Devices: path_to_url .. _OpenOCD Windows: path_to_url .. _Lauterbach TRACE32: path_to_url .. _Lauterbach TRACE32 download website: path_to_url .. _Lauterbach TRACE32 Installation Guide: path_to_url .. _Lauterbach TRACE32 Zephyr OS Awareness Manual: path_to_url .. _BOSSA official releases: path_to_url .. _NXP MCUXpresso for Visual Studio Code: path_to_url .. _MCUXpresso Installer: path_to_url .. _NXP S32 Design Studio for S32 Platform: path_to_url .. _S32 Design Studio for S32 Platform Installation User Guide: path_to_url .. _probe-rs Installation: path_to_url .. _probe-rs Supported Devices: path_to_url ```	/content/code_sandbox/doc/develop/flash_debug/host-tools.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	4,253
```restructuredtext .. _dev_tools: Tools and IDEs ############## .. toctree:: :maxdepth: 1 clion.rst coccinelle.rst vscode.rst ```	/content/code_sandbox/doc/develop/tools/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	45
```restructuredtext :orphan: .. _nordic_segger: Nordic nRF5x Segger J-Link ########################## Overview ******** All Nordic nRF5x Development Kits, Preview Development Kits and Dongles are equipped with a Debug IC (Atmel ATSAM3U2C) which provides the following functionality: * Segger J-Link firmware and desktop tools * SWD debug for the nRF5x IC * Mass Storage device for drag-and-drop image flashing * USB CDC ACM Serial Port bridged to the nRF5x UART peripheral * Segger RTT Console * Segger Ozone Debugger Segger J-Link Software Installation ********************************* To install the J-Link Software and documentation pack, follow the steps below: #. Download the appropriate package from the `J-Link Software and documentation pack`_ website #. Depending on your platform, install the package or run the installer #. When connecting a J-Link-enabled board such as an nRF5x DK, PDK or dongle, a drive corresponding to a USB Mass Storage device as well as a serial port should come up nRF5x Command-Line Tools Installation ********************************* The nRF5x command-line Tools allow you to control your nRF5x device from the command line, including resetting it, erasing or programming the flash memory and more. To install them, visit `nRF5x Command-Line Tools`_ and select your operating system. After installing, make sure that ``nrfjprog`` is somewhere in your executable path to be able to invoke it from anywhere. .. _nordic_segger_flashing: Flashing ****** To program the flash with a compiled Zephyr image after having followed the instructions to install the Segger J-Link Software and the nRF5x Command-Line Tools, follow the steps below: * Connect the micro-USB cable to the nRF5x board and to your computer * Erase the flash memory in the nRF5x IC: .. code-block:: console nrfjprog --eraseall -f nrf5<x> Where ``<x>`` is either 1 for nRF51-based boards or 2 for nRF52-based boards * Flash the Zephyr image from the sample folder of your choice: .. code-block:: console nrfjprog --program outdir/<board>/zephyr.hex -f nrf5<x> Where: ``<board>`` is the board name you used in the BOARD directive when building (for example nrf52dk/nrf52832) and ``<x>`` is either 1 for nRF51-based boards or 2 for nRF52-based boards * Reset and start Zephyr: .. code-block:: console nrfjprog --reset -f nrf5<x> Where ``<x>`` is either 1 for nRF51-based boards or 2 for nRF52-based boards USB CDC ACM Serial Port Setup *************************** Important note: An issue with Segger J-Link firmware on the nRF5x boards might cause data loss and/or corruption on the USB CDC ACM Serial Port on some machines. To work around this disable the Mass Storage Device on your board as described in :ref:`nordic_segger_msd`. Windows ======= The serial port will appear as ``COMxx``. Simply check the "Ports (COM & LPT)" section in the Device Manager. GNU/Linux ========= The serial port will appear as ``/dev/ttyACMx``. By default the port is not accessible to all users. Type the command below to add your user to the dialout group to give it access to the serial port. Note that re-login is required for this to take effect. .. code-block:: bash sudo usermod -a -G dialout `whoami` Recent versions of `ModemManager send AT commands to TTY-like devices`_; this includes Nordic development kits. This will prevent you from using the serial port for a few seconds, and can make your application misbehave if it reads data from the UART. Before running your application, you might want to temporarily disable ModemManager by running these commands: .. code-block:: bash systemctl stop ModemManager.service systemctl disable ModemManager.service You can also `blacklist Segger devices by editing udev rules`_ so ModemManager ignores them, by running: .. code-block:: bash sudo sh -c 'echo "ATTRS{idVendor}==\"1366\", ENV{ID_MM_DEVICE_IGNORE}=\"1\" " \ >> /etc/udev/rules.d/99-segger-modemmanager-blacklist.rules' sudo service udev restart A fix for this is expected in ModemManager 1.8 and new firmware for the Segger IMCUs. Apple macOS (OS X) ================== The serial port will appear as ``/dev/tty.usbmodemXXXX``. .. _nordic_segger_msd: Disabling the Mass Storage Device functionality ********************************************* Due to a known issue in Segger's J-Link firmware, depending on your operating system and version you might experience data corruption or drops if you use the USB CDC ACM Serial Port with packets larger than 64 bytes. This has been observed on both GNU/Linux and macOS (OS X). To avoid this, you can simply disable the Mass Storage Device by opening: * On GNU/Linux or macOS (OS X) JLinkExe from a terminal * On Microsoft Windows the "JLink Commander" application And then typing the following: .. code-block:: bat MSDDisable And finally unplugging and replugging the board. The Mass Storage Device should not appear anymore and you should now be able to send long packets over the virtual Serial Port. Further information from Segger can be found in the `Segger SAM3U Wiki`_. RTT Console *********** Segger's J-Link supports `Real-Time Tracing (RTT)`_, a technology that allows a terminal connection (both input and output) to be established between the target (nRF5x board) and the development computer for logging and input. Zephyr supports RTT on nRF5x targets, which can be very useful if the UART (through USB CDC ACM) is already being used for a purpose different than logging (such as HCI traffic in the hci_uart application). To use RTT, you will first need to enable it by adding the following lines in your ``.conf`` file: .. code-block:: cfg CONFIG_USE_SEGGER_RTT=y CONFIG_RTT_CONSOLE=y .. warning:: There is also a ``HAS_SEGGER_RTT`` symbol that indicates that the platform supports SEGGER J-Link RTT. This symbol is set automatically by the SoC Kconfig files. Do not confuse it with ``USE_SEGGER_RTT``. ``USE_SEGGER_RTT`` depends on ``HAS_SEGGER_RTT``. If you get no RTT output you might need to disable other consoles which conflict with the RTT one if they are enabled by default in the particular sample or application you are running. For example, to disable the UART console, add this to your ``.conf`` file: .. code-block:: cfg CONFIG_UART_CONSOLE=n Once compiled and flashed with RTT enabled, you will be able to display RTT console messages by doing the following: Windows ======= * Open the "J-Link RTT Viewer" application * Select the following options: * Connection: USB * Target Device: Select your IC from the list * Target Interface and Speed: SWD, 4000 KHz * RTT Control Block: Auto Detection GNU/Linux and macOS (OS X) ========================== * Open ``JLinkRTTLogger`` from a terminal * Select the following options: * Device Name: Use the fully qualified device name for your IC * Target Interface: SWD * Interface Speed: 4000 KHz * RTT Control Block address: auto-detection * RTT Channel name or index: 0 * Output file: filename or ``/dev/stdout`` to display on the terminal directly Python viewer ============= A Python RTT viewer tool can be found in the `pyrtt-viewer`_ GitHub repository. Segger Ozone ************ Segger J-Link is compatible with `Segger Ozone`_, a visual debugger that can be obtained here: * `Segger Ozone Download`_ Once downloaded you can install it and configure it like so: * Target Device: Select your IC from the list * Target Interface: SWD * Target Interface Speed: 4 MHz * Host Interface: USB Once configured, you can then use the File->Open menu to open the ``zephyr.elf`` file that you can find in your build folder. References ********** .. target-notes:: .. _nRF5x Command-Line Tools: path_to_url .. _Segger SAM3U Wiki: path_to_url .. _Real-Time Tracing (RTT): path_to_url .. _pyrtt-viewer: path_to_url .. _Segger Ozone: path_to_url .. _Segger Ozone Download: path_to_url#Ozone .. _ModemManager send AT commands to TTY-like devices: path_to_url .. _blacklist Segger devices by editing udev rules: path_to_url#Device_or_resource_busy_dev_ttyA .. _J-Link Software and documentation pack: path_to_url ```	/content/code_sandbox/doc/develop/flash_debug/nordic_segger.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,053
```restructuredtext .. _vscode_ide: Visual Studio Code ################## `Visual Studio Code`_ (VS Code for short) is a popular cross-platform IDE that supports C projects and has a rich set of extensions. This guide describes the process of setting up VS Code for Zephyr's :zephyr:code-sample:`blinky` sample in VS Code. The instructions have been tested on Linux, but the steps should be the same for macOS and Windows, just make sure to adjust the paths if needed. Get VS Code ********* `Download VS Code`_ and install it. Install the required extensions through the `Extensions` marketplace in the left panel. Search for the `C/C++ Extension Pack`_ and install it. Initialize a new workspace ********************** This guide gives details on how to configure the :zephyr:code-sample:`blinky` sample application, but the instructions would be similar for any Zephyr project and :ref:`workspace layout <west-workspaces>`. Before you start, make sure you have a working Zephyr development environment, as per the instructions in the :ref:`getting_started`. Open the project in VS Code *********************** #. In VS Code, select :menuselection:`File --> Open Folder` from the main menu. #. Navigate to your Zephyr workspace and select it (i.e. the :file:`zephyrproject` folder in your HOME directory if you have followed the Getting Started instructions). #. If prompted, enable workspace trust. Generate compile commands ********************* In order to support code navigation and linting capabilities, you must compile your project once to generate the :file:`compile_commands.json` file that will provide the C/C++ extension with the required information (ex. include paths): .. zephyr-app-commands:: :zephyr-app: samples/basic/blinky :board: native_sim/native/64 :goals: build :compact: Configure the C/C++ extension ************************* You'll now need to point to the generated :file:`compile_commands.json` file to enable linting and code navigation in VS Code. #. Go to the :menuselection:`File --> Preferences --> Settings` in the VS Code top menu. #. Search for the parameter :guilabel:`C_Cpp > Default: Compile Commands` and set its value to: ``zephyr/build/compile_commands.json``. Linting errors in the code should now be resolved, and you should be able to navigate through the code. Additional resources ****************** There are many other extensions that can be useful when working with Zephyr and VS Code. While this guide does not cover them yet, you may refer to their documentation to set them up: Contribution tooling ==================== - `Checkpatch Extension`_ - `EditorConfig Extension`_ Documentation languages extensions ================================== - `reStructuredText Extension Pack`_ IDE extensions ============== - `CMake Extension documentation`_ - `nRF Kconfig Extension`_ - `nRF DeviceTree Extension`_ - `GNU Linker Map files Extension`_ Additional guides ================= - `How to Develop Zephyr Apps with a Modern, Visual IDE`_ .. note:: Please be aware that these extensions might not all have the same level of quality and maintenance. .. _Visual Studio Code: path_to_url .. _Download VS Code: path_to_url .. _VS Code documentation: path_to_url .. _C/C++ Extension Pack: path_to_url .. _C/C++ Extension documentation: path_to_url .. _CMake Extension documentation: path_to_url .. _Checkpatch Extension: path_to_url .. _EditorConfig Extension: path_to_url .. _reStructuredText Extension Pack: path_to_url .. _nRF Kconfig Extension: path_to_url .. _nRF DeviceTree Extension: path_to_url .. _GNU Linker Map files Extension: path_to_url .. _How to Develop Zephyr Apps with a Modern, Visual IDE: path_to_url ```	/content/code_sandbox/doc/develop/tools/vscode.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	856
```restructuredtext .. _clion_ide: CLion ##### CLion_ is a cross-platform C/C++ IDE that supports multi-threaded RTOS debugging. This guide describes the process of setting up, building, and debugging Zephyr's :zephyr:code-sample:`multi-thread-blinky` sample in CLion. The instructions have been tested on Windows. In terms of the CLion workflow, the steps would be the same for macOS and Linux, but make sure to select the correct environment file and to adjust the paths. Get CLion ******* `Download CLion`_ and install it. Initialize a new workspace ********************** This guide gives details on how to build and debug the :zephyr:code-sample:`multi-thread-blinky` sample application, but the instructions would be similar for any Zephyr project and :ref:`workspace layout <west-workspaces>`. Before you start, make sure you have a working Zephyr development environment, as per the instructions in the :ref:`getting_started`. Open the project in CLion ********************** #. In CLion, click :guilabel:`Open` on the Welcome screen or select :menuselection:`File --> Open` from the main menu. #. Navigate to your Zephyr workspace (i.e.the :file:`zephyrproject` folder in your HOME directory if you have followed the Getting Started instructions), then select :file:`zephyr/samples/basic/threads` or another sample project folder. Click :guilabel:`OK`. #. If prompted, click :guilabel:`Trust Project`. See the `Project security`_ section in CLion web help for more information on project security. Configure the toolchain and CMake profile ************************************* CLion will open the :guilabel:`Open Project Wizard` with the CMake profile settings. If that does not happen, go to :menuselection:`Settings --> Build, Execution, Deployment --> CMake`. #. Click :guilabel:`Manage Toolchains` next to the :guilabel:`Toolchain` field. This will open the :guilabel:`Toolchain` settings dialog. #. We recommend that you use the :guilabel:`Bundled MinGW` toolchain with default settings on Windows, or the :guilabel:`System` (default) toolchain on Unix machines. #. Click :menuselection:`Add environment --> From file` and select ``..\.venv\Scripts\activate.bat``. .. figure:: img/clion_toolchain_mingw.webp :width: 600px :align: center :alt: MinGW toolchain with environment script Click :guilabel:`Apply` to save the changes. #. Back in the CMake profile settings dialog, specify your board in the :guilabel:`CMake options` field. For example: .. code-block:: -DBOARD=nrf52840dk/nrf52840 .. figure:: img/clion_cmakeprofile.webp :width: 600px :align: center :alt: CMake profile #. Click :guilabel:`Apply` to save the changes. CMake load should finish successfully. Configure Zephyr parameters for debug ********************************* #. In the configuration switcher on the top right, select :guilabel:`guiconfig` and click the hammer icon. #. Use the GUI application to set the following flags: .. code-block:: DEBUG_THREAD_INFO THREAD_RUNTIME_STATS DEBUG_OPTIMIZATIONS Build the project ************* In the configuration switcher, select zephyr_final and click the hammer icon. Note that other CMake targets like ``puncover`` or ``hardenconfig`` can also be called at this point. Enable RTOS integration ******************* #. Go to :menuselection:`Settings --> Build, Execution, Deployment --> Embedded Development --> RTOS Integration`. #. Set the :guilabel:`Enable RTOS Integration` checkbox. This option enables Zephyr tasks view during debugging. See `Multi-threaded RTOS debug`_ in CLion web help for more information. You can leave the option set to :guilabel:`Auto`. CLion will detect Zephyr automatically. Create an Embedded GDB Server configuration ***************************************** In order to debug a Zephyr application in CLion, you need to create a run/debug configuration out of the Embedded GDB Server template. Instructions below show the case of a Nordic Semiconductor board and a Segger J-Link debug probe. If your setup is different, make sure to adjust the configuration settings accordingly. #. Select :menuselection:`Run --> New Embedded Configuration` from the main menu. #. Configure the settings: .. list-table:: :header-rows: 1 * - Option - Value * - :guilabel:`Name` (optional) - Zephyr-threads * - :guilabel:`GDB Server Type` - Segger JLink * - :guilabel:`Location` - The path to ``JLinkGDBServerCL.exe`` on Windows or the ``JLinkGDBServer`` binary on macOS/Linux. * - :guilabel:`Debugger` - Bundled GDB .. note:: For non-ARM and non-x86 architectures, use a GDB executable from Zephyr SDK. Make sure to pick a version with Python support (for example, riscv64-zephyr-elf-gdb-py) and check that Python is present in the system ``PATH``. * - :guilabel:`Target` - zephyr-final * - :guilabel:`Executable binary` - zephyr-final * - :guilabel:`Download binary` - Always * - :guilabel:`TCP/IP port` - Auto .. figure:: img/clion_gdbserverconfig.webp :width: 500px :align: center :alt: Embedded GDB server configuration #. Click :guilabel:`Next` to set the Segger J-Link parameters. .. figure:: img/clion_segger_settings.webp :width: 500px :align: center :alt: Segger J-Link parameters #. Click :guilabel:`Create` when ready. Start debugging ************* #. Place breakpoints by clicking in the left gutter next to the code lines. #. Make sure that Zephyr-threads** is selected in the configuration switcher and click the bug icon or press :kbd:`Ctrl+D`. #. When a breakpoint is hit, CLion opens the Debug tool window. Zephyr tasks are listed in the :guilabel:`Threads & Variables` pane. You can switch between them and inspect the variables for each task. .. figure:: img/clion_debug_threads.webp :width: 800px :align: center :alt: Viewing Zephyr tasks during a debug session Refer to `CLion web help`_ for detailed description of the IDE debug capabilities. .. _CLion: path_to_url .. _Download CLion: path_to_url .. _Project security: path_to_url#projects_security .. _Multi-threaded RTOS debug: path_to_url .. _CLion web help: path_to_url ```	/content/code_sandbox/doc/develop/tools/clion.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,610
```restructuredtext .. _west-troubleshooting: Troubleshooting West #################### This page covers common issues with west and how to solve them. ``west update`` fetching failures ******************************* One good way to troubleshoot fetching issues is to run ``west update`` in verbose mode, like this: .. code-block:: shell west -v update The output includes Git commands run by west and their outputs. Look for something like this: .. code-block:: none === updating your_project (path/to/your/project): west.manifest: your_project: checking if cloned [...other west.manifest logs...] --- your_project: fetching, need revision SOME_SHA west.manifest: running 'git fetch ... path_to_url ...' in /some/directory The ``git fetch`` command example in the last line above is what needs to succeed. One strategy is to go to ``/path/to/your/project``, copy/paste and run the entire ``git fetch`` command, then debug from there using the documentation for your credential storage helper. If you're behind a corporate firewall and may have proxy or other issues, ``curl -v FETCH_URL`` (for HTTPS URLs) or ``ssh -v FETCH_URL`` (for SSH URLs) may be helpful. If you can get the ``git fetch`` command to run successfully without prompting for a password when you run it directly, you will be able to run ``west update`` without entering your password in that same shell. "'west' is not recognized as an internal or external command, operable program or batch file.' ****************************************************************************************** On Windows, this means that either west is not installed, or your :envvar:`PATH` environment variable does not contain the directory where pip installed :file:`west.exe`. First, make sure you've installed west; see :ref:`west-install`. Then try running ``west`` from a new ``cmd.exe`` window. If that still doesn't work, keep reading. You need to find the directory containing :file:`west.exe`, then add it to your :envvar:`PATH`. (This :envvar:`PATH` change should have been done for you when you installed Python and pip, so ordinarily you should not need to follow these steps.) Run this command in ``cmd.exe``:: pip3 show west Then: #. Look for a line in the output that looks like ``Location: C:\foo\python\python38\lib\site-packages``. The exact location will be different on your computer. #. Look for a file named ``west.exe`` in the ``scripts`` directory ``C:\foo\python\python38\scripts``. .. important:: Notice how ``lib\site-packages`` in the ``pip3 show`` output was changed to ``scripts``! #. If you see ``west.exe`` in the ``scripts`` directory, add the full path to ``scripts`` to your :envvar:`PATH` using a command like this:: setx PATH "%PATH%;C:\foo\python\python38\scripts" Do not just copy/paste this command. The ``scripts`` directory location will be different on your system. #. Close your ``cmd.exe`` window and open a new one. You should be able to run ``west``. "Error: unexpected keyword argument 'requires_workspace'" ***************************************************** This error occurs on some Linux distributions after upgrading to west 0.7.0 or later from 0.6.x. For example: .. code-block:: none $ west update [... stack trace ...] TypeError: __init__() got an unexpected keyword argument 'requires_workspace' This appears to be a problem with the distribution's pip; see `this comment in west issue 373`_ for details. Some versions of Ubuntu and Linux Mint are known to have this problem. Some users report issues on Fedora as well. Neither macOS nor Windows users have reported this issue. There have been no reports of this issue on other Linux distributions, like Arch Linux, either. .. _this comment in west issue 373: path_to_url#issuecomment-583489272 Workaround 1: remove the old version, then upgrade: .. code-block:: none $ pip3 show west \| grep Location: \| cut -f 2 -d ' ' /home/foo/.local/lib/python3.6/site-packages $ rm -r /home/foo/.local/lib/python3.6/site-packages/west $ pip3 install --user west==0.7.0 Workaround 2: install west in a Python virtual environment One option is to use the `venv module`_ that's part of the Python 3 standard library. Some distributions remove this module from their base Python 3 packages, so you may need to do some additional work to get it installed on your system. .. _venv module: path_to_url "invalid choice: 'build'" (or 'flash', etc.) **************************************** If you see an unexpected error like this when trying to run a Zephyr extension command (like :ref:`west flash <west-flashing>`, :ref:`west build <west-building>`, etc.): .. code-block:: none $ west build [...] west: error: argument <command>: invalid choice: 'build' (choose from 'init', [...]) $ west flash [...] west: error: argument <command>: invalid choice: 'flash' (choose from 'init', [...]) The most likely cause is that you're running the command outside of a :ref:`west workspace <west-workspace>`. West needs to know where your workspace is to find :ref:`west-extensions`. To fix this, you have two choices: #. Run the command from inside a workspace (e.g. the :file:`zephyrproject` directory you created when you :ref:`got started <getting_started>`). For example, create your build directory inside the workspace, or run ``west flash --build-dir YOUR_BUILD_DIR`` from inside the workspace. #. Set the :envvar:`ZEPHYR_BASE` :ref:`environment variable <env_vars>` and re-run the west extension command. If set, west will use :envvar:`ZEPHYR_BASE` to find your workspace. If you're unsure whether a command is built-in or an extension, run ``west help`` from inside your workspace. The output prints extension commands separately, and looks like this for mainline Zephyr: .. code-block:: none $ west help built-in commands for managing git repositories: init: create a west workspace [...] other built-in commands: help: get help for west or a command [...] extension commands from project manifest (path: zephyr): build: compile a Zephyr application flash: flash and run a binary on a board [...] "invalid choice: 'post-init'" ************************* If you see this error when running ``west init``: .. code-block:: none west: error: argument <command>: invalid choice: 'post-init' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'config', 'selfupdate', 'help') Then you have an old version of west installed, and are trying to use it in a workspace that requires a more recent version. The easiest way to resolve this issue is to upgrade west and retry as follows: #. Install the latest west with the ``-U`` option for ``pip3 install`` as shown in :ref:`west-install`. #. Back up any contents of :file:`zephyrproject/.west/config` that you want to save. (If you don't have any configuration options set, it's safe to skip this step.) #. Completely remove the :file:`zephyrproject/.west` directory (if you don't, you will get the "already in a workspace" error message discussed next). #. Run ``west init`` again. "already in an installation" ************************** You may see this error when running ``west init`` with west 0.6: .. code-block:: none FATAL ERROR: already in an installation (<some directory>), aborting If this is unexpected and you're really trying to create a new west workspace, then it's likely that west is using the :envvar:`ZEPHYR_BASE` :ref:`environment variable <env_vars>` to locate a workspace elsewhere on your system. This is intentional; it allows you to put your Zephyr applications in any directory and still use west to build, flash, and debug them, for example. To resolve this issue, unset :envvar:`ZEPHYR_BASE` and try again. ```	/content/code_sandbox/doc/develop/west/troubleshooting.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,897
```restructuredtext .. _coccinelle: .. Coccinelle ########## Coccinelle is a tool for pattern matching and text transformation that has many uses in kernel development, including the application of complex, tree-wide patches and detection of problematic programming patterns. .. note:: Linux and macOS development environments are supported, but not Windows. Getting Coccinelle ****************** The semantic patches included in the kernel use features and options which are provided by Coccinelle version 1.0.0-rc11 and above. Using earlier versions will fail as the option names used by the Coccinelle files and ``coccicheck`` have been updated. Coccinelle is available through the package manager of many distributions, e.g. : .. rst-class:: rst-columns * Debian * Fedora * Ubuntu * OpenSUSE * Arch Linux * NetBSD * FreeBSD Some distribution packages are obsolete and it is recommended to use the latest version released from the Coccinelle homepage at path_to_url Or from Github at: path_to_url Once you have it, run the following commands: .. code-block:: console ./autogen ./configure make as a regular user, and install it with: .. code-block:: console sudo make install More detailed installation instructions to build from source can be found at: path_to_url Supplemental documentation ************************ For Semantic Patch Language(SmPL) grammar documentation refer to: path_to_url Using Coccinelle on Zephyr ************************ ``coccicheck`` checker is the front-end to the Coccinelle infrastructure and has various modes: Four basic modes are defined: ``patch``, ``report``, ``context``, and ``org``. The mode to use is specified by setting ``--mode=<mode>`` or ``-m=<mode>``. * ``patch`` proposes a fix, when possible. * ``report`` generates a list in the following format: file:line:column-column: message * ``context`` highlights lines of interest and their context in a diff-like style.Lines of interest are indicated with ``-``. * ``org`` generates a report in the Org mode format of Emacs. Note that not all semantic patches implement all modes. For easy use of Coccinelle, the default mode is ``report``. Two other modes provide some common combinations of these modes. - ``chain`` tries the previous modes in the order above until one succeeds. - ``rep+ctxt`` runs successively the report mode and the context mode. It should be used with the C option (described later) which checks the code on a file basis. Examples ****** To make a report for every semantic patch, run the following command: .. code-block:: console ./scripts/coccicheck --mode=report To produce patches, run: .. code-block:: console ./scripts/coccicheck --mode=patch The ``coccicheck`` target applies every semantic patch available in the sub-directories of ``scripts/coccinelle`` to the entire source code tree. For each semantic patch, a commit message is proposed. It gives a description of the problem being checked by the semantic patch, and includes a reference to Coccinelle. As any static code analyzer, Coccinelle produces false positives. Thus, reports must be carefully checked, and patches reviewed. To enable verbose messages set ``--verbose=1`` option, for example: .. code-block:: console ./scripts/coccicheck --mode=report --verbose=1 Coccinelle parallelization ********************** By default, ``coccicheck`` tries to run as parallel as possible. To change the parallelism, set the ``--jobs=<number>`` option. For example, to run across 4 CPUs: .. code-block:: console ./scripts/coccicheck --mode=report --jobs=4 As of Coccinelle 1.0.2 Coccinelle uses Ocaml parmap for parallelization, if support for this is detected you will benefit from parmap parallelization. When parmap is enabled ``coccicheck`` will enable dynamic load balancing by using ``--chunksize 1`` argument, this ensures we keep feeding threads with work one by one, so that we avoid the situation where most work gets done by only a few threads. With dynamic load balancing, if a thread finishes early we keep feeding it more work. When parmap is enabled, if an error occurs in Coccinelle, this error value is propagated back, the return value of the ``coccicheck`` command captures this return value. Using Coccinelle with a single semantic patch ***************************************** The option ``--cocci`` can be used to check a single semantic patch. In that case, the variable must be initialized with the name of the semantic patch to apply. For instance: .. code-block:: console ./scripts/coccicheck --mode=report --cocci=<example.cocci> or: .. code-block:: console ./scripts/coccicheck --mode=report --cocci=./path/to/<example.cocci> Controlling which files are processed by Coccinelle *********************************************** By default the entire source tree is checked. To apply Coccinelle to a specific directory, pass the path of specific directory as an argument. For example, to check ``drivers/usb/`` one may write: .. code-block:: console ./scripts/coccicheck --mode=patch drivers/usb/ The ``report`` mode is the default. You can select another one with the ``--mode=<mode>`` option explained above. Debugging Coccinelle SmPL patches ***************************** Using ``coccicheck`` is best as it provides in the spatch command line include options matching the options used when we compile the kernel. You can learn what these options are by using verbose option, you could then manually run Coccinelle with debug options added. Alternatively you can debug running Coccinelle against SmPL patches by asking for stderr to be redirected to stderr, by default stderr is redirected to /dev/null, if you'd like to capture stderr you can specify the ``--debug=file.err`` option to ``coccicheck``. For instance: .. code-block:: console rm -f cocci.err ./scripts/coccicheck --mode=patch --debug=cocci.err cat cocci.err Debugging support is only supported when using Coccinelle >= 1.0.2. Additional Flags ************ Additional flags can be passed to spatch through the SPFLAGS variable. This works as Coccinelle respects the last flags given to it when options are in conflict. .. code-block:: console ./scripts/coccicheck --sp-flag="--use-glimpse" Coccinelle supports idutils as well but requires coccinelle >= 1.0.6. When no ID file is specified coccinelle assumes your ID database file is in the file .id-utils.index on the top level of the kernel, coccinelle carries a script scripts/idutils_index.sh which creates the database with: .. code-block:: console mkid -i C --output .id-utils.index If you have another database filename you can also just symlink with this name. .. code-block:: console ./scripts/coccicheck --sp-flag="--use-idutils" Alternatively you can specify the database filename explicitly, for instance: .. code-block:: console ./scripts/coccicheck --sp-flag="--use-idutils /full-path/to/ID" Sometimes coccinelle doesn't recognize or parse complex macro variables due to insufficient definition. Therefore, to make it parsable we explicitly provide the prototype of the complex macro using the ``---macro-file-builtins <headerfile.h>`` flag. The ``<headerfile.h>`` should contain the complete prototype of the complex macro from which spatch engine can extract the type information required during transformation. For example: ``Z_SYSCALL_HANDLER`` is not recognized by coccinelle. Therefore, we put its prototype in a header file, say for example ``mymacros.h``. .. code-block:: console $ cat mymacros.h #define Z_SYSCALL_HANDLER int xxx Now we pass the header file ``mymacros.h`` during transformation: .. code-block:: console ./scripts/coccicheck --sp-flag="---macro-file-builtins mymacros.h" See ``spatch --help`` to learn more about spatch options. Note that the ``--use-glimpse`` and ``--use-idutils`` options require external tools for indexing the code. None of them is thus active by default. However, by indexing the code with one of these tools, and according to the cocci file used, spatch could proceed the entire code base more quickly. SmPL patch specific options *********************** SmPL patches can have their own requirements for options passed to Coccinelle. SmPL patch specific options can be provided by providing them at the top of the SmPL patch, for instance: .. code-block:: console // Options: --no-includes --include-headers Proposing new semantic patches **************************** New semantic patches can be proposed and submitted by kernel developers. For sake of clarity, they should be organized in the sub-directories of ``scripts/coccinelle/``. The cocci script should have the following properties: * The script must have ``report`` mode. * The first few lines should state the purpose of the script using ``///`` comments . Usually, this message would be used as the commit log when proposing a patch based on the script. Example ======= .. code-block:: console /// Use ARRAY_SIZE instead of dividing sizeof array with sizeof an element * A more detailed information about the script with exceptional cases or false positives (if any) can be listed using ``//#`` comments. Example ======= .. code-block:: console //# This makes an effort to find cases where ARRAY_SIZE can be used such as //# where there is a division of sizeof the array by the sizeof its first //# element or by any indexed element or the element type. It replaces the //# division of the two sizeofs by ARRAY_SIZE. * Confidence: It is a property defined to specify the accuracy level of the script. It can be either ``High``, ``Moderate`` or ``Low`` depending upon the number of false positives observed. Example ======= .. code-block:: console // Confidence: High * Virtual rules: These are required to support the various modes framed in the script. The virtual rule specified in the script should have the corresponding mode handling rule. Example ======= .. code-block:: console virtual context @depends on context@ type T; T[] E; @@ ( * (sizeof(E)/sizeof(E)) \| (sizeof(E)/sizeof(E[...])) \| * (sizeof(E)/sizeof(T)) ) Detailed description of the ``report`` mode ******************************************* ``report`` generates a list in the following format: .. code-block:: console file:line:column-column: message Example ======= Running: .. code-block:: console ./scripts/coccicheck --mode=report --cocci=scripts/coccinelle/array_size.cocci will execute the following part of the SmPL script: .. code-block:: console <smpl> @r depends on (org \|\| report)@ type T; T[] E; position p; @@ ( (sizeof(E)@p /sizeof(E)) \| (sizeof(E)@p /sizeof(E[...])) \| (sizeof(E)@p /sizeof(T)) ) @script:python depends on report@ p << r.p; @@ msg="WARNING: Use ARRAY_SIZE" coccilib.report.print_report(p[0], msg) </smpl> This SmPL excerpt generates entries on the standard output, as illustrated below: .. code-block:: console ext/hal/nxp/mcux/drivers/lpc/fsl_wwdt.c:66:49-50: WARNING: Use ARRAY_SIZE ext/hal/nxp/mcux/drivers/lpc/fsl_ctimer.c:74:53-54: WARNING: Use ARRAY_SIZE ext/hal/nxp/mcux/drivers/imx/fsl_dcp.c:944:45-46: WARNING: Use ARRAY_SIZE Detailed description of the ``patch`` mode ***************************************** When the ``patch`` mode is available, it proposes a fix for each problem identified. Example ======= Running: .. code-block:: console ./scripts/coccicheck --mode=patch --cocci=scripts/coccinelle/misc/array_size.cocci will execute the following part of the SmPL script: .. code-block:: console <smpl> @depends on patch@ type T; T[] E; @@ ( - (sizeof(E)/sizeof(E)) + ARRAY_SIZE(E) \| - (sizeof(E)/sizeof(E[...])) + ARRAY_SIZE(E) \| - (sizeof(E)/sizeof(T)) + ARRAY_SIZE(E) ) </smpl> This SmPL excerpt generates patch hunks on the standard output, as illustrated below: .. code-block:: console diff -u -p a/ext/lib/encoding/tinycbor/src/cborvalidation.c b/ext/lib/encoding/tinycbor/src/cborvalidation.c --- a/ext/lib/encoding/tinycbor/src/cborvalidation.c +++ b/ext/lib/encoding/tinycbor/src/cborvalidation.c @@ -325,7 +325,7 @@ static inline CborError validate_number( static inline CborError validate_tag(CborValue it, CborTag tag, int flags, int recursionLeft) { CborType type = cbor_value_get_type(it); - const size_t knownTagCount = sizeof(knownTagData) / sizeof(knownTagData[0]); + const size_t knownTagCount = ARRAY_SIZE(knownTagData); const struct KnownTagData tagData = knownTagData; const struct KnownTagData const knownTagDataEnd = knownTagData + knownTagCount; Detailed description of the ``context`` mode ******************************************** ``context`` highlights lines of interest and their context in a diff-like style. .. note:: The diff-like output generated is NOT an applicable patch. The intent of the ``context`` mode is to highlight the important lines (annotated with minus, ``-``) and gives some surrounding context lines around. This output can be used with the diff mode of Emacs to review the code. Example ======= Running: .. code-block:: console ./scripts/coccicheck --mode=context --cocci=scripts/coccinelle/array_size.cocci will execute the following part of the SmPL script: .. code-block:: console <smpl> @depends on context@ type T; T[] E; @@ ( * (sizeof(E)/sizeof(E)) \| (sizeof(E)/sizeof(E[...])) \| * (sizeof(E)/sizeof(T)) ) </smpl> This SmPL excerpt generates diff hunks on the standard output, as illustrated below: .. code-block:: console diff -u -p ext/lib/encoding/tinycbor/src/cborvalidation.c /tmp/nothing/ext/lib/encoding/tinycbor/src/cborvalidation.c --- ext/lib/encoding/tinycbor/src/cborvalidation.c +++ /tmp/nothing/ext/lib/encoding/tinycbor/src/cborvalidation.c @@ -325,7 +325,6 @@ static inline CborError validate_number( static inline CborError validate_tag(CborValue it, CborTag tag, int flags, int recursionLeft) { CborType type = cbor_value_get_type(it); - const size_t knownTagCount = sizeof(knownTagData) / sizeof(knownTagData[0]); const struct KnownTagData tagData = knownTagData; const struct KnownTagData * const knownTagDataEnd = knownTagData + knownTagCount; Detailed description of the ``org`` mode **************************************** ``org`` generates a report in the Org mode format of Emacs. Example ======= Running: .. code-block:: console ./scripts/coccicheck --mode=org --cocci=scripts/coccinelle/misc/array_size.cocci will execute the following part of the SmPL script: .. code-block:: console <smpl> @r depends on (org \|\| report)@ type T; T[] E; position p; @@ ( (sizeof(E)@p /sizeof(E)) \| (sizeof(E)@p /sizeof(E[...])) \| (sizeof(E)@p /sizeof(T)) ) @script:python depends on org@ p << r.p; @@ coccilib.org.print_todo(p[0], "WARNING should use ARRAY_SIZE") </smpl> This SmPL excerpt generates Org entries on the standard output, as illustrated below: .. code-block:: console TODO [[view:ext/lib/encoding/tinycbor/src/cborvalidation.c::face=ovl-face1::linb=328::colb=52::cole=53][WARNING should use ARRAY_SIZE]] Coccinelle Mailing List *********************** Subscribe to the coccinelle mailing list: * path_to_url Archives: * path_to_url * path_to_url ```	/content/code_sandbox/doc/develop/tools/coccinelle.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	3,879
```restructuredtext .. _west-extensions: Extensions ########## West is "pluggable": you can add your own commands to west without editing its source code. These are called west extension commands, or just "extensions" for short. Extensions show up in the ``west --help`` output in a special section for the project which defines them. This page provides general information on west extension commands, and has a tutorial for writing your own. Some commands you can run when using west with Zephyr, like the ones used to :ref:`build, flash, and debug <west-build-flash-debug>` and the :ref:`ones described here <west-zephyr-ext-cmds>` , are extensions. That's why help for them shows up like this in ``west --help``: .. code-block:: none commands from project at "zephyr": completion: display shell completion scripts boards: display information about supported boards build: compile a Zephyr application sign: sign a Zephyr binary for bootloader chain-loading flash: flash and run a binary on a board debug: flash and interactively debug a Zephyr application debugserver: connect to board and launch a debug server attach: interactively debug a board See :file:`zephyr/scripts/west-commands.yml` and the :file:`zephyr/scripts/west_commands` directory for the implementation details. Disabling Extension Commands ************************** To disable support for extension commands, set the ``commands.allow_extensions`` :ref:`configuration <west-config>` option to ``false``. To set this globally for whenever you run west, use: .. code-block:: console west config --global commands.allow_extensions false If you want to, you can then re-enable them in a particular :term:`west workspace` with: .. code-block:: console west config --local commands.allow_extensions true Note that the files containing extension commands are not imported by west unless the commands are explicitly run. See below for details. Adding a West Extension ********************* There are three steps to adding your own extension: #. Write the code implementing the command. #. Add information about it to a :file:`west-commands.yml` file. #. Make sure the :file:`west-commands.yml` file is referenced in the :term:`west manifest`. Note that west ignores extension commands whose names are the same as a built-in command. Step 1: Implement Your Command ============================== Create a Python file to contain your command implementation (see the "Meta > Requires" information on the `west PyPI page`_ for details on the currently supported versions of Python). You can put it in anywhere in any project tracked by your :term:`west manifest`, or the manifest repository itself. This file must contain a subclass of the ``west.commands.WestCommand`` class; this class will be instantiated and used when your extension is run. Here is a basic skeleton you can use to get started. It contains a subclass of ``WestCommand``, with implementations for all the abstract methods. For more details on the west APIs you can use, see :ref:`west-apis`. .. code-block:: py '''my_west_extension.py Basic example of a west extension.''' from textwrap import dedent # just for nicer code indentation from west.commands import WestCommand # your extension must subclass this from west import log # use this for user output class MyCommand(WestCommand): def __init__(self): super().__init__( 'my-command-name', # gets stored as self.name 'one-line help for what my-command-name does', # self.help # self.description: dedent(''' A multi-line description of my-command. You can split this up into multiple paragraphs and they'll get reflowed for you. You can also pass formatter_class=argparse.RawDescriptionHelpFormatter when calling parser_adder.add_parser() below if you want to keep your line endings.''')) def do_add_parser(self, parser_adder): # This is a bit of boilerplate, which allows you full control over the # type of argparse handling you want. The "parser_adder" argument is # the return value of an argparse.ArgumentParser.add_subparsers() call. parser = parser_adder.add_parser(self.name, help=self.help, description=self.description) # Add some example options using the standard argparse module API. parser.add_argument('-o', '--optional', help='an optional argument') parser.add_argument('required', help='a required argument') return parser # gets stored as self.parser def do_run(self, args, unknown_args): # This gets called when the user runs the command, e.g.: # # $ west my-command-name -o FOO BAR # --optional is FOO # required is BAR log.inf('--optional is', args.optional) log.inf('required is', args.required) You can ignore the second argument to ``do_run()`` (``unknown_args`` above), as ``WestCommand`` will reject unknown arguments by default. If you want to be passed a list of unknown arguments instead, add ``accepts_unknown_args=True`` to the ``super().__init__()`` arguments. Step 2: Add or Update Your :file:`west-commands.yml` ==================================================== You now need to add a :file:`west-commands.yml` file to your project which describes your extension to west. Here is an example for the above class definition, assuming it's in :file:`my_west_extension.py` at the project root directory: .. code-block:: yaml west-commands: - file: my_west_extension.py commands: - name: my-command-name class: MyCommand help: one-line help for what my-command-name does The top level of this YAML file is a map with a ``west-commands`` key. The key's value is a sequence of "command descriptors". Each command descriptor gives the location of a file implementing west extensions, along with the names of those extensions, and optionally the names of the classes which define them (if not given, the ``class`` value defaults to the same thing as ``name``). Some information in this file is redundant with definitions in the Python code. This is because west won't import :file:`my_west_extension.py` until the user runs ``west my-command-name``, since: - It allows users to run ``west update`` with a manifest from an untrusted source, then use other west commands without your code being imported along the way. Since importing a Python module is shell-equivalent, this provides some peace of mind. - It's a small optimization, since your code will only be imported if it is needed. So, unless your command is explicitly run, west will just load the :file:`west-commands.yml` file to get the basic information it needs to display information about your extension to the user in ``west --help`` output, etc. If you have multiple extensions, or want to split your extensions across multiple files, your :file:`west-commands.yml` will look something like this: .. code-block:: yaml west-commands: - file: my_west_extension.py commands: - name: my-command-name class: MyCommand help: one-line help for what my-command-name does - file: another_file.py commands: - name: command2 help: another cool west extension - name: a-third-command class: ThirdCommand help: a third command in the same file as command2 Above: - :file:`my_west_extension.py` defines extension ``my-command-name`` with class ``MyCommand`` - :file:`another_file.py` defines two extensions: #. ``command2`` with class ``command2`` #. ``a-third-command`` with class ``ThirdCommand`` See the file :file:`west-commands-schema.yml` in the `west repository`_ for a schema describing the contents of a :file:`west-commands.yml`. Step 3: Update Your Manifest ============================ Finally, you need to specify the location of the :file:`west-commands.yml` you just edited in your west manifest. If your extension is in a project, add it like this: .. code-block:: yaml manifest: # [... other contents ...] projects: - name: your-project west-commands: path/to/west-commands.yml # [... other projects ...] Where :file:`path/to/west-commands.yml` is relative to the root of the project. Note that the name :file:`west-commands.yml`, while encouraged, is just a convention; you can name the file something else if you need to. Alternatively, if your extension is in the manifest repository, just do the same thing in the manifest's ``self`` section, like this: .. code-block:: yaml manifest: # [... other contents ...] self: west-commands: path/to/west-commands.yml That's it; you can now run ``west my-command-name``. Your command's name, help, and the project which contains its code will now also show up in the ``west --help`` output. If you share the updated repositories with others, they'll be able to use it, too. .. _west PyPI page: path_to_url .. _west repository: path_to_url ```	/content/code_sandbox/doc/develop/west/extensions.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,084
```restructuredtext .. _west-sign: Signing Binaries ################ The ``west sign`` :ref:`extension <west-extensions>` command can be used to sign a Zephyr application binary for consumption by a bootloader using an external tool. In some configurations, ``west sign`` is also used to invoke an external, post-processing tool that "stitches" the final components of the image together. Run ``west sign -h`` for command line help. MCUboot / imgtool *************** The Zephyr build system has special support for signing binaries for use with the `MCUboot`_ bootloader using the `imgtool`_ program provided by its developers. You can both build and sign this type of application binary in one step by setting some Kconfig options. If you do, ``west flash`` will use the signed binaries. If you use this feature, you don't need to run ``west sign`` yourself; the build system will do it for you. Here is an example workflow, which builds and flashes MCUboot, as well as the :ref:`hello_world` application for chain-loading by MCUboot. Run these commands from the :file:`zephyrproject` workspace you created in the :ref:`getting_started`. .. code-block:: console west build -b YOUR_BOARD bootloader/mcuboot/boot/zephyr -d build-mcuboot west build -b YOUR_BOARD zephyr/samples/hello_world -d build-hello-signed -- \ -DCONFIG_BOOTLOADER_MCUBOOT=y \ -DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE=\"bootloader/mcuboot/root-rsa-2048.pem\" west flash -d build-mcuboot west flash -d build-hello-signed Notes on the above commands: - ``YOUR_BOARD`` should be changed to match your board - The ``CONFIG_MCUBOOT_SIGNATURE_KEY_FILE`` value is the insecure default provided and used by MCUboot for development and testing - You can change the ``hello_world`` application directory to any other application that can be loaded by MCUboot, such as the :zephyr:code-sample:`smp-svr` sample. For more information on these and other related configuration options, see: - :kconfig:option:`CONFIG_BOOTLOADER_MCUBOOT`: build the application for loading by MCUboot - :kconfig:option:`CONFIG_MCUBOOT_SIGNATURE_KEY_FILE`: the key file to use with ``west sign``. If you have your own key, change this appropriately - :kconfig:option:`CONFIG_MCUBOOT_EXTRA_IMGTOOL_ARGS`: optional additional command line arguments for ``imgtool`` - :kconfig:option:`CONFIG_MCUBOOT_GENERATE_CONFIRMED_IMAGE`: also generate a confirmed image, which may be more useful for flashing in production environments than the OTA-able default image - On Windows, if you get "Access denied" issues, the recommended fix is to run ``pip3 install imgtool``, then retry with a pristine build directory. If your ``west flash`` :ref:`runner <west-runner>` uses an image format supported by imgtool, you should see something like this on your device's serial console when you run ``west flash -d build-mcuboot``: .. code-block:: none * Booting Zephyr OS build zephyr-v2.3.0-2310-gcebac69c8ae1 * [00:00:00.004,669] <inf> mcuboot: Starting bootloader [00:00:00.011,169] <inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3 [00:00:00.021,636] <inf> mcuboot: Boot source: none [00:00:00.027,313] <wrn> mcuboot: Failed reading image headers; Image=0 [00:00:00.035,064] <err> mcuboot: Unable to find bootable image Then, you should see something like this when you run ``west flash -d build-hello-signed``: .. code-block:: none * Booting Zephyr OS build zephyr-v2.3.0-2310-gcebac69c8ae1 * [00:00:00.004,669] <inf> mcuboot: Starting bootloader [00:00:00.011,169] <inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3 [00:00:00.021,636] <inf> mcuboot: Boot source: none [00:00:00.027,374] <inf> mcuboot: Swap type: none [00:00:00.115,142] <inf> mcuboot: Bootloader chainload address offset: 0xc000 [00:00:00.123,168] <inf> mcuboot: Jumping to the first image slot * Booting Zephyr OS build zephyr-v2.3.0-2310-gcebac69c8ae1 * Hello World! nrf52840dk_nrf52840 Whether ``west flash`` supports this feature depends on your runner. The ``nrfjprog`` and ``pyocd`` runners work with the above flow. If your runner does not support this flow and you would like it to, please send a patch or file an issue for adding support. .. _west-extending-signing: Extending signing externally ************************** The signing script used when running ``west flash`` can be extended or replaced to change features or introduce different signing mechanisms. By default with MCUboot enabled, signing is setup by the :file:`cmake/mcuboot.cmake` file in Zephyr which adds extra post build commands for generating the signed images. The file used for signing can be replaced from a sysbuild scope (if being used) or from a zephyr/zephyr module scope, the priority of which is: * Sysbuild * Zephyr property * Default MCUboot script (if enabled) From sysbuild, ``-D<target>_SIGNING_SCRIPT`` can be used to set a signing script for a specific image or ``-DSIGNING_SCRIPT`` can be used to set a signing script for all images, for example: .. code-block:: console west build -b <board> <application> -DSIGNING_SCRIPT=<file> The zephyr property method is achieved by adjusting the ``SIGNING_SCRIPT`` property on the `zephyr_property_target`, ideally from by a module by using: .. code-block:: cmake if(CONFIG_BOOTLOADER_MCUBOOT) set_target_properties(zephyr_property_target PROPERTIES SIGNING_SCRIPT ${CMAKE_CURRENT_LIST_DIR}/custom_signing.cmake) endif() This will include the custom signing CMake file instead of the default Zephyr one when projects are built with MCUboot signing support enabled. The base Zephyr MCUboot signing file can be used as a reference for creating a new signing system or extending the default behaviour. .. _MCUboot: path_to_url .. _imgtool: path_to_url rimage ****** rimage configuration uses a different approach that does not rely on Kconfig or CMake but on :ref:`west config<west-config>` instead, similar to :ref:`west-building-cmake-config`. Signing involves a number of "wrapper" scripts stacked on top of each other: ``west flash`` invokes ``west build`` which invokes ``cmake`` and ``ninja`` which invokes ``west sign`` which invokes ``imgtool`` or `rimage`_. As long as the signing parameters desired are the default ones and fairly static, these indirections are not a problem. On the other hand, passing ``imgtool`` or ``rimage`` options through all these layers can causes issues typical when the layers don't abstract anything. First, this usually requires boilerplate code in each layer. Quoting whitespace or other special characters through all the wrappers can be difficult. Reproducing a lower ``west sign`` command to debug some build-time issue can be very time-consuming: it requires at least enabling and searching verbose build logs to find which exact options were used. Copying these options from the build logs can be unreliable: it may produce different results because of subtle environment differences. Last and worst: new signing feature and options are impossible to use until more boilerplate code has been added in each layer. To avoid these issues, ``rimage`` parameters can bet set in ``west config`` instead. Here's a ``workspace/.west/config`` example: .. code-block:: ini [sign] # Not needed when invoked from CMake tool = rimage [rimage] # Quoting is optional and works like in Unix shells # Not needed when rimage can be found in the default PATH path = "/home/me/zworkspace/build-rimage/rimage" # Not needed when using the default development key extra-args = -i 4 -k 'keys/key argument with space.pem' In order to support quoting, values are parsed by Python's ``shlex.split()`` like in :ref:`west-building-cmake-args`. The ``extra-args`` are passed directly to the ``rimage`` command. The example above has the same effect as appending them on command line after ``--`` like this: ``west sign --tool rimage -- -i 4 -k 'keys/key argument with space.pem'``. In case both are used, the command-line arguments go last. .. _rimage: path_to_url ```	/content/code_sandbox/doc/develop/west/sign.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,153
```restructuredtext .. _west-zephyr-ext-cmds: Additional Zephyr extension commands #################################### This page documents miscellaneous :ref:`west-zephyr-extensions`. .. _west-boards: Listing boards: ``west boards`` ***************************** The ``boards`` command can be used to list the boards that are supported by Zephyr without having to resort to additional sources of information. It can be run by typing:: west boards This command lists all supported boards in a default format. If you prefer to specify the display format yourself you can use the ``--format`` (or ``-f``) flag:: west boards -f "{arch}:{name}" Additional help about the formatting options can be found by running:: west boards -h .. _west-completion: Shell completion scripts: ``west completion`` ***************************************** The ``completion`` extension command outputs shell completion scripts that can then be used directly to enable shell completion for the supported shells. It currently supports the following shells: - bash - zsh - fish Additional instructions are available in the command's help:: west help completion .. _west-zephyr-export: Installing CMake packages: ``west zephyr-export`` ********************************************* This command registers the current Zephyr installation as a CMake config package in the CMake user package registry. In Windows, the CMake user package registry is found in ``HKEY_CURRENT_USER\Software\Kitware\CMake\Packages``. In Linux and MacOS, the CMake user package registry is found in. :file:`~/.cmake/packages`. You may run this command when setting up a Zephyr workspace. If you do, application CMakeLists.txt files that are outside of your workspace will be able to find the Zephyr repository with the following: .. code-block:: cmake find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE}) See :zephyr_file:`share/zephyr-package/cmake` for details. .. _west-spdx: Software bill of materials: ``west spdx`` ************************************* This command generates SPDX 2.3 tag-value documents, creating relationships from source files to the corresponding generated build files. into the SPDX documents. To use this command: #. Pre-populate a build directory :file:`BUILD_DIR` like this: .. code-block:: bash west spdx --init -d BUILD_DIR This step ensures the build directory contains CMake metadata required for SPDX document generation. #. Enable :file:`CONFIG_BUILD_OUTPUT_META` in your project. #. Build your application using this pre-created build directory, like so: .. code-block:: bash west build -d BUILD_DIR [...] #. Generate SPDX documents using this build directory: .. code-block:: bash west spdx -d BUILD_DIR This generates the following SPDX bill-of-materials (BOM) documents in :file:`BUILD_DIR/spdx/`: - :file:`app.spdx`: BOM for the application source files used for the build - :file:`zephyr.spdx`: BOM for the specific Zephyr source code files used for the build - :file:`build.spdx`: BOM for the built output files - :file:`modules-deps.spdx`: BOM for modules dependencies. Check :ref:`modules <modules-vulnerability-monitoring>` for more details. Each file in the bill-of-materials is scanned, so that its hashes (SHA256 and SHA1) can be recorded, along with any detected licenses if an SPDX Relationships are created to indicate dependencies between CMake build targets, build targets that are linked together, and source files that are compiled to generate the built library files. ``west spdx`` accepts these additional options: - ``-n PREFIX``: a prefix for the Document Namespaces that will be included in the generated SPDX documents. See `SPDX specification clause 6`_ for details. If ``-n`` is omitted, a default namespace will be generated according to the default format described in section 2.5 using a random UUID. - ``-s SPDX_DIR``: specifies an alternate directory where the SPDX documents should be written instead of :file:`BUILD_DIR/spdx/`. - ``--analyze-includes``: in addition to recording the compiled source code files (e.g. ``.c``, ``.S``) in the bills-of-materials, also attempt to determine the specific header files that are included for each ``.c`` file. This takes longer, as it performs a dry run using the C compiler for each ``.c`` file using the same arguments that were passed to it for the actual build. - ``--include-sdk``: with ``--analyze-includes``, also create a fourth SPDX document, :file:`sdk.spdx`, which lists header files included from the SDK. .. _SPDX specification clause 6: path_to_url .. _west-blobs: Working with binary blobs: ``west blobs`` ************************************* The ``blobs`` command allows users to interact with :ref:`binary blobs <bin-blobs>` declared in one or more :ref:`modules <modules>` via their :ref:`module.yml <module-yml>` file. The ``blobs`` command has three sub-commands, used to list, fetch or clean (i.e. delete) the binary blobs themselves. You can list binary blobs while specifying the format of the output:: west blobs list -f '{module}: {type} {path}' For the full set of variables available in ``-f/--format`` run ``west blobs -h``. Fetching blobs works in a similar manner:: west blobs fetch Note that, as described in :ref:`the modules section <modules-bin-blobs>`, fetched blobs are stored in a :file:`zephyr/blobs/` folder relative to the root of the corresponding module repository. As does deleting them:: west blobs clean Additionally the tool allows you to specify the modules you want to list, fetch or clean blobs for by typing the module names as a command-line parameter. .. _west-twister: Twister wrapper: ``west twister`` ***************************** This command is a wrapper for :ref:`twister <twister_script>`. Twister can then be invoked via west as follows:: west twister -help west twister -T tests/ztest/base .. _west-bindesc: Working with binary descriptors: ``west bindesc`` *********************************************** The ``bindesc`` command allows users to read :ref:`binary descriptors<binary_descriptors>` of executable files. It currently supports ``.bin``, ``.hex``, ``.elf`` and ``.uf2`` files as input. You can search for a specific descriptor in an image, for example:: west bindesc search KERNEL_VERSION_STRING build/zephyr/zephyr.bin You can search for a custom descriptor by type and ID, for example:: west bindesc custom_search STR 0x200 build/zephyr/zephyr.bin You can dump all of the descriptors in an image using:: west bindesc dump build/zephyr/zephyr.bin You can list all known standard descriptor names using:: west bindesc list ```	/content/code_sandbox/doc/develop/west/zephyr-cmds.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,546
```restructuredtext .. _west: West (Zephyr's meta-tool) ######################### The Zephyr project includes a swiss-army knife command line tool named ``west``\ [#west-name]_. West is developed in its own `repository`_. West's built-in commands provide a multiple repository management system with features inspired by Google's Repo tool and Git submodules. West is also "pluggable": you can write your own west extension commands which add additional features to west. Zephyr uses this to provide conveniences for building applications, flashing and debugging them, and more. Like ``git`` and ``docker``, the top-level ``west`` command takes some common options, a sub-command to run, and then options and arguments for that sub-command:: west [common-opts] <command> [opts] <args> Since west v0.8, you can also run west like this:: python3 -m west [common-opts] <command> [opts] <args> You can run ``west --help`` (or ``west -h`` for short) to get top-level help for available west commands, and ``west <command> -h`` for detailed help on each command. .. toctree:: :maxdepth: 1 install.rst release-notes.rst troubleshooting.rst basics.rst built-in.rst workspaces.rst manifest.rst config.rst extensions.rst build-flash-debug.rst sign.rst zephyr-cmds.rst why.rst moving-to-west.rst without-west.rst For details on west's Python APIs, see :ref:`west-apis`. .. rubric:: Footnotes .. [#west-name] Zephyr is an English name for the Latin `Zephyrus <path_to_url`_, the ancient Greek god of the west wind. .. _repository: path_to_url ```	/content/code_sandbox/doc/develop/west/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	432
```restructuredtext .. _moving-to-west: Moving to West ############## To convert a "pre-west" Zephyr setup on your computer to west, follow these steps. If you are starting from scratch, use the :ref:`getting_started` instead. See :ref:`west-troubleshooting` for advice on common issues. #. Install west. On Linux:: pip3 install --user -U west On Windows and macOS:: pip3 install -U west For details, see :ref:`west-install`. #. Move your zephyr repository to a new :file:`zephyrproject` parent directory, and change directory there. On Linux and macOS:: mkdir zephyrproject mv zephyr zephyrproject cd zephyrproject On Windows ``cmd.exe``:: mkdir zephyrproject move zephyr zephyrproject chdir zephyrproject The name :file:`zephyrproject` is recommended, but you can choose any name with no spaces anywhere in the path. #. Create a :ref:`west workspace <west-workspace>` using the zephyr repository as a local manifest repository:: west init -l zephyr This creates :file:`zephyrproject/.west`, marking the root of your workspace, and does some other setup. It will not change the contents of the zephyr repository in any way. #. Clone the rest of the repositories used by zephyr:: west update Make sure to run this command whenever you pull zephyr. Otherwise, your local repositories will get out of sync. (Run ``west list`` for current information on these repositories.) You are done: :file:`zephyrproject` is now set up to use west. ```	/content/code_sandbox/doc/develop/west/moving-to-west.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	393
```restructuredtext .. _west-install: Installing west ############### West is written in Python 3 and distributed through `PyPI`_. Use :file:`pip3` to install or upgrade west: On Linux:: pip3 install --user -U west On Windows and macOS:: pip3 install -U west .. note:: See :ref:`python-pip` for additional clarification on using the ``--user`` switch. Afterwards, you can run ``pip3 show -f west`` for information on where the west binary and related files were installed. Once west is installed, you can use it to :ref:`clone the Zephyr repositories <clone-zephyr>`. .. _west-struct: Structure ******* West's code is distributed via PyPI in a Python package named ``west``. This distribution includes a launcher executable, which is also named ``west`` (or ``west.exe`` on Windows). When west is installed, the launcher is placed by :file:`pip3` somewhere in the user's filesystem (exactly where depends on the operating system, but should be on the ``PATH`` :ref:`environment variable <env_vars>`). This launcher is the command-line entry point to running both built-in commands like ``west init``, ``west update``, along with any extensions discovered in the workspace. In addition to its command-line interface, you can also use west's Python APIs directly. See :ref:`west-apis` for details. .. _west-shell-completion: Enabling shell completion *********************** West currently supports shell completion in the following shells: * bash * zsh * fish In order to enable shell completion, you will need to obtain the corresponding completion script and have it sourced. Using the completion scripts: .. tabs:: .. group-tab:: bash One-time setup: .. code-block:: bash source <(west completion bash) Permanent setup: .. code-block:: bash west completion bash > ~/west-completion.bash; echo "source ~/west-completion.bash" >> ~/.bashrc .. group-tab:: zsh One-time setup: .. code-block:: zsh source <(west completion zsh) Permanent setup: .. code-block:: zsh west completion zsh > "${fpath[1]}/_west" .. group-tab:: fish One-time setup: .. code-block:: fish west completion fish \| source Permanent setup: .. code-block:: fish west completion fish > $HOME/.config/fish/completions/west.fish .. _PyPI: path_to_url ```	/content/code_sandbox/doc/develop/west/install.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	581
```restructuredtext .. _west-history: History and Motivation ###################### West was added to the Zephyr project to fulfill two fundamental requirements: * The ability to work with multiple Git repositories * The ability to provide an extensible and user-friendly command-line interface for basic Zephyr workflows During the development of west, a set of :ref:`west-design-constraints` were identified to avoid the common pitfalls of tools of this kind. Requirements ************ Although the motivation behind splitting the Zephyr codebase into multiple repositories is outside of the scope of this page, the fundamental requirements, along with a clear justification of the choice not to use existing tools and instead develop a new one, do belong here. The basic requirements are: * R1: Keep externally maintained code in separately maintained repositories outside of the main zephyr repository, without requiring users to manually clone each of the external repositories * R2: Provide a tool that both Zephyr users and distributors can make use of to benefit from and extend * R3: Allow users and downstream distributions to override or remove repositories without having to make changes to the zephyr repository * R4: Support both continuous tracking and commit-based (bisectable) project updating Rationale for a custom tool *************************** Some of west's features are similar to those provided by `Git Submodules <path_to_url`_ and Google's `repo <path_to_url`_. Existing tools were considered during west's initial design and development. None were found suitable for Zephyr's requirements. In particular, these were examined in detail: * Google repo - Does not cleanly support using zephyr as the manifest repository (R4) - Python 2 only - Does not play well with Windows - Assumes Gerrit is used for code review * Git submodules - Does not fully support R1, since the externally maintained repositories would still need to be inside the main zephyr Git tree - Does not support R3, since downstream copies would need to either delete or replace submodule definitions - Does not support continuous tracking of the latest ``HEAD`` in external repositories (R4) - Requires hardcoding of the paths/locations of the external repositories Multiple Git Repositories ************************* Zephyr intends to provide all required building blocks needed to deploy complex IoT applications. This in turn means that the Zephyr project is much more than an RTOS kernel, and is instead a collection of components that work together. In this context, there are a few reasons to work with multiple Git repositories in a standardized manner within the project: * Clean separation of Zephyr original code and imported projects and libraries * Avoidance of license incompatibilities between original and imported code * Reduction in size and scope of the core Zephyr codebase, with additional repositories containing optional components instead of being imported directly into the tree * Safety and security certifications * Enforcement of modularization of the components * Out-of-tree development based on subsets of the supported boards and SoCs See :ref:`west-basics` for information on how west workspaces manage multiple git repositories. .. _west-design-constraints: Design Constraints **************** West is: - Optional*: it is always possible* to drop back to "raw" command-line tools, i.e. use Zephyr without using west (although west itself might need to be installed and accessible to the build system). It may not always be convenient to do so, however. (If all of west's features were already conveniently available, there would be no reason to develop it.) - Compatible with CMake: building, flashing and debugging, and emulator support will always remain compatible with direct use of CMake. - Cross-platform: West is written in Python 3, and works on all platforms supported by Zephyr. - Usable as a Library: whenever possible, west features are implemented as libraries that can be used standalone in other programs, along with separate command line interfaces that wrap them. West itself is a Python package named ``west``; its libraries are implemented as subpackages. - Conservative about features: no features will be accepted without strong and compelling motivation. - Clearly specified: West's behavior in cases where it wraps other commands is clearly specified and documented. This enables interoperability with third party tools, and means Zephyr developers can always find out what is happening "under the hood" when using west. See :github:`Zephyr issue #6205 <6205>` and for more details and discussion. ```	/content/code_sandbox/doc/develop/west/why.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,022
```restructuredtext .. _west-build-flash-debug: Building, Flashing and Debugging ################################ Zephyr provides several :ref:`west extension commands <west-extensions>` for building, flashing, and interacting with Zephyr programs running on a board: ``build``, ``flash``, ``debug``, ``debugserver`` and ``attach``. For information on adding board support for the flashing and debugging commands, see :ref:`flash-and-debug-support` in the board porting guide. .. Add a per-page contents at the top of the page. This page is nested deeply enough that it doesn't have any subheadings in the main nav. .. only:: html .. contents:: :local: .. _west-building: Building: ``west build`` ************************ .. tip:: Run ``west build -h`` for a quick overview. The ``build`` command helps you build Zephyr applications from source. You can use :ref:`west config <west-config-cmd>` to configure its behavior. Its default behavior tries to "do what you mean": - If there is a Zephyr build directory named :file:`build` in your current working directory, it is incrementally re-compiled. The same is true if you run ``west build`` from a Zephyr build directory. - Otherwise, if you run ``west build`` from a Zephyr application's source directory and no build directory is found, a new one is created and the application is compiled in it. Basics ====== The easiest way to use ``west build`` is to go to an application's root directory (i.e. the folder containing the application's :file:`CMakeLists.txt`) and then run:: west build -b <BOARD> Where ``<BOARD>`` is the name of the board you want to build for. This is exactly the same name you would supply to CMake if you were to invoke it with: ``cmake -DBOARD=<BOARD>``. .. tip:: You can use the :ref:`west boards <west-boards>` command to list all supported boards. A build directory named :file:`build` will be created, and the application will be compiled there after ``west build`` runs CMake to create a build system in that directory. If ``west build`` finds an existing build directory, the application is incrementally re-compiled there without re-running CMake. You can force CMake to run again with ``--cmake``. You don't need to use the ``--board`` option if you've already got an existing build directory; ``west build`` can figure out the board from the CMake cache. For new builds, the ``--board`` option, :envvar:`BOARD` environment variable, or ``build.board`` configuration option are checked (in that order). .. _west-multi-domain-builds: Sysbuild (multi-domain builds) ============================== :ref:`sysbuild` can be used to create a multi-domain build system combining multiple images for a single or multiple boards. Use ``--sysbuild`` to select the :ref:`sysbuild` build infrastructure with ``west build`` to build multiple domains. More detailed information regarding the use of sysbuild can be found in the :ref:`sysbuild` guide. .. tip:: The ``build.sysbuild`` configuration option can be enabled to tell ``west build`` to default build using sysbuild. ``--no-sysbuild`` can be used to disable sysbuild for a specific build. ``west build`` will build all domains through the top-level build folder of the domains specified by sysbuild. A single domain from a multi-domain project can be built by using ``--domain`` argument. Examples ======== Here are some ``west build`` usage examples, grouped by area. Forcing CMake to Run Again -------------------------- To force a CMake re-run, use the ``--cmake`` (or ``-c``) option:: west build -c Setting a Default Board ----------------------- To configure ``west build`` to build for the ``reel_board`` by default:: west config build.board reel_board (You can use any other board supported by Zephyr here; it doesn't have to be ``reel_board``.) .. _west-building-dirs: Setting Source and Build Directories ------------------------------------ To set the application source directory explicitly, give its path as a positional argument:: west build -b <BOARD> path/to/source/directory To set the build directory explicitly, use ``--build-dir`` (or ``-d``):: west build -b <BOARD> --build-dir path/to/build/directory To change the default build directory from :file:`build`, use the ``build.dir-fmt`` configuration option. This lets you name build directories using format strings, like this:: west config build.dir-fmt "build/{board}/{app}" With the above, running ``west build -b reel_board samples/hello_world`` will use build directory :file:`build/reel_board/hello_world`. See :ref:`west-building-config` for more details on this option. Setting the Build System Target ------------------------------- To specify the build system target to run, use ``--target`` (or ``-t``). For example, on host platforms with QEMU, you can use the ``run`` target to build and run the :ref:`hello_world` sample for the emulated :ref:`qemu_x86 <qemu_x86>` board in one command:: west build -b qemu_x86 -t run samples/hello_world As another example, to use ``-t`` to list all build system targets:: west build -t help As a final example, to use ``-t`` to run the ``pristine`` target, which deletes all the files in the build directory:: west build -t pristine .. _west-building-pristine: Pristine Builds --------------- A pristine build directory is essentially a new build directory. All byproducts from previous builds have been removed. To force ``west build`` make the build directory pristine before re-running CMake to generate a build system, use the ``--pristine=always`` (or ``-p=always``) option. Giving ``--pristine`` or ``-p`` without a value has the same effect as giving it the value ``always``. For example, these commands are equivalent:: west build -p -b reel_board samples/hello_world west build -p=always -b reel_board samples/hello_world By default, ``west build`` makes no attempt to detect if the build directory needs to be made pristine. This can lead to errors if you do something like try to reuse a build directory for a different ``--board``. Using ``--pristine=auto`` makes ``west build`` detect some of these situations and make the build directory pristine before trying the build. .. tip:: You can run ``west config build.pristine always`` to always do a pristine build, or ``west config build.pristine never`` to disable the heuristic. See the ``west build`` :ref:`west-building-config` for details. .. _west-building-verbose: Verbose Builds -------------- To print the CMake and compiler commands run by ``west build``, use the global west verbosity option, ``-v``:: west -v build -b reel_board samples/hello_world .. _west-building-generator: .. _west-building-cmake-args: One-Time CMake Arguments ------------------------ To pass additional arguments to the CMake invocation performed by ``west build``, pass them after a ``--`` at the end of the command line. .. important:: Passing additional CMake arguments like this forces ``west build`` to re-run the CMake build configuration step, even if a build system has already been generated. This will make incremental builds slower (but still much faster than building from scratch). After using ``--`` once to generate the build directory, use ``west build -d <build-dir>`` on subsequent runs to do incremental builds. Alternatively, make your CMake arguments permanent as described in the next section; it will not slow down incremental builds. For example, to use the Unix Makefiles CMake generator instead of Ninja (which ``west build`` uses by default), run:: west build -b reel_board -- -G'Unix Makefiles' To use Unix Makefiles and set `CMAKE_VERBOSE_MAKEFILE`_ to ``ON``:: west build -b reel_board -- -G'Unix Makefiles' -DCMAKE_VERBOSE_MAKEFILE=ON Notice how the ``--`` only appears once, even though multiple CMake arguments are given. All command-line arguments to ``west build`` after a ``--`` are passed to CMake. .. _west-building-dtc-overlay-file: To set :ref:`DTC_OVERLAY_FILE <important-build-vars>` to :file:`enable-modem.overlay`, using that file as a :ref:`devicetree overlay <dt-guide>`:: west build -b reel_board -- -DDTC_OVERLAY_FILE=enable-modem.overlay To merge the :file:`file.conf` Kconfig fragment into your build's :file:`.config`:: west build -- -DEXTRA_CONF_FILE=file.conf .. _west-building-cmake-config: Permanent CMake Arguments ------------------------- The previous section describes how to add CMake arguments for a single ``west build`` command. If you want to save CMake arguments for ``west build`` to use every time it generates a new build system instead, you should use the ``build.cmake-args`` configuration option. Whenever ``west build`` runs CMake to generate a build system, it splits this option's value according to shell rules and includes the results in the ``cmake`` command line. Remember that, by default, ``west build`` tries to avoid generating a new build system if one is present in your build directory. Therefore, you need to either delete any existing build directories or do a :ref:`pristine build <west-building-pristine>` after setting ``build.cmake-args`` to make sure it will take effect. For example, to always enable :makevar:`CMAKE_EXPORT_COMPILE_COMMANDS`, you can run:: west config build.cmake-args -- -DCMAKE_EXPORT_COMPILE_COMMANDS=ON (The extra ``--`` is used to force the rest of the command to be treated as a positional argument. Without it, :ref:`west config <west-config-cmd>` would treat the ``-DVAR=VAL`` syntax as a use of its ``-D`` option.) To enable :makevar:`CMAKE_VERBOSE_MAKEFILE`, so CMake always produces a verbose build system:: west config build.cmake-args -- -DCMAKE_VERBOSE_MAKEFILE=ON To save more than one argument in ``build.cmake-args``, use a single string whose value can be split into distinct arguments (``west build`` uses the Python function `shlex.split()`_ internally to split the value). .. _shlex.split(): path_to_url#shlex.split For example, to enable both :makevar:`CMAKE_EXPORT_COMPILE_COMMANDS` and :makevar:`CMAKE_VERBOSE_MAKEFILE`:: west config build.cmake-args -- "-DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_VERBOSE_MAKEFILE=ON" If you want to save your CMake arguments in a separate file instead, you can combine CMake's ``-C <initial-cache>`` option with ``build.cmake-args``. For instance, another way to set the options used in the previous example is to create a file named :file:`~/my-cache.cmake` with the following contents: .. code-block:: cmake set(CMAKE_EXPORT_COMPILE_COMMANDS ON CACHE BOOL "") set(CMAKE_VERBOSE_MAKEFILE ON CACHE BOOL "") Then run:: west config build.cmake-args "-C ~/my-cache.cmake" See the `cmake(1) manual page`_ and the `set() command`_ documentation for more details. .. _cmake(1) manual page: path_to_url .. _set() command: path_to_url Build tool arguments -------------------- Use ``-o`` to pass options to the underlying build tool. This works with both ``ninja`` (:ref:`the default <west-building-generator>`) and ``make`` based build systems. For example, to pass ``-dexplain`` to ``ninja``:: west build -o=-dexplain As another example, to pass ``--keep-going`` to ``make``:: west build -o=--keep-going Note that using ``-o=--foo`` instead of ``-o --foo`` is required to prevent ``--foo`` from being treated as a ``west build`` option. Build parallelism ----------------- By default, ``ninja`` uses all of your cores to build, while ``make`` uses only one. You can control this explicitly with the ``-j`` option supported by both tools. For example, to build with 4 cores:: west build -o=-j4 The ``-o`` option is described further in the previous section. Build a single domain --------------------- In a multi-domain build with :ref:`hello_world` and `MCUboot`_, you can use ``--domain hello_world`` to only build this domain:: west build --sysbuild --domain hello_world The ``--domain`` argument can be combined with the ``--target`` argument to build the specific target for the target, for example:: west build --sysbuild --domain hello_world --target help Use a snippet ------------- See :ref:`using-snippets`. .. _west-building-config: Configuration Options ===================== You can :ref:`configure <west-config-cmd>` ``west build`` using these options. .. NOTE: docs authors: keep this table sorted alphabetically .. list-table:: :widths: 10 30 :header-rows: 1 * - Option - Description * - ``build.board`` - String. If given, this the board used by :ref:`west build <west-building>` when ``--board`` is not given and ``BOARD`` is unset in the environment. * - ``build.board_warn`` - Boolean, default ``true``. If ``false``, disables warnings when ``west build`` can't figure out the target board. * - ``build.cmake-args`` - String. If present, the value will be split according to shell rules and passed to CMake whenever a new build system is generated. See :ref:`west-building-cmake-config`. * - ``build.dir-fmt`` - String, default ``build``. The build folder format string, used by west whenever it needs to create or locate a build folder. The currently available arguments are: - ``board``: The board name - ``source_dir``: The relative path from the current working directory to the source directory. If the current working directory is inside the source directory this will be set to an empty string. - ``app``: The name of the source directory. * - ``build.generator`` - String, default ``Ninja``. The `CMake Generator`_ to use to create a build system. (To set a generator for a single build, see the :ref:`above example <west-building-generator>`) * - ``build.guess-dir`` - String, instructs west whether to try to guess what build folder to use when ``build.dir-fmt`` is in use and not enough information is available to resolve the build folder name. Can take these values: - ``never`` (default): Never try to guess, bail out instead and require the user to provide a build folder with ``-d``. - ``runners``: Try to guess the folder when using any of the 'runner' commands. These are typically all commands that invoke an external tool, such as ``flash`` and ``debug``. * - ``build.pristine`` - String. Controls the way in which ``west build`` may clean the build folder before building. Can take the following values: - ``never`` (default): Never automatically make the build folder pristine. - ``auto``: ``west build`` will automatically make the build folder pristine before building, if a build system is present and the build would fail otherwise (e.g. the user has specified a different board or application from the one previously used to make the build directory). - ``always``: Always make the build folder pristine before building, if a build system is present. * - ``build.sysbuild`` - Boolean, default ``false``. If ``true``, build application using the sysbuild infrastructure. .. _west-flashing: Flashing: ``west flash`` ********************** .. tip:: Run ``west flash -h`` for additional help. Basics ====== From a Zephyr build directory, re-build the binary and flash it to your board:: west flash Without options, the behavior is the same as ``ninja flash`` (or ``make flash``, etc.). To specify the build directory, use ``--build-dir`` (or ``-d``):: west flash --build-dir path/to/build/directory If you don't specify the build directory, ``west flash`` searches for one in :file:`build`, then the current working directory. If you set the ``build.dir-fmt`` configuration option (see :ref:`west-building-dirs`), ``west flash`` searches there instead of :file:`build`. Choosing a Runner ================= If your board's Zephyr integration supports flashing with multiple programs, you can specify which one to use using the ``--runner`` (or ``-r``) option. For example, if West flashes your board with ``nrfjprog`` by default, but it also supports JLink, you can override the default with:: west flash --runner jlink You can override the default flash runner at build time by using the ``BOARD_FLASH_RUNNER`` CMake variable, and the debug runner with ``BOARD_DEBUG_RUNNER``. For example:: # Set the default runner to "jlink", overriding the board's # usual default. west build [...] -- -DBOARD_FLASH_RUNNER=jlink See :ref:`west-building-cmake-args` and :ref:`west-building-cmake-config` for more information on setting CMake arguments. See :ref:`west-runner` below for more information on the ``runner`` library used by West. The list of runners which support flashing can be obtained with ``west flash -H``; if run from a build directory or with ``--build-dir``, this will print additional information on available runners for your board. Configuration Overrides ======================= The CMake cache contains default values West uses while flashing, such as where the board directory is on the file system, the path to the zephyr binaries to flash in several formats, and more. You can override any of this configuration at runtime with additional options. For example, to override the HEX file containing the Zephyr image to flash (assuming your runner expects a HEX file), but keep other flash configuration at default values:: west flash --hex-file path/to/some/other.hex The ``west flash -h`` output includes a complete list of overrides supported by all runners. Runner-Specific Overrides ========================= Each runner may support additional options related to flashing. For example, some runners support an ``--erase`` flag, which mass-erases the flash storage on your board before flashing the Zephyr image. To view all of the available options for the runners your board supports, as well as their usage information, use ``--context`` (or ``-H``):: west flash --context .. important:: Note the capital H in the short option name. This re-runs the build in order to ensure the information displayed is up to date! When running West outside of a build directory, ``west flash -H`` just prints a list of runners. You can use ``west flash -H -r <runner-name>`` to print usage information for options supported by that runner. For example, to print usage information about the ``jlink`` runner:: west flash -H -r jlink .. _west-multi-domain-flashing: Multi-domain flashing ===================== When a :ref:`west-multi-domain-builds` folder is detected, then ``west flash`` will flash all domains in the order defined by sysbuild. It is possible to flash the image from a single domain in a multi-domain project by using ``--domain``. For example, in a multi-domain build with :ref:`hello_world` and `MCUboot`_, you can use the ``--domain hello_world`` domain to only flash only the image from this domain:: west flash --domain hello_world .. _west-debugging: Debugging: ``west debug``, ``west debugserver`` ******************************************* .. tip:: Run ``west debug -h`` or ``west debugserver -h`` for additional help. Basics ====== From a Zephyr build directory, to attach a debugger to your board and open up a debug console (e.g. a GDB session):: west debug To attach a debugger to your board and open up a local network port you can connect a debugger to (e.g. an IDE debugger):: west debugserver Without options, the behavior is the same as ``ninja debug`` and ``ninja debugserver`` (or ``make debug``, etc.). To specify the build directory, use ``--build-dir`` (or ``-d``):: west debug --build-dir path/to/build/directory west debugserver --build-dir path/to/build/directory If you don't specify the build directory, these commands search for one in :file:`build`, then the current working directory. If you set the ``build.dir-fmt`` configuration option (see :ref:`west-building-dirs`), ``west debug`` searches there instead of :file:`build`. Choosing a Runner ================= If your board's Zephyr integration supports debugging with multiple programs, you can specify which one to use using the ``--runner`` (or ``-r``) option. For example, if West debugs your board with ``pyocd-gdbserver`` by default, but it also supports JLink, you can override the default with:: west debug --runner jlink west debugserver --runner jlink See :ref:`west-runner` below for more information on the ``runner`` library used by West. The list of runners which support debugging can be obtained with ``west debug -H``; if run from a build directory or with ``--build-dir``, this will print additional information on available runners for your board. Configuration Overrides ======================= The CMake cache contains default values West uses for debugging, such as where the board directory is on the file system, the path to the zephyr binaries containing symbol tables, and more. You can override any of this configuration at runtime with additional options. For example, to override the ELF file containing the Zephyr binary and symbol tables (assuming your runner expects an ELF file), but keep other debug configuration at default values:: west debug --elf-file path/to/some/other.elf west debugserver --elf-file path/to/some/other.elf The ``west debug -h`` output includes a complete list of overrides supported by all runners. Runner-Specific Overrides ========================= Each runner may support additional options related to debugging. For example, some runners support flags which allow you to set the network ports used by debug servers. To view all of the available options for the runners your board supports, as well as their usage information, use ``--context`` (or ``-H``):: west debug --context (The command ``west debugserver --context`` will print the same output.) .. important:: Note the capital H in the short option name. This re-runs the build in order to ensure the information displayed is up to date! When running West outside of a build directory, ``west debug -H`` just prints a list of runners. You can use ``west debug -H -r <runner-name>`` to print usage information for options supported by that runner. For example, to print usage information about the ``jlink`` runner:: west debug -H -r jlink .. _west-multi-domain-debugging: Multi-domain debugging ====================== ``west debug`` can only debug a single domain at a time. When a :ref:`west-multi-domain-builds` folder is detected, ``west debug`` will debug the ``default`` domain specified by sysbuild. The default domain will be the application given as the source directory. See the following example:: west build --sysbuild path/to/source/directory For example, when building ``hello_world`` with `MCUboot`_ using sysbuild, ``hello_world`` becomes the default domain:: west build --sysbuild samples/hello_world So to debug ``hello_world`` you can do:: west debug or:: west debug --domain hello_world If you wish to debug MCUboot, you must explicitly specify MCUboot as the domain to debug:: west debug --domain mcuboot .. _west-runner: Flash and debug runners ********************* The flash and debug commands use Python wrappers around various :ref:`flash-debug-host-tools`. These wrappers are all defined in a Python library at :zephyr_file:`scripts/west_commands/runners`. Each wrapper is called a runner. Runners can flash and/or debug Zephyr programs. The central abstraction within this library is ``ZephyrBinaryRunner``, an abstract class which represents runners. The set of available runners is determined by the imported subclasses of ``ZephyrBinaryRunner``. ``ZephyrBinaryRunner`` is available in the ``runners.core`` module; individual runner implementations are in other submodules, such as ``runners.nrfjprog``, ``runners.openocd``, etc. Running Robot Framework tests: ``west robot`` ******************************************* .. tip:: Run ``west robot -h`` for additional help. Basics ====== Currently the command supports only one runner which is using ``renode-test``, (essentially a wrapper for running Robot tests in Renode), but can be easily extended by adding other runners. From a Zephyr build directory, to run a Robot test suite:: west robot --runner=renode-robot --testsuite path/to/testsuite.robot This will run all tests from testsuite.robot and print output provided by Robot Framework. To pass additional parameters to Renode use ``--renode-robot-args`` switch. For example to show Renode logs in addition to Robot Framework's output: west robot --runner=renode-robot --testsuite path/to/testsuite.robot --renode-robot-arg="--show-log" Runner-Specific Overrides ========================= To view all of the available options for the Robot runners your board supports, as well as their usage information, use ``--context`` (or ``-H``):: west robot --runner=renode-robot --context To view all available options "renode-test" runner supports, use:: west robot --runner=renode-robot --renode-robot-help Simulating a board with: ``west simulate`` ************************************** Basics ====== Currently the command supports only one runner which is using Renode, but can be easily extended by adding other runners. From a Zephyr build directory, to run the built binary:: west simulate --runner=renode This will start Renode and configure simulation based on a default ``.resc`` script for the current platform with the zephyr.elf file loaded by default. The simulation then can be started by typing "start" or "s" in Renode's Monitor. This can also be done by passing a command to Renode, using an argument provided by the runner: west simulate --runner=renode --renode-command start To pass an argument to Renode itself, for example to start Renode in console mode instead of a separate window: west simulate --runner=renode --renode-arg="--console" From that point on Renode can be used normally in both console and window modes. For details on using Renode see `Renode - documentation`_. .. _Renode - documentation: path_to_url Runner-Specific Overrides ========================= To view all of the available options supported by the runners, as well as their usage information, use ``--context`` (or``-H``):: west simulate --runner=renode --context To view all available options Renode supports, use:: west simulate --runner=renode --renode-help Hacking *** This section documents the ``runners.core`` module used by the flash and debug commands. This is the core abstraction used to implement support for these features. .. warning:: These APIs are provided for reference, but they are more "shared code" used to implement multiple extension commands than a stable API. Developers can add support for new ways to flash and debug Zephyr programs by implementing additional runners. To get this support into upstream Zephyr, the runner should be added into a new or existing ``runners`` module, and imported from :file:`runners/__init__.py`. .. note:: The test cases in :zephyr_file:`scripts/west_commands/tests` add unit test coverage for the runners package and individual runner classes. Please try to add tests when adding new runners. Note that if your changes break existing test cases, CI testing on upstream pull requests will fail. .. automodule:: runners.core :members: Doing it By Hand ************** If you prefer not to use West to flash or debug your board, simply inspect the build directory for the binaries output by the build system. These will be named something like ``zephyr/zephyr.elf``, ``zephyr/zephyr.hex``, etc., depending on your board's build system integration. These binaries may be flashed to a board using alternative tools of your choice, or used for debugging as needed, e.g. as a source of symbol tables. By default, these West commands rebuild binaries before flashing and debugging. This can of course also be accomplished using the usual targets provided by Zephyr's build system (in fact, that's how these commands do it). .. _cmake(1): path_to_url .. _CMAKE_VERBOSE_MAKEFILE: path_to_url .. _CMake Generator: path_to_url .. _MCUboot: path_to_url ```	/content/code_sandbox/doc/develop/west/build-flash-debug.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	6,715
```restructuredtext .. _west-workspaces: Workspaces ########## This page describes the west workspace concept introduced in :ref:`west-basics` in more detail. .. _west-manifest-rev: The ``manifest-rev`` branch ************************* West creates and controls a Git branch named ``manifest-rev`` in each project. This branch points to the revision that the manifest file specified for the project at the time :ref:`west-update` was last run. Other workspace management commands may use ``manifest-rev`` as a reference point for the upstream revision as of this latest update. Among other purposes, the ``manifest-rev`` branch allows the manifest file to use SHAs as project revisions. Although ``manifest-rev`` is a normal Git branch, west will recreate and/or reset it on the next update. For this reason, it is dangerous** to check it out or otherwise modify it yourself. For instance, any commits you manually add to this branch may be lost the next time you run ``west update``. Instead, check out a local branch with another name, and either rebase it on top of a new ``manifest-rev``, or merge ``manifest-rev`` into it. .. note:: West does not create a ``manifest-rev`` branch in the manifest repository, since west does not manage the manifest repository's branches or revisions. The ``refs/west/`` Git refs ************************* West also reserves all Git refs that begin with ``refs/west/`` (such as ``refs/west/foo``) for itself in local project repositories. Unlike ``manifest-rev``, these refs are not regular branches. West's behavior here is an implementation detail; users should not rely on these refs' existence or behavior. Private repositories **************** You can use west to fetch from private repositories. There is nothing west-specific about this. The ``west update`` command essentially runs ``git fetch YOUR_PROJECT_URL`` when a project's ``manifest-rev`` branch must be updated to a newly fetched commit. It's up to your environment to make sure the fetch succeeds. You can either enter the password manually or use any of the `credential helpers built in to Git`_. Since Git has credential storage built in, there is no need for a west-specific feature. The following sections cover common cases for running ``west update`` without having to enter your password, as well as how to troubleshoot issues. .. _credential helpers built in to Git: path_to_url Fetching via HTTPS ================== On Windows when fetching from GitHub, recent versions of Git prompt you for your GitHub password in a graphical window once, then store it for future use (in a default installation). Passwordless fetching from GitHub should therefore work "out of the box" on Windows after you have done it once. In general, you can store your credentials on disk using the "store" git credential helper. See the `git-credential-store`_ manual page for details. To use this helper for all the repositories in your workspace, run: .. code-block:: shell west forall -c "git config credential.helper store" To use this helper on just the projects ``foo`` and ``bar``, run: .. code-block:: shell west forall -c "git config credential.helper store" foo bar To use this helper by default on your computer, run: .. code-block:: shell git config --global credential.helper store On GitHub, you can set up a `personal access token`_ to use in place of your account password. (This may be required if your account has two-factor authentication enabled, and may be preferable to storing your account password in plain text even if two-factor authentication is disabled.) You can use the Git credential store to authenticate with a GitHub PAT (Personal Access Token) like so: .. code-block:: shell echo "path_to_url" >> ~/.git-credentials If you don't want to store any credentials on the file system, you can store them in memory temporarily using `git-credential-cache`_ instead. If you setup fetching via SSH, you can use Git URL rewrite feature. The following command instructs Git to use SSH URLs for GitHub instead of HTTPS ones: .. code-block:: shell git config --global url."git@github.com:".insteadOf "path_to_url" .. _git-credential-store: path_to_url#_examples .. _git-credential-cache: path_to_url .. _personal access token: path_to_url Fetching via SSH ================ If your SSH key has no password, fetching should just work. If it does have a password, you can avoid entering it manually every time using `ssh-agent`_. On GitHub, see `Connecting to GitHub with SSH`_ for details on configuration and key creation. .. _ssh-agent: path_to_url .. _Connecting to GitHub with SSH: path_to_url Project locations ************* Projects can be located anywhere inside the workspace, but they may not "escape" it. In other words, project repositories need not be located in subdirectories of the manifest repository or as immediate subdirectories of the topdir. However, projects must have paths inside the workspace. You may replace a project's repository directory within the workspace with a symbolic link to elsewhere on your computer, but west will not do this for you. .. _west-topologies: Topologies supported ****************** The following are example source code topologies supported by west. - T1: star topology, zephyr is the manifest repository - T2: star topology, a Zephyr application is the manifest repository - T3: forest topology, freestanding manifest repository T1: Star topology, zephyr is the manifest repository ==================================================== - The zephyr repository acts as the central repository and specifies its :ref:`modules` in its :file:`west.yml` - Analogy with existing mechanisms: Git submodules with zephyr as the super-project This is the default. See :ref:`west-workspace` for how mainline Zephyr is an example of this topology. .. _west-t2: T2: Star topology, application is the manifest repository ========================================================= - Useful for those focused on a single application - A repository containing a Zephyr application acts as the central repository and names other projects required to build it in its :file:`west.yml`. This includes the zephyr repository and any modules. - Analogy with existing mechanisms: Git submodules with the application as the super-project, zephyr and other projects as submodules A workspace using this topology looks like this: .. code-block:: none west-workspace/ application/ # .git/ CMakeLists.txt prj.conf never modified by west src/ main.c west.yml # main manifest with optional import(s) and override(s) modules/ lib/ zcbor/ # .git/ project from either the main manifest or some import. zephyr/ # .git/ project west.yml # This can be partially imported with lower precedence or ignored. # Only the 'manifest-rev' version can be imported. Here is an example :file:`application/west.yml` which uses :ref:`west-manifest-import`, available since west 0.7, to import Zephyr v2.5.0 and its modules into the application manifest file: .. code-block:: yaml # Example T2 west.yml, using manifest imports. manifest: remotes: - name: zephyrproject-rtos url-base: path_to_url projects: - name: zephyr remote: zephyrproject-rtos revision: v2.5.0 import: true self: path: application You can still selectively "override" individual Zephyr modules if you use ``import:`` in this way; see :ref:`west-manifest-ex1.3` for an example. Another way to do the same thing is to copy/paste :file:`zephyr/west.yml` to :file:`application/west.yml`, adding an entry for the zephyr project itself, like this: .. code-block:: yaml # Equivalent to the above, but with manually maintained Zephyr modules. manifest: remotes: - name: zephyrproject-rtos url-base: path_to_url defaults: remote: zephyrproject-rtos projects: - name: zephyr revision: v2.5.0 west-commands: scripts/west-commands.yml - name: net-tools revision: some-sha-goes-here path: tools/net-tools # ... other Zephyr modules go here ... self: path: application (The ``west-commands`` is there for :ref:`west-build-flash-debug` and other Zephyr-specific :ref:`west-extensions`. It's not necessary when using ``import``.) The main advantage to using ``import`` is not having to track the revisions of imported projects separately. In the above example, using ``import`` means Zephyr's :ref:`module <modules>` versions are automatically determined from the :file:`zephyr/west.yml` revision, instead of having to be copy/pasted (and maintained) on their own. T3: Forest topology =================== - Useful for those supporting multiple independent applications or downstream distributions with no "central" repository - A dedicated manifest repository which contains no Zephyr source code, and specifies a list of projects all at the same "level" - Analogy with existing mechanisms: Google repo-based source distribution A workspace using this topology looks like this: .. code-block:: none west-workspace/ app1/ # .git/ project CMakeLists.txt prj.conf src/ main.c app2/ # .git/ project CMakeLists.txt prj.conf src/ main.c manifest-repo/ # .git/ never modified by west west.yml # main manifest with optional import(s) and override(s) modules/ lib/ zcbor/ # .git/ project from either the main manifest or # from some import zephyr/ # .git/ project west.yml # This can be partially imported with lower precedence or ignored. # Only the 'manifest-rev' version can be imported. Here is an example T3 :file:`manifest-repo/west.yml` which uses :ref:`west-manifest-import`, available since west 0.7, to import Zephyr v2.5.0 and its modules, then add the ``app1`` and ``app2`` projects: .. code-block:: yaml manifest: remotes: - name: zephyrproject-rtos url-base: path_to_url - name: your-git-server url-base: path_to_url defaults: remote: your-git-server projects: - name: zephyr remote: zephyrproject-rtos revision: v2.5.0 import: true - name: app1 revision: SOME_SHA_OR_BRANCH_OR_TAG - name: app2 revision: ANOTHER_SHA_OR_BRANCH_OR_TAG self: path: manifest-repo You can also do this "by hand" by copy/pasting :file:`zephyr/west.yml` as shown :ref:`above <west-t2>` for the T2 topology, with the same caveats. ```	/content/code_sandbox/doc/develop/west/workspaces.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,545
```restructuredtext .. _west-config: Configuration ############# This page documents west's configuration file system, the ``west config`` command, and configuration options used by built-in commands. For API documentation on the ``west.configuration`` module, see :ref:`west-apis-configuration`. West Configuration Files ------------------------ West's configuration file syntax is INI-like; here is an example file: .. code-block:: ini [manifest] path = zephyr [zephyr] base = zephyr Above, the ``manifest`` section has option ``path`` set to ``zephyr``. Another way to say the same thing is that ``manifest.path`` is ``zephyr`` in this file. There are three types of configuration file: 1. System: Settings in this file affect west's behavior for every user logged in to the computer. Its location depends on the platform: - Linux: :file:`/etc/westconfig` - macOS: :file:`/usr/local/etc/westconfig` - Windows: :file:`%PROGRAMDATA%\\west\\config` 2. Global (per user): Settings in this file affect how west behaves when run by a particular user on the computer. - All platforms: the default is :file:`.westconfig` in the user's home directory. - Linux note: if the environment variable ``XDG_CONFIG_HOME`` is set, then :file:`$XDG_CONFIG_HOME/west/config` is used. - Windows note: the following environment variables are tested to find the home directory: ``%HOME%``, then ``%USERPROFILE%``, then a combination of ``%HOMEDRIVE%`` and ``%HOMEPATH%``. 3. Local: Settings in this file affect west's behavior for the current :term:`west workspace`. The file is :file:`.west/config`, relative to the workspace's root directory. A setting in a file which appears lower down on this list overrides an earlier setting. For example, if ``color.ui`` is ``true`` in the system's configuration file, but ``false`` in the workspace's, then the final value is ``false``. Similarly, settings in the user configuration file override system settings, and so on. .. _west-config-cmd: west config ----------- The built-in ``config`` command can be used to get and set configuration values. You can pass ``west config`` the options ``--system``, ``--global``, or ``--local`` to specify which configuration file to use. Only one of these can be used at a time. If none is given, then writes default to ``--local``, and reads show the final value after applying overrides. Some examples for common uses follow; run ``west config -h`` for detailed help, and see :ref:`west-config-index` for more details on built-in options. To set ``manifest.path`` to :file:`some-other-manifest`: .. code-block:: console west config manifest.path some-other-manifest Doing the above means that commands like ``west update`` will look for the :term:`west manifest` inside the :file:`some-other-manifest` directory (relative to the workspace root directory) instead of the directory given to ``west init``, so be careful! To read ``zephyr.base``, the value which will be used as ``ZEPHYR_BASE`` if it is unset in the calling environment (also relative to the workspace root): .. code-block:: console west config zephyr.base You can switch to another zephyr repository without changing ``manifest.path`` -- and thus the behavior of commands like ``west update`` -- using: .. code-block:: console west config zephyr.base some-other-zephyr This can be useful if you use commands like ``git worktree`` to create your own zephyr directories, and want commands like ``west build`` to use them instead of the zephyr repository specified in the manifest. (You can go back to using the directory in the upstream manifest by running ``west config zephyr.base zephyr``.) To set ``color.ui`` to ``false`` in the global (user-wide) configuration file, so that west will no longer print colored output for that user when run in any workspace: .. code-block:: console west config --global color.ui false To undo the above change: .. code-block:: console west config --global color.ui true .. _west-config-index: Built-in Configuration Options ------------------------------ The following table documents configuration options supported by west's built-in commands. Configuration options supported by Zephyr's extension commands are documented in the pages for those commands. .. NOTE: docs authors: keep this table sorted by section, then option. .. list-table:: :widths: 10 30 :header-rows: 1 * - Option - Description * - ``color.ui`` - Boolean. If ``true`` (the default), then west output is colorized when stdout is a terminal. * - ``commands.allow_extensions`` - Boolean, default ``true``, disables :ref:`west-extensions` if ``false`` * - ``grep.color`` - String, default empty. Set this to ``never`` to disable ``west grep`` color output. If set, ``west grep`` passes the value to the grep tool's ``--color`` option. * - ``grep.tool`` - String, one of ``"git-grep"`` (default), ``"ripgrep"``, or ``"grep"``. The grep tool that ``west grep`` should use. * - ``grep.<TOOL>-args`` - String, default empty. The ``<TOOL>`` part is a pattern that can be any ``grep.tool`` value, so ``grep.ripgrep-args`` is an example configuration option. If set, arguments that ``west grep`` should pass to the corresponding grep tool. Run ``west help grep`` for details. * - ``grep.<TOOL>-path`` - String, default empty. The ``<TOOL>`` part is a pattern that can be any ``grep.tool`` value, so ``grep.ripgrep-path`` is an example configuration option. The path to the corresponding tool that ``west grep`` should use instead of searching for the command. Run ``west help grep`` for details. * - ``manifest.file`` - String, default ``west.yml``. Relative path from the manifest repository root directory to the manifest file used by ``west init`` and other commands which parse the manifest. * - ``manifest.group-filter`` - String, default empty. A comma-separated list of project groups to enable and disable within the workspace. Prefix enabled groups with ``+`` and disabled groups with ``-``. For example, the value ``"+foo,-bar"`` enables group ``foo`` and disables ``bar``. See :ref:`west-manifest-groups`. * - ``manifest.path`` - String, relative path from the :term:`west workspace` root directory to the manifest repository used by ``west update`` and other commands which parse the manifest. Set locally by ``west init``. * - ``manifest.project-filter`` - Comma-separated list of strings. The option's value is a comma-separated list of regular expressions, each prefixed with ``+`` or ``-``, like this: .. code-block:: none +re1,-re2,-re3 Project names are matched against each regular expression (``re1``, ``re2``, ``re3``, ...) in the list, in order. If the entire project name matches the regular expression, that element of the list either deactivates or activates the project. The project is deactivated if the element begins with ``-``. The project is activated if the element begins with ``+``. (Project names cannot contain ``,`` if this option is used, so the regular expressions do not need to contain a literal ``,`` character.) If a project's name matches multiple regular expressions in the list, the result from the last regular expression is used. For example, if ``manifest.project-filter`` is: .. code-block:: none -hal_.,+hal_foo Then a project named ``hal_bar`` is inactive, but a project named ``hal_foo`` is active. If a project is made inactive or active by a list element, the project is active or not regardless of whether any or all of its groups are disabled. (This is currently the only way to make a project that has no groups inactive.) Otherwise, i.e. if a project does not match any regular expressions in the list, it is active or inactive according to the usual rules related to its groups (see :ref:`west-project-group-examples` for examples in that case). Within an element of a ``manifest.project-filter`` list, leading and trailing whitespace are ignored. That means these example values are equivalent: .. code-block:: none +foo,-bar +foo , -bar Any empty elements are ignored. That means these example values are equivalent: .. code-block:: none +foo,,-bar +foo,-bar - ``update.fetch`` - String, one of ``"smart"`` (the default behavior starting in v0.6.1) or ``"always"`` (the previous behavior). If set to ``"smart"``, the :ref:`west-update` command will skip fetching from project remotes when those projects' revisions in the manifest file are SHAs or tags which are already available locally. The ``"always"`` behavior is to unconditionally fetch from the remote. * - ``update.name-cache`` - String. If non-empty, ``west update`` will use its value as the ``--name-cache`` option's value if not given on the command line. * - ``update.narrow`` - Boolean. If ``true``, ``west update`` behaves as if ``--narrow`` was given on the command line. The default is ``false``. * - ``update.path-cache`` - String. If non-empty, ``west update`` will use its value as the ``--path-cache`` option's value if not given on the command line. * - ``update.sync-submodules`` - Boolean. If ``true`` (the default), :ref:`west-update` will synchronize Git submodules before updating them. * - ``zephyr.base`` - String, default value to set for the :envvar:`ZEPHYR_BASE` environment variable while the west command is running. By default, this is set to the path to the manifest project with path :file:`zephyr` (if there is one) during ``west init``. If the variable is already set, then this setting is ignored unless ``zephyr.base-prefer`` is ``"configfile"``. * - ``zephyr.base-prefer`` - String, one the values ``"env"`` and ``"configfile"``. If set to ``"env"`` (the default), setting :envvar:`ZEPHYR_BASE` in the calling environment overrides the value of the ``zephyr.base`` configuration option. If set to ``"configfile"``, the configuration option wins instead. ```	/content/code_sandbox/doc/develop/west/config.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,544
```restructuredtext .. _west-release-notes: West Release Notes ################## v1.2.0 ****** Major changes: - New ``west grep`` command for running a "grep tool" in your west workspace's repositories. Currently, ``git grep``, `ripgrep`_, and standard ``grep`` are supported grep tools. To run this command to get ``git grep foo`` results from all cloned, active repositories, run: .. code-block:: console west grep foo Here are some other examples for running different grep commands with ``west grep``: .. list-table:: * - ``git grep --untracked`` - ``west grep --untracked foo`` * - ``ripgrep`` - ``west grep --tool ripgrep foo`` * - ``grep --recursive`` - ``west grep --tool grep foo`` To switch the default grep tool in your workspace, run the appropriate command in this table: .. list-table:: * - ``ripgrep`` - ``west config grep.tool ripgrep`` * - ``grep`` - ``west config grep.tool grep`` For more details, run ``west help grep``. Other changes: - The manifest file format now supports a ``description`` field in each ``projects:`` element. See :ref:`west-manifests-projects` for examples. - ``west list --format`` now accepts ``{description}`` in the format string, which prints the project's ``description:`` value. - ``west compare`` now always prints information about :ref:`west-manifest-rev`. Bug fixes: - ``west init`` aborts if the destination directory already exists. API changes: - ``west.commands.WestCommand`` methods ``check_call()`` and ``check_output()`` now take any kwargs that can be passed on to the underlying subprocess function. - ``west.commands.WestCommand.run_subprocess()``: new wrapper around ``subprocess.run()``. This could not be named ``run()`` because ``WestCommand`` already had a method by this name. - ``west.commands.WestCommand`` methods ``dbg()``, ``inf()``, ``wrn()``, and ``err()`` now all take an ``end`` kwarg, which is passed on to the call to ``print()``. - ``west.manifest.Project`` now has a ``description`` attribute, which contains the parsed value of the ``description:`` field in the manifest data. .. _ripgrep: path_to_url#readme v1.1.0 **** Major changes: - ``west compare``: new command that compares the state of the workspace against the manifest. - Support for a new ``manifest.project-filter`` configuration option. See :ref:`west-config-index` for details. The ``west manifest --freeze`` and ``west manifest --resolve`` commands currently cannot be used when this option is set. This restriction can be removed in a later release. - Project names which contain comma (``,``) or whitespace now generate warnings. These warnings are errors if the new ``manifest.project-filter`` configuration option is set. The warnings may be promoted to errors in a future major version of west. Other changes: - ``west forall`` now takese a ``--group`` argument that can be used to restrict the command to only run in one or more groups. Run ``west help forall`` for details. - All west commands will now output log messages from west API modules at warning level or higher. In addition, the ``--verbose`` argument to west can be used once to include informational messages, or twice to include debug messages, from all commands. Bug fixes: - Various improvements to error messages, debug logging, and error handling. API changes: - ``west.manifest.Manifest.is_active()`` now respects the ``manifest.project-filter`` configuration option's value. v1.0.1 ** Major changes: - Manifest schema version "1.0" is now available for use in this release. This is identical to the "0.13" schema version in terms of features, but can be used by applications that do not wish to use a "0.x" manifest "version:" field. See :ref:`west-manifest-schema-version` for details on this feature. Bug fixes: - West no longer exits with a successful error code when sent an interrupt signal. Instead, it exits with a platform-specific error code and signals to the calling environment that the process was interrupted. v1.0.0 ** Major changes in this release: - The :ref:`west-apis` are now declared stable. Any breaking changes will be communicated by a major version bump from v1.x.y to v2.x.y. - West v1.0 no longer works with the Zephyr v1.14 LTS releases. This LTS has long been obsoleted by Zephyr v2.7 LTS. If you need to use Zephyr v1.14, you must use west v0.14 or earlier. - Like the rest of Zephyr, west now requires Python v3.8 or later - West commands no longer accept abbreviated command line arguments. For example, you must now specify ``west update --keep-descendants`` instead of using an abbreviation like ``west update --keep-d``. This is part of a change applied to all of Zephyr's Python scripts' command-line interfaces. The abbreviations were causing problems in practice when commands were updated to add new options with similar names but different behavior to existing ones. Other changes: - All built-in west functions have stopped using ``west.log`` - ``west update``: new ``--submodule-init-config`` option. See commit `9ba92b05`_ for details. Bug fixes: - West extension commands that failed to load properly sometimes dumped stack. This has been fixed and west now prints a sensible error message in this case. - ``west config`` now fails on malformed configuration option arguments which lack a ``.`` in the option name API changes: - The west package now contains the metadata files necessary for some static analyzers (such as `mypy`_) to auto-detect its type annotations. See commit `d9f00e24`_ for details. - the deprecated ``west.build`` module used for Zephyr v1.14 LTS compatibility was removed - the deprecated ``west.cmake`` module used for Zephyr v1.14 LTS compatibility was removed - the ``west.log`` module is now deprecated. This module uses global state, which can make it awkward to use it as an API which multiple different python modules may rely on. - The :ref:`west-apis-commands` module got some new APIs which lay groundwork for a future change to add a global verbosity control to a command's output, and work to remove global state from the ``west`` package's API: - New ``west.commands.WestCommand.__init__()`` keyword argument: ``verbosity`` - New ``west.commands.WestCommand`` property: ``color_ui`` - New ``west.commands.WestCommand`` methods, which should be used to print output from extension commands instead of writing directly to sys.stdout or sys.stderr: ``inf()``, ``wrn()``, ``err()``, ``die()``, ``banner()``, ``small_banner()`` - New ``west.commands.VERBOSITY`` enum .. _9ba92b05: path_to_url .. _d9f00e24: path_to_url .. _mypy: path_to_url v0.14.0 *** Bug fixes: - West commands that were run with a bad local configuration file dumped stack in a confusing way. This has been fixed and west now prints a sensible error message in this case. - A bug in the way west looks for the zephyr repository was fixed. The bug itself usually appeared when running an extension command like ``west build`` in a new workspace for the first time; this used to fail (just for the first time, not on subsequent command invocations) unless you ran the command in the workspace's top level directory. - West now prints sensible error messages when the user lacks permission to open the manifest file instead of dumping stack traces. API changes: - The ``west.manifest.MalformedConfig`` exception type has been moved to the ``west.configuration`` module - The ``west.manifest.MalformedConfig`` exception type has been moved to the :ref:`west.configuration <west-apis-configuration>` module - The ``west.configuration.Configuration`` class now raises ``MalformedConfig`` instead of ``RuntimeError`` in some cases v0.13.1 *** Bug fix: - When calling west.manifest.Manifest.from_file() when outside of a workspace, west again falls back on the ZEPHYR_BASE environment variable to locate the workspace. v0.13.0 *** New features: - You can now associate arbitrary user data with the manifest repository itself in the ``manifest: self: userdata:`` value, like so: .. code-block:: YAML manifest: self: userdata: <any YAML value can go here> Bug fixes: - The path to the manifest repository reported by west could be incorrect in certain circumstances detailed in [issue #572](path_to_url This has been fixed as part of a larger overhaul of path handling support in the ``west.manifest`` API module. - The ``west.Manifest.ManifestProject.__repr__`` return value was fixed :ref:`API <west-apis>` changes: - ``west.configuration.Configuration``: new object-oriented interface to the current configuration. This reflects the system, global, and workspace-local configuration values, and allows you to read, write, and delete configuration options from any or all of these locations. - ``west.commands.WestCommand``: - ``config``: new attribute, returns a ``Configuration`` object or aborts the program if none is set. This is always usable from within extension command ``do_run()`` implementations. - ``has_config``: new boolean attribute, which is ``True`` if and only if reading ``self.config`` will abort the program. - The path handling in the ``west.manifest`` package has been overhauled in a backwards-incompatible way. For more details, see commit [56cfe8d1d1](path_to_url - ``west.manifest.Manifest.validate()``: this now returns the validated data as a Python dict. This can be useful if the value passed to this function was a str, and the dict is desired. - ``west.manifest.Manifest``: new: - path attributes ``abspath``, ``posixpath``, ``relative_path``, ``yaml_path``, ``repo_path``, ``repo_posixpath`` - ``userdata`` attribute, which contains the parsed value from ``manifest: self: userdata:``, or is None - ``from_topdir()`` factory method - ``west.manifest.ManifestProject``: new ``userdata`` attribute, which also contains the parsed value from ``manifest: self: userdata:``, or is None - ``west.manifest.ManifestImportFailed``: the constructor can now take any value; this can be used to reflect failed imports from a :ref:`map <west-manifest-import-map>` or other compound value. - Deprecated configuration APIs: The following APIs are now deprecated in favor of using a ``Configuration`` object. Usually this will be done via ``self.config`` from a ``WestCommand`` instance, but this can be done directly by instantiating a ``Configuration`` object for other usages. - ``west.configuration.config`` - ``west.configuration.read_config`` - ``west.configuration.update_config`` - ``west.configuration.delete_config`` v0.12.0 *** New features: - West now works on the `MSYS2 <path_to_url`_ platform. - West manifest files can now contain arbitrary user data associated with each project. See :ref:`west-project-userdata` for details. Bug fixes: - The ``west list`` command's ``{sha}`` format key has been fixed for the manifest repository; it now prints ``N/A`` ("not applicable") as expected. :ref:`API <west-apis>` changes: - The ``west.manifest.Project.userdata`` attribute was added to support project user data. v0.11.1 *** New features: - ``west status`` now only prints output for projects which have a nonempty status. Bug fixes: - The manifest file parser was incorrectly allowing project names which contain the path separator characters ``/`` and ``\``. These invalid characters are now rejected. Note: if you need to place a project within a subdirectory of the workspace topdir, use the ``path:`` key. If you need to customize a project's fetch URL relative to its remote ``url-base:``, use ``repo-path:``. See :ref:`west-manifests-projects` for examples. - The changes made in west v0.10.1 to the ``west init --manifest-rev`` option which selected the default branch name were leaving the manifest repository in a detached HEAD state. This has been fixed by using ``git clone`` internally instead of ``git init`` and ``git fetch``. See `issue #522`_ for details. - The ``WEST_CONFIG_LOCAL`` environment variable now correctly overrides the default location, :file:`<workspace topdir>/.west/config`. - ``west update --fetch=smart`` (``smart`` is the default) now correctly skips fetches for project revisions which are `lightweight tags`_ (it already worked correctly for annotated tags; only lightweight tags were unnecessarily fetched). Other changes: - The fix for issue #522 mentioned above introduces a new restriction. The ``west init --manifest-rev`` option value, if given, must now be either a branch or a tag. In particular, "pseudo-branches" like GitHub's ``pull/1234/head`` references which could previously be used to fetch a pull request can no longer be passed to ``--manifest-rev``. Users must now fetch and check out such revisions manually after running ``west init``. :ref:`API <west-apis>` changes: - ``west.manifest.Manifest.get_projects()`` avoids incorrect results in some edge cases described in `issue #523`_. - ``west.manifest.Project.sha()`` now works correctly for tag revisions. (This applies to both lightweight and annotated tags.) .. _lightweight tags: path_to_url .. _issue #522: path_to_url .. _issue #523: path_to_url v0.11.0 *** New features: - ``west update`` now supports ``--narrow``, ``--name-cache``, and ``--path-cache`` options. These can be influenced by the ``update.narrow``, ``update.name-cache``, and ``update.path-cache`` :ref:`west-config` options. These can be used to optimize the speed of the update. - ``west update`` now supports a ``--fetch-opt`` option that will be passed to the ``git fetch`` command used to fetch remote revisions when updating each project. Bug fixes: - ``west update`` now synchronizes Git submodules in projects by default. This avoids issues if the URL changes in the manifest file from when the submodule was first initialized. This behavior can be disabled by setting the ``update.sync-submodules`` configuration option to ``false``. Other changes: - the :ref:`west-apis-manifest` module has fixed docstrings for the Project class v0.10.1 *** New features: - The :ref:`west-init` command's ``--manifest-rev`` (``--mr``) option no longer defaults to ``master``. Instead, the command will query the repository for its default branch name and use that instead. This allows users to move from ``master`` to ``main`` without breaking scripts that do not provide this option. .. _west_0_10_0: v0.10.0 *** New features: - The ``name`` key in a project's :ref:`submodules list <west-manifest-submodules>` is now optional. Bug fixes: - West now checks that the manifest schema version is one of the explicitly allowed values documented in :ref:`west-manifest-schema-version`. The old behavior was just to check that the schema version was newer than the west version where the ``manifest: version:`` key was introduced. This incorrectly allowed invalid schema versions, like ``0.8.2``. Other changes: - A manifest file's ``group-filter`` is now propagated through an ``import``. This is a change from how west v0.9.x handled this. In west v0.9.x, only the top level manifest file's ``group-filter`` had any effect; the group filter lists from any imported manifests were ignored. Starting with west v0.10.0, the group filter lists from imported manifests are also imported. For details, see :ref:`west-group-filter-imports`. The new behavior will take effect if ``manifest: version:`` is not given or is at least ``0.10``. The old behavior is still available in the top level manifest file only with an explicit ``manifest: version: 0.9``. See :ref:`west-manifest-schema-version` for more information on schema versions. See `west pull request #482 <path_to_url`_ for the motivation for this change and additional context. v0.9.1 ** Bug fixes: - Commands like ``west manifest --resolve`` now correctly include group and group filter information. Other changes: - West now warns if you combine ``import`` with ``group-filter``. Semantics for this combination have changed starting with v0.10.x. See the v0.10.0 release notes above for more information. .. _west_0_9_0: v0.9.0 ** .. warning:: The ``west config`` fix described below comes at a cost: any comments or other manual edits in configuration files will be removed when setting a configuration option via that command or the ``west.configuration`` API. .. warning:: Combining the ``group-filter`` feature introduced in this release with manifest imports is discouraged. The resulting behavior has changed in west v0.10. New features: - West manifests now support :ref:`west-manifest-submodules`. This allows you to clone `Git submodules <path_to_url`_ into a west project repository in addition to the project repository itself. - West manifests now support :ref:`west-manifest-groups`. Project groups can be enabled and disabled to determine what projects are "active", and therefore will be acted upon by the following commands: ``west update``, ``west list``, ``west diff``, ``west status``, ``west forall``. - ``west update`` no longer updates inactive projects by default. It now supports a ``--group-filter`` option which allows for one-time modifications to the set of enabled and disabled project groups. - Running ``west list``, ``west diff``, ``west status``, or ``west forall`` with no arguments does not print information for inactive projects by default. If the user specifies a list of projects explicitly at the command line, output for them is included regardless of whether they are active. These commands also now support ``--all`` arguments to include all projects, even inactive ones. - ``west list`` now supports a ``{groups}`` format string key in its ``--format`` argument. Bug fixes: - The ``west config`` command and ``west.configuration`` API did not correctly store some configuration values, such as strings which contain commas. This has been fixed; see `commit 36f3f91e <path_to_url`_ for details. - A manifest file with an empty ``manifest: self: path:`` value is invalid, but west used to let it pass silently. West now rejects such manifests. - A bug affecting the behavior of the ``west init -l .`` command was fixed; see `issue #435 <path_to_url`_. :ref:`API <west-apis>` changes: - added ``west.manifest.Manifest.is_active()`` - added ``west.manifest.Manifest.group_filter`` - added ``submodules`` attribute to ``west.manifest.Project``, which has newly added type ``west.manifest.Submodule`` Other changes: - The :ref:`west-manifest-import` feature now supports the terms ``allowlist`` and ``blocklist`` instead of ``whitelist`` and ``blacklist``, respectively. The old terms are still supported for compatibility, but the documentation has been updated to use the new ones exclusively. v0.8.0 ** This is a feature release which changes the manifest schema by adding support for a ``path-prefix:`` key in an ``import:`` mapping, along with some other features and fixes. - Manifest import mappings now support a ``path-prefix:`` key, which places the project and its imported repositories in a subdirectory of the workspace. See :ref:`west-manifest-ex3.4` for an example. - The west command line application can now also be run using ``python3 -m west``. This makes it easier to run west under a particular Python interpreter without modifying the :envvar:`PATH` environment variable. - :ref:`west manifest --path <west-manifest-path>` prints the absolute path to west.yml - ``west init`` now supports an ``--mf foo.yml`` option, which initializes the workspace using :file:`foo.yml` instead of :file:`west.yml`. - ``west list`` now prints the manifest repository's path using the ``manifest.path`` :ref:`configuration option <west-config>`, which may differ from the ``self: path:`` value in the manifest data. The old behavior is still available, but requires passing a new ``--manifest-path-from-yaml`` option. - Various Python API changes; see :ref:`west-apis` for details. v0.7.3 ** This is a bugfix release. - Fix an error where a failed import could leave the workspace in an unusable state (see [PR #415](path_to_url for details) v0.7.2 ** This is a bugfix and minor feature release. - Filter out duplicate extension commands brought in by manifest imports - Fix ``west.Manifest.get_projects()`` when finding the manifest repository by path v0.7.1 ** This is a bugfix and minor feature release. - ``west update --stats`` now prints timing for operations which invoke a subprocess, time spent in west's Python process for each project, and total time updating each project. - ``west topdir`` always prints a POSIX style path - minor console output changes v0.7.0 ** The main user-visible feature in west 0.7 is the :ref:`west-manifest-import` feature. This allows users to load west manifest data from multiple different files, resolving the results into a single logical manifest. Additional user-visible changes: - The idea of a "west installation" has been renamed to "west workspace" in this documentation and in the west API documentation. The new term seems to be easier for most people to work with than the old one. - West manifests now support a :ref:`schema version <west-manifest-schema-version>`. - The "west config" command can now be run outside of a workspace, e.g. to run ``west config --global section.key value`` to set a configuration option's value globally. - There is a new :ref:`west topdir <west-built-in-misc>` command, which prints the root directory of the current west workspace. - The ``west -vv init`` command now prints the git operations being performed, and their results. - The restriction that no project can be named "manifest" is now enforced; the name "manifest" is reserved for the manifest repository, and is usable as such in commands like ``west list manifest``, instead of ``west list path-to-manifest-repository`` being the only way to say that - It's no longer an error if there is no project named "zephyr". This is part of an effort to make west generally usable for non-Zephyr use cases. - Various bug fixes. The developer-visible changes to the :ref:`west-apis` are: - west.build and west.cmake: deprecated; this is Zephyr-specific functionality and should never have been part of west. Since Zephyr v1.14 LTS relies on it, it will continue to be included in the distribution, but will be removed when that version of Zephyr is obsoleted. - west.commands: - WestCommand.requires_installation: deprecated; use requires_workspace instead - WestCommand.requires_workspace: new - WestCommand.has_manifest: new - WestCommand.manifest: this is now settable - west.configuration: callers can now identify the workspace directory when reading and writing configuration files - west.log: - msg(): new - west.manifest: - The module now uses the standard logging module instead of west.log - QUAL_REFS_WEST: new - SCHEMA_VERSION: new - Defaults: removed - Manifest.as_dict(): new - Manifest.as_frozen_yaml(): new - Manifest.as_yaml(): new - Manifest.from_file() and from_data(): these factory methods are more flexible to use and less reliant on global state - Manifest.validate(): new - ManifestImportFailed: new - ManifestProject: semi-deprecated and will likely be removed later. - Project: the constructor now takes a topdir argument - Project.format() and its callers are removed. Use f-strings instead. - Project.name_and_path: new - Project.remote_name: new - Project.sha() now captures stderr - Remote: removed West now requires Python 3.6 or later. Additionally, some features may rely on Python dictionaries being insertion-ordered; this is only an implementation detail in CPython 3.6, but it is part of the language specification as of Python 3.7. v0.6.3 ** This point release fixes an error in the behavior of the deprecated ``west.cmake`` module. v0.6.2 ** This point release fixes an error in the behavior of ``west update --fetch=smart``, introduced in v0.6.1. All v0.6.1 users must upgrade. v0.6.1 ** .. warning:: Do not use this point release. Make sure to use v0.6.2 instead. The user-visible features in this point release are: - The :ref:`west-update` command has a new ``--fetch`` command line flag and ``update.fetch`` :ref:`configuration option <west-config>`. The default value, "smart", skips fetching SHAs and tags which are available locally. - Better and more consistent error-handling in the ``west diff``, ``west status``, ``west forall``, and ``west update`` commands. Each of these commands can operate on multiple projects; if a subprocess related to one project fails, these commands now continue to operate on the rest of the projects. All of them also now report a nonzero error code from the west process if any of these subprocesses fails (this was previously not true of ``west forall`` in particular). - The :ref:`west manifest <west-built-in-misc>` command also handles errors better. - The :ref:`west list <west-built-in-misc>` command now works even when the projects are not cloned, as long as its format string only requires information which can be read from the manifest file. It still fails if the format string requires data stored in the project repository, e.g. if it includes the ``{sha}`` format string key. - Commands and options which operate on git revisions now accept abbreviated SHAs. For example, ``west init --mr SHA_PREFIX`` now works. Previously, the ``--mr`` argument needed to be the entire 40 character SHA if it wasn't a branch or a tag. The developer-visible changes to the :ref:`west-apis` are: - west.log.banner(): new - west.log.small_banner(): new - west.manifest.Manifest.get_projects(): new - west.manifest.Project.is_cloned(): new - west.commands.WestCommand instances can now access the parsed Manifest object via a new self.manifest property during the do_run() call. If read, it returns the Manifest object or aborts the command if it could not be parsed. - west.manifest.Project.git() now has a capture_stderr kwarg v0.6.0 **** - No separate bootstrapper In west v0.5.x, the program was split into two components, a bootstrapper and a per-installation clone. See `Multiple Repository Management in the v1.14 documentation`_ for more details. This is similar to how Google's Repo tool works, and lets west iterate quickly at first. It caused confusion, however, and west is now stable enough to be distributed entirely as one piece via PyPI. From v0.6.x onwards, all of the core west commands and helper classes are part of the west package distributed via PyPI. This eliminates complexity and makes it possible to import west modules from anywhere in the system, not just extension commands. - The ``selfupdate`` command still exists for backwards compatibility, but now simply exits after printing an error message. - Manifest syntax changes - A west manifest file's ``projects`` elements can now specify their fetch URLs directly, like so: .. code-block:: yaml manifest: projects: - name: example-project-name url: path_to_url Project elements with ``url`` attributes set in this way may not also have ``remote`` attributes. - Project names must be unique: this restriction is needed to support future work, but was not possible in west v0.5.x because distinct projects may have URLs with the same final pathname component, like so: .. code-block:: yaml manifest: remotes: - name: remote-1 url-base: path_to_url - name: remote-2 url-base: path_to_url projects: - name: project remote: remote-1 path: remote-1-project - name: project remote: remote-2 path: remote-2-project These manifests can now be written with projects that use ``url`` instead of ``remote``, like so: .. code-block:: yaml manifest: projects: - name: remote-1-project url: path_to_url - name: remote-2-project url: path_to_url - The ``west list`` command now supports a ``{sha}`` format string key - The default format string for ``west list`` was changed to ``"{name:12} {path:28} {revision:40} {url}"``. - The command ``west manifest --validate`` can now be run to load and validate the current manifest file, among other error-handling fixes related to manifest parsing. - Incompatible API changes were made to west's APIs. Further changes are expected until API stability is declared in west v1.0. - The ``west.manifest.Project`` constructor's ``remote`` and ``defaults`` positional arguments are now kwargs. A new ``url`` kwarg was also added; if given, the ``Project`` URL is set to that value, and the ``remote`` kwarg is ignored. - ``west.manifest.MANIFEST_SECTIONS`` was removed. There is only one section now, namely ``manifest``. The sections kwargs in the ``west.manifest.Manifest`` factory methods and constructor were also removed. - The ``west.manifest.SpecialProject`` class was removed. Use ``west.manifest.ManifestProject`` instead. v0.5.x **** West v0.5.x is the first version used widely by the Zephyr Project as part of its v1.14 Long-Term Support (LTS) release. The `west v0.5.x documentation`_ is available as part of the Zephyr's v1.14 documentation. West's main features in v0.5.x are: - Multiple repository management using Git repositories, including self-update of west itself - Hierarchical configuration files - Extension commands Versions Before v0.5.x ******************** Tags in the west repository before v0.5.x are prototypes which are of historical interest only. .. _Multiple Repository Management in the v1.14 documentation: path_to_url .. _west v0.5.x documentation: path_to_url ```	/content/code_sandbox/doc/develop/west/release-notes.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	7,345
```restructuredtext .. _west-basics: Basics ###### This page introduces west's basic concepts and provides references to further reading. West's built-in commands allow you to work with :term:`projects <west project>` (Git repositories) under a common :term:`workspace <west workspace>` directory. West works in the following manner: the ``west init`` command creates the :term:`west workspace`, and clones the :term:`manifest repo <west manifest repository>`, while the ``west update`` command initially clones, and later updates, the :term:`projects <west project>` listed in the manifest in the workspace. Example workspace *************** If you've followed the :ref:`getting_started`, your local :term:`west workspace`, which in this case is the folder named :file:`zephyrproject` as well as all its subfolders, looks like this: .. code-block:: none zephyrproject/ # west topdir .west/ # marks the location of the topdir config # per-workspace local configuration file # The manifest repository, never modified by west after creation: zephyr/ # .git/ repo west.yml # manifest file [... other files ...] # Projects managed by west: modules/ lib/ zcbor/ # .git/ project net-tools/ # .git/ project [ ... other projects ...] .. _west-workspace: Workspace concepts **************** Here are the basic concepts you should understand about this structure. Additional details are in :ref:`west-workspaces`. topdir Above, :file:`zephyrproject` is the name of the workspace's top level directory, or topdir. (The name :file:`zephyrproject` is just an example -- it could be anything, like ``z``, ``my-zephyr-workspace``, etc.) You'll typically create the topdir and a few other files and directories using :ref:`west init <west-init-basics>`. .west directory The topdir contains the :file:`.west` directory. When west needs to find the topdir, it searches for :file:`.west`, and uses its parent directory. The search starts from the current working directory (and starts again from the location in the :envvar:`ZEPHYR_BASE` environment variable as a fallback if that fails). configuration file The file :file:`.west/config` is the workspace's :ref:`local configuration file <west-config>`. manifest repository Every west workspace contains exactly one manifest repository, which is a Git repository containing a manifest file. The location of the manifest repository is given by the :ref:`manifest.path configuration option <west-config-index>` in the local configuration file. For upstream Zephyr, :file:`zephyr` is the manifest repository, but you can configure west to use any Git repository in the workspace as the manifest repository. The only requirement is that it contains a valid manifest file. See :ref:`west-topologies` for information on other options, and :ref:`west-manifests` for details on the manifest file format. manifest file The manifest file is a YAML file that defines projects, which are the additional Git repositories in the workspace managed by west. The manifest file is named :file:`west.yml` by default; this can be overridden using the ``manifest.file`` local configuration option. You use the :ref:`west update <west-update-basics>` command to update the workspace's projects based on the contents of the manifest file. projects Projects are Git repositories managed by west. Projects are defined in the manifest file and can be located anywhere inside the workspace. In the above example workspace, ``zcbor`` and ``net-tools`` are projects. By default, the Zephyr :ref:`build system <build_overview>` uses west to get the locations of all the projects in the workspace, so any code they contain can be used as :ref:`modules`. Note however that modules and projects :ref:`are conceptually different <modules-vs-projects>`. extensions Any repository known to west (either the manifest repository or any project repository) can define :ref:`west-extensions`. Extensions are extra west commands you can run when using that workspace. The zephyr repository uses this feature to provide Zephyr-specific commands like :ref:`west build <west-building>`. Defining these as extensions keeps west's core agnostic to the specifics of any workspace's Zephyr version, etc. ignored files A workspace can contain additional Git repositories or other files and directories not managed by west. West basically ignores anything in the workspace except :file:`.west`, the manifest repository, and the projects specified in the manifest file. west init and west update *********************** The two most important workspace-related commands are ``west init`` and ``west update``. .. _west-init-basics: ``west init`` basics -------------------- This command creates a west workspace. .. important:: West doesn't change your manifest repository contents after ``west init`` is run. Use ordinary Git commands to pull new versions, etc. You will typically run it once, like this: .. code-block:: shell west init -m path_to_url --mr v2.5.0 zephyrproject This will: #. Create the topdir, :file:`zephyrproject`, along with :file:`.west` and :file:`.west/config` inside it #. Clone the manifest repository from path_to_url placing it into :file:`zephyrproject/zephyr` #. Check out the ``v2.5.0`` git tag in your local zephyr clone #. Set ``manifest.path`` to ``zephyr`` in :file:`.west/config` #. Set ``manifest.file`` to ``west.yml`` Your workspace is now almost ready to use; you just need to run ``west update`` to clone the rest of the projects into the workspace to finish. For more details, see :ref:`west-init`. .. _west-update-basics: ``west update`` basics ---------------------- This command makes sure your workspace contains Git repositories matching the projects in the manifest file. .. important:: Whenever you check out a different revision in your manifest repository, you should run ``west update`` to make sure your workspace contains the project repositories the new revision expects. The ``west update`` command reads the manifest file's contents by: #. Finding the topdir. In the ``west init`` example above, that means finding :file:`zephyrproject`. #. Loading :file:`.west/config` in the topdir to read the ``manifest.path`` (e.g. ``zephyr``) and ``manifest.file`` (e.g. ``west.yml``) options. #. Loading the manifest file given by these options (e.g. :file:`zephyrproject/zephyr/west.yml`). It then uses the manifest file to decide where missing projects should be placed within the workspace, what URLs to clone them from, and what Git revisions should be checked out locally. Project repositories which already exist are updated in place by fetching and checking out their respective Git revisions in the manifest file. For more details, see :ref:`west-update`. Other built-in commands ******************* See :ref:`west-built-in-cmds`. .. _west-zephyr-extensions: Zephyr Extensions ************* See the following pages for information on Zephyr's extension commands: - :ref:`west-build-flash-debug` - :ref:`west-sign` - :ref:`west-zephyr-ext-cmds` - :ref:`west-shell-completion` Troubleshooting ************* See :ref:`west-troubleshooting`. ```	/content/code_sandbox/doc/develop/west/basics.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,727
```restructuredtext .. _no-west: Using Zephyr without west ######################### This page provides information on using Zephyr without west. This is not recommended for beginners due to the extra effort involved. In particular, you will have to do work "by hand" to replace these features: - cloning the additional source code repositories used by Zephyr in addition to the main zephyr repository, and keeping them up to date - specifying the locations of these repositories to the Zephyr build system - flashing and debugging without understanding detailed usage of the relevant host tools .. note:: If you have previously installed west and want to stop using it, uninstall it first: .. code-block:: console pip3 uninstall west Otherwise, Zephyr's build system will find it and may try to use it. Getting the Source ------------------ In addition to downloading the zephyr source code repository itself, you will need to manually clone the additional projects listed in the :term:`west manifest` file inside that repository. .. code-block:: console mkdir zephyrproject cd zephyrproject git clone path_to_url # clone additional repositories listed in zephyr/west.yml, # and check out the specified revisions as well. As you pull changes in the zephyr repository, you will also need to maintain those additional repositories, adding new ones as necessary and keeping existing ones up to date at the latest revisions. Building applications --------------------- You can build a Zephyr application using CMake and Ninja (or make) directly without west installed if you specify any modules manually. .. zephyr-app-commands:: :zephyr-app: samples/hello_world :tool: cmake :goals: build :gen-args: -DZEPHYR_MODULES=module1;module2;... :compact: When building with west installed, the Zephyr build system will use it to set :ref:`ZEPHYR_MODULES <important-build-vars>`. If you don't have west installed and your application does not need any of these repositories, the build will still work. If you don't have west installed and your application does need one of these repositories, you must set :makevar:`ZEPHYR_MODULES` yourself as shown above. See :ref:`modules` for more details. Similarly, if your application requires binary blobs and you are not using west, you will need to download and place those blobs in the right places instead of using ``west blobs``. See :ref:`bin-blobs` for more details. Flashing and Debugging ---------------------- Running build system targets like ``ninja flash``, ``ninja debug``, etc. is just a call to the corresponding :ref:`west command <west-build-flash-debug>`. For example, ``ninja flash`` calls ``west flash``\ [#wbninja]_. If you don't have west installed on your system, running those targets will fail. You can of course still flash and debug using any :ref:`flash-debug-host-tools` which work for your board (and which those west commands wrap). If you want to use these build system targets but do not want to install west on your system using ``pip``, it is possible to do so by manually creating a :term:`west workspace`: .. code-block:: console # cd into zephyrproject if not already there git clone path_to_url .west/west Then create a file :file:`.west/config` with the following contents: .. code-block:: none [manifest] path = zephyr [zephyr] base = zephyr After that, and in order for ``ninja`` to be able to invoke ``west`` to flash and debug, you must specify the west directory. This can be done by setting the environment variable ``WEST_DIR`` to point to :file:`zephyrproject/.west/west` before running CMake to set up a build directory. .. rubric:: Footnotes .. [#wbninja] Note that ``west build`` invokes ``ninja``, among other tools. There's no recursive invocation of either ``west`` or ``ninja`` involved by default, however, as ``west build`` does not invoke ``ninja flash``, ``debug``, etc. The one exception is if you specifically run one of these build system targets with a command line like ``west build -t flash``. In that case, west is run twice: once for ``west build``, and in a subprocess, again for ``west flash``. Even in this case, ``ninja`` is only run once, as ``ninja flash``. This is because these build system targets depend on an up to date build of the Zephyr application, so it's compiled before ``west flash`` is run. ```	/content/code_sandbox/doc/develop/west/without-west.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,069
```restructuredtext :orphan: .. _west-apis: .. _west-apis-west: .. _west-apis-commands: .. _west-apis-westcommand: .. _west-apis-configuration: .. _west-apis-log: .. _west-apis-manifest: .. _west-apis-util: West APIs ######### The west APIs are not documented since either west was missing or the zephyr repository was not initialized using west during the documentation build. ```	/content/code_sandbox/doc/develop/west/west-not-found.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	97
```restructuredtext :orphan: .. _west-apis: .. _west-apis-west: West APIs ######### This page documents the Python APIs provided by :ref:`west <west>`, as well as some additional APIs used by the :ref:`west extensions <west-extensions>` in the zephyr repository. Contents: .. contents:: :local: .. NOTE: documentation authors: 1. keep these sorted by package/module name. 2. if you add a :ref: target here, add it to west-not-found.rst too. .. _west-apis-commands: west.commands ************* .. module:: west.commands All built-in and extension commands are implemented as subclasses of the :py:class:`WestCommand` class defined here. Some exception types are also provided. WestCommand =========== .. autoclass:: west.commands.WestCommand Instance attributes: .. py:attribute:: name As passed to the constructor. .. py:attribute:: help As passed to the constructor. .. py:attribute:: description As passed to the constructor. .. py:attribute:: accepts_unknown_args As passed to the constructor. .. py:attribute:: requires_workspace As passed to the constructor. .. versionadded:: 0.7.0 .. py:attribute:: parser The argument parser created by calling ``WestCommand.add_parser()``. Instance properties: .. py:attribute:: manifest A property which returns the :py:class:`west.manifest.Manifest` instance for the current manifest file or aborts the program if one was not provided. This is only safe to use from the ``do_run()`` method. .. versionadded:: 0.6.1 .. versionchanged:: 0.7.0 This is now settable. .. py:attribute:: has_manifest True if reading the manifest property will succeed instead of erroring out. .. py:attribute:: config A settable property which returns the :py:class:`west.configuration.Configuration` instance or aborts the program if one was not provided. This is only safe to use from the ``do_run()`` method. .. versionadded:: 0.13.0 .. py:attribute:: has_config True if reading the config property will succeed instead of erroring out. .. versionadded:: 0.13.0 .. py:attribute:: git_version_info A tuple of Git version information. .. versionadded:: 0.11.0 .. py:attribute:: color_ui True if the west configuration permits colorized output, False otherwise. .. versionadded:: 1.0.0 Constructor: .. automethod:: __init__ .. versionadded:: 0.6.0 The requires_installation parameter (removed in v0.13.0). .. versionadded:: 0.7.0 The requires_workspace parameter. .. versionchanged:: 0.8.0 The topdir parameter can now be any ``os.PathLike``. .. versionchanged:: 0.13.0 The deprecated requires_installation parameter was removed. .. versionadded:: 1.0.0 The verbosity parameter. Methods: .. automethod:: run .. versionchanged:: 0.6.0 The topdir argument was added. .. automethod:: add_parser .. automethod:: add_pre_run_hook .. versionadded:: 1.0.0 .. NOTE: the following 'method' (not 'automethod') directives were added for expediency during the west v1.2 release time frame to work around a build failure in this zephyr documentation that could not be fixed without cutting a west point release. (The docstrings in west had some RST syntax errors). These should be reverted back to automethod calls at the next release. .. method:: check_call(args, kwargs) Runs ``subprocess.check_call(args, kwargs)`` after logging the call at Verbosity.DBG_MORE`` level. .. versionchanged:: 1.2.0 The cwd keyword argument was replaced with a catch-all ``kwargs``. .. versionchanged:: 0.11.0 .. method:: check_output(args, kwargs) Runs ``subprocess.check_output(args, *kwargs)`` after logging the call at Verbosity.DBG_MORE level. .. versionchanged:: 1.2.0 The cwd* keyword argument was replaced with a catch-all ``kwargs``. .. versionchanged:: 0.11.0 .. method:: run_subprocess(args, kwargs) Runs ``subprocess.run(args, *kwargs)`` after logging the call at Verbosity.DBG_MORE level. .. versionadded:: 1.2.0 All subclasses must provide the following abstract methods, which are used to implement the above: .. automethod:: do_add_parser .. automethod:: do_run The following methods should be used when the command needs to print output. These were introduced to enable a transition from the deprecated ``west.log`` module to a per-command interface that will allow for a global "quiet" mode for west commands in a future release: .. automethod:: dbg .. versionchanged:: 1.2.0 The end* argument. .. versionadded:: 1.0.0 .. automethod:: inf .. versionchanged:: 1.2.0 The end argument. .. versionadded:: 1.0.0 .. automethod:: wrn .. versionchanged:: 1.2.0 The end argument. .. versionadded:: 1.0.0 .. automethod:: err .. versionchanged:: 1.2.0 The end argument. .. versionadded:: 1.0.0 .. automethod:: die .. versionadded:: 1.0.0 .. automethod:: banner .. versionadded:: 1.0.0 .. automethod:: small_banner .. versionadded:: 1.0.0 .. _west-apis-commands-output: Verbosity ========= Since west v1.0, west commands should print output using methods like west.commands.WestCommand.dbg(), west.commands.WestCommand.inf(), etc. (see above). This section documents a related enum used to declare verbosity levels. .. autoclass:: west.commands.Verbosity .. autoattribute:: QUIET .. autoattribute:: ERR .. autoattribute:: WRN .. autoattribute:: INF .. autoattribute:: DBG .. autoattribute:: DBG_MORE .. autoattribute:: DBG_EXTREME .. versionadded:: 1.0.0 Exceptions ========== .. autoclass:: west.commands.CommandError :show-inheritance: .. py:attribute:: returncode Recommended program exit code for this error. .. autoclass:: west.commands.CommandContextError :show-inheritance: .. _west-apis-configuration: west.configuration ****************** .. automodule:: west.configuration Since west v0.13, the recommended class for reading this is :py:class:`west.configuration.Configuration`. Note that if you are writing a :ref:`west extension <west-extensions>`, you can access the current ``Configuration`` object as ``self.config``. See :py:class:`west.commands.WestCommand`. Configuration API ================= This is the recommended API to use since west v0.13. .. autoclass:: west.configuration.ConfigFile .. autoclass:: west.configuration.Configuration :members: .. versionadded:: 0.13.0 Deprecated APIs =============== The following APIs also use :py:class:`west.configuration.ConfigFile`, but they operate by default on a global object which stores the current workspace configuration. This has proven to be a bad design decision since west's APIs can be used from multiple workspaces. They were deprecated in west v0.13.0. These APIs are preserved for compatibility with older extensions. They should not be used in new code when west v0.13.0 or later may be assumed. .. autofunction:: west.configuration.read_config .. versionchanged:: 0.8.0 The deprecated read_config parameter was removed. .. versionchanged:: 0.6.0 Errors due to an inability to find a local configuration file are ignored. .. autofunction:: west.configuration.update_config .. py:data:: west.configuration.config Module-global ConfigParser instance for the current configuration. This should be initialized with :py:func:`west.configuration.read_config` before being read. .. _west-apis-log: west.log (deprecated) ******************* .. automodule:: west.log Verbosity control ================= To set the global verbosity level, use ``set_verbosity()``. .. autofunction:: set_verbosity These verbosity levels are defined. .. autodata:: VERBOSE_NONE .. autodata:: VERBOSE_NORMAL .. autodata:: VERBOSE_VERY .. autodata:: VERBOSE_EXTREME Output functions ================ The main functions are ``dbg()``, ``inf()``, ``wrn()``, ``err()``, and ``die()``. Two special cases of ``inf()``, ``banner()`` and ``small_banner()``, are also available for grouping output into "sections". .. autofunction:: dbg .. autofunction:: inf .. autofunction:: wrn .. autofunction:: err .. autofunction:: die .. autofunction:: banner .. autofunction:: small_banner .. _west-apis-manifest: west.manifest *********** .. automodule:: west.manifest The main classes are :py:class:`Manifest` and :py:class:`Project`. These represent the contents of a :ref:`manifest file <west-manifests>`. The recommended method for parsing west manifests is :py:meth:`Manifest.from_topdir`. Constants and functions ======================= .. autodata:: MANIFEST_PROJECT_INDEX .. autodata:: MANIFEST_REV_BRANCH .. autodata:: QUAL_MANIFEST_REV_BRANCH .. autodata:: QUAL_REFS_WEST .. autodata:: SCHEMA_VERSION .. autofunction:: west.manifest.manifest_path .. autofunction:: west.manifest.validate .. versionchanged:: 0.13.0 This returns the validated dict containing the parsed YAML data. Manifest and sub-objects ======================== .. autoclass:: west.manifest.Manifest .. automethod:: __init__ .. versionchanged:: 0.7.0 The importer and import_flags keyword arguments. .. versionchanged:: 0.13.0 All arguments were made keyword-only. The source_file argument was removed (use topdir instead). The function no longer raises ``WestNotFound``. .. versionadded:: 0.13.0 The config argument. .. versionadded:: 0.13.0 The abspath, posixpath, relative_path, yaml_path, repo_path, repo_posixpath, and userdata attributes. .. automethod:: from_topdir .. versionadded:: 0.13.0 .. automethod:: from_file .. versionchanged:: 0.7.0 ``*kwargs`` added. .. versionchanged:: 0.8.0 The source_file, manifest_path, and topdir* arguments can now be any ``os.PathLike``. .. versionchanged:: 0.13.0 The manifest_path and topdir arguments were removed. .. automethod:: from_data .. versionchanged:: 0.7.0 ``*kwargs`` added, and source_data* may be a ``str``. .. versionchanged:: 0.13.0 The manifest_path and topdir arguments were removed. Conveniences for accessing sub-objects by name or other identifier: .. automethod:: get_projects .. versionchanged:: 0.8.0 The project_ids sequence can now contain any ``os.PathLike``. .. versionadded:: 0.6.1 Additional methods: .. automethod:: as_dict .. versionadded:: 0.7.0 .. automethod:: as_frozen_dict .. automethod:: as_yaml .. versionadded:: 0.7.0 .. automethod:: as_frozen_yaml .. versionadded:: 0.7.0 .. automethod:: is_active .. versionadded:: 0.9.0 .. versionchanged:: 1.1.0 This respects the ``manifest.project-filter`` configuration option. See :ref:`west-config-index`. .. autoclass:: west.manifest.ImportFlag :members: :member-order: bysource .. autoclass:: west.manifest.Project .. (note: attributes are part of the class docstring) .. versionchanged:: 0.7.0 The remote attribute was removed. Its semantics could no longer be preserved when support for manifest ``import`` keys was added. .. versionadded:: 0.7.0 The remote_name and name_and_path attributes. .. versionchanged:: 0.8.0 The west_commands attribute is now always a list. In previous releases, it could be a string or ``None``. .. versionadded:: 0.9.0 The group_filter and submodules attributes. .. versionadded:: 0.12.0 The userdata attribute. .. versionadded:: 1.2.0 The description attribute. Constructor: .. automethod:: __init__ .. versionchanged:: 0.8.0 The path and topdir parameters can now be any ``os.PathLike``. .. versionchanged:: 0.7.0 The parameters were incompatibly changed from previous versions. Methods: .. automethod:: as_dict .. versionadded:: 0.7.0 .. automethod:: git .. versionchanged:: 0.6.1 The capture_stderr kwarg. .. versionchanged:: 0.7.0 The (now removed) ``Project.format`` method is no longer called on arguments. .. automethod:: sha .. versionchanged:: 0.7.0 Standard error is now captured. .. automethod:: is_ancestor_of .. versionchanged:: 0.8.0 The cwd parameter can now be any ``os.PathLike``. .. automethod:: is_cloned .. versionchanged:: 0.8.0 The cwd parameter can now be any ``os.PathLike``. .. versionadded:: 0.6.1 .. automethod:: is_up_to_date_with .. versionchanged:: 0.8.0 The cwd parameter can now be any ``os.PathLike``. .. automethod:: is_up_to_date .. versionchanged:: 0.8.0 The cwd parameter can now be any ``os.PathLike``. .. automethod:: read_at .. versionchanged:: 0.8.0 The cwd parameter can now be any ``os.PathLike``. .. versionadded:: 0.7.0 .. automethod:: listdir_at .. versionchanged:: 0.8.0 The cwd parameter can now be any ``os.PathLike``. .. versionadded:: 0.7.0 .. autoclass:: west.manifest.ManifestProject A limited subset of Project methods is supported. Results for calling others are not specified. .. versionchanged:: 0.8.0 The url attribute is now the empty string instead of ``None``. The abspath attribute is created using ``os.path.abspath()`` instead of ``os.path.realpath()``, improving support for symbolic links. .. automethod:: as_dict .. versionadded:: 0.6.0 .. autoclass:: west.manifest.Submodule .. versionadded:: 0.9.0 Exceptions ========== .. autoclass:: west.configuration.MalformedConfig :show-inheritance: .. autoclass:: west.manifest.MalformedManifest :show-inheritance: .. autoclass:: west.manifest.ManifestVersionError :show-inheritance: .. versionchanged:: 0.8.0 The file argument can now be any ``os.PathLike``. .. autoclass:: west.manifest.ManifestImportFailed :show-inheritance: .. versionchanged:: 0.8.0 The filename argument can now be any ``os.PathLike``. .. versionchanged:: 0.13.0 The filename argument was renamed imp, and can now take any value. .. _west-apis-util: west.util ********* .. canon_path(), escapes_directory(), etc. intentionally not documented here. .. automodule:: west.util Functions ========= .. autofunction:: west.util.west_dir .. versionchanged:: 0.8.0 The start parameter can be any ``os.PathLike``. .. autofunction:: west.util.west_topdir .. versionchanged:: 0.8.0 The start parameter can be any ``os.PathLike``. Exceptions ========== .. autoclass:: west.util.WestNotFound :show-inheritance: ```	/content/code_sandbox/doc/develop/west/west-apis.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	3,929
```restructuredtext .. _west-built-in-cmds: Built-in commands ################# This page describes west's built-in commands, some of which were introduced in :ref:`west-basics`, in more detail. Some commands are related to Git commands with the same name, but operate on the entire workspace. For example, ``west diff`` shows local changes in multiple Git repositories in the workspace. Some commands take projects as arguments. These arguments can be project names as specified in the manifest file, or (as a fallback) paths to them on the local file system. Omitting project arguments to commands which accept them (such as ``west list``, ``west forall``, etc.) usually defaults to using all projects in the manifest file plus the manifest repository itself. For additional help, run ``west <command> -h`` (e.g. ``west init -h``). .. _west-init: west init ******* This command creates a west workspace. It can be used in two ways: 1. Cloning a new manifest repository from a remote URL 2. Creating a workspace around an existing local manifest repository Option 1: to clone a new manifest repository from a remote URL, use: .. code-block:: none west init [-m URL] [--mr REVISION] [--mf FILE] [directory] The new workspace is created in the given :file:`directory`, creating a new :file:`.west` inside this directory. You can give the manifest URL using the ``-m`` switch, the initial revision to check out using ``--mr``, and the location of the manifest file within the repository using ``--mf``. For example, running: .. code-block:: shell west init -m path_to_url --mr v1.14.0 zp would clone the upstream official zephyr repository into :file:`zp/zephyr`, and check out the ``v1.14.0`` release. This command creates :file:`zp/.west`, and set the ``manifest.path`` :ref:`configuration option <west-config>` to ``zephyr`` to record the location of the manifest repository in the workspace. The default manifest file location is used. The ``-m`` option defaults to ``path_to_url``. The ``--mf`` option defaults to ``west.yml``. Since west v0.10.1, west will use the default branch in the manifest repository unless the ``--mr`` option is used to override it. (In prior versions, ``--mr`` defaulted to ``master``.) If no ``directory`` is given, the current working directory is used. Option 2: to create a workspace around an existing local manifest repository, use: .. code-block:: none west init -l [--mf FILE] directory This creates :file:`.west` next to :file:`directory` in the file system, and sets ``manifest.path`` to ``directory``. As above, ``--mf`` defaults to ``west.yml``. Reconfiguring the workspace: If you change your mind later, you are free to change ``manifest.path`` and ``manifest.file`` using :ref:`west-config-cmd` after running ``west init``. Just be sure to run ``west update`` afterwards to update your workspace to match the new manifest file. .. _west-update: west update ******* .. code-block:: none west update [-f {always,smart}] [-k] [-r] [--group-filter FILTER] [--stats] [PROJECT ...] Which projects are updated: By default, this command parses the manifest file, usually :file:`west.yml`, and updates each project specified there. If your manifest uses :ref:`project groups <west-manifest-groups>`, then only the active projects are updated. To operate on a subset of projects only, give ``PROJECT`` argument(s). Each ``PROJECT`` is either a project name as given in the manifest file, or a path that points to the project within the workspace. If you specify projects explicitly, they are updated regardless of whether they are active. Project update procedure: For each project that is updated, this command: #. Initializes a local Git repository for the project in the workspace, if it does not already exist #. Inspects the project's ``revision`` field in the manifest, and fetches it from the remote if it is not already available locally #. Sets the project's :ref:`manifest-rev <west-manifest-rev>` branch to the commit specified by the revision in the previous step #. Checks out ``manifest-rev`` in the local working copy as a `detached HEAD <path_to_url#_detached_head>`_ #. If the manifest file specifies a :ref:`submodules <west-manifest-submodules>` key for the project, recursively updates the project's submodules as described below. To avoid unnecessary fetches, ``west update`` will not fetch project ``revision`` values which are Git SHAs or tags that are already available locally. This is the behavior when the ``-f`` (``--fetch``) option has its default value, ``smart``. To force this command to fetch from project remotes even if the revisions appear to be available locally, either use ``-f always`` or set the ``update.fetch`` :ref:`configuration option <west-config>` to ``always``. SHAs may be given as unique prefixes as long as they are acceptable to Git [#fetchall]_. If the project ``revision`` is a Git ref that is neither a tag nor a SHA (i.e. if the project is tracking a branch), ``west update`` always fetches, regardless of ``-f`` and ``update.fetch``. Some branch names might look like short SHAs, like ``deadbeef``. West treats these like SHAs. You can disambiguate by prefixing the ``revision`` value with ``refs/heads/``, e.g. ``revision: refs/heads/deadbeef``. For safety, ``west update`` uses ``git checkout --detach`` to check out a detached ``HEAD`` at the manifest revision for each updated project, leaving behind any branches which were already checked out. This is typically a safe operation that will not modify any of your local branches. However, if you had added some local commits onto a previously detached ``HEAD`` checked out by west, then git will warn you that you've left behind some commits which are no longer referred to by any branch. These may be garbage-collected and lost at some point in the future. To avoid this if you have local commits in the project, make sure you have a local branch checked out before running ``west update``. If you would rather rebase any locally checked out branches instead, use the ``-r`` (``--rebase``) option. If you would like ``west update`` to keep local branches checked out as long as they point to commits that are descendants of the new ``manifest-rev``, use the ``-k`` (``--keep-descendants``) option. .. note:: ``west update --rebase`` will fail in projects that have git conflicts between your branch and new commits brought in by the manifest. You should immediately resolve these conflicts as you usually do with ``git``, or you can use ``git -C <project_path> rebase --abort`` to ignore incoming changes for the moment. With a clean working tree, a plain ``west update`` never fails because it does not try to hold on to your commits and simply leaves them aside. ``west update --keep-descendants`` offers an intermediate option that never fails either but does not treat all projects the same: - in projects where your branch diverged from the incoming commits, it does not even try to rebase and leaves your branches behind just like a plain ``west update`` does; - in all other projects where no rebase or merge is needed it keeps your branches in place. One-time project group manipulation: The ``--group-filter`` option can be used to change which project groups are enabled or disabled for the duration of a single ``west update`` command. See :ref:`west-manifest-groups` for details on the project group feature. The ``west update`` command behaves as if the ``--group-filter`` option's value were appended to the ``manifest.group-filter`` :ref:`configuration option <west-config-index>`. For example, running ``west update --group-filter=+foo,-bar`` would behave the same way as if you had temporarily appended the string ``"+foo,-bar"`` to the value of ``manifest.group-filter``, run ``west update``, then restored ``manifest.group-filter`` to its original value. Note that using the syntax ``--group-filter=VALUE`` instead of ``--group-filter VALUE`` avoids issues parsing command line options if you just want to disable a single group, e.g. ``--group-filter=-bar``. Submodule update procedure: If a project in the manifest has a ``submodules`` key, the submodules are updated as follows, depending on the value of the ``submodules`` key. If the project has ``submodules: true``, west first synchronizes the project's submodules with: .. code-block:: git submodule sync --recursive West then runs one of the following in the project repository, depending on whether you run ``west update`` with the ``--rebase`` option or without it: .. code-block:: # without --rebase, e.g. "west update": git submodule update --init --checkout --recursive # with --rebase, e.g. "west update --rebase": git submodule update --init --rebase --recursive Otherwise, the project has ``submodules: <list-of-submodules>``. In this case, west synchronizes the project's submodules with: .. code-block:: git submodule sync --recursive -- <submodule-path> Then it updates each submodule in the list as follows, depending on whether you run ``west update`` with the ``--rebase`` option or without it: .. code-block:: # without --rebase, e.g. "west update": git submodule update --init --checkout --recursive <submodule-path> # with --rebase, e.g. "west update --rebase": git submodule update --init --rebase --recursive <submodule-path> The ``git submodule sync`` commands are skipped if the ``update.sync-submodules`` :ref:`west-config` option is false. .. _west-built-in-misc: Other project commands ****************** West has a few more commands for managing the projects in the workspace, which are summarized here. Run ``west <command> -h`` for detailed help. - ``west compare``: compare the state of the workspace against the manifest - ``west diff``: run ``git diff`` in local project repositories - ``west forall``: run an arbitrary command in local project repositories - ``west grep``: search for patterns in local project repositories - ``west list``: print a line of information about each project in the manifest, according to a format string - ``west manifest``: manage the manifest file. See :ref:`west-manifest-cmd`. - ``west status``: run ``git status`` in local project repositories Other built-in commands ********************* Finally, here is a summary of other built-in commands. - ``west config``: get or set :ref:`configuration options <west-config>` - ``west topdir``: print the top level directory of the west workspace - ``west help``: get help about a command, or print information about all commands in the workspace, including :ref:`west-extensions` .. rubric:: Footnotes .. [#fetchall] West may fetch all refs from the Git server when given a SHA as a revision. This is because some Git servers have historically not allowed fetching SHAs directly. ```	/content/code_sandbox/doc/develop/west/built-in.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,590
```restructuredtext .. _twister_script: Test Runner (Twister) ##################### Twister scans for the set of test applications in the git repository and attempts to execute them. By default, it tries to build each test application on boards marked as default in the board definition file. The default options will build the majority of the test applications on a defined set of boards and will run in an emulated environment if available for the architecture or configuration being tested. Because of the limited test execution coverage, twister cannot guarantee local changes will succeed in the full build environment, but it does sufficient testing by building samples and tests for different boards and different configurations to help keep the complete code tree buildable. When using (at least) one ``-v`` option, twister's console output shows for every test application how the test is run (qemu, native_sim, etc.) or whether the binary was just built. There are a few reasons why twister only builds a test and doesn't run it: - The test is marked as ``build_only: true`` in its ``.yaml`` configuration file. - The test configuration has defined a ``harness`` but you don't have it or haven't set it up. - The target device is not connected and not available for flashing - You or some higher level automation invoked twister with ``--build-only``. To run the script in the local tree, follow the steps below: .. tabs:: .. group-tab:: Linux .. code-block:: bash $ source zephyr-env.sh $ ./scripts/twister .. group-tab:: Windows .. code-block:: bat zephyr-env.cmd python .\scripts\twister If you have a system with a large number of cores and plenty of free storage space, you can build and run all possible tests using the following options: .. tabs:: .. group-tab:: Linux .. code-block:: bash $ ./scripts/twister --all --enable-slow .. group-tab:: Windows .. code-block:: bat python .\scripts\twister --all --enable-slow This will build for all available boards and run all applicable tests in a simulated (for example QEMU) environment. If you want to run tests on one or more specific platforms, you can use the ``--platform`` option, it is a platform filter for testing, with this option, test suites will only be built/run on the platforms specified. This option also supports different revisions of one same board, you can use ``--platform board@revision`` to test on a specific revision. The list of command line options supported by twister can be viewed using: .. tabs:: .. group-tab:: Linux .. code-block:: bash $ ./scripts/twister --help .. group-tab:: Windows .. code-block:: bat python .\scripts\twister --help Board Configuration ***************** To build tests for a specific board and to execute some of the tests on real hardware or in an emulation environment such as QEMU a board configuration file is required which is generic enough to be used for other tasks that require a board inventory with details about the board and its configuration that is only available during build time otherwise. The board metadata file is located in the board directory and is structured using the YAML markup language. The example below shows a board with a data required for best test coverage for this specific board: .. code-block:: yaml identifier: frdm_k64f name: NXP FRDM-K64F type: mcu arch: arm toolchain: - zephyr - gnuarmemb - xtools supported: - arduino_gpio - arduino_i2c - netif:eth - adc - i2c - nvs - spi - gpio - usb_device - watchdog - can - pwm testing: default: true identifier: A string that matches how the board is defined in the build system. This same string is used when building, for example when calling ``west build`` or ``cmake``: .. code-block:: console # with west west build -b reel_board # with cmake cmake -DBOARD=reel_board .. name: The actual name of the board as it appears in marketing material. type: Type of the board or configuration, currently we support 2 types: mcu, qemu simulation: Simulator used to simulate the platform, e.g. qemu. arch: Architecture of the board toolchain: The list of supported toolchains that can build this board. This should match one of the values used for :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` when building on the command line ram: Available RAM on the board (specified in KB). This is used to match test scenario requirements. If not specified we default to 128KB. flash: Available FLASH on the board (specified in KB). This is used to match test scenario requirements. If not specified we default to 512KB. supported: A list of features this board supports. This can be specified as a single word feature or as a variant of a feature class. For example: .. code-block:: yaml supported: - pci This indicates the board does support PCI. You can make a test scenario build or run only on such boards, or: .. code-block:: yaml supported: - netif:eth - sensor:bmi16 A test scenario can depend on 'eth' to only test ethernet or on 'netif' to run on any board with a networking interface. testing: testing relating keywords to provide best coverage for the features of this board. .. _twister_default_testing_board: default: [True\|False]: This is a default board, it will tested with the highest priority and is covered when invoking the simplified twister without any additional arguments. ignore_tags: Do not attempt to build (and therefore run) tests marked with this list of tags. only_tags: Only execute tests with this list of tags on a specific platform. .. _twister_board_timeout_multiplier: timeout_multiplier: <float> (default 1) Multiply each test scenario timeout by specified ratio. This option allows to tune timeouts only for required platform. It can be useful in case naturally slow platform I.e.: HW board with power-efficient but slow CPU or simulation platform which can perform instruction accurate simulation but does it slowly. env: A list of environment variables. Twister will check if all these environment variables are set, and otherwise skip this platform. This allows the user to define a platform which should be used, for example, only if some required software or hardware is present, and to signal that presence to twister using these environment variables. Tests **** Tests are detected by the presence of a ``testcase.yaml`` or a ``sample.yaml`` files in the application's project directory. This test application configuration file may contain one or more entries in the tests section each identifying a test scenario. .. _twister_test_project_diagram: .. figure:: figures/twister_test_project.svg :alt: Twister and a Test applications' project. :figclass: align-center Twister and a Test applications' project. Test application configurations are written using the YAML syntax and share the same structure as samples. A test scenario is a set of conditions or variables, defined in test scenario entry, under which a set of test suites will be executed. Can be used interchangeably with test scenario entry. A test suite is a collection of test cases that are intended to be used to test a software program to ensure it meets certain requirements. The test cases in a test suite are often related or meant to be executed together. The name of each test scenario needs to be unique in the context of the overall test application and has to follow basic rules: #. The format of the test scenario identifier shall be a string without any spaces or special characters (allowed characters: alphanumeric and [\_=]) consisting of multiple sections delimited with a dot (.). #. Each test scenario identifier shall start with a section followed by a subsection separated by a dot. For example, a test scenario that covers semaphores in the kernel shall start with ``kernel.semaphore``. #. All test scenario identifiers within a ``testcase.yaml`` file need to be unique. For example a ``testcase.yaml`` file covering semaphores in the kernel can have: * ``kernel.semaphore``: For general semaphore tests * ``kernel.semaphore.stress``: Stress testing semaphores in the kernel. #. Depending on the nature of the test, an identifier can consist of at least two sections: * Ztest tests: The individual test cases in the ztest testsuite will be concatenated by dot (`.`) to the identifier in the ``testcase.yaml`` file generating unique identifiers for every test case in the suite. * Standalone tests and samples: This type of test should at least have 3 sections concatnated by dot (`.`) in the test scenario identifier in the ``testcase.yaml`` (or ``sample.yaml``) file. The last section of the name shall signify the test case itself. The following is an example test configuration with a few options that are explained in this document. .. code-block:: yaml tests: bluetooth.gatt: build_only: true platform_allow: qemu_cortex_m3 qemu_x86 tags: bluetooth bluetooth.gatt.br: build_only: true extra_args: CONF_FILE="prj_br.conf" filter: not CONFIG_DEBUG platform_exclude: up_squared platform_allow: qemu_cortex_m3 qemu_x86 tags: bluetooth A sample with tests will have the same structure with additional information related to the sample and what is being demonstrated: .. code-block:: yaml sample: name: hello world description: Hello World sample, the simplest Zephyr application tests: sample.basic.hello_world: build_only: true tags: tests min_ram: 16 sample.basic.hello_world.singlethread: build_only: true extra_args: CONF_FILE=prj_single.conf filter: not CONFIG_BT tags: tests min_ram: 16 The full canonical name for each test scenario is:``<path to test application>/<test scenario identifier>`` A test scenario entry is a a block or entry starting with test scenario identifier in the YAML files. Each test scenario entry in the test application configuration can define the following key/value pairs: .. _test_config_args: tags: <list of tags> (required) A set of string tags for the test scenario. Usually pertains to functional domains but can be anything. Command line invocations of this script can filter the set of tests to run based on tag. skip: <True\|False> (default False) skip test scenario unconditionally. This can be used for broken tests for example. slow: <True\|False> (default False) Don't run this test scenario unless ``--enable-slow`` or ``--enable-slow-only`` was passed in on the command line. Intended for time-consuming test scenarios that are only run under certain circumstances, like daily builds. These test scenarios are still compiled. extra_args: <list of extra arguments> Extra arguments to pass to build tool when building or running the test scenario. extra_configs: <list of extra configurations> Extra configuration options to be merged with a main prj.conf when building or running the test scenario. For example: .. code-block:: yaml common: tags: drivers adc tests: test: depends_on: adc test_async: extra_configs: - CONFIG_ADC_ASYNC=y Using namespacing, it is possible to apply a configuration only to some hardware. Currently both architectures and platforms are supported: .. code-block:: yaml common: tags: drivers adc tests: test: depends_on: adc test_async: extra_configs: - arch:x86:CONFIG_ADC_ASYNC=y - platform:qemu_x86:CONFIG_DEBUG=y build_only: <True\|False> (default False) If true, twister will not try to run the test even if the test is runnable on the platform. This keyword is reserved for tests that are used to test if some code actually builds. A ``build_only`` test is not designed to be run in any environment and should not be testing any functionality, it only verifies that the code builds. This option is often used to test drivers and the fact that they are correctly enabled in Zephyr and that the code builds, for example sensor drivers. Such test shall not be used to verify the functionality of the driver. build_on_all: <True\|False> (default False) If true, attempt to build test scenario on all available platforms. This is mostly used in CI for increased coverage. Do not use this flag in new tests. depends_on: <list of features> A board or platform can announce what features it supports, this option will enable the test only those platforms that provide this feature. levels: <list of levels> Test levels this test should be part of. If a level is present, this test will be selectable using the command line option ``--level <level name>`` min_ram: <integer> minimum amount of RAM in KB needed for this test to build and run. This is compared with information provided by the board metadata. min_flash: <integer> minimum amount of ROM in KB needed for this test to build and run. This is compared with information provided by the board metadata. .. _twister_test_case_timeout: timeout: <number of seconds> Length of time to run test before automatically killing it. Default to 60 seconds. arch_allow: <list of arches, such as x86, arm, arc> Set of architectures that this test scenario should only be run for. arch_exclude: <list of arches, such as x86, arm, arc> Set of architectures that this test scenario should not run on. platform_allow: <list of platforms> Set of platforms that this test scenario should only be run for. Do not use this option to limit testing or building in CI due to time or resource constraints, this option should only be used if the test or sample can only be run on the allowed platform and nothing else. integration_platforms: <YML list of platforms/boards> This option limits the scope to the listed platforms when twister is invoked with the ``--integration`` option. Use this instead of platform_allow if the goal is to limit scope due to timing or resource constraints. platform_exclude: <list of platforms> Set of platforms that this test scenario should not run on. extra_sections: <list of extra binary sections> When computing sizes, twister will report errors if it finds extra, unexpected sections in the Zephyr binary unless they are named here. They will not be included in the size calculation. sysbuild: <True\|False> (default False) Build the project using sysbuild infrastructure. Only the main project's generated devicetree and Kconfig will be used for filtering tests. on device testing must use the hardware map, or west flash to load the images onto the target. The ``--erase`` option of west flash is not supported with this option. Usage of unsupported options will result in tests requiring sysbuild support being skipped. harness: <string> A harness keyword in the ``testcase.yaml`` file identifies a Twister harness needed to run a test successfully. A harness is a feature of Twister and implemented by Twister, some harnesses are defined as placeholders and have no implementation yet. A harness can be seen as the handler that needs to be implemented in Twister to be able to evaluate if a test passes criteria. For example, a keyboard harness is set on tests that require keyboard interaction to reach verdict on whether a test has passed or failed, however, Twister lack this harness implementation at the moment. Supported harnesses: - ztest - test - console - pytest - gtest - robot Harnesses ``ztest``, ``gtest`` and ``console`` are based on parsing of the output and matching certain phrases. ``ztest`` and ``gtest`` harnesses look for pass/fail/etc. frames defined in those frameworks. Use ``gtest`` harness if you've already got tests written in the gTest framework and do not wish to update them to zTest. The ``console`` harness tells Twister to parse a test's text output for a regex defined in the test's YAML file. The ``robot`` harness is used to execute Robot Framework test suites in the Renode simulation framework. Some widely used harnesses that are not supported yet: - keyboard - net - bluetooth Harness ``bsim`` is implemented in limited way - it helps only to copy the final executable (``zephyr.exe``) from build directory to BabbleSim's ``bin`` directory (``${BSIM_OUT_PATH}/bin``). This action is useful to allow BabbleSim's tests to directly run after. By default, the executable file name is (with dots and slashes replaced by underscores): ``bs_<platform_name>_<test_path>_<test_scenario_name>``. This name can be overridden with the ``bsim_exe_name`` option in ``harness_config`` section. platform_key: <list of platform attributes> Often a test needs to only be built and run once to qualify as passing. Imagine a library of code that depends on the platform architecture where passing the test on a single platform for each arch is enough to qualify the tests and code as passing. The platform_key attribute enables doing just that. For example to key on (arch, simulation) to ensure a test is run once per arch and simulation (as would be most common): .. code-block:: yaml platform_key: - arch - simulation Adding platform (board) attributes to include things such as soc name, soc family, and perhaps sets of IP blocks implementing each peripheral interface would enable other interesting uses. For example, this could enable building and running SPI tests once for each unique IP block. harness_config: <harness configuration options> Extra harness configuration options to be used to select a board and/or for handling generic Console with regex matching. Config can announce what features it supports. This option will enable the test to run on only those platforms that fulfill this external dependency. The following options are currently supported: type: <one_line\|multi_line> (required) Depends on the regex string to be matched regex: <list of regular expressions> (required) Strings with regular expressions to match with the test's output to confirm the test runs as expected. ordered: <True\|False> (default False) Check the regular expression strings in orderly or randomly fashion record: <recording options> (optional) regex: <regular expression> (required) The regular expression with named subgroups to match data fields at the test's output lines where the test provides some custom data for further analysis. These records will be written into the build directory ``recording.csv`` file as well as ``recording`` property of the test suite object in ``twister.json``. For example, to extract three data fields ``metric``, ``cycles``, ``nanoseconds``: .. code-block:: yaml record: regex: "(?P<metric>.):(?P<cycles>.) cycles, (?P<nanoseconds>.) ns" as_json: <list of regex subgroup names> (optional) Data fields, extracted by the regular expression into named subgroups, which will be additionally parsed as JSON encoded strings and written into ``twister.json`` as nested ``recording`` object properties. The corresponding ``recording.csv`` columns will contain strings as-is. Using this option, a test log can convey layered data structures passed from the test image for further analysis with summary results, traces, statistics, etc. For example, this configuration: .. code-block:: yaml record: regex: "RECORD:(?P<type>.):DATA:(?P<metrics>.)" as_json: [metrics] when matched to a test log string: .. code-block:: none RECORD:jitter_drift:DATA:{"rollovers":0, "mean_us":1000.0} will be reported in ``twister.json`` as: .. code-block:: json "recording":[ { "type":"jitter_drift", "metrics":{ "rollovers":0, "mean_us":1000.0 } } ] fixture: <expression> Specify a test scenario dependency on an external device(e.g., sensor), and identify setups that fulfill this dependency. It depends on specific test setup and board selection logic to pick the particular board(s) out of multiple boards that fulfill the dependency in an automation setup based on ``fixture`` keyword. Some sample fixture names are i2c_hts221, i2c_bme280, i2c_FRAM, ble_fw and gpio_loop. Only one fixture can be defined per test scenario and the fixture name has to be unique across all tests in the test suite. .. _pytest_root: pytest_root: <list of pytest testpaths> (default pytest) Specify a list of pytest directories, files or subtests that need to be executed when a test scenario begins to run. The default pytest directory is ``pytest``. After the pytest run is finished, Twister will check if the test scenario passed or failed according to the pytest report. As an example, a list of valid pytest roots is presented below: .. code-block:: yaml harness_config: pytest_root: - "pytest/test_shell_help.py" - "../shell/pytest/test_shell.py" - "/tmp/test_shell.py" - "~/tmp/test_shell.py" - "$ZEPHYR_BASE/samples/subsys/testsuite/pytest/shell/pytest/test_shell.py" - "pytest/test_shell_help.py::test_shell2_sample" # select pytest subtest - "pytest/test_shell_help.py::test_shell2_sample[param_a]" # select pytest parametrized subtest .. _pytest_args: pytest_args: <list of arguments> (default empty) Specify a list of additional arguments to pass to ``pytest`` e.g.: ``pytest_args: [-k=test_method, --log-level=DEBUG]``. Note that ``--pytest-args`` can be passed multiple times to pass several arguments to the pytest. .. _pytest_dut_scope: pytest_dut_scope: <function\|class\|module\|package\|session> (default function) The scope for which ``dut`` and ``shell`` pytest fixtures are shared. If the scope is set to ``function``, DUT is launched for every test case in python script. For ``session`` scope, DUT is launched only once. robot_testsuite: <robot file path> (default empty) Specify one or more paths to a file containing a Robot Framework test suite to be run. robot_option: <robot option> (default empty) One or more options to be send to robotframework. bsim_exe_name: <string> If provided, the executable filename when copying to BabbleSim's bin directory, will be ``bs_<platform_name>_<bsim_exe_name>`` instead of the default based on the test path and scenario name. The following is an example yaml file with a few harness_config options. .. code-block:: yaml sample: name: HTS221 Temperature and Humidity Monitor common: tags: sensor harness: console harness_config: type: multi_line ordered: false regex: - "Temperature:(.)C" - "Relative Humidity:(.)%" fixture: i2c_hts221 tests: test: tags: sensors depends_on: i2c The following is an example yaml file with pytest harness_config options, default pytest_root name "pytest" will be used if pytest_root not specified. please refer the examples in samples/subsys/testsuite/pytest/. .. code-block:: yaml common: harness: pytest tests: pytest.example.directories: harness_config: pytest_root: - pytest_dir1 - $ENV_VAR/samples/test/pytest_dir2 pytest.example.files_and_subtests: harness_config: pytest_root: - pytest/test_file_1.py - test_file_2.py::test_A - test_file_2.py::test_B[param_a] The following is an example yaml file with robot harness_config options. .. code-block:: yaml tests: robot.example: harness: robot harness_config: robot_testsuite: [robot file path] It can be more than one test suite using a list. .. code-block:: yaml tests: robot.example: harness: robot harness_config: robot_testsuite: - [robot file path 1] - [robot file path 2] - [robot file path n] One or more options can be passed to robotframework. .. code-block:: yaml tests: robot.example: harness: robot harness_config: robot_testsuite: [robot file path] robot_option: - --exclude tag - --stop-on-error filter: <expression> Filter whether the test scenario should be run by evaluating an expression against an environment containing the following values: .. code-block:: none { ARCH : <architecture>, PLATFORM : <platform>, <all CONFIG_ key/value pairs in the test's generated defconfig>, <env>: any environment variable available } Twister will first evaluate the expression to find if a "limited" cmake call, i.e. using package_helper cmake script, can be done. Existence of "dt_" entries indicates devicetree is needed. Existence of "CONFIG" entries indicates kconfig is needed. If there are no other types of entries in the expression a filtration can be done without creating a complete build system. If there are entries of other types a full cmake is required. The grammar for the expression language is as follows: .. code-block:: antlr expression : expression 'and' expression \| expression 'or' expression \| 'not' expression \| '(' expression ')' \| symbol '==' constant \| symbol '!=' constant \| symbol '<' NUMBER \| symbol '>' NUMBER \| symbol '>=' NUMBER \| symbol '<=' NUMBER \| symbol 'in' list \| symbol ':' STRING \| symbol ; list : '[' list_contents ']'; list_contents : constant (',' constant); constant : NUMBER \| STRING; For the case where ``expression ::= symbol``, it evaluates to ``true`` if the symbol is defined to a non-empty string. Operator precedence, starting from lowest to highest: * or (left associative) * and (left associative) * not (right associative) * all comparison operators (non-associative) ``arch_allow``, ``arch_exclude``, ``platform_allow``, ``platform_exclude`` are all syntactic sugar for these expressions. For instance: .. code-block:: none arch_exclude = x86 arc Is the same as: .. code-block:: none filter = not ARCH in ["x86", "arc"] The ``:`` operator compiles the string argument as a regular expression, and then returns a true value only if the symbol's value in the environment matches. For example, if ``CONFIG_SOC="stm32f107xc"`` then .. code-block:: none filter = CONFIG_SOC : "stm." Would match it. required_snippets: <list of needed snippets> :ref:`Snippets <snippets>` are supported in twister for test scenarios that require them. As with normal applications, twister supports using the base zephyr snippet directory and test application directory for finding snippets. Listed snippets will filter supported tests for boards (snippets must be compatible with a board for the test to run on them, they are not optional). The following is an example yaml file with 2 required snippets. .. code-block:: yaml tests: snippet.example: required_snippets: - cdc-acm-console - user-snippet-example The set of test scenarios that actually run depends on directives in the test scenario filed and options passed in on the command line. If there is any confusion, running with ``-v`` or examining the discard report (:file:`twister_discard.csv`) can help show why particular test scenarios were skipped. Metrics (such as pass/fail state and binary size) for the last code release are stored in ``scripts/release/twister_last_release.csv``. To update this, pass the ``--all --release`` options. To load arguments from a file, add ``+`` before the file name, e.g., ``+file_name``. File content must be one or more valid arguments separated by line break instead of white spaces. Most everyday users will run with no arguments. Selecting platform scope *********************** One of the key features of Twister is its ability to decide on which platforms a given test scenario should run. This behavior has its roots in Twister being developed as a test runner for Zephyr's CI. With hundreds of available platforms and thousands of tests, the testing tools should be able to adapt the scope and select/filter out what is relevant and what is not. Twister always prepares an initial list of platforms in scope for a given test, based on command line arguments and the :ref:`test's configuration <test_config_args>`. Then, platforms that don't fulfill the conditions required in the configuration yaml (e.g. minimum ram) are filtered out from the scope. Using ``--force-platform`` allows to override filtering caused by ``platform_allow``, ``platform_exclude``, ``arch_allow`` and ``arch_exclude`` keys in test configuration files. Command line arguments define the initial scope in the following way: * ``-p/--platform <platform_name>`` (can be used multiple times): only platforms passed with this argument; * ``-l/--all``: all available platforms; * ``-G/--integration``: all platforms from an ``integration_platforms`` list in a given test configuration file. If a test has no ``integration_platforms`` `"scope presumption"` will happen; * No scope argument: `"scope presumption"` will happen. `"Scope presumption"`: A list of Twister's :ref:`default platforms <twister_default_testing_board>` is used as the initial list. If nothing is left after the filtration, the ``platform_allow`` list is used as the initial scope. Managing tests timeouts *********************** There are several parameters which control tests timeouts on various levels: * ``timeout`` option in each test scenario. See :ref:`here <twister_test_case_timeout>` for more details. * ``timeout_multiplier`` option in board configuration. See :ref:`here <twister_board_timeout_multiplier>` for more details. * ``--timeout-multiplier`` twister option which can be used to adjust timeouts in exact twister run. It can be useful in case of simulation platform as simulation time may depend on the host speed & load or we may select different simulation method (i.e. cycle accurate but slower one), etc... Overall test scenario timeout is a multiplication of these three parameters. Running in Integration Mode ************************* This mode is used in continuous integration (CI) and other automated environments used to give developers fast feedback on changes. The mode can be activated using the ``--integration`` option of twister and narrows down the scope of builds and tests if applicable to platforms defined under the integration keyword in the test configuration file (``testcase.yaml`` and ``sample.yaml``). Running tests on custom emulator **************************** Apart from the already supported QEMU and other simulated environments, Twister supports running any out-of-tree custom emulator defined in the board's :file:`board.cmake`. To use this type of simulation, add the following properties to :file:`custom_board/custom_board.yaml`: .. code-block:: yaml simulation: custom simulation_exec: <name_of_emu_binary> This tells Twister that the board is using a custom emulator called ``<name_of_emu_binary>``, make sure this binary exists in the PATH. Then, in :file:`custom_board/board.cmake`, set the supported emulation platforms to ``custom``: .. code-block:: cmake set(SUPPORTED_EMU_PLATFORMS custom) Finally, implement the ``run_custom`` target in :file:`custom_board/board.cmake`. It should look something like this: .. code-block:: cmake add_custom_target(run_custom COMMAND <name_of_emu_binary to invoke during 'run'> <any args to be passed to the command, i.e. ${BOARD}, ${APPLICATION_BINARY_DIR}/zephyr/zephyr.elf> WORKING_DIRECTORY ${APPLICATION_BINARY_DIR} DEPENDS ${logical_target_for_zephyr_elf} USES_TERMINAL ) Running Tests on Hardware ********************* Beside being able to run tests in QEMU and other simulated environments, twister supports running most of the tests on real devices and produces reports for each run with detailed FAIL/PASS results. Executing tests on a single device =================================== To use this feature on a single connected device, run twister with the following new options: .. tabs:: .. group-tab:: Linux .. code-block:: bash scripts/twister --device-testing --device-serial /dev/ttyACM0 \ --device-serial-baud 115200 -p frdm_k64f -T tests/kernel .. group-tab:: Windows .. code-block:: bat python .\scripts\twister --device-testing --device-serial COM1 \ --device-serial-baud 115200 -p frdm_k64f -T tests/kernel The ``--device-serial`` option denotes the serial device the board is connected to. This needs to be accessible by the user running twister. You can run this on only one board at a time, specified using the ``--platform`` option. The ``--device-serial-baud`` option is only needed if your device does not run at 115200 baud. To support devices without a physical serial port, use the ``--device-serial-pty`` option. In this cases, log messages are captured for example using a script. In this case you can run twister with the following options: .. tabs:: .. group-tab:: Linux .. code-block:: bash scripts/twister --device-testing --device-serial-pty "script.py" \ -p intel_adsp/cavs25 -T tests/kernel .. group-tab:: Windows .. note:: Not supported on Windows OS The script is user-defined and handles delivering the messages which can be used by twister to determine the test execution status. The ``--device-flash-timeout`` option allows to set explicit timeout on the device flash operation, for example when device flashing takes significantly large time. The ``--device-flash-with-test`` option indicates that on the platform the flash operation also executes a test scenario, so the flash timeout is increased by a test scenario timeout. Executing tests on multiple devices =================================== To build and execute tests on multiple devices connected to the host PC, a hardware map needs to be created with all connected devices and their details such as the serial device, baud and their IDs if available. Run the following command to produce the hardware map: .. tabs:: .. group-tab:: Linux .. code-block:: bash ./scripts/twister --generate-hardware-map map.yml .. group-tab:: Windows .. code-block:: bat python .\scripts\twister --generate-hardware-map map.yml The generated hardware map file (map.yml) will have the list of connected devices, for example: .. tabs:: .. group-tab:: Linux .. code-block:: yaml - connected: true id: OSHW000032254e4500128002ab98002784d1000097969900 platform: unknown product: DAPLink CMSIS-DAP runner: pyocd serial: /dev/cu.usbmodem146114202 - connected: true id: 000683759358 platform: unknown product: J-Link runner: unknown serial: /dev/cu.usbmodem0006837593581 .. group-tab:: Windows .. code-block:: yaml - connected: true id: OSHW000032254e4500128002ab98002784d1000097969900 platform: unknown product: unknown runner: unknown serial: COM1 - connected: true id: 000683759358 platform: unknown product: unknown runner: unknown serial: COM2 Any options marked as ``unknown`` need to be changed and set with the correct values, in the above example the platform names, the products and the runners need to be replaced with the correct values corresponding to the connected hardware. In this example we are using a reel_board and an nrf52840dk/nrf52840: .. tabs:: .. group-tab:: Linux .. code-block:: yaml - connected: true id: OSHW000032254e4500128002ab98002784d1000097969900 platform: reel_board product: DAPLink CMSIS-DAP runner: pyocd serial: /dev/cu.usbmodem146114202 baud: 9600 - connected: true id: 000683759358 platform: nrf52840dk/nrf52840 product: J-Link runner: nrfjprog serial: /dev/cu.usbmodem0006837593581 baud: 9600 .. group-tab:: Windows .. code-block:: yaml - connected: true id: OSHW000032254e4500128002ab98002784d1000097969900 platform: reel_board product: DAPLink CMSIS-DAP runner: pyocd serial: COM1 baud: 9600 - connected: true id: 000683759358 platform: nrf52840dk/nrf52840 product: J-Link runner: nrfjprog serial: COM2 baud: 9600 The baud entry is only needed if not running at 115200. If the map file already exists, then new entries are added and existing entries will be updated. This way you can use one single master hardware map and update it for every run to get the correct serial devices and status of the devices. With the hardware map ready, you can run any tests by pointing to the map .. tabs:: .. group-tab:: Linux .. code-block:: bash ./scripts/twister --device-testing --hardware-map map.yml -T samples/hello_world/ .. group-tab:: Windows .. code-block:: bat python .\scripts\twister --device-testing --hardware-map map.yml -T samples\hello_world The above command will result in twister building tests for the platforms defined in the hardware map and subsequently flashing and running the tests on those platforms. .. note:: Currently only boards with support for pyocd, nrfjprog, jlink, openocd, or dediprog are supported with the hardware map features. Boards that require other runners to flash the Zephyr binary are still work in progress. Hardware map allows to set ``--device-flash-timeout`` and ``--device-flash-with-test`` command line options as ``flash-timeout`` and ``flash-with-test`` fields respectively. These hardware map values override command line options for the particular platform. Serial PTY support using ``--device-serial-pty`` can also be used in the hardware map: .. code-block:: yaml - connected: true id: None platform: intel_adsp/cavs25 product: None runner: intel_adsp serial_pty: path/to/script.py runner_params: - --remote-host=remote_host_ip_addr - --key=/path/to/key.pem The runner_params field indicates the parameters you want to pass to the west runner. For some boards the west runner needs some extra parameters to work. It is equivalent to following west and twister commands. .. tabs:: .. group-tab:: Linux .. code-block:: bash west flash --remote-host remote_host_ip_addr --key /path/to/key.pem twister -p intel_adsp/cavs25 --device-testing --device-serial-pty script.py --west-flash="--remote-host=remote_host_ip_addr,--key=/path/to/key.pem" .. group-tab:: Windows .. note:: Not supported on Windows OS .. note:: For serial PTY, the "--generate-hardware-map" option cannot scan it out and generate a correct hardware map automatically. You have to edit it manually according to above example. This is because the serial port of the PTY is not fixed and being allocated in the system at runtime. Fixtures +++++++++ Some tests require additional setup or special wiring specific to the test. Running the tests without this setup or test fixture may fail. A test scenario can specify the fixture it needs which can then be matched with hardware capability of a board and the fixtures it supports via the command line or using the hardware map file. Fixtures are defined in the hardware map file as a list: .. code-block:: yaml - connected: true fixtures: - gpio_loopback id: 0240000026334e450015400f5e0e000b4eb1000097969900 platform: frdm_k64f product: DAPLink CMSIS-DAP runner: pyocd serial: /dev/ttyACM9 When running ``twister`` with ``--device-testing``, the configured fixture in the hardware map file will be matched to test scenarios requesting the same fixtures and these tests will be executed on the boards that provide this fixture. .. figure:: figures/fixtures.svg :figclass: align-center Fixtures can also be provided via twister command option ``--fixture``, this option can be used multiple times and all given fixtures will be appended as a list. And the given fixtures will be assigned to all boards, this means that all boards set by current twister command can run those test scenarios which request the same fixtures. Some fixtures allow for configuration strings to be appended, separated from the fixture name by a ``:``. Only the fixture name is matched against the fixtures requested by test scenarios. Notes +++++ It may be useful to annotate board descriptions in the hardware map file with additional information. Use the ``notes`` keyword to do this. For example: .. code-block:: yaml - connected: false fixtures: - gpio_loopback id: 000683290670 notes: An nrf5340dk/nrf5340 is detected as an nrf52840dk/nrf52840 with no serial port, and three serial ports with an unknown platform. The board id of the serial ports is not the same as the board id of the development kit. If you regenerate this file you will need to update serial to reference the third port, and platform to nrf5340dk/nrf5340/cpuapp or another supported board target. platform: nrf52840dk/nrf52840 product: J-Link runner: jlink serial: null Overriding Board Identifier +++++++++++++++++++++++++++ When (re-)generated the hardware map file will contain an ``id`` keyword that serves as the argument to ``--board-id`` when flashing. In some cases the detected ID is not the correct one to use, for example when using an external J-Link probe. The ``probe_id`` keyword overrides the ``id`` keyword for this purpose. For example: .. code-block:: yaml - connected: false id: 0229000005d9ebc600000000000000000000000097969905 platform: mimxrt1060_evk probe_id: 000609301751 product: DAPLink CMSIS-DAP runner: jlink serial: null Quarantine ++++++++++ Twister allows user to provide configuration files defining a list of tests or platforms to be put under quarantine. Such tests will be skipped and marked accordingly in the output reports. This feature is especially useful when running larger test suits, where a failure of one test can affect the execution of other tests (e.g. putting the physical board in a corrupted state). To use the quarantine feature one has to add the argument ``--quarantine-list <PATH_TO_QUARANTINE_YAML>`` to a twister call. Multiple quarantine files can be used. The current status of tests on the quarantine list can also be verified by adding ``--quarantine-verify`` to the above argument. This will make twister skip all tests which are not on the given list. A quarantine yaml has to be a sequence of dictionaries. Each dictionary has to have ``scenarios`` and ``platforms`` entries listing combinations of scenarios and platforms to put under quarantine. In addition, an optional entry ``comment`` can be used, where some more details can be given (e.g. link to a reported issue). These comments will also be added to the output reports. When quarantining a class of tests or many scenarios in a single testsuite or when dealing with multiple issues within a subsystem, it is possible to use regular expressions, for example, kernel.*** would quarantine all kernel tests. An example of entries in a quarantine yaml: .. code-block:: yaml - scenarios: - sample.basic.helloworld comment: "Link to the issue: path_to_url" - scenarios: - kernel.common - kernel.common.(misra\|tls) - kernel.common.nano64 platforms: - ._cortex_. - native_sim To exclude a platform, use the following syntax: .. code-block:: yaml - platforms: - qemu_x86 comment: "broken qemu" Additionally you can quarantine entire architectures or a specific simulator for executing tests. Test Configuration ****************** A test configuration can be used to customize various aspects of twister and the default enabled options and features. This allows tweaking the filtering capabilities depending on the environment and makes it possible to adapt and improve coverage when targeting different sets of platforms. The test configuration also adds support for test levels and the ability to assign a specific test to one or more levels. Using command line options of twister it is then possible to select a level and just execute the tests included in this level. Additionally, the test configuration allows defining level dependencies and additional inclusion of tests into a specific level if the test itself does not have this information already. In the configuration file you can include complete components using regular expressions and you can specify which test level to import from the same file, making management of levels easier. To help with testing outside of upstream CI infrastructure, additional options are available in the configuration file, which can be hosted locally. As of now, those options are available: - Ability to ignore default platforms as defined in board definitions (Those are mostly emulation platforms used to run tests in upstream CI) - Option to specify your own list of default platforms overriding what upstream defines. - Ability to override `build_on_all` options used in some test scenarios. This will treat tests or sample as any other just build for default platforms you specify in the configuration file or on the command line. - Ignore some logic in twister to expand platform coverage in cases where default platforms are not in scope. Platform Configuration ====================== The following options control platform filtering in twister: - `override_default_platforms`: override default key a platform sets in board configuration and instead use the list of platforms provided in the configuration file as the list of default platforms. This option is set to False by default. - `increased_platform_scope`: This option is set to True by default, when disabled, twister will not increase platform coverage automatically and will only build and run tests on the specified platforms. - `default_platforms`: A list of additional default platforms to add. This list can either be used to replace the existing default platforms or can extend it depending on the value of `override_default_platforms`. And example platforms configuration: .. code-block:: yaml platforms: override_default_platforms: true increased_platform_scope: false default_platforms: - qemu_x86 Test Level Configuration ======================== The test configuration allows defining test levels, level dependencies and additional inclusion of tests into a specific test level if the test itself does not have this information already. In the configuration file you can include complete components using regular expressions and you can specify which test level to import from the same file, making management of levels simple. And example test level configuration: .. code-block:: yaml levels: - name: my-test-level description: > my custom test level adds: - kernel.threads.* - kernel.timer.behavior - arch.interrupt - boards.* Combined configuration ====================== To mix the Platform and level configuration, you can take an example as below: An example platforms plus level configuration: .. code-block:: yaml platforms: override_default_platforms: true default_platforms: - frdm_k64f levels: - name: smoke description: > A plan to be used verifying basic zephyr features. - name: unit description: > A plan to be used verifying unit test. - name: integration description: > A plan to be used verifying integration. - name: acceptance description: > A plan to be used verifying acceptance. - name: system description: > A plan to be used verifying system. - name: regression description: > A plan to be used verifying regression. To run with above test_config.yaml file, only default_platforms with given test level test scenarios will run. .. tabs:: .. group-tab:: Linux .. code-block:: bash scripts/twister --test-config=<path to>/test_config.yaml -T tests --level="smoke" Running in Tests in Random Order ****************************** Enable ZTEST framework's :kconfig:option:`CONFIG_ZTEST_SHUFFLE` config option to run your tests in random order. This can be beneficial for identifying dependencies between test cases. For native_sim platforms, you can provide the seed to the random number generator by providing ``-seed=value`` as an argument to twister. See :ref:`Shuffling Test Sequence <ztest_shuffle>` for more details. Robot Framework Tests ******************* Zephyr supports `Robot Framework <path_to_url`_ as one of solutions for automated testing. Robot files allow you to express interactive test scenarios in human-readable text format and execute them in simulation or against hardware. At this moment Zephyr integration supports running Robot tests in the `Renode <path_to_url`_ simulation framework. To execute a Robot test suite with twister, run the following command: .. tabs:: .. group-tab:: Linux .. code-block:: bash $ ./scripts/twister --platform hifive1 --test samples/subsys/shell/shell_module/sample.shell.shell_module.robot .. group-tab:: Windows .. code-block:: bat python .\scripts\twister --platform hifive1 --test samples/subsys/shell/shell_module/sample.shell.shell_module.robot Writing Robot tests =================== For the list of keywords provided by the Robot Framework itself, refer to `the official Robot documentation <path_to_url`_. Information on writing and running Robot Framework tests in Renode can be found in `the testing section <path_to_url`_ of Renode documentation. It provides a list of the most commonly used keywords together with links to the source code where those are defined. It's possible to extend the framework by adding new keywords expressed directly in Robot test suite files, as an external Python library or, like Renode does it, dynamically via XML-RPC. For details see the `extending Robot Framework <path_to_url#extending-robot-framework>`_ section in the official Robot documentation. Running a single testsuite ========================== To run a single testsuite instead of a whole group of test you can run: .. code-block:: bash $ twister -p qemu_riscv32 -s tests/kernel/interrupt/arch.shared_interrupt ```	/content/code_sandbox/doc/develop/test/twister.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	11,784
```c #include <zephyr/ztest.h> static void expect_two_parameters(int a, int b) { ztest_check_expected_value(a); ztest_check_expected_value(b); } static void parameter_tests(void) { ztest_expect_value(expect_two_parameters, a, 2); ztest_expect_value(expect_two_parameters, b, 3); expect_two_parameters(2, 3); } static int returns_int(void) { return ztest_get_return_value(); } static void return_value_tests(void) { ztest_returns_value(returns_int, 5); zassert_equal(returns_int(), 5, NULL); } void test_main(void) { ztest_test_suite(mock_framework_tests, ztest_unit_test(parameter_test), ztest_unit_test(return_value_test) ); ztest_run_test_suite(mock_framework_tests); } ```	/content/code_sandbox/doc/develop/test/mocking.c	c	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	170
```restructuredtext .. _coverage: Generating coverage reports ########################### With Zephyr, you can generate code coverage reports to analyze which parts of the code are covered by a given test or application. You can do this in two ways: * In a real embedded target or QEMU, using Zephyr's gcov integration * Directly in your host computer, by compiling your application targeting the POSIX architecture Test coverage reports in embedded devices or QEMU ************************************************* Overview ======== `GCC GCOV <gcov_>`_ is a test coverage program used together with the GCC compiler to analyze and create test coverage reports for your programs, helping you create more efficient, faster running code and discovering untested code paths In Zephyr, gcov collects coverage profiling data in RAM (and not to a file system) while your application is running. Support for gcov collection and reporting is limited by available RAM size and so is currently enabled only for QEMU emulation of embedded targets. Details ======= There are 2 parts to enable this feature. The first is to enable the coverage for the device and the second to enable in the test application. As explained earlier the code coverage with gcov is a function of RAM available. Therefore ensure that the device has enough RAM when enabling the coverage for it. For example a small device like frdm_k64f can run a simple test application but the more complex test cases which consume more RAM will crash when coverage is enabled. To enable the device for coverage, select :kconfig:option:`CONFIG_HAS_COVERAGE_SUPPORT` in the Kconfig.board file. To report the coverage for the particular test application set :kconfig:option:`CONFIG_COVERAGE`. Steps to generate code coverage reports ======================================= These steps will produce an HTML coverage report for a single application. 1. Build the code with CONFIG_COVERAGE=y. .. zephyr-app-commands:: :board: mps2/an385 :gen-args: -DCONFIG_COVERAGE=y -DCONFIG_COVERAGE_DUMP=y :goals: build :compact: #. Capture the emulator output into a log file. You may need to terminate the emulator with :kbd:`Ctrl-A X` for this to complete after the coverage dump has been printed: .. code-block:: console ninja -Cbuild run \| tee log.log or .. code-block:: console ninja -Cbuild run \| tee log.log #. Generate the gcov ``.gcda`` and ``.gcno`` files from the log file that was saved:: $ python3 scripts/gen_gcov_files.py -i log.log #. Find the gcov binary placed in the SDK. You will need to pass the path to the gcov binary for the appropriate architecture when you later invoke ``gcovr``:: $ find $ZEPHYR_SDK_INSTALL_DIR -iregex ".gcov" #. Create an output directory for the reports:: $ mkdir -p gcov_report #. Run ``gcovr`` to get the reports:: $ gcovr -r $ZEPHYR_BASE . --html -o gcov_report/coverage.html --html-details --gcov-executable <gcov_path_in_SDK> .. _coverage_posix: Coverage reports using the POSIX architecture ****************************************** When compiling for the POSIX architecture, you utilize your host native tooling to build a native executable which contains your application, the Zephyr OS, and some basic HW emulation. That means you can use the same tools you would while developing any other desktop application. To build your application with ``gcc``'s `gcov`_, simply set :kconfig:option:`CONFIG_COVERAGE` before compiling it. When you run your application, ``gcov`` coverage data will be dumped into the respective ``gcda`` and ``gcno`` files. You may postprocess these with your preferred tools. For example: .. zephyr-app-commands:: :zephyr-app: samples/hello_world :gen-args: -DCONFIG_COVERAGE=y :host-os: unix :board: native_sim :goals: build :compact: .. code-block:: console $ ./build/zephyr/zephyr.exe # Press Ctrl+C to exit lcov --capture --directory ./ --output-file lcov.info -q --rc lcov_branch_coverage=1 genhtml lcov.info --output-directory lcov_html -q --ignore-errors source --branch-coverage --highlight --legend .. note:: You need a recent version of lcov (at least 1.14) with support for intermediate text format. Such packages exist in recent Linux distributions. Alternatively, you can use gcovr (at least version 4.2). Coverage reports using Twister **************************** Zephyr's :ref:`twister script <twister_script>` can automatically generate a coverage report from the tests which were executed. You just need to invoke it with the ``--coverage`` command line option. For example, you may invoke:: $ twister --coverage -p qemu_x86 -T tests/kernel or:: $ twister --coverage -p native_sim -T tests/bluetooth which will produce ``twister-out/coverage/index.html`` report as well as the coverage data collected by ``gcovr`` tool in ``twister-out/coverage.json``. Other reports might be chosen with ``--coverage-tool`` and ``--coverage-formats`` command line options. The process differs for unit tests, which are built with the host toolchain and require a different board:: $ twister --coverage -p unit_testing -T tests/unit which produces a report in the same location as non-unit testing. .. _gcov: path_to_url Using different toolchains ========================== Twister looks at the environment variable ``ZEPHYR_TOOLCHAIN_VARIANT`` to check which gcov tool to use by default. The following are used as the default for the Twister ``--gcov-tool`` argument default: +-----------+-----------------------+ \| Toolchain \| ``--gcov-tool`` value \| +-----------+-----------------------+ \| host \| ``gcov`` \| +-----------+-----------------------+ \| llvm \| ``llvm-cov gcov`` \| +-----------+-----------------------+ \| zephyr \| ``gcov`` \| +-----------+-----------------------+ ```	/content/code_sandbox/doc/develop/test/coverage.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,382
```restructuredtext .. _testing: Testing ####### .. toctree:: :maxdepth: 1 ztest twister twister/twister_blackbox pytest coverage BabbleSim<bsim> ztest_deprecated ```	/content/code_sandbox/doc/develop/test/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	59
```restructuredtext .. _west-manifests: West Manifests ############## This page contains detailed information about west's multiple repository model, manifest files, and the ``west manifest`` command. For API documentation on the ``west.manifest`` module, see :ref:`west-apis-manifest`. For a more general introduction and command overview, see :ref:`west-basics`. .. only:: html .. contents:: :depth: 3 .. _west-mr-model: Multiple Repository Model *********************** West's view of the repositories in a :term:`west workspace`, and their history, looks like the following figure (though some parts of this example are specific to upstream Zephyr's use of west): .. figure:: west-mr-model.png :align: center :alt: West multi-repo history :figclass: align-center West multi-repo history The history of the manifest repository is the line of Git commits which is "floating" on top of the gray plane. Parent commits point to child commits using solid arrows. The plane below contains the Git commit history of the repositories in the workspace, with each project repository boxed in by a rectangle. Parent/child commit relationships in each repository are also shown with solid arrows. The commits in the manifest repository (again, for upstream Zephyr this is the zephyr repository itself) each have a manifest file. The manifest file in each commit specifies the corresponding commits which it expects in each of the project repositories. This relationship is shown using dotted line arrows in the diagram. Each dotted line arrow points from a commit in the manifest repository to a corresponding commit in a project repository. Notice the following important details: - Projects can be added (like ``P1`` between manifest repository commits ``D`` and ``E``) and removed (``P2`` between the same manifest repository commits) - Project and manifest repository histories don't have to move forwards or backwards together: - ``P2`` stays the same from ``A B``, as do ``P1`` and ``P3`` from ``F G``. - ``P3`` moves forward from ``A B``. - ``P3`` moves backward from ``C D``. One use for moving backward in project history is to "revert" a regression by going back to a revision before it was introduced. - Project repository commits can be "skipped": ``P3`` moves forward multiple commits in its history from ``B C``. - In the above diagram, no project repository has two revisions "at the same time": every manifest file refers to exactly one commit in the projects it cares about. This can be relaxed by using a branch name as a manifest revision, at the cost of being able to bisect manifest repository history. .. _west-manifest-files: Manifest Files ************ West manifests are YAML files. Manifests have a top-level ``manifest`` section with some subsections, like this: .. code-block:: yaml manifest: remotes: # short names for project URLs projects: # a list of projects managed by west defaults: # default project attributes self: # configuration related to the manifest repository itself, # i.e. the repository containing west.yml version: "<schema-version>" group-filter: # a list of project groups to enable or disable In YAML terms, the manifest file contains a mapping, with a ``manifest`` key. Any other keys and their contents are ignored (west v0.5 also required a ``west`` key, but this is ignored starting with v0.6). The manifest contains subsections, like ``defaults``, ``remotes``, ``projects``, and ``self``. In YAML terms, the value of the ``manifest`` key is also a mapping, with these "subsections" as keys. As of west v0.10, all of these "subsection" keys are optional. The ``projects`` value is a list of repositories managed by west and associated metadata. We'll discuss it soon, but first we will describe the ``remotes`` section, which can be used to save typing in the ``projects`` list. Remotes ======= The ``remotes`` subsection contains a sequence which specifies the base URLs where projects can be fetched from. Each ``remotes`` element has a name and a "URL base". These are used to form the complete Git fetch URL for each project. A project's fetch URL can be set by appending a project-specific path onto a remote URL base. (As we'll see below, projects can also specify their complete fetch URLs.) For example: .. code-block:: yaml manifest: # ... remotes: - name: remote1 url-base: path_to_url - name: remote2 url-base: path_to_url The ``remotes`` keys and their usage are in the following table. .. list-table:: remotes keys :header-rows: 1 :widths: 1 5 * - Key - Description * - ``name`` - Mandatory; a unique name for the remote. * - ``url-base`` - A prefix that is prepended to the fetch URL for each project with this remote. Above, two remotes are given, with names ``remote1`` and ``remote2``. Their URL bases are respectively ``path_to_url`` and ``path_to_url``. You can use SSH URL bases as well; for example, you might use ``git@example.com:base1`` if ``remote1`` supported Git over SSH as well. Anything acceptable to Git will work. .. _west-manifests-projects: Projects ======== The ``projects`` subsection contains a sequence describing the project repositories in the west workspace. Every project has a unique name. You can specify what Git remote URLs to use when cloning and fetching the projects, what revisions to track, and where the project should be stored on the local file system. Note that west projects :ref:`are different from modules <modules-vs-projects>`. Here is an example. We'll assume the ``remotes`` given above. .. Note: if you change this example, keep the equivalent manifest below in sync. .. code-block:: yaml manifest: # [... same remotes as above...] projects: - name: proj1 description: the first example project remote: remote1 path: extra/project-1 - name: proj2 description: \| A multi-line description of the second example project. repo-path: my-path remote: remote2 revision: v1.3 - name: proj3 url: path_to_url revision: abcde413a111 In this manifest: - ``proj1`` has remote ``remote1``, so its Git fetch URL is ``path_to_url``. The remote ``url-base`` is appended with a ``/`` and the project ``name`` to form the URL. Locally, this project will be cloned at path ``extra/project-1`` relative to the west workspace's root directory, since it has an explicit ``path`` attribute with this value. Since the project has no ``revision`` specified, ``master`` is used by default. The current tip of this branch will be fetched and checked out as a detached ``HEAD`` when west next updates this project. - ``proj2`` has a ``remote`` and a ``repo-path``, so its fetch URL is ``path_to_url``. The ``repo-path`` attribute, if present, overrides the default ``name`` when forming the fetch URL. Since the project has no ``path`` attribute, its ``name`` is used by default. It will be cloned into a directory named ``proj2``. The commit pointed to by the ``v1.3`` tag will be checked out when west updates the project. - ``proj3`` has an explicit ``url``, so it will be fetched from ``path_to_url``. Its local path defaults to its name, ``proj3``. Commit ``abcde413a111`` will be checked out when it is next updated. The available project keys and their usage are in the following table. Sometimes we'll refer to the ``defaults`` subsection; it will be described next. .. list-table:: projects elements keys :header-rows: 1 :widths: 1 5 * - Key(s) - Description * - ``name`` - Mandatory; a unique name for the project. The name cannot be one of the reserved values "west" or "manifest". The name must be unique in the manifest file. * - ``description`` - Optional, an informational description of the project. Added in west v1.2.0. * - ``remote``, ``url`` - Mandatory (one of the two, but not both). If the project has a ``remote``, that remote's ``url-base`` will be combined with the project's ``name`` (or ``repo-path``, if it has one) to form the fetch URL instead. If the project has a ``url``, that's the complete fetch URL for the remote Git repository. If the project has neither, the ``defaults`` section must specify a ``remote``, which will be used as the project's remote. Otherwise, the manifest is invalid. * - ``repo-path`` - Optional. If given, this is concatenated on to the remote's ``url-base`` instead of the project's ``name`` to form its fetch URL. Projects may not have both ``url`` and ``repo-path`` attributes. * - ``revision`` - Optional. The Git revision that ``west update`` should check out. This will be checked out as a detached HEAD by default, to avoid conflicting with local branch names. If not given, the ``revision`` value from the ``defaults`` subsection will be used if present. A project revision can be a branch, tag, or SHA. The default ``revision`` is ``master`` if not otherwise specified. Using ``HEAD~0`` [#f1]_ as the ``revision`` will cause west to keep the current state of the project. * - ``path`` - Optional. Relative path specifying where to clone the repository locally, relative to the top directory in the west workspace. If missing, the project's ``name`` is used as a directory name. * - ``clone-depth`` - Optional. If given, a positive integer which creates a shallow history in the cloned repository limited to the given number of commits. This can only be used if the ``revision`` is a branch or tag. * - ``west-commands`` - Optional. If given, a relative path to a YAML file within the project which describes additional west commands provided by that project. This file is named :file:`west-commands.yml` by convention. See :ref:`west-extensions` for details. * - ``import`` - Optional. If ``true``, imports projects from manifest files in the given repository into the current manifest. See :ref:`west-manifest-import` for details. * - ``groups`` - Optional, a list of groups the project belongs to. See :ref:`west-manifest-groups` for details. * - ``submodules`` - Optional. You can use this to make ``west update`` also update `Git submodules`_ defined by the project. See :ref:`west-manifest-submodules` for details. * - ``userdata`` - Optional. The value is an arbitrary YAML value. See :ref:`west-project-userdata`. .. rubric:: Footnotes .. [#f1] In git, HEAD is a reference, whereas HEAD~<n> is a valid revision but not a reference. West fetches references, such as refs/heads/main or HEAD, and commits not available locally, but will not fetch commits if they are already available. HEAD~0 is resolved to a specific commit that is locally available, and therefore west will simply checkout the locally available commit, identified by HEAD~0. .. _Git submodules: path_to_url Defaults ======== The ``defaults`` subsection can provide default values for project attributes. In particular, the default remote name and revision can be specified here. Another way to write the same manifest we have been describing so far using ``defaults`` is: .. code-block:: yaml manifest: defaults: remote: remote1 revision: v1.3 remotes: - name: remote1 url-base: path_to_url - name: remote2 url-base: path_to_url projects: - name: proj1 description: the first example project path: extra/project-1 revision: master - name: proj2 description: \| A multi-line description of the second example project. repo-path: my-path remote: remote2 - name: proj3 url: path_to_url revision: abcde413a111 The available ``defaults`` keys and their usage are in the following table. .. list-table:: defaults keys :header-rows: 1 :widths: 1 5 * - Key - Description * - ``remote`` - Optional. This will be used for a project's ``remote`` if it does not have a ``url`` or ``remote`` key set. * - ``revision`` - Optional. This will be used for a project's ``revision`` if it does not have one set. If not given, the default is ``master``. Self ==== The ``self`` subsection can be used to control the manifest repository itself. As an example, let's consider this snippet from the zephyr repository's :file:`west.yml`: .. code-block:: yaml manifest: # ... self: path: zephyr west-commands: scripts/west-commands.yml This ensures that the zephyr repository is cloned into path ``zephyr``, though as explained above that would have happened anyway if cloning from the default manifest URL, ``path_to_url``. Since the zephyr repository does contain extension commands, its ``self`` entry declares the location of the corresponding :file:`west-commands.yml` relative to the repository root. The available ``self`` keys and their usage are in the following table. .. list-table:: self keys :header-rows: 1 :widths: 1 5 * - Key - Description * - ``path`` - Optional. The path ``west init`` should clone the manifest repository into, relative to the west workspace topdir. If not given, the basename of the path component in the manifest repository URL will be used by default. For example, if the URL is ``path_to_url``, the manifest repository would be cloned to the directory :file:`project-repo`. * - ``west-commands`` - Optional. This is analogous to the same key in a project sequence element. * - ``import`` - Optional. This is also analogous to the ``projects`` key, but allows importing projects from other files in the manifest repository. See :ref:`west-manifest-import`. .. _west-manifest-schema-version: Version ======= The ``version`` subsection declares that the manifest file uses features which were introduced in some version of west. Attempts to load the manifest with older versions of west will fail with an error message that explains the minimum required version of west which is needed. Here is an example: .. code-block:: yaml manifest: # Marks that this file uses version 0.10 of the west manifest # file format. # # An attempt to load this manifest file with west v0.8.0 will # fail with an error message saying that west v0.10.0 or # later is required. version: "0.10" The pykwalify schema :file:`manifest-schema.yml` in the `west source code repository`_ is used to validate the manifest section. .. _west source code repository: path_to_url Here is a table with the valid ``version`` values, along with information about the manifest file features that were introduced in that version. .. list-table:: :header-rows: 1 :widths: 1 4 * - ``version`` - New features * - ``"0.7"`` - Initial support for the ``version`` feature. All manifest file features that are not otherwise mentioned in this table were introduced in west v0.7.0 or earlier. * - ``"0.8"`` - Support for ``import: path-prefix:`` (:ref:`west-manifest-import-map`) * - ``"0.9"`` - Use of west v0.9.x is discouraged. This schema version is provided to allow users to explicitly request compatibility with west :ref:`west_0_9_0`. However, west :ref:`west_0_10_0` and later have incompatible behavior for features that were introduced in west v0.9.0. You should ignore version "0.9" if possible. * - ``"0.10"`` - Support for: - ``submodules:`` in ``projects:`` (:ref:`west-manifest-submodules`) - ``manifest: group-filter:``, and ``groups:`` in ``projects:`` (:ref:`west-manifest-groups`) - The ``import:`` feature now supports ``allowlist:`` and ``blocklist:``; these are respectively recommended as replacements for older names as part of a general Zephyr-wide inclusive language change. The older key names are still supported for backwards compatibility. (:ref:`west-manifest-import`, :ref:`west-manifest-import-map`) * - ``"0.12"`` - Support for ``userdata:`` in ``projects:`` (:ref:`west-project-userdata`) * - ``"0.13"`` - Support for ``self: userdata:`` (:ref:`west-project-userdata`) * - ``"1.0"`` - Identical to ``"0.13"``, but available for use by users that do not wish to use a ``"0.x"`` version field. * - ``"1.2"`` - Support for ``description:`` in ``projects:`` (:ref:`west-manifests-projects`) .. note:: Versions of west without any new features in the manifest file format do not change the list of valid ``version`` values. For example, ``version: "0.11"`` is not valid, because west v0.11.x did not introduce new manifest file format features. Quoting the ``version`` value as shown above forces the YAML parser to treat it as a string. Without quotes, ``0.10`` in YAML is just the floating point value ``0.1``. You can omit the quotes if the value is the same when cast to string, but it's best to include them. Always use quotes if you're not sure. If you do not include a ``version`` in your manifest, each new release of west assumes that it should try to load it using the features that were available in that release. This may result in error messages that are harder to understand if that version of west is too old to load the manifest. Group-filter ============ See :ref:`west-manifest-groups`. .. _west-active-inactive-projects: Active and Inactive Projects **************************** Projects defined in the west manifest can be inactive or active. The difference is that an inactive project is generally ignored by west. For example, ``west update`` will not update inactive projects, and ``west list`` will not print information about them by default. As another example, any :ref:`west-manifest-import` in an inactive project will be ignored by west. There are two ways to make a project inactive: 1. Using the ``manifest.project-filter`` configuration option. If a project is made active or inactive using this option, then the rules related to making a project inactive using its ``groups:`` are ignored. That is, if a regular expression in ``manifest.project-filter`` applies to a project, the project's groups have no effect on whether it is active or inactive. See the entry for this option in :ref:`west-config-index` for details. 2. Otherwise, if a project has groups, and they are all disabled, then the project is inactive. See the following section for details. .. _west-manifest-groups: Project Groups ************ You can use the ``groups`` and ``group-filter`` keys briefly described :ref:`above <west-manifest-files>` to place projects into groups, and to enable or disable groups. For example, this lets you run a ``west forall`` command only on the projects in the group by using ``west forall --group``. This can also let you make projects inactive; see the previous section for more information on inactive projects. The next section introduces project groups. The following section describes :ref:`west-enabled-disabled-groups`. There are some basic examples in :ref:`west-project-group-examples`. Finally, :ref:`west-group-filter-imports` provides a simplified overview of how ``group-filter`` interacts with the :ref:`west-manifest-import` feature. Groups Basics ============= The ``groups:`` and ``group-filter:`` keys appear in the manifest like this: .. code-block:: yaml manifest: projects: - name: some-project groups: ... group-filter: ... The ``groups`` key's value is a list of group names. Group names are strings. You can enable or disable project groups using ``group-filter``. Projects whose groups are all disabled, and which are not otherwise made active by a ``manifest.project-filter`` configuration option, are inactive. For example, in this manifest fragment: .. code-block:: yaml manifest: projects: - name: project-1 groups: - groupA - name: project-2 groups: - groupB - groupC - name: project-3 The projects are in these groups: - ``project-1``: one group, named ``groupA`` - ``project-2``: two groups, named ``groupB`` and ``groupC`` - ``project-3``: no groups Project group names must not contain commas (,), colons (:), or whitespace. Group names must not begin with a dash (-) or the plus sign (+), but they may contain these characters elsewhere in their names. For example, ``foo-bar`` and ``foo+bar`` are valid groups, but ``-foobar`` and ``+foobar`` are not. Group names are otherwise arbitrary strings. Group names are case sensitive. As a restriction, no project may use both ``import:`` and ``groups:``. (This is necessary to avoid some pathological edge cases.) .. _west-enabled-disabled-groups: Enabled and Disabled Project Groups =================================== All project groups are enabled by default. You can enable or disable groups in both your manifest file and :ref:`west-config`. Within a manifest file, ``manifest: group-filter:`` is a YAML list of groups to enable and disable. To enable a group, prefix its name with a plus sign (+). For example, ``groupA`` is enabled in this manifest fragment: .. code-block:: yaml manifest: group-filter: [+groupA] Although this is redundant for groups that are already enabled by default, it can be used to override settings in an imported manifest file. See :ref:`west-group-filter-imports` for more information. To disable a group, prefix its name with a dash (-). For example, ``groupA`` and ``groupB`` are disabled in this manifest fragment: .. code-block:: yaml manifest: group-filter: [-groupA,-groupB] .. note:: Since ``group-filter`` is a YAML list, you could have written this fragment as follows: .. code-block:: yaml manifest: group-filter: - -groupA - -groupB However, this syntax is harder to read and therefore discouraged. In addition to the manifest file, you can control which groups are enabled and disabled using the ``manifest.group-filter`` configuration option. This option is a comma-separated list of groups to enable and/or disable. To enable a group, add its name to the list prefixed with ``+``. To disable a group, add its name prefixed with ``-``. For example, setting ``manifest.group-filter`` to ``+groupA,-groupB`` enables ``groupA``, and disables ``groupB``. The value of the configuration option overrides any data in the manifest file. You can think of this as if the ``manifest.group-filter`` configuration option is appended to the ``manifest: group-filter:`` list from YAML, with "last entry wins" semantics. .. _west-project-group-examples: Project Group Examples ====================== This section contains example situations involving project groups and active projects. The examples use both ``manifest: group-filter:`` YAML lists and ``manifest.group-filter`` configuration lists, to show how they work together. Note that the ``defaults`` and ``remotes`` data in the following manifests isn't relevant except to make the examples complete and self-contained. .. note:: In all of the examples that follow, the ``manifest.project-filter`` option is assumed to be unset. Example 1: no disabled groups ----------------------------- The entire manifest file is: .. code-block:: yaml manifest: projects: - name: foo groups: - groupA - name: bar groups: - groupA - groupB - name: baz defaults: remote: example-remote remotes: - name: example-remote url-base: path_to_url The ``manifest.group-filter`` configuration option is not set (you can ensure this by running ``west config -D manifest.group-filter``). No groups are disabled, because all groups are enabled by default. Therefore, all three projects (``foo``, ``bar``, and ``baz``) are active. Note that there is no way to make project ``baz`` inactive, since it has no groups. Example 2: Disabling one group via manifest ------------------------------------------- The entire manifest file is: .. code-block:: yaml manifest: projects: - name: foo groups: - groupA - name: bar groups: - groupA - groupB group-filter: [-groupA] defaults: remote: example-remote remotes: - name: example-remote url-base: path_to_url The ``manifest.group-filter`` configuration option is not set (you can ensure this by running ``west config -D manifest.group-filter``). Since ``groupA`` is disabled, project ``foo`` is inactive. Project ``bar`` is active, because ``groupB`` is enabled. Example 3: Disabling multiple groups via manifest ------------------------------------------------- The entire manifest file is: .. code-block:: yaml manifest: projects: - name: foo groups: - groupA - name: bar groups: - groupA - groupB group-filter: [-groupA,-groupB] defaults: remote: example-remote remotes: - name: example-remote url-base: path_to_url The ``manifest.group-filter`` configuration option is not set (you can ensure this by running ``west config -D manifest.group-filter``). Both ``foo`` and ``bar`` are inactive, because all of their groups are disabled. Example 4: Disabling a group via configuration ---------------------------------------------- The entire manifest file is: .. code-block:: yaml manifest: projects: - name: foo groups: - groupA - name: bar groups: - groupA - groupB defaults: remote: example-remote remotes: - name: example-remote url-base: path_to_url The ``manifest.group-filter`` configuration option is set to ``-groupA`` (you can ensure this by running ``west config manifest.group-filter -- -groupA``; the extra ``--`` is required so the argument parser does not treat ``-groupA`` as a command line option ``-g`` with value ``roupA``). Project ``foo`` is inactive because ``groupA`` has been disabled by the ``manifest.group-filter`` configuration option. Project ``bar`` is active because ``groupB`` is enabled. Example 5: Overriding a disabled group via configuration -------------------------------------------------------- The entire manifest file is: .. code-block:: yaml manifest: projects: - name: foo - name: bar groups: - groupA - name: baz groups: - groupA - groupB group-filter: [-groupA] defaults: remote: example-remote remotes: - name: example-remote url-base: path_to_url The ``manifest.group-filter`` configuration option is set to ``+groupA`` (you can ensure this by running ``west config manifest.group-filter +groupA``). In this case, ``groupA`` is enabled: the ``manifest.group-filter`` configuration option has higher precedence than the ``manifest: group-filter: [-groupA]`` content in the manifest file. Therefore, projects ``foo`` and ``bar`` are both active. Example 6: Overriding multiple disabled groups via configuration your_sha256_hash The entire manifest file is: .. code-block:: yaml manifest: projects: - name: foo - name: bar groups: - groupA - name: baz groups: - groupA - groupB group-filter: [-groupA,-groupB] defaults: remote: example-remote remotes: - name: example-remote url-base: path_to_url The ``manifest.group-filter`` configuration option is set to ``+groupA,+groupB`` (you can ensure this by running ``west config manifest.group-filter "+groupA,+groupB"``). In this case, both ``groupA`` and ``groupB`` are enabled, because the configuration value overrides the manifest file for both groups. Therefore, projects ``foo`` and ``bar`` are both active. Example 7: Disabling multiple groups via configuration ------------------------------------------------------ The entire manifest file is: .. code-block:: yaml manifest: projects: - name: foo - name: bar groups: - groupA - name: baz groups: - groupA - groupB defaults: remote: example-remote remotes: - name: example-remote url-base: path_to_url The ``manifest.group-filter`` configuration option is set to ``-groupA,-groupB`` (you can ensure this by running ``west config manifest.group-filter -- "-groupA,-groupB"``). In this case, both ``groupA`` and ``groupB`` are disabled. Therefore, projects ``foo`` and ``bar`` are both inactive. .. _west-group-filter-imports: Group Filters and Imports ========================= This section provides a simplified description of how the ``manifest: group-filter:`` value behaves when combined with :ref:`west-manifest-import`. For complete details, see :ref:`west-manifest-formal`. .. warning:: The below semantics apply to west v0.10.0 and later. West v0.9.x semantics are different, and combining ``group-filter`` with ``import`` in west v0.9.x is discouraged. In short: - if you only import one manifest, any groups it disables in its ``group-filter`` are also disabled in your manifest - you can override this in your manifest file's ``manifest: group-filter:`` value, your workspace's ``manifest.group-filter`` configuration option, or both Here are some examples. Example 1: no overrides ----------------------- You are using this :file:`parent/west.yml` manifest: .. code-block:: yaml # parent/west.yml: manifest: projects: - name: child url: path_to_url import: true - name: project-1 url: path_to_url groups: - unstable And :file:`child/west.yml` contains: .. code-block:: yaml # child/west.yml: manifest: group-filter: [-unstable] projects: - name: project-2 url: path_to_url - name: project-3 url: path_to_url groups: - unstable Only ``child`` and ``project-2`` are active in the resolved manifest. The ``unstable`` group is disabled in :file:`child/west.yml`, and that is not overridden in :file:`parent/west.yml`. Therefore, the final ``group-filter`` for the resolved manifest is ``[-unstable]``. Since ``project-1`` and ``project-3`` are in the ``unstable`` group and are not in any other group, they are inactive. Example 2: overriding an imported ``group-filter`` via manifest --------------------------------------------------------------- You are using this :file:`parent/west.yml` manifest: .. code-block:: yaml # parent/west.yml: manifest: group-filter: [+unstable,-optional] projects: - name: child url: path_to_url import: true - name: project-1 url: path_to_url groups: - unstable And :file:`child/west.yml` contains: .. code-block:: yaml # child/west.yml: manifest: group-filter: [-unstable] projects: - name: project-2 url: path_to_url groups: - optional - name: project-3 url: path_to_url groups: - unstable Only the ``child``, ``project-1``, and ``project-3`` projects are active. The ``[-unstable]`` group filter in :file:`child/west.yml` is overridden in :file:`parent/west.yml`, so the ``unstable`` group is enabled. Since ``project-1`` and ``project-3`` are in the ``unstable`` group, they are active. The same :file:`parent/west.yml` file disables the ``optional`` group, so ``project-2`` is inactive. The final group filter specified by :file:`parent/west.yml` is ``[+unstable,-optional]``. Example 3: overriding an imported ``group-filter`` via configuration your_sha256_hash---- You are using this :file:`parent/west.yml` manifest: .. code-block:: yaml # parent/west.yml: manifest: projects: - name: child url: path_to_url import: true - name: project-1 url: path_to_url groups: - unstable And :file:`child/west.yml` contains: .. code-block:: yaml # child/west.yml: manifest: group-filter: [-unstable] projects: - name: project-2 url: path_to_url groups: - optional - name: project-3 url: path_to_url groups: - unstable If you run: .. code-block:: shell west config manifest.group-filter +unstable,-optional Then only the ``child``, ``project-1``, and ``project-3`` projects are active. The ``-unstable`` group filter in :file:`child/west.yml` is overridden in the ``manifest.group-filter`` configuration option, so the ``unstable`` group is enabled. Since ``project-1`` and ``project-3`` are in the ``unstable`` group, they are active. The same configuration option disables the ``optional`` group, so ``project-2`` is inactive. The final group filter specified by :file:`parent/west.yml` and the ``manifest.group-filter`` configuration option is ``[+unstable,-optional]``. .. _west-manifest-submodules: Git Submodules in Projects ********************** You can use the ``submodules`` keys briefly described :ref:`above <west-manifest-files>` to force ``west update`` to also handle any `Git submodules`_ configured in project's git repository. The ``submodules`` key can appear inside ``projects``, like this: .. code-block:: YAML manifest: projects: - name: some-project submodules: ... The ``submodules`` key can be a boolean or a list of mappings. We'll describe these in order. Option 1: Boolean ================= This is the easiest way to use ``submodules``. If ``submodules`` is ``true`` as a ``projects`` attribute, ``west update`` will recursively update the project's Git submodules whenever it updates the project itself. If it's ``false`` or missing, it has no effect. For example, let's say you have a source code repository ``foo``, which has some submodules, and you want ``west update`` to keep all of them in sync, along with another project named ``bar`` in the same workspace. You can do that with this manifest file: .. code-block:: yaml manifest: projects: - name: foo submodules: true - name: bar Here, ``west update`` will initialize and update all submodules in ``foo``. If ``bar`` has any submodules, they are ignored, because ``bar`` does not have a ``submodules`` value. Option 2: List of mappings ========================== The ``submodules`` key may be a list of mappings, one list element for each desired submodule. Each submodule listed is updated recursively. You can still track and update unlisted submodules with ``git`` commands manually; present or not they will be completely ignored by ``west``. The ``path`` key must match exactly the path of one submodule relative to its parent west project, as shown in the output of ``git submodule status``. The ``name`` key is optional and not used by west for now; it's not passed to ``git submodule`` commands either. The ``name`` key was briefly mandatory in west version 0.9.0, but was made optional in 0.9.1. For example, let's say you have a source code repository ``foo``, which has many submodules, and you want ``west update`` to keep some but not all of them in sync, along with another project named ``bar`` in the same workspace. You can do that with this manifest file: .. code-block:: yaml manifest: projects: - name: foo submodules: - path: path/to/foo-first-sub - name: foo-second-sub path: path/to/foo-second-sub - name: bar Here, ``west update`` will recursively initialize and update just the submodules in ``foo`` with paths ``path/to/foo-first-sub`` and ``path/to/foo-second-sub``. Any submodules in ``bar`` are still ignored. .. _west-project-userdata: Repository user data **************** West versions v0.12 and later support an optional ``userdata`` key in projects. West versions v0.13 and later supports this key in the ``manifest: self:`` section. It is meant for consumption by programs that require user-specific project metadata. Beyond parsing it as YAML, west itself ignores the value completely. The key's value is arbitrary YAML. West parses the value and makes it accessible to programs using :ref:`west-apis` as the ``userdata`` attribute of the corresponding ``west.manifest.Project`` object. Example manifest fragment: .. code-block:: yaml manifest: projects: - name: foo - name: bar userdata: a-string - name: baz userdata: key: value self: userdata: blub Example Python usage: .. code-block:: python manifest = west.manifest.Manifest.from_file() foo, bar, baz = manifest.get_projects(['foo', 'bar', 'baz']) foo.userdata # None bar.userdata # 'a-string' baz.userdata # {'key': 'value'} manifest.userdata # 'blub' .. _west-manifest-import: Manifest Imports ************ You can use the ``import`` key briefly described above to include projects from other manifest files in your :file:`west.yml`. This key can be either a ``project`` or ``self`` section attribute: .. code-block:: yaml manifest: projects: - name: some-project import: ... self: import: ... You can use a "self: import:" to load additional files from the repository containing your :file:`west.yml`. You can use a "project: ... import:" to load additional files defined in that project's Git history. West resolves the final manifest from individual manifest files in this order: #. imported files in ``self`` #. your :file:`west.yml` file #. imported files in ``projects`` During resolution, west ignores projects which have already been defined in other files. For example, a project named ``foo`` in your :file:`west.yml` makes west ignore other projects named ``foo`` imported from your ``projects`` list. The ``import`` key can be a boolean, path, mapping, or sequence. We'll describe these in order, using examples: - :ref:`Boolean <west-manifest-import-bool>` - :ref:`west-manifest-ex1.1` - :ref:`west-manifest-ex1.2` - :ref:`west-manifest-ex1.3` - :ref:`Relative path <west-manifest-import-path>` - :ref:`west-manifest-ex2.1` - :ref:`west-manifest-ex2.2` - :ref:`west-manifest-ex2.3` - :ref:`Mapping with additional configuration <west-manifest-import-map>` - :ref:`west-manifest-ex3.1` - :ref:`west-manifest-ex3.2` - :ref:`west-manifest-ex3.3` - :ref:`west-manifest-ex3.4` - :ref:`Sequence of paths and mappings <west-manifest-import-seq>` - :ref:`west-manifest-ex4.1` - :ref:`west-manifest-ex4.2` A more :ref:`formal description <west-manifest-formal>` of how this works is last, after the examples. Troubleshooting Note ==================== If you're using this feature and find west's behavior confusing, try :ref:`resolving your manifest <west-manifest-resolve>` to see the final results after imports are done. .. _west-manifest-import-bool: Option 1: Boolean ================= This is the easiest way to use ``import``. If ``import`` is ``true`` as a ``projects`` attribute, west imports projects from the :file:`west.yml` file in that project's root directory. If it's ``false`` or missing, it has no effect. For example, this manifest would import :file:`west.yml` from the ``p1`` git repository at revision ``v1.0``: .. code-block:: yaml manifest: # ... projects: - name: p1 revision: v1.0 import: true # Import west.yml from p1's v1.0 git tag - name: p2 import: false # Nothing is imported from p2. - name: p3 # Nothing is imported from p3 either. It's an error to set ``import`` to either ``true`` or ``false`` inside ``self``, like this: .. code-block:: yaml manifest: # ... self: import: true # Error .. _west-manifest-ex1.1: Example 1.1: Downstream of a Zephyr release ------------------------------------------- You have a source code repository you want to use with Zephyr v1.14.1 LTS. You want to maintain the whole thing using west. You don't want to modify any of the mainline repositories. In other words, the west workspace you want looks like this: .. code-block:: none my-downstream/ .west/ # west directory zephyr/ # mainline zephyr repository west.yml # the v1.14.1 version of this file is imported modules/ # modules from mainline zephyr hal/ [...other directories..] [ ... other projects ...] # other mainline repositories my-repo/ # your downstream repository west.yml # main manifest importing zephyr/west.yml v1.14.1 [...other files..] You can do this with the following :file:`my-repo/west.yml`: .. code-block:: yaml # my-repo/west.yml: manifest: remotes: - name: zephyrproject-rtos url-base: path_to_url projects: - name: zephyr remote: zephyrproject-rtos revision: v1.14.1 import: true You can then create the workspace on your computer like this, assuming ``my-repo`` is hosted at ``path_to_url``: .. code-block:: console west init -m path_to_url my-downstream cd my-downstream west update After ``west init``, :file:`my-downstream/my-repo` will be cloned. After ``west update``, all of the projects defined in the ``zephyr`` repository's :file:`west.yml` at revision ``v1.14.1`` will be cloned into :file:`my-downstream` as well. You can add and commit any code to :file:`my-repo` you please at this point, including your own Zephyr applications, drivers, etc. See :ref:`application`. .. _west-manifest-ex1.2: Example 1.2: "Rolling release" Zephyr downstream ------------------------------------------------ This is similar to :ref:`west-manifest-ex1.1`, except we'll use ``revision: main`` for the zephyr repository: .. code-block:: yaml # my-repo/west.yml: manifest: remotes: - name: zephyrproject-rtos url-base: path_to_url projects: - name: zephyr remote: zephyrproject-rtos revision: main import: true You can create the workspace in the same way: .. code-block:: console west init -m path_to_url my-downstream cd my-downstream west update This time, whenever you run ``west update``, the special :ref:`manifest-rev <west-manifest-rev>` branch in the ``zephyr`` repository will be updated to point at a newly fetched ``main`` branch tip from the URL path_to_url The contents of :file:`zephyr/west.yml` at the new ``manifest-rev`` will then be used to import projects from Zephyr. This lets you stay up to date with the latest changes in the Zephyr project. The cost is that running ``west update`` will not produce reproducible results, since the remote ``main`` branch can change every time you run it. It's also important to understand that west ignores your working tree's** :file:`zephyr/west.yml` entirely when resolving imports. West always uses the contents of imported manifests as they were committed to the latest ``manifest-rev`` when importing from a project. You can only import manifest from the file system if they are in your manifest repository's working tree. See :ref:`west-manifest-ex2.2` for an example. .. _west-manifest-ex1.3: Example 1.3: Downstream of a Zephyr release, with module fork ------------------------------------------------------------- This manifest is similar to the one in :ref:`west-manifest-ex1.1`, except it: - is a downstream of Zephyr 2.0 - includes a downstream fork of the :file:`modules/hal/nordic` :ref:`module <modules>` which was included in that release .. code-block:: yaml # my-repo/west.yml: manifest: remotes: - name: zephyrproject-rtos url-base: path_to_url - name: my-remote url-base: path_to_url projects: - name: hal_nordic # higher precedence remote: my-remote revision: my-sha path: modules/hal/nordic - name: zephyr remote: zephyrproject-rtos revision: v2.0.0 import: true # imported projects have lower precedence # subset of zephyr/west.yml contents at v2.0.0: manifest: defaults: remote: zephyrproject-rtos remotes: - name: zephyrproject-rtos url-base: path_to_url projects: # ... - name: hal_nordic # lower precedence, values ignored path: modules/hal/nordic revision: another-sha With this manifest file, the project named ``hal_nordic``: - is cloned from ``path_to_url`` instead of ``path_to_url``. - is updated to commit ``my-sha`` by ``west update``, instead of the mainline commit ``another-sha`` In other words, when your top-level manifest defines a project, like ``hal_nordic``, west will ignore any other definition it finds later on while resolving imports. This does mean you have to copy the ``path: modules/hal/nordic`` value into :file:`my-repo/west.yml` when defining ``hal_nordic`` there. The value from :file:`zephyr/west.yml` is ignored entirely. See :ref:`west-manifest-resolve` for troubleshooting advice if this gets confusing in practice. When you run ``west update``, west will: - update zephyr's ``manifest-rev`` to point at the ``v2.0.0`` tag - import :file:`zephyr/west.yml` at that ``manifest-rev`` - locally check out the ``v2.0.0`` revisions for all zephyr projects except ``hal_nordic`` - update ``hal_nordic`` to ``my-sha`` instead of ``another-sha`` .. _west-manifest-import-path: Option 2: Relative path ======================= The ``import`` value can also be a relative path to a manifest file or a directory containing manifest files. The path is relative to the root directory of the ``projects`` or ``self`` repository the ``import`` key appears in. Here is an example: .. code-block:: yaml manifest: projects: - name: project-1 revision: v1.0 import: west.yml - name: project-2 revision: main import: p2-manifests self: import: submanifests This will import the following: - the contents of :file:`project-1/west.yml` at ``manifest-rev``, which points at tag ``v1.0`` after running ``west update`` - any YAML files in the directory tree :file:`project-2/p2-manifests` at the latest commit in the ``main`` branch, as fetched by ``west update``, sorted by file name - YAML files in :file:`submanifests` in your manifest repository, as they appear on your file system, sorted by file name Notice how ``projects`` imports get data from Git using ``manifest-rev``, while ``self`` imports get data from your file system. This is because as usual, west leaves version control for your manifest repository up to you. .. _west-manifest-ex2.1: Example 2.1: Downstream of a Zephyr release with explicit path -------------------------------------------------------------- This is an explicit way to write an equivalent manifest to the one in :ref:`west-manifest-ex1.1`. .. code-block:: yaml manifest: remotes: - name: zephyrproject-rtos url-base: path_to_url projects: - name: zephyr remote: zephyrproject-rtos revision: v1.14.1 import: west.yml The setting ``import: west.yml`` means to use the file :file:`west.yml` inside the ``zephyr`` project. This example is contrived, but shows the idea. This can be useful in practice when the name of the manifest file you want to import is not :file:`west.yml`. .. _west-manifest-ex2.2: Example 2.2: Downstream with directory of manifest files -------------------------------------------------------- Your Zephyr downstream has a lot of additional repositories. So many, in fact, that you want to split them up into multiple manifest files, but keep track of them all in a single manifest repository, like this: .. code-block:: none my-repo/ submanifests 01-libraries.yml 02-vendor-hals.yml 03-applications.yml west.yml You want to add all the files in :file:`my-repo/submanifests` to the main manifest file, :file:`my-repo/west.yml`, in addition to projects in :file:`zephyr/west.yml`. You want to track the latest development code in the Zephyr repository's ``main`` branch instead of using a fixed revision. Here's how: .. code-block:: yaml # my-repo/west.yml: manifest: remotes: - name: zephyrproject-rtos url-base: path_to_url projects: - name: zephyr remote: zephyrproject-rtos revision: main import: true self: import: submanifests Manifest files are imported in this order during resolution: #. :file:`my-repo/submanifests/01-libraries.yml` #. :file:`my-repo/submanifests/02-vendor-hals.yml` #. :file:`my-repo/submanifests/03-applications.yml` #. :file:`my-repo/west.yml` #. :file:`zephyr/west.yml` .. note:: The :file:`.yml` file names are prefixed with numbers in this example to make sure they are imported in the specified order. You can pick arbitrary names. West sorts files in a directory by name before importing. Notice how the manifests in :file:`submanifests` are imported before :file:`my-repo/west.yml` and :file:`zephyr/west.yml`. In general, an ``import`` in the ``self`` section is processed before the manifest files in ``projects`` and the main manifest file. This means projects defined in :file:`my-repo/submanifests` take highest precedence. For example, if :file:`01-libraries.yml` defines ``hal_nordic``, the project by the same name in :file:`zephyr/west.yml` is simply ignored. As usual, see :ref:`west-manifest-resolve` for troubleshooting advice. This may seem strange, but it allows you to redefine projects "after the fact", as we'll see in the next example. .. _west-manifest-ex2.3: Example 2.3: Continuous Integration overrides --------------------------------------------- Your continuous integration system needs to fetch and test multiple repositories in your west workspace from a developer's forks instead of your mainline development trees, to see if the changes all work well together. Starting with :ref:`west-manifest-ex2.2`, the CI scripts add a file :file:`00-ci.yml` in :file:`my-repo/submanifests`, with these contents: .. code-block:: yaml # my-repo/submanifests/00-ci.yml: manifest: projects: - name: a-vendor-hal url: path_to_url revision: a-pull-request-branch - name: an-application url: path_to_url revision: another-pull-request-branch The CI scripts run ``west update`` after generating this file in :file:`my-repo/submanifests`. The projects defined in :file:`00-ci.yml` have higher precedence than other definitions in :file:`my-repo/submanifests`, because the name :file:`00-ci.yml` comes before the other file names. Thus, ``west update`` always checks out the developer's branches in the projects named ``a-vendor-hal`` and ``an-application``, even if those same projects are also defined elsewhere. .. _west-manifest-import-map: Option 3: Mapping ================= The ``import`` key can also contain a mapping with the following keys: - ``file``: Optional. The name of the manifest file or directory to import. This defaults to :file:`west.yml` if not present. - ``name-allowlist``: Optional. If present, a name or sequence of project names to include. - ``path-allowlist``: Optional. If present, a path or sequence of project paths to match against. This is a shell-style globbing pattern, currently implemented with `pathlib`_. Note that this means case sensitivity is platform specific. - ``name-blocklist``: Optional. Like ``name-allowlist``, but contains project names to exclude rather than include. - ``path-blocklist``: Optional. Like ``path-allowlist``, but contains project paths to exclude rather than include. - ``path-prefix``: Optional (new in v0.8.0). If given, this will be prepended to the project's path in the workspace, as well as the paths of any imported projects. This can be used to place these projects in a subdirectory of the workspace. .. _re: path_to_url .. _pathlib: path_to_url#pathlib.PurePath.match Allowlists override blocklists if both are given. For example, if a project is blocked by path, then allowed by name, it will still be imported. .. _west-manifest-ex3.1: Example 3.1: Downstream with name allowlist ------------------------------------------- Here is a pair of manifest files, representing a mainline and a downstream. The downstream doesn't want to use all the mainline projects, however. We'll assume the mainline :file:`west.yml` is hosted at ``path_to_url``. .. code-block:: yaml # mainline west.yml: manifest: projects: - name: mainline-app # included path: examples/app url: path_to_url - name: lib path: libraries/lib url: path_to_url - name: lib2 # included path: libraries/lib2 url: path_to_url # downstream west.yml: manifest: projects: - name: mainline url: path_to_url import: name-allowlist: - mainline-app - lib2 - name: downstream-app url: path_to_url - name: lib3 path: libraries/lib3 url: path_to_url An equivalent manifest in a single file would be: .. code-block:: yaml manifest: projects: - name: mainline url: path_to_url - name: downstream-app url: path_to_url - name: lib3 path: libraries/lib3 url: path_to_url - name: mainline-app # imported path: examples/app url: path_to_url - name: lib2 # imported path: libraries/lib2 url: path_to_url If an allowlist had not been used, the ``lib`` project from the mainline manifest would have been imported. .. _west-manifest-ex3.2: Example 3.2: Downstream with path allowlist ------------------------------------------- Here is an example showing how to allowlist mainline's libraries only, using ``path-allowlist``. .. code-block:: yaml # mainline west.yml: manifest: projects: - name: app path: examples/app url: path_to_url - name: lib path: libraries/lib # included url: path_to_url - name: lib2 path: libraries/lib2 # included url: path_to_url # downstream west.yml: manifest: projects: - name: mainline url: path_to_url import: path-allowlist: libraries/* - name: app url: path_to_url - name: lib3 path: libraries/lib3 url: path_to_url An equivalent manifest in a single file would be: .. code-block:: yaml manifest: projects: - name: lib # imported path: libraries/lib url: path_to_url - name: lib2 # imported path: libraries/lib2 url: path_to_url - name: mainline url: path_to_url - name: app url: path_to_url - name: lib3 path: libraries/lib3 url: path_to_url .. _west-manifest-ex3.3: Example 3.3: Downstream with path blocklist ------------------------------------------- Here's an example showing how to block all vendor HALs from mainline by common path prefix in the workspace, add your own version for the chip you're targeting, and keep everything else. .. code-block:: yaml # mainline west.yml: manifest: defaults: remote: mainline remotes: - name: mainline url-base: path_to_url projects: - name: app - name: lib path: libraries/lib - name: lib2 path: libraries/lib2 - name: hal_foo path: modules/hals/foo # excluded - name: hal_bar path: modules/hals/bar # excluded - name: hal_baz path: modules/hals/baz # excluded # downstream west.yml: manifest: projects: - name: mainline url: path_to_url import: path-blocklist: modules/hals/* - name: hal_foo path: modules/hals/foo url: path_to_url An equivalent manifest in a single file would be: .. code-block:: yaml manifest: defaults: remote: mainline remotes: - name: mainline url-base: path_to_url projects: - name: app # imported - name: lib # imported path: libraries/lib - name: lib2 # imported path: libraries/lib2 - name: mainline repo-path: path_to_url - name: hal_foo path: modules/hals/foo url: path_to_url .. _west-manifest-ex3.4: Example 3.4: Import into a subdirectory --------------------------------------- You want to import a manifest and its projects, placing everything into a subdirectory of your :term:`west workspace`. For example, suppose you want to import this manifest from project ``foo``, adding this project and its projects ``bar`` and ``baz`` to your workspace: .. code-block:: yaml # foo/west.yml: manifest: defaults: remote: example remotes: - name: example url-base: path_to_url projects: - name: bar - name: baz Instead of importing these into the top level workspace, you want to place all three project repositories in an :file:`external-code` subdirectory, like this: .. code-block:: none workspace/ external-code/ foo/ bar/ baz/ You can do this using this manifest: .. code-block:: yaml manifest: projects: - name: foo url: path_to_url import: path-prefix: external-code An equivalent manifest in a single file would be: .. code-block:: yaml # foo/west.yml: manifest: defaults: remote: example remotes: - name: example url-base: path_to_url projects: - name: foo path: external-code/foo - name: bar path: external-code/bar - name: baz path: external-code/baz .. _west-manifest-import-seq: Option 4: Sequence ================== The ``import`` key can also contain a sequence of files, directories, and mappings. .. _west-manifest-ex4.1: Example 4.1: Downstream with sequence of manifest files ------------------------------------------------------- This example manifest is equivalent to the manifest in :ref:`west-manifest-ex2.2`, with a sequence of explicitly named files. .. code-block:: yaml # my-repo/west.yml: manifest: projects: - name: zephyr url: path_to_url import: west.yml self: import: - submanifests/01-libraries.yml - submanifests/02-vendor-hals.yml - submanifests/03-applications.yml .. _west-manifest-ex4.2: Example 4.2: Import order illustration -------------------------------------- This more complicated example shows the order that west imports manifest files: .. code-block:: yaml # my-repo/west.yml manifest: # ... projects: - name: my-library - name: my-app - name: zephyr import: true - name: another-manifest-repo import: submanifests self: import: - submanifests/libraries.yml - submanifests/vendor-hals.yml - submanifests/applications.yml defaults: remote: my-remote For this example, west resolves imports in this order: #. the listed files in :file:`my-repo/submanifests` are first, in the order they occur (e.g. :file:`libraries.yml` comes before :file:`applications.yml`, since this is a sequence of files), since the ``self: import:`` is always imported first #. :file:`my-repo/west.yml` is next (with projects ``my-library`` etc. as long as they weren't already defined somewhere in :file:`submanifests`) #. :file:`zephyr/west.yml` is after that, since that's the first ``import`` key in the ``projects`` list in :file:`my-repo/west.yml` #. files in :file:`another-manifest-repo/submanifests` are last (sorted by file name), since that's the final project ``import`` .. _west-manifest-formal: Manifest Import Details ======================= This section describes how west resolves a manifest file that uses ``import`` a bit more formally. Overview -------- The ``import`` key can appear in a west manifest's ``projects`` and ``self`` sections. The general case looks like this: .. code-block:: yaml # Top-level manifest file. manifest: projects: - name: foo import: ... # import-1 - name: bar import: ... # import-2 # ... - name: baz import: ... # import-N self: import: ... # self-import Import keys are optional. If any of ``import-1, ..., import-N`` are missing, west will not import additional manifest data from that project. If ``self-import`` is missing, no additional files in the manifest repository (beyond the top-level file) are imported. The ultimate outcomes of resolving manifest imports are: - a ``projects`` list, which is produced by combining the ``projects`` defined in the top-level file with those defined in imported files - a set of extension commands, which are drawn from the ``west-commands`` keys in the top-level file and any imported files - a ``group-filter`` list, which is produced by combining the top-level and any imported filters Importing is done in this order: #. Manifests from ``self-import`` are imported first. #. The top-level manifest file's definitions are handled next. #. Manifests from ``import-1``, ..., ``import-N``, are imported in that order. When an individual ``import`` key refers to multiple manifest files, they are processed in this order: - If the value is a relative path naming a directory (or a map whose ``file`` is a directory), the manifest files it contains are processed in lexicographic order -- i.e., sorted by file name. - If the value is a sequence, its elements are recursively imported in the order they appear. This process recurses if necessary. E.g., if ``import-1`` produces a manifest file that contains an ``import`` key, it is resolved recursively using the same rules before its contents are processed further. The following sections describe these outcomes. Projects -------- This section describes how the final ``projects`` list is created. Projects are identified by name. If the same name occurs in multiple manifests, the first definition is used, and subsequent definitions are ignored. For example, if ``import-1`` contains a project named ``bar``, that is ignored, because the top-level :file:`west.yml` has already defined a project by that name. The contents of files named by ``import-1`` through ``import-N`` are imported from Git at the latest ``manifest-rev`` revisions in their projects. These revisions can be updated to the values ``rev-1`` through ``rev-N`` by running ``west update``. If any ``manifest-rev`` reference is missing or out of date, ``west update`` also fetches project data from the remote fetch URL and updates the reference. Also note that all imported manifests, from the root manifest to the repository which defines a project ``P``, must be up to date in order for west to update ``P`` itself. For example, this means ``west update P`` would update ``manifest-rev`` in the ``baz`` project if :file:`baz/west.yml` defines ``P``, as well as updating the ``manifest-rev`` branch in the local git clone of ``P``. Confusingly, updating ``baz`` may result in the removal of ``P`` from :file:`baz/west.yml`, which "should" cause ``west update P`` to fail with an unrecognized project! For this reason, it's not possible to run ``west update P`` if ``P`` is defined in an imported manifest; you must update this project along with all the others with a plain ``west update``. By default, west won't fetch any project data over the network if a project's revision is a SHA or tag which is already available locally, so updating the extra projects shouldn't take too much time unless it's really needed. See the documentation for the :ref:`update.fetch <west-config-index>` configuration option for more information. Extensions ---------- All extension commands defined using ``west-commands`` keys discovered while handling imports are available in the resolved manifest. If an imported manifest file has a ``west-commands:`` definition in its ``self:`` section, the extension commands defined there are added to the set of available extensions at the time the manifest is imported. They will thus take precedence over any extension commands with the same names added later on. Group filters ------------- The resolved manifest has a ``group-filter`` value which is the result of concatenating the ``group-filter`` values in the top-level manifest and any imported manifests. Manifest files which appear earlier in the import order have higher precedence and are therefore concatenated later into the final ``group-filter``. In other words, let: - the submanifest resolved from ``self-import`` have group filter ``self-filter`` - the top-level manifest file have group filter ``top-filter`` - the submanifests resolved from ``import-1`` through ``import-N`` have group filters ``filter-1`` through ``filter-N`` respectively The final resolved ``group-filter`` value is then ``filterN + ... + filter-2 + filter-1 + top-filter + self-filter``, where ``+`` here refers to list concatenation. .. important:: The order that filters appear in the above list matters. The last filter element in the final concatenated list "wins" and determines if the group is enabled or disabled. For example, in ``[-foo] + [+foo]``, group ``foo`` is enabled. However, in ``[+foo] + [-foo]``, group ``foo`` is disabled. For simplicity, west and this documentation may elide concatenated group filter elements which are redundant using these rules. For example, ``[+foo] + [-foo]`` could be written more simply as ``[-foo]``, for the reasons given above. As another example, ``[-foo] + [+foo]`` could be written as the empty list ``[]``, since all groups are enabled by default. .. _west-manifest-cmd: Manifest Command **************** The ``west manifest`` command can be used to manipulate manifest files. It takes an action, and action-specific arguments. The following sections describe each action and provides a basic signature for simple uses. Run ``west manifest --help`` for full details on all options. .. _west-manifest-resolve: Resolving Manifests =================== The ``--resolve`` action outputs a single manifest file equivalent to your current manifest and all its :ref:`imported manifests <west-manifest-import>`: .. code-block:: none west manifest --resolve [-o outfile] The main use for this action is to see the "final" manifest contents after performing any ``import``\ s. To print detailed information about each imported manifest file and how projects are handled during manifest resolution, set the maximum verbosity level using ``-v``: .. code-block:: console west -v manifest --resolve Freezing Manifests ================== The ``--freeze`` action outputs a frozen manifest: .. code-block:: none west manifest --freeze [-o outfile] A "frozen" manifest is a manifest file where every project's revision is a SHA. You can use ``--freeze`` to produce a frozen manifest that's equivalent to your current manifest file. The ``-o`` option specifies an output file; if not given, standard output is used. Validating Manifests ==================== The ``--validate`` action either succeeds if the current manifest file is valid, or fails with an error: .. code-block:: none west manifest --validate The error message can help diagnose errors. Here, "invalid" means that the syntax of the manifest file doesn't follow the rules documented on this page. If your manifest is valid but it's not working the way you want it to, turning up the verbosity with ``-v`` is a good way to get detailed information about what decisions west made about your manifest, and why: .. code-block:: none west -v manifest --validate .. _west-manifest-path: Get the manifest path ===================== The ``--path`` action prints the path to the top level manifest file: .. code-block:: none west manifest --path The output is something like ``/path/to/workspace/west.yml``. The path format depends on your operating system. ```	/content/code_sandbox/doc/develop/west/manifest.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	16,820
```restructuredtext .. _integration_with_pytest: Integration with pytest test framework ###################################### Please mind that integration of twister with pytest is still work in progress. Not every platform type is supported in pytest (yet). If you find any issue with the integration or have an idea for an improvement, please, let us know about it and open a GitHub issue/enhancement. Introduction ************ Pytest is a python framework that makes it easy to write small, readable tests, and can scale to support complex functional testing for applications and libraries (`<path_to_url`_). Python is known for its free libraries and ease of using it for scripting. In addition, pytest utilizes the concept of plugins and fixtures, increasing its expendability and reusability. A pytest plugin `pytest-twister-harness` was introduced to provide an integration between pytest and twister, allowing Zephyrs community to utilize pytest functionality with keeping twister as the main framework. Integration with twister ********************** By default, there is nothing to be done to enable pytest support in twister. The plugin is developed as a part of Zephyrs tree. To enable install-less operation, twister first extends ``PYTHONPATH`` with path to this plugin, and then during pytest call, it appends the command with ``-p twister_harness.plugin`` argument. If one prefers to use the installed version of the plugin, they must add ``--allow-installed-plugin`` flag to twisters call. Pytest-based test suites are discovered the same way as other twister tests, i.e., by a presence of test/sample.yaml. Inside, a keyword ``harness`` tells twister how to handle a given test. In the case of ``harness: pytest``, most of twister workflow (test suites discovery, parallelization, building and reporting) remains the same as for other harnesses. The change happens during the execution step. The below picture presents a simplified overview of the integration. .. figure:: figures/twister_and_pytest.svg :figclass: align-center If ``harness: pytest`` is used, twister delegates the test execution to pytest, by calling it as a subprocess. Required parameters (such as build directory, device to be used, etc.) are passed through a CLI command. When pytest is done, twister looks for a pytest report (results.xml) and sets the test result accordingly. How to create a pytest test *********************** An example folder containing a pytest test, application source code and Twister configuration .yaml file can look like the following: .. code-block:: none test_foo/ pytest/ test_foo.py src/ main.c CMakeList.txt prj.conf testcase.yaml An example of a pytest test is given at :zephyr_file:`samples/subsys/testsuite/pytest/shell/pytest/test_shell.py`. Using the configuration provided in the ``testcase.yaml`` file, Twister builds the application from ``src`` and then, if the .yaml file contains a ``harness: pytest`` entry, it calls pytest in a separate subprocess. A sample configuration file may look like this: .. code-block:: yaml tests: some.foo.test: harness: pytest tags: foo By default, pytest tries to look for tests in a ``pytest`` directory located next to a directory with binary sources. A keyword ``pytest_root`` placed under ``harness_config`` section in .yaml file can be used to point to other files, directories or subtests (more info :ref:`here <pytest_root>`). Pytest scans the given locations looking for tests, following its default `discovery rules <path_to_url#conventions-for-python-test-discovery>`_. Passing extra arguments ======================= There are two ways for passing extra arguments to the called pytest subprocess: #. From .yaml file, using ``pytest_args`` placed under ``harness_config`` section - more info :ref:`here <pytest_args>`. #. Through Twister command line interface as ``--pytest-args`` argument. This can be particularly useful when one wants to select a specific testcase from a test suite. For instance, one can use a command: .. code-block:: console $ ./scripts/twister --platform native_sim -T samples/subsys/testsuite/pytest/shell \ -s samples/subsys/testsuite/pytest/shell/sample.pytest.shell \ --pytest-args='-k test_shell_print_version' The command line arguments will extend those from the .yaml file. If the same argument is present in both places, the one from the command line will take precedence. Fixtures **** dut === Give access to a `DeviceAdapter`_ type object, that represents Device Under Test. This fixture is the core of pytest harness plugin. It is required to launch DUT (initialize logging, flash device, connect serial etc). This fixture yields a device prepared according to the requested type (``native``, ``qemu``, ``hardware``, etc.). All types of devices share the same API. This allows for writing tests which are device-type-agnostic. Scope of this fixture is determined by the ``pytest_dut_scope`` keyword placed under ``harness_config`` section (more info :ref:`here <pytest_dut_scope>`). .. code-block:: python from twister_harness import DeviceAdapter def test_sample(dut: DeviceAdapter): dut.readlines_until('Hello world') shell ===== Provide a `Shell <shell_class_>`_ class object with methods used to interact with shell application. It calls ``wait_for_promt`` method, to not start scenario until DUT is ready. The shell fixture calls ``dut`` fixture, hence has access to all its methods. The ``shell`` fixture adds methods optimized for interactions with a shell. It can be used instead of ``dut`` for tests. Scope of this fixture is determined by the ``pytest_dut_scope`` keyword placed under ``harness_config`` section (more info :ref:`here <pytest_dut_scope>`). .. code-block:: python from twister_harness import Shell def test_shell(shell: Shell): shell.exec_command('help') mcumgr ====== Sample fixture to wrap ``mcumgr`` command-line tool used to manage remote devices. More information about MCUmgr can be found here :ref:`mcu_mgr`. .. note:: This fixture requires the ``mcumgr`` available in the system PATH Only selected functionality of MCUmgr is wrapped by this fixture. For example, here is a test with a fixture ``mcumgr`` .. code-block:: python from twister_harness import DeviceAdapter, Shell, McuMgr def test_upgrade(dut: DeviceAdapter, shell: Shell, mcumgr: McuMgr): # free the serial port for mcumgr dut.disconnect() # upload the signed image mcumgr.image_upload('path/to/zephyr.signed.bin') # obtain the hash of uploaded image from the device second_hash = mcumgr.get_hash_to_test() # test a new upgrade image mcumgr.image_test(second_hash) # reset the device remotely mcumgr.reset_device() # continue test scenario, check version etc. unlauched_dut ============= Similar to the ``dut`` fixture, but it does not initialize the device. It can be used when a finer control over the build process is needed. It becomes responsibility of the test to initialize the device. .. code-block:: python from twister_harness import DeviceAdapter def test_sample(unlauched_dut: DeviceAdapter): unlaunched_dut.launch() unlaunched_dut.readlines_until('Hello world') Classes *** DeviceAdapter ============= .. autoclass:: twister_harness.DeviceAdapter .. automethod:: launch .. automethod:: connect .. automethod:: readline .. automethod:: readlines .. automethod:: readlines_until .. automethod:: write .. automethod:: disconnect .. automethod:: close .. _shell_class: Shell ===== .. autoclass:: twister_harness.Shell .. automethod:: exec_command .. automethod:: wait_for_prompt Examples of pytest tests in the Zephyr project ******************************************** * :zephyr:code-sample:`pytest_shell` * MCUmgr tests - :zephyr_file:`tests/boot/with_mcumgr` * LwM2M tests - :zephyr_file:`tests/net/lib/lwm2m/interop` * GDB stub tests - :zephyr_file:`tests/subsys/debug/gdbstub` FAQ * How to flash/run application only once per pytest session? ========================================================== ``dut`` is a fixture responsible for flashing/running application. By default, its scope is set as ``function``. This can be changed by adding to .yaml file ``pytest_dut_scope`` keyword placed under ``harness_config`` section: .. code-block:: yaml harness: pytest harness_config: pytest_dut_scope: session More info can be found :ref:`here <pytest_dut_scope>`. How to run only one particular test from a python file? ======================================================= This can be achieved in several ways. In .yaml file it can be added using a ``pytest_root`` entry placed under ``harness_config`` with list of tests which should be run: .. code-block:: yaml harness: pytest harness_config: pytest_root: - "pytest/test_shell.py::test_shell_print_help" Particular tests can be also chosen by pytest ``-k`` option (more info about pytest keyword filter can be found `here <path_to_url#using-k-expr-to-select-tests-based-on-their-name>`_ ). It can be applied by adding ``-k`` filter in ``pytest_args`` in .yaml file: .. code-block:: yaml harness: pytest harness_config: pytest_args: - "-k test_shell_print_help" or by adding it to Twister command overriding parameters from the .yaml file: .. code-block:: console $ ./scripts/twister ... --pytest-args='-k test_shell_print_help' How to get information about used device type in test? ====================================================== This can be taken from ``dut`` fixture (which represents `DeviceAdapter`_ object): .. code-block:: python device_type: str = dut.device_config.type if device_type == 'hardware': ... elif device_type == 'native': ... How to rerun locally pytest tests without rebuilding application by Twister? ============================================================================ This can be achieved by running Twister once again with ``--test-only`` argument added to Twister command. Another way is running Twister with highest verbosity level (``-vv``) and then copy-pasting from logs command dedicated for spawning pytest (log started by ``Running pytest command: ...``). Is this possible to run pytest tests in parallel? ================================================= Basically ``pytest-harness-plugin`` wasn't written with intention of running pytest tests in parallel. Especially those one dedicated for hardware. There was assumption that parallelization of tests is made by Twister, and it is responsible for managing available sources (jobs and hardwares). If anyone is interested in doing this for some reasons (for example via `pytest-xdist plugin <path_to_url`_) they do so at their own risk. Limitations ********* * Not every platform type is supported in the plugin (yet). ```	/content/code_sandbox/doc/develop/test/pytest.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,523
```restructuredtext .. _test-framework: Test Framework ############### The Zephyr Test Framework (Ztest) provides a simple testing framework intended to be used during development. It provides basic assertion macros and a generic test structure. The framework can be used in two ways, either as a generic framework for integration testing, or for unit testing specific modules. Creating a test suite ********************* Using Ztest to create a test suite is as easy as calling the :c:macro:`ZTEST_SUITE`. The macro accepts the following arguments: * ``suite_name`` - The name of the suite. This name must be unique within a single binary. * :c:type:`ztest_suite_predicate_t` - An optional predicate function to allow choosing when the test will run. The predicate will get a pointer to the global state passed in through :c:func:`ztest_run_all` and should return a boolean to decide if the suite should run. * :c:type:`ztest_suite_setup_t` - An optional setup function which returns a test fixture. This will be called and run once per test suite run. * :c:type:`ztest_suite_before_t` - An optional before function which will run before every single test in this suite. * :c:type:`ztest_suite_after_t` - An optional after function which will run after every single test in this suite. * :c:type:`ztest_suite_teardown_t` - An optional teardown function which will run at the end of all the tests in the suite. Below is an example of a test suite using a predicate: .. code-block:: C #include <zephyr/ztest.h> #include "test_state.h" static bool predicate(const void global_state) { return ((const struct test_state)global_state)->x == 5; } ZTEST_SUITE(alternating_suite, predicate, NULL, NULL, NULL, NULL); Adding tests to a suite *********************** There are 4 macros used to add a test to a suite, they are: * :c:macro:`ZTEST` ``(suite_name, test_name)`` - Which can be used to add a test by ``test_name`` to a given suite by ``suite_name``. * :c:macro:`ZTEST_USER` ``(suite_name, test_name)`` - Which behaves the same as :c:macro:`ZTEST`, only that when :kconfig:option:`CONFIG_USERSPACE` is enabled, then the test will be run in a userspace thread. * :c:macro:`ZTEST_F` ``(suite_name, test_name)`` - Which behaves the same as :c:macro:`ZTEST`, only that the test function will already include a variable named ``fixture`` with the type ``<suite_name>_fixture``. * :c:macro:`ZTEST_USER_F` ``(suite_name, test_name)`` - Which combines the fixture feature of :c:macro:`ZTEST_F` with the userspace threading for the test. Test fixtures ============= Test fixtures can be used to help simplify repeated test setup operations. In many cases, tests in the same suite will require some initial setup followed by some form of reset between each test. This is achieved via fixtures in the following way: .. code-block:: C #include <zephyr/ztest.h> struct my_suite_fixture { size_t max_size; size_t size; uint8_t buff[1]; }; static void my_suite_setup(void) { / Allocate the fixture with 256 byte buffer / struct my_suite_fixture fixture = malloc(sizeof(struct my_suite_fixture) + 255); zassume_not_null(fixture, NULL); fixture->max_size = 256; return fixture; } static void my_suite_before(void f) { struct my_suite_fixture fixture = (struct my_suite_fixture )f; memset(fixture->buff, 0, fixture->max_size); fixture->size = 0; } static void my_suite_teardown(void f) { free(f); } ZTEST_SUITE(my_suite, NULL, my_suite_setup, my_suite_before, NULL, my_suite_teardown); ZTEST_F(my_suite, test_feature_x) { zassert_equal(0, fixture->size); zassert_equal(256, fixture->max_size); } Using memory allocated by a test fixture in a userspace thread, such as during execution of :c:macro:`ZTEST_USER` or :c:macro:`ZTEST_USER_F`, requires that memory to be declared userspace accessible. This is because the fixture memory is owned and initialized by kernel space. The Ztest framework provides the :c:macro:`ZTEST_DMEM` and :c:macro:`ZTEST_BMEM` macros for use of such user/kernel space shared memory. Advanced features *************** Test result expectations ======================== Some tests were made to be broken. In cases where the test is expected to fail or skip due to the nature of the code, it's possible to annotate the test as such. For example: .. code-block:: C #include <zephyr/ztest.h> ZTEST_SUITE(my_suite, NULL, NULL, NULL, NULL, NULL); ZTEST_EXPECT_FAIL(my_suite, test_fail); ZTEST(my_suite, test_fail) { / This will fail the test / zassert_true(false, NULL); } ZTEST_EXPECT_SKIP(my_suite, test_skip); ZTEST(my_suite, test_skip) { /* This will skip the test / zassume_true(false, NULL); } In this example, the above tests should be marked as failed and skipped respectively. Instead, Ztest will mark both as passed due to the expectation. Test rules ========== Test rules are a way to run the same logic for every test and every suite. There are a lot of cases where you might want to reset some state for every test in the binary (regardless of which suite is currently running). As an example, this could be to reset mocks, reset emulators, flush the UART, etc.: .. code-block:: C #include <zephyr/fff.h> #include <zephyr/ztest.h> #include "test_mocks.h" DEFINE_FFF_GLOBALS; DEFINE_FAKE_VOID_FUN(my_weak_func); static void fff_reset_rule_before(const struct ztest_unit_test test, void fixture) { ARG_UNUSED(test); ARG_UNUSED(fixture); RESET_FAKE(my_weak_func); } ZTEST_RULE(fff_reset_rule, fff_reset_rule_before, NULL); A custom ``test_main`` ====================== While the Ztest framework provides a default :c:func:`test_main` function, it's possible that some applications will want to provide custom behavior. This is particularly true if there's some global state that the tests depend on and that state either cannot be replicated or is difficult to replicate without starting the process over. For example, one such state could be a power sequence. Assuming there's a board with several steps in the power-on sequence a test suite can be written using the ``predicate`` to control when it would run. In that case, the :c:func:`test_main` function can be written as follows: .. code-block:: C #include <zephyr/ztest.h> #include "my_test.h" void test_main(void) { struct power_sequence_state state; / Only suites that use a predicate checking for phase == PWR_PHASE_0 will run. / state.phase = PWR_PHASE_0; ztest_run_all(&state, false, 1, 1); / Only suites that use a predicate checking for phase == PWR_PHASE_1 will run. / state.phase = PWR_PHASE_1; ztest_run_all(&state, false, 1, 1); / Only suites that use a predicate checking for phase == PWR_PHASE_2 will run. / state.phase = PWR_PHASE_2; ztest_run_all(&state, false, 1, 1); / Check that all the suites in this binary ran at least once. / ztest_verify_all_test_suites_ran(); } Quick start - Integration testing ****************************** A simple working base is located at :zephyr_file:`samples/subsys/testsuite/integration`. To make a test application for the bar component of foo*, you should copy the sample folder to ``tests/foo/bar`` and edit files there adjusting for your test application's purposes. To build and execute all applicable test scenarios defined in your test application use the :ref:`Twister <twister_script>` tool, for example: .. code-block:: console ./scripts/twister -T tests/foo/bar/ To select just one of the test scenarios, run Twister with ``--scenario`` command: .. code-block:: console ./scripts/twister --scenario tests/foo/bar/your.test.scenario.name In the command line above ``tests/foo/bar`` is the path to your test application and ``your.test.scenario.name`` references a test scenario defined in :file:`testcase.yaml` file, which is like ``sample.testing.ztest`` in the boilerplate test suite sample. See :ref:`Twister test project diagram <twister_test_project_diagram>` for more details on how Twister deals with Ztest application. The sample contains the following files: CMakeLists.txt .. literalinclude:: ../../../samples/subsys/testsuite/integration/CMakeLists.txt :language: CMake :linenos: testcase.yaml .. literalinclude:: ../../../samples/subsys/testsuite/integration/testcase.yaml :language: yaml :linenos: prj.conf .. literalinclude:: ../../../samples/subsys/testsuite/integration/prj.conf :language: text :linenos: src/main.c (see :ref:`best practices <main_c_bp>`) .. literalinclude:: ../../../samples/subsys/testsuite/integration/src/main.c :language: c :linenos: .. contents:: :depth: 1 :local: :backlinks: top A test application may consist of multiple test suites that either can be testing functionality or APIs. Functions implementing a test case should follow the guidelines below: Test cases function names should be prefixed with test_ * Test cases should be documented using doxygen * Test case function names should be unique within the section or component being tested For example: .. code-block:: C /** * @brief Test Asserts * * This test case verifies the zassert_true macro. / ZTEST(my_suite, test_assert) { zassert_true(1, "1 was false"); } Listing Tests ============= Tests (test applications) in the Zephyr tree consist of many test scenarios that run as part of a project and test similar functionality, for example an API or a feature. The ``twister`` script can parse the test scenarios, suites and cases in all test applications or a subset of them, and can generate reports on a granular level, i.e. if test cases have passed or failed or if they were blocked or skipped. Twister parses the source files looking for test case names, so you can list all kernel test cases, for example, by running: .. code-block:: console ./scripts/twister --list-tests -T tests/kernel Skipping Tests ============== Special- or architecture-specific tests cannot run on all platforms and architectures, however we still want to count those and report them as being skipped. Because the test inventory and the list of tests is extracted from the code, adding conditionals inside the test suite is sub-optimal. Tests that need to be skipped for a certain platform or feature need to explicitly report a skip using :c:func:`ztest_test_skip` or :c:macro:`Z_TEST_SKIP_IFDEF`. If the test runs, it needs to report either a pass or fail. For example: .. code-block:: C #ifdef CONFIG_TEST1 ZTEST(common, test_test1) { zassert_true(1, "true"); } #else ZTEST(common, test_test1) { ztest_test_skip(); } #endif ZTEST(common, test_test2) { Z_TEST_SKIP_IFDEF(CONFIG_BUGxxxxx); zassert_equal(1, 0, NULL); } ZTEST_SUITE(common, NULL, NULL, NULL, NULL, NULL); .. _ztest_unit_testing: Quick start - Unit testing *********************** Ztest can be used for unit testing. This means that rather than including the entire Zephyr OS for testing a single function, you can focus the testing efforts into the specific module in question. This will speed up testing since only the module will have to be compiled in, and the tested functions will be called directly. Examples of unit tests can be found in the :zephyr_file:`tests/unit/` folder. In order to declare the unit tests present in a source folder, you need to add the relevant source files to the ``testbinary`` target from the CMake :zephyr_file:`unittest <cmake/modules/unittest.cmake>` component. See a minimal example below: .. code-block:: cmake cmake_minimum_required(VERSION 3.20.0) project(app) find_package(Zephyr COMPONENTS unittest REQUIRED HINTS $ENV{ZEPHYR_BASE}) target_sources(testbinary PRIVATE main.c) Since you won't be including basic kernel data structures that most code depends on, you have to provide function stubs in the test. Ztest provides some helpers for mocking functions, as demonstrated below. In a unit test, mock objects can simulate the behavior of complex real objects and are used to decide whether a test failed or passed by verifying whether an interaction with an object occurred, and if required, to assert the order of that interaction. Best practices for declaring the test suite ***************************************** twister and other validation tools need to obtain the list of test cases that a Zephyr ztest test image will expose. .. admonition:: Rationale This all is for the purpose of traceability. It's not enough to have only a semaphore test application. We also need to show that we have testpoints for all APIs and functionality, and we trace back to documentation of the API, and functional requirements. The idea is that test reports show results for every test case as passed, failed, blocked, or skipped. Reporting on only the high-level test application, particularly when tests do too many things, is too vague. Other questions: - Why not pre-scan with CPP and then parse? or post scan the ELF file? If C pre-processing or building fails because of any issue, then we won't be able to tell the subcases. - Why not declare them in the YAML test configuration? A separate test case description file would be harder to maintain than just keeping the information in the test source files themselves -- only one file to update when changes are made eliminates duplication. Stress test framework ******************* Zephyr stress test framework (Ztress) provides an environment for executing user functions in multiple priority contexts. It can be used to validate that code is resilient to preemptions. The framework tracks the number of executions and preemptions for each context. Execution can have various completion conditions like timeout, number of executions or number of preemptions. The framework is setting up the environment by creating the requested number of threads (each on different priority), optionally starting a timer. For each context, a user function (different for each context) is called and then the context sleeps for a randomized amount of system ticks. The framework is tracking CPU load and adjusts sleeping periods to achieve higher CPU load. In order to increase the probability of preemptions, the system clock frequency should be relatively high. The default 100 Hz on QEMU x86 is much too low and it is recommended to increase it to 100 kHz. The stress test environment is setup and executed using :c:macro:`ZTRESS_EXECUTE` which accepts a variable number of arguments. Each argument is a context that is specified by :c:macro:`ZTRESS_TIMER` or :c:macro:`ZTRESS_THREAD` macros. Contexts are specified in priority descending order. Each context specifies completion conditions by providing the minimum number of executions and preemptions. When all conditions are met and the execution has completed, an execution report is printed and the macro returns. Note that while the test is executing, a progress report is periodically printed. Execution can be prematurely completed by specifying a test timeout (:c:func:`ztress_set_timeout`) or an explicit abort (:c:func:`ztress_abort`). User function parameters contains an execution counter and a flag indicating if it is the last execution. The example below presents how to setup and run 3 contexts (one of which is k_timer interrupt handler context). Completion criteria is set to at least 10000 executions of each context and 1000 preemptions of the lowest priority context. Additionally, the timeout is configured to complete after 10 seconds if those conditions are not met. The last argument of each context is the initial sleep time which will be adjusted throughout the test to achieve the highest CPU load. .. code-block:: C ztress_set_timeout(K_MSEC(10000)); ZTRESS_EXECUTE(ZTRESS_TIMER(foo_0, user_data_0, 10000, Z_TIMEOUT_TICKS(20)), ZTRESS_THREAD(foo_1, user_data_1, 10000, 0, Z_TIMEOUT_TICKS(20)), ZTRESS_THREAD(foo_2, user_data_2, 10000, 1000, Z_TIMEOUT_TICKS(20))); Configuration ============= Static configuration of Ztress contains: - :kconfig:option:`CONFIG_ZTRESS_MAX_THREADS` - number of supported threads. - :kconfig:option:`CONFIG_ZTRESS_STACK_SIZE` - Stack size of created threads. - :kconfig:option:`CONFIG_ZTRESS_REPORT_PROGRESS_MS` - Test progress report interval. API reference ********* Running tests ============= .. doxygengroup:: ztest_test Assertions ========== These macros will instantly fail the test if the related assertion fails. When an assertion fails, it will print the current file, line and function, alongside a reason for the failure and an optional message. If the config :kconfig:option:`CONFIG_ZTEST_ASSERT_VERBOSE` is 0, the assertions will only print the file and line numbers, reducing the binary size of the test. Example output for a failed macro from ``zassert_equal(buf->ref, 2, "Invalid refcount")``: .. code-block:: none Assertion failed at main.c:62: test_get_single_buffer: Invalid refcount (buf->ref not equal to 2) Aborted at unit test function .. doxygengroup:: ztest_assert Expectations ============ These macros will continue test execution if the related expectation fails and subsequently fail the test at the end of its execution. When an expectation fails, it will print the current file, line, and function, alongside a reason for the failure and an optional message but continue executing the test. If the config :kconfig:option:`CONFIG_ZTEST_ASSERT_VERBOSE` is 0, the expectations will only print the file and line numbers, reducing the binary size of the test. For example, if the following expectations fail: .. code-block:: C zexpect_equal(buf->ref, 2, "Invalid refcount"); zexpect_equal(buf->ref, 1337, "Invalid refcount"); The output will look something like: .. code-block:: none START - test_get_single_buffer Expectation failed at main.c:62: test_get_single_buffer: Invalid refcount (buf->ref not equal to 2) Expectation failed at main.c:63: test_get_single_buffer: Invalid refcount (buf->ref not equal to 1337) FAIL - test_get_single_buffer in 0.0 seconds .. doxygengroup:: ztest_expect Assumptions =========== These macros will instantly skip the test or suite if the related assumption fails. When an assumption fails, it will print the current file, line, and function, alongside a reason for the failure and an optional message. If the config :kconfig:option:`CONFIG_ZTEST_ASSERT_VERBOSE` is 0, the assumptions will only print the file and line numbers, reducing the binary size of the test. Example output for a failed macro from ``zassume_equal(buf->ref, 2, "Invalid refcount")``: .. code-block::none START - test_get_single_buffer Assumption failed at main.c:62: test_get_single_buffer: Invalid refcount (buf->ref not equal to 2) SKIP - test_get_single_buffer in 0.0 seconds .. doxygengroup:: ztest_assume Ztress ====== .. doxygengroup:: ztest_ztress .. _mocking-fff: Mocking via FFF =============== Zephyr has integrated with FFF for mocking. See `FFF`_ for documentation. To use it, include the relevant header: .. code-block:: C #include <zephyr/fff.h> Zephyr provides several FFF-based fake drivers which can be used as either stubs or mocks. Fake driver instances are configured via :ref:`devicetree` and :ref:`kconfig`. See the following devicetree bindings for more information: - :dtcompatible:`zephyr,fake-can` - :dtcompatible:`zephyr,fake-eeprom` Zephyr also has defined extensions to FFF for simplified declarations of fake functions. See :ref:`FFF Extensions <fff-extensions>`. Customizing Test Output ********************* Customization is enabled by setting :kconfig:option:`CONFIG_ZTEST_TC_UTIL_USER_OVERRIDE` to "y" and adding a file :file:`tc_util_user_override.h` with your overrides. Add the line ``zephyr_include_directories(my_folder)`` to your project's :file:`CMakeLists.txt` to let Zephyr find your header file during builds. See the file :zephyr_file:`subsys/testsuite/include/zephyr/tc_util.h` to see which macros and/or defines can be overridden. These will be surrounded by blocks such as: .. code-block:: C #ifndef SOMETHING #define SOMETHING <default implementation> #endif /* SOMETHING / .. _ztest_shuffle: Shuffling Test Sequence ******************** By default the tests are sorted and ran in alphanumerical order. Test cases may be dependent on this sequence. Enable :kconfig:option:`CONFIG_ZTEST_SHUFFLE` to randomize the order. The output from the test will display the seed for failed tests. For native simulator builds you can provide the seed as an argument to twister with `--seed` Static configuration of ZTEST_SHUFFLE contains: - :kconfig:option:`CONFIG_ZTEST_SHUFFLE_SUITE_REPEAT_COUNT` - Number of iterations the test suite will run. - :kconfig:option:`CONFIG_ZTEST_SHUFFLE_TEST_REPEAT_COUNT` - Number of iterations the test will run. Test Selection ************ For tests built for native simulator, use command line arguments to list or select tests to run. The test argument expects a comma separated list of ``suite::test`` . You can substitute the test name with an ```` to run all tests within a suite. For example .. code-block:: bash $ zephyr.exe -list $ zephyr.exe -test="fixture_tests::test_fixture_pointer,framework_tests::test_assert_mem_equal" $ zephyr.exe -test="framework_tests::" .. _fff-extensions: FFF Extensions ************** .. doxygengroup:: fff_extensions .. _FFF: path_to_url ```	/content/code_sandbox/doc/develop/test/ztest.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	5,252
```restructuredtext .. _test-framework-deprecated: ZTest Deprecated APIs ##################### Ztest is currently being migrated to a new API, this documentation provides information about the deprecated APIs which will eventually be removed. See :ref:`Test Framework <test-framework>` for the new API. Similarly, ZTest's mocking framework is also deprecated (see :ref:`Mocking via FFF <mocking-fff>`). Quick start - Unit testing ************************** Ztest can be used for unit testing. This means that rather than including the entire Zephyr OS for testing a single function, you can focus the testing efforts into the specific module in question. This will speed up testing since only the module will have to be compiled in, and the tested functions will be called directly. Since you won't be including basic kernel data structures that most code depends on, you have to provide function stubs in the test. Ztest provides some helpers for mocking functions, as demonstrated below. In a unit test, mock objects can simulate the behavior of complex real objects and are used to decide whether a test failed or passed by verifying whether an interaction with an object occurred, and if required, to assert the order of that interaction. .. _main_c_bp: Best practices for declaring the test suite =========================================== twister and other validation tools need to obtain the list of subcases that a Zephyr ztest test image will expose. .. admonition:: Rationale This all is for the purpose of traceability. It's not enough to have only a semaphore test project. We also need to show that we have testpoints for all APIs and functionality, and we trace back to documentation of the API, and functional requirements. The idea is that test reports show results for every sub-testcase as passed, failed, blocked, or skipped. Reporting on only the high-level test project level, particularly when tests do too many things, is too vague. There exist two alternatives to writing tests. The first, and more verbose, approach is to directly declare and run the test suites. Here is a generic template for a test showing the expected use of :c:func:`ztest_test_suite`: .. code-block:: C #include <zephyr/ztest.h> extern void test_sometest1(void); extern void test_sometest2(void); #ifndef CONFIG_WHATEVER /* Conditionally skip test_sometest3 / void test_sometest3(void) { ztest_test_skip(); } #else extern void test_sometest3(void); #endif extern void test_sometest4(void); ... void test_main(void) { ztest_test_suite(common, ztest_unit_test(test_sometest1), ztest_unit_test(test_sometest2), ztest_unit_test(test_sometest3), ztest_unit_test(test_sometest4) ); ztest_run_test_suite(common); } Alternatively, it is possible to split tests across multiple files using :c:func:`ztest_register_test_suite` which bypasses the need for ``extern``: .. code-block:: C #include <zephyr/ztest.h> void test_sometest1(void) { zassert_true(1, "true"); } ztest_register_test_suite(common, NULL, ztest_unit_test(test_sometest1) ); The above sample simple registers the test suite and uses a ``NULL`` pragma function (more on that later). It is important to note that the test suite isn't directly run in this file. Instead two alternatives exist for running the suite. First, if to do nothing. A default ``test_main`` function is provided by ztest. This is the preferred approach if the test doesn't involve a state and doesn't require use of the pragma. In cases of an integration test it is possible that some general state needs to be set between test suites. This can be thought of as a state diagram in which ``test_main`` simply goes through various actions that modify the board's state and different test suites need to run. This is achieved in the following: .. code-block:: C #include <zephyr/ztest.h> struct state { bool is_hibernating; bool is_usb_connected; } static bool pragma_always(const void state) { return true; } static bool pragma_not_hibernating_not_connected(const void s) { struct state state = s; return !state->is_hibernating && !state->is_usb_connected; } static bool pragma_usb_connected(const void s) { return ((struct state )s)->is_usb_connected; } ztest_register_test_suite(baseline, pragma_always, ztest_unit_test(test_case0)); ztest_register_test_suite(before_usb, pragma_not_hibernating_not_connected, ztest_unit_test(test_case1), ztest_unit_test(test_case2)); ztest_register_test_suite(with_usb, pragma_usb_connected,, ztest_unit_test(test_case3), ztest_unit_test(test_case4)); void test_main(void) { struct state state; /* Should run `baseline` test suite only. / ztest_run_registered_test_suites(&state); / Simulate power on and update state. / emulate_power_on(); / Should run `baseline` and `before_usb` test suites. / ztest_run_registered_test_suites(&state); / Simulate plugging in a USB device. / emulate_plugging_in_usb(); / Should run `baseline` and `with_usb` test suites. / ztest_run_registered_test_suites(&state); / Verify that all the registered test suites actually ran. / ztest_verify_all_registered_test_suites_ran(); } For twister* to parse source files and create a list of subcases, the declarations of :c:func:`ztest_test_suite` and :c:func:`ztest_register_test_suite` must follow a few rules: - one declaration per line - conditional execution by using :c:func:`ztest_test_skip` What to avoid: - packing multiple testcases in one source file .. code-block:: C void test_main(void) { #ifdef TEST_feature1 ztest_test_suite(feature1, ztest_unit_test(test_1a), ztest_unit_test(test_1b), ztest_unit_test(test_1c) ); ztest_run_test_suite(feature1); #endif #ifdef TEST_feature2 ztest_test_suite(feature2, ztest_unit_test(test_2a), ztest_unit_test(test_2b) ); ztest_run_test_suite(feature2); #endif } - Do not use ``#if`` .. code-block:: C ztest_test_suite(common, ztest_unit_test(test_sometest1), ztest_unit_test(test_sometest2), #ifdef CONFIG_WHATEVER ztest_unit_test(test_sometest3), #endif ztest_unit_test(test_sometest4), ... - Do not add comments on lines with a call to :c:func:`ztest_unit_test`: .. code-block:: C ztest_test_suite(common, ztest_unit_test(test_sometest1), ztest_unit_test(test_sometest2) /* will fail /, / will fail! / ztest_unit_test(test_sometest3), ztest_unit_test(test_sometest4), ... - Do not define multiple definitions of unit / user unit test case per line .. code-block:: C ztest_test_suite(common, ztest_unit_test(test_sometest1), ztest_unit_test(test_sometest2), ztest_unit_test(test_sometest3), ztest_unit_test(test_sometest4), ... Other questions: - Why not pre-scan with CPP and then parse? or post scan the ELF file? If C pre-processing or building fails because of any issue, then we won't be able to tell the subcases. - Why not declare them in the YAML testcase description? A separate testcase description file would be harder to maintain than just keeping the information in the test source files themselves -- only one file to update when changes are made eliminates duplication. Mocking ****** These functions allow abstracting callbacks and related functions and controlling them from specific tests. You can enable the mocking framework by setting :kconfig:option:`CONFIG_ZTEST_MOCKING` to "y" in the configuration file of the test. The amount of concurrent return values and expected parameters is limited by :kconfig:option:`CONFIG_ZTEST_PARAMETER_COUNT`. Here is an example for configuring the function ``expect_two_parameters`` to expect the values ``a=2`` and ``b=3``, and telling ``returns_int`` to return ``5``: .. literalinclude:: mocking.c :language: c :linenos: .. doxygengroup:: ztest_mock ```	/content/code_sandbox/doc/develop/test/ztest_deprecated.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,006
```restructuredtext .. _bsim: BabbleSim ######### BabbleSim and Zephyr ****************** In the Zephyr project we use the `Babblesim`_ simulator to test some of the Zephyr radio protocols, including the BLE stack, 802.15.4, and some of the networking stack. BabbleSim_ is a physical layer simulator, which in combination with the Zephyr :ref:`bsim boards<bsim boards>` can be used to simulate a network of BLE and 15.4 devices. When we build Zephyr targeting a :ref:`bsim board<bsim boards>` we produce a Linux executable, which includes the application, Zephyr OS, and models of the HW. When there is radio activity, this Linux executable will connect to the BabbleSim Phy simulation to simulate the radio channel. In the BabbleSim documentation you can find more information on how to `get <path_to_url`_ and `build <path_to_url`_ the simulator. In the :ref:`nrf52_bsim<nrf52_bsim>`, :ref:`nrf5340bsim<nrf5340bsim>`, and :ref:`nrf54l15bsim<nrf54l15bsim>` boards documentation you can find more information about how to build Zephyr targeting these particular boards, and a few examples. Types of tests ************ Tests without radio activity: bsim tests with twister ===================================================== The :ref:`bsim boards<bsim boards>` can be used without radio activity, and in that case, it is not necessary to connect them to a physical layer simulation. Thanks to this, these target boards can be used just like :ref:`native_sim<native_sim>` with :ref:`twister <twister_script>`, to run all standard Zephyr twister tests, but with models of a real SOC HW, and their drivers. Tests with radio activity ========================= When there is radio activity, BabbleSim tests require at the very least a physical layer simulation running, and most, more than 1 simulated device. Due to this, these tests are not build and run with twister, but with a dedicated set of tests scripts. These tests are kept in the :code:`tests/bsim/` folder. The ``compile.sh`` and ``run_parallel.sh`` scripts contained in that folder are used by the CI system to build the needed images and execute these tests in batch. See sections below for more information about how to build and run them, as well as the conventions they follow. There are two main sets of tests: * Self checking embedded application/tests: In which some of the simulated devices applications are built with some checks which decide if the test is passing or failing. These embedded applications tests use the :ref:`bs_tests<bsim_boards_bs_tests>` system to report the pass or failure, and in many cases to build several tests into the same binary. * Test using the EDTT_ tool, in which a EDTT (python) test controls the embedded applications over an RPC mechanism, and decides if the test passes or not. Today these tests include a very significant subset of the BT qualification test suite. More information about how different tests types relate to BabbleSim and the bsim boards can be found in the :ref:`bsim boards tests section<bsim_boards_tests>`. Test coverage and BabbleSim ************************* As the :ref:`nrf52_bsim<nrf52_bsim>` and :ref:`nrf5340bsim<nrf5340bsim>`, and :ref:`nrf54l15bsim<nrf54l15bsim>` boards are based on the POSIX architecture, you can easily collect test coverage information. You can use the script :zephyr_file:`tests/bsim/generate_coverage_report.sh` to generate an html coverage report from tests. Check :ref:`the page on coverage generation <coverage_posix>` for more info. .. _BabbleSim: path_to_url .. _EDTT: path_to_url Building and running the tests **************************** See the :ref:`nrf52_bsim` page for setting up the simulator. The scripts also expect a few environment variables to be set. For example, from Zephyr's root folder, you can run: .. code-block:: bash # Build all the tests ${ZEPHYR_BASE}/tests/bsim/compile.sh # Run them (in parallel) RESULTS_FILE=${ZEPHYR_BASE}/myresults.xml \ SEARCH_PATH=${ZEPHYR_BASE}/tests/bsim \ ${ZEPHYR_BASE}/tests/bsim/run_parallel.sh Or to build and run only a specific subset, e.g. host advertising tests: .. code-block:: bash # Build the Bluetooth host advertising tests ${ZEPHYR_BASE}/tests/bsim/bluetooth/host/adv/compile.sh # Run them (in parallel) RESULTS_FILE=${ZEPHYR_BASE}/myresults.xml \ SEARCH_PATH=${ZEPHYR_BASE}/tests/bsim/bluetooth/host/adv \ ${ZEPHYR_BASE}/tests/bsim/run_parallel.sh Check the ``run_parallel.sh`` help for more options and examples on how to use this script to run the tests in batch. After building the tests' required binaries you can run a test directly using its individual test script. For example you can build the required binaries for the networking tests with .. code-block:: bash WORK_DIR=${ZEPHYR_BASE}/bsim_out ${ZEPHYR_BASE}/tests/bsim/net/compile.sh and then directly run one of the tests: .. code-block:: bash ${ZEPHYR_BASE}/tests/bsim/net/sockets/echo_test/tests_scripts/echo_test_802154.sh Conventions =========== Test code --------- See the :zephyr_file:`Bluetooth sample test <tests/bsim/bluetooth/host/misc/sample_test/README.rst>` for conventions that apply to test code. Build scripts ------------- The build scripts ``compile.sh`` simply build all the required test and sample applications for the tests' scripts placed in the subfolders below. This build scripts use the common compile.source which provide a function (compile) which calls cmake and ninja with the provided application, configuration and overlay files. To speed up compilation for users interested only in a subset of tests, several compile scripts exist in several subfolders, where the upper ones call into the lower ones. Note that cmake and ninja are used directly instead of the ``west build`` wrapper as west is not required, and some Zephyr users do not use or have west, but still use the build and tests scripts. Test scripts ------------ Please follow the existing conventions and do not design one-off bespoke runners (e.g. a python script, or another shell abstraction). The rationale is that it is easier and faster for the maintainers to perform tree-wide updates for build system or compatibility changes if the tests are run in the same manner, with the same variables, etc.. If you have a good idea for improving your test script, please make a PR changing all the test scripts in order to benefit everyone and conserve homogeneity. You can of course discuss it first in an RFC issue or on the babblesim discord channel. Scripts starting with an underscore (``_``) are not automatically discovered and run. They can serve as either helper functions for the main script, or can be used for local development utilities, e.g. building and running tests locally, debugging, etc.. Here are the conventions: - Each test is defined by a shell script with the extension ``.sh``, in a subfolder called ``test_scripts/``. - It is recommended to run a single test per script file. It allows for better parallelization of the runs in CI. - Scripts expect that the binaries they require are already built. They should not compile binaries. - Scripts will spawn the processes for every simulated device and the physical layer simulation. - Scripts must return 0 to the invoking shell if the test passes, and not 0 if the test fails. - Each test must have a unique simulation id, to enable running different tests in parallel. - Neither the scripts nor the images should modify the workstation filesystem content beyond the ``${BSIM_OUT_PATH}/results/<simulation_id>/`` or ``/tmp/`` folders. That is, they should not leave stray files behind. - Tests that require several consecutive simulations (e.g, if simulating a device pairing, powering off, and powering up after as a new simulation) should use separate simulation ids for each simulation segment, ensuring that the radio activity of each segment can be inspected a posteriori. - Avoid overly long tests. If the test takes over 20 seconds of runtime, consider if it is possible to split it in several separate tests. - If the test takes over 5 seconds, set ``EXECUTE_TIMEOUT`` to a value that is at least 5 times bigger than the measured run-time. - Do not set ``EXECUTE_TIMEOUT`` to a value lower than the default. - Tests should not be overly verbose: less than a hundred lines are expected on the outputs. Do make use of ``LOG_DBG()`` extensively, but don't enable the ``DBG`` log level by default. ```	/content/code_sandbox/doc/develop/test/bsim.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,015
```python #!/usr/bin/env python3 # import importlib import mock import os import pytest import sys import json from conftest import ZEPHYR_BASE, TEST_DATA, testsuite_filename_mock from twisterlib.testplan import TestPlan class TestDummy: TESTDATA_X = [ ("smoke", 5), ("acceptance", 6), ] @classmethod def setup_class(cls): apath = os.path.join(ZEPHYR_BASE, "scripts", "twister") cls.loader = importlib.machinery.SourceFileLoader("__main__", apath) cls.spec = importlib.util.spec_from_loader(cls.loader.name, cls.loader) cls.twister_module = importlib.util.module_from_spec(cls.spec) @classmethod def teardown_class(cls): pass @pytest.mark.parametrize( "level, expected_tests", TESTDATA_X, ids=["smoke", "acceptance"] ) @mock.patch.object(TestPlan, "TESTSUITE_FILENAME", testsuite_filename_mock) def test_level(self, capfd, out_path, level, expected_tests): # Select platforms used for the tests test_platforms = ["qemu_x86", "frdm_k64f"] # Select test root path = os.path.join(TEST_DATA, "tests") config_path = os.path.join(TEST_DATA, "test_config.yaml") # Set flags for our Twister command as a list of strs args = ( # Flags related to the generic test setup: # * Control the level of detail in stdout/err # * Establish the output directory # * Select Zephyr tests to use # * Control whether to only build or build and run aforementioned tests ["-i", "--outdir", out_path, "-T", path, "-y"] # Flags under test + ["--level", level] # Flags required for the test + ["--test-config", config_path] # Flags related to platform selection + [ val for pair in zip(["-p"] * len(test_platforms), test_platforms) for val in pair ] ) # First, provide the args variable as our Twister command line arguments. # Then, catch the exit code in the sys_exit variable. with mock.patch.object(sys, "argv", [sys.argv[0]] + args), pytest.raises( SystemExit ) as sys_exit: # Execute the Twister call itself. self.loader.exec_module(self.twister_module) # Check whether the Twister call succeeded assert str(sys_exit.value) == "0" # Access to the test file output with open(os.path.join(out_path, "testplan.json")) as f: j = json.load(f) filtered_j = [ (ts["platform"], ts["name"], tc["identifier"]) for ts in j["testsuites"] for tc in ts["testcases"] if "reason" not in tc ] # Read stdout and stderr to out and err variables respectively out, err = capfd.readouterr() # Rewrite the captured buffers to stdout and stderr so the user can still read them sys.stdout.write(out) sys.stderr.write(err) # Test-relevant checks assert expected_tests == len(filtered_j) ```	/content/code_sandbox/doc/develop/test/twister/sample_blackbox_test.py	python	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	726
```restructuredtext .. _language_support: Language Support ################ .. toctree:: :maxdepth: 2 c/index.rst cpp/index.rst ```	/content/code_sandbox/doc/develop/languages/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	36
```restructuredtext .. _twister_blackbox: Twister blackbox tests ###################### This guide aims to explain the structure of a test file so the reader will be able to understand existing files and create their own. All developers should fix any tests they break and create new ones when introducing new features, so this knowledge is important for any Twister developer. Basics **** Twister blackbox tests are written in python, using the ``pytest`` library. Read up on it :ref:`here <integration_with_pytest>` . Auxiliary test data follows whichever format it was in originally. Tests and data are wholly contained in the :zephyr_file:`scripts/tests/twister_blackbox` directory and prepended with ``test_``. Blackbox tests should not be aware of the internal twister code. Instead, they should call twister as user would and check the results. Sample test file ************ .. literalinclude:: ./sample_blackbox_test.py :language: python :linenos: Comparison with CLI *************** Test above runs the command .. code-block:: console twister -i --outdir $OUTDIR -T $TEST_DATA/tests -y --level $LEVEL --test-config $TEST_DATA/test_config.yaml -p qemu_x86 -p frdm_k64f It presumes a CLI with the ``zephyr-env.sh`` or ``zephyr-env.cmd`` already run. Such a test provides us with all the outputs we typically expect of a Twister run thanks to ``importlib`` 's ``exec_module()`` [#f1]_ . We can easily set up all flags that we expect from a Twister call via ``args`` variable [#f2]_ . We can check the standard output or stderr in ``out`` and ``err`` variables. Beside the standard outputs, we can also investigate the file outputs, normally placed in ``twister-out`` directories. Most of the time, we will use the ``out_path`` fixture in conjunction with ``--outdir`` flag (L52) to keep test-generated files in temporary directories. Typical files read in blackbox tests are ``testplan.json`` , ``twister.xml`` and ``twister.log`` . Other functionalities ******************* Decorators ========== * ``@pytest.mark.usefixtures('clear_log')`` - allows us to use ``clear_log`` fixture from ``conftest.py`` . The fixture is to become ``autouse`` in the future. After that, this decorator can be removed. * ``@pytest.mark.parametrize('level, expected_tests', TESTDATA_X, ids=['smoke', 'acceptance'])`` - this is an example of ``pytest`` 's test parametrization. Read up on it `here <path_to_url#different-options-for-test-ids>`__. TESTDATAs are most often declared as class fields. * ``@mock.patch.object(TestPlan, 'TESTSUITE_FILENAME', testsuite_filename_mock)`` - this decorator allows us to use only tests defined in the ``test_data`` and ignore the Zephyr testcases in the ``tests`` directory. Note that all ``test_data`` tests use ``test_data.yaml`` as a filename, not ``testcase.yaml`` ! Read up on the ``mock`` library `here <path_to_url`__. Fixtures ======== Blackbox tests use ``pytest`` 's fixtures, further reading on which is available `here <path_to_url`__. If you would like to add your own fixtures, consider whether they will be used in just one test file, or in many. * If in many, create such a fixture in the :zephyr_file:`scripts/tests/twister_blackbox/conftest.py` file. - :zephyr_file:`scripts/tests/twister_blackbox/conftest.py` already contains some fixtures - take a look there for an example. * If in just one, declare it in that file. - Consider using class fields instead - look at TESTDATAs for an example. How do I... *********** Call Twister multiple times in one test? ======================================== Sometimes we want to test something that requires prior Twister use. ``--test-only`` flag would be a typical example, as it is to be coupled with previous ``--build-only`` Twister call. How should we approach that? If we just call the ``importlib`` 's ``exec_module`` two times, we will experience log duplication. ``twister.log`` will duplicate every line (triplicate if we call it three times, etc.) instead of overwriting the log or appending to the end of it. It is caused by the use of logger module variables in the Twister files. Thus us executing the module again causes the loggers to have multiple handles. To overcome this, between the calls you ought to use .. code:: python capfd.readouterr() # To remove output from the buffer # Note that if you want output from all runs after each other, # skip this line. clear_log_in_test() # To remove log duplication ------ .. rubric:: Footnotes .. [#f1] Take note of the ``setup_class()`` class function, which allows us to run ``twister`` python file as if it were called directly (bypassing the ``__name__ == '__main__'`` check). .. [#f2] We advise you to keep the first section of ``args`` definition intact in almost all of your tests, as it is used for the common test setup. ```	/content/code_sandbox/doc/develop/test/twister/twister_blackbox.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,198
```restructuredtext .. _c_library_minimal: Minimal libc ############ The most basic C library, named "minimal libc", is part of the Zephyr codebase and provides the minimal subset of the standard C library required to meet the needs of Zephyr and its subsystems, primarily in the areas of string manipulation and display. It is very low footprint and is suitable for projects that do not rely on less frequently used portions of the ISO C standard library. It can also be used with a number of different toolchains. The minimal libc implementation can be found in :file:`lib/libc/minimal` in the main Zephyr tree. Functions ******* The minimal libc implements the minimal subset of the ISO/IEC 9899:2011 standard C library functions required to meet the needs of the Zephyr kernel, as defined by the :ref:`Coding Guidelines Rule A.4 <coding_guideline_libc_usage_restrictions_in_zephyr_kernel>`. Formatted Output ************ The minimal libc does not implement its own formatted output processor; instead, it maps the C standard formatted output functions such as ``printf`` and ``sprintf`` to the :c:func:`cbprintf` function, which is Zephyr's own C99-compatible formatted output implementation. For more details, refer to the :ref:`Formatted Output <formatted_output>` OS service documentation. Dynamic Memory Management ********************* The minimal libc uses the malloc api family implementation provided by the :ref:`common C library <c_library_common>`, which itself is built upon the :ref:`kernel memory heap API <heap_v2>`. Error numbers *********** Error numbers are used throughout Zephyr APIs to signal error conditions as return values from functions. They are typically returned as the negative value of the integer literals defined in this section, and are defined in the :file:`errno.h` header file. A subset of the error numbers defined in the `POSIX errno.h specification`_ and other de-facto standard sources have been added to the minimal libc. A conscious effort is made in Zephyr to keep the values of the minimal libc error numbers consistent with the different implementations of the C standard libraries supported by Zephyr. The minimal libc :file:`errno.h` is checked against that of the :ref:`Newlib <c_library_newlib>` to ensure that the error numbers are kept aligned. Below is a list of the error number definitions. For the actual numeric values please refer to `errno.h`_. .. doxygengroup:: system_errno .. _`POSIX errno.h specification`: path_to_url .. _`errno.h`: path_to_url ```	/content/code_sandbox/doc/develop/languages/c/minimal_libc.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	570
```restructuredtext .. _language_c: C Language Support ################## C is a general-purpose low-level programming language that is widely used for writing code for embedded systems. Zephyr is primarily written in C and natively supports applications written in the C language. All Zephyr API functions and macros are implemented in C and available as part of the C header files under the :file:`include` directory, so writing Zephyr applications in C gives the developers access to the most features. The ``main()`` function must have the return type of ``int`` as Zephyr applications run in a "hosted" environment as defined by the C standard. Applications must return zero (0) from main. All non-zero return values are reserved. .. _c_standards: Language Standards ****************** Zephyr does not target a specific version of the C standards; however, the Zephyr codebase makes extensive use of the features newly introduced in the 1999 release of the ISO C standard (ISO/IEC 9899:1999, hereinafter referred to as C99) such as those listed below, effectively requiring the use of a compiler toolchain that supports the C99 standard and above: * inline functions * standard boolean types (``bool`` in ``<stdbool.h>``) * fixed-width integer types (``[u]intN_t`` in ``<stdint.h>``) * designated initializers * variadic macros * ``restrict`` qualification Some Zephyr components make use of the features newly introduced in the 2011 release of the ISO C standard (ISO/IEC 9899:2011, hereinafter referred to as C11) such as the type-generic expressions using the ``_Generic`` keyword. For example, the :c:func:`cbprintf` component, used as the default formatted output processor for Zephyr, makes use of the C11 type-generic expressions, and this effectively requires most Zephyr applications to be compiled using a compiler toolchain that supports the C11 standard and above. In summary, it is recommended to use a compiler toolchain that supports at least the C11 standard for developing with Zephyr. It is, however, important to note that some optional Zephyr components and external modules may make use of the C language features that have been introduced in more recent versions of the standards, in which case it will be necessary to use a more up-to-date compiler toolchain that supports such standards. .. _c_library: Standard Library ************** The `C Standard Library`_ is an integral part of any C program, and Zephyr provides the support for a number of different C libraries for the applications to choose from, depending on the compiler toolchain being used to build the application. .. toctree:: :maxdepth: 2 common_libc.rst minimal_libc.rst newlib.rst picolibc.rst .. _`C Standard Library`: path_to_url .. _c_library_formatted_output: Formatted Output ************ C defines standard formatted output functions such as ``printf`` and ``sprintf`` and these functions are implemented by the C standard libraries. Each C standard library has its own set of requirements and configurations for selecting the formatted output modes and capabilities. Refer to each C standard library documentation for more details. .. _c_library_dynamic_mem: Dynamic Memory Management *********************** C defines a standard dynamic memory management interface (for example, :c:func:`malloc` and :c:func:`free`) and these functions are implemented by the C standard libraries. While the details of the dynamic memory management implementation varies across different C standard libraries, all supported libraries must conform to the following conventions. Every supported C standard library shall: * manage its own memory heap either internally or by invoking the hook functions (for example, :c:func:`sbrk`) implemented in :file:`libc-hooks.c`. * maintain the architecture- and memory region-specific alignment requirements for the memory blocks allocated by the standard dynamic memory allocation interface (for example, :c:func:`malloc`). * allocate memory blocks inside the ``z_malloc_partition`` memory partition when userspace is enabled. See :ref:`memory_domain_predefined_partitions`. For more details regarding the C standard library-specific memory management implementation, refer to each C standard library documentation. .. note:: Native Zephyr applications should use the :ref:`memory management API <memory_management_api>` supported by the Zephyr kernel such as :c:func:`k_malloc` in order to take advantage of the advanced features that they offer. C standard dynamic memory management interface functions such as :c:func:`malloc` should be used only by the portable applications and libraries that target multiple operating systems. ```	/content/code_sandbox/doc/develop/languages/c/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,037
```restructuredtext .. _language_cpp: C++ Language Support #################### C++ is a general-purpose object-oriented programming language that is based on the C language. Enabling C++ Support ****************** Zephyr supports applications written in both C and C++. However, to use C++ in an application you must configure Zephyr to include C++ support by selecting the :kconfig:option:`CONFIG_CPP` in the application configuration file. To enable C++ support, the compiler toolchain must also include a C++ compiler and the included compiler must be supported by the Zephyr build system. The :ref:`toolchain_zephyr_sdk`, which includes the GNU C++ Compiler (part of GCC), is supported by Zephyr, and the features and their availability documented here assume the use of the Zephyr SDK. The default C++ standard level (i.e. the language enforced by the compiler flags passed) for Zephyr apps is C++11. Other standards are available via kconfig choice, for example :kconfig:option:`CONFIG_STD_CPP98`. The oldest standard supported and tested in Zephyr is C++98. When compiling a source file, the build system selects the C++ compiler based on the suffix (extension) of the files. Files identified with either a cpp or a cxx suffix are compiled using the C++ compiler. For example, :file:`myCplusplusApp.cpp` is compiled using C++. The C++ standard requires the ``main()`` function to have the return type of ``int``. Your ``main()`` must be defined as ``int main(void)``. Zephyr ignores the return value from main, so applications should not return status information and should, instead, return zero. .. note:: Do not use C++ for kernel, driver, or system initialization code. Language Features *************** Zephyr currently provides only a subset of C++ functionality. The following features are not supported: * Static global object destruction * OS-specific C++ standard library classes (e.g. ``std::thread``, ``std::mutex``) While not an exhaustive list, support for the following functionality is included: * Inheritance * Virtual functions * Virtual tables * Static global object constructors * Dynamic object management with the new and delete operators * Exceptions * :abbr:`RTTI (runtime type information)` * Standard Template Library (STL) Static global object constructors are initialized after the drivers are initialized but before the application :c:func:`main()` function. Therefore, use of C++ is restricted to application code. In order to make use of the C++ exceptions, the :kconfig:option:`CONFIG_CPP_EXCEPTIONS` must be selected in the application configuration file. Zephyr Minimal C++ Library ************************** Zephyr minimal C++ library (:file:`lib/cpp/minimal`) provides a minimal subset of the C++ standard library and application binary interface (ABI) functions to enable basic C++ language support. This includes: * ``new`` and ``delete`` operators * virtual function stub and vtables * static global initializers for global constructors The scope of the minimal C++ library is strictly limited to providing the basic C++ language support, and it does not implement any `Standard Template Library (STL)`_ classes and functions. For this reason, it is only suitable for use in the applications that implement their own (non-standard) class library and do not rely on the Standard Template Library (STL) components. Any application that makes use of the Standard Template Library (STL) components, such as ``std::string`` and ``std::vector``, must enable the C++ standard library support. C++ Standard Library ******************** The `C++ Standard Library`_ is a collection of classes and functions that are part of the ISO C++ standard (``std`` namespace). Zephyr does not include any C++ standard library implementation in source code form. Instead, it allows configuring the build system to link against the pre-built C++ standard library included in the C++ compiler toolchain. To enable C++ standard library, select an applicable toolchain-specific C++ standard library type from the :kconfig:option:`CONFIG_LIBCPP_IMPLEMENTATION` in the application configuration file. For instance, when building with the :ref:`toolchain_zephyr_sdk`, the build system can be configured to link against the GNU C++ Library (``libstdc++.a``), which is a fully featured C++ standard library that provides all features required by the ISO C++ standard including the Standard Template Library (STL), by selecting :kconfig:option:`CONFIG_GLIBCXX_LIBCPP` in the application configuration file. The following C++ standard libraries are supported by Zephyr: * GNU C++ Library (:kconfig:option:`CONFIG_GLIBCXX_LIBCPP`) * ARC MetaWare C++ Library (:kconfig:option:`CONFIG_ARCMWDT_LIBCPP`) A Zephyr subsystem that requires the features from the full C++ standard library can select, from its config, :kconfig:option:`CONFIG_REQUIRES_FULL_LIBCPP`, which automatically selects a compatible C++ standard library unless the Kconfig symbol for a specific C++ standard library is selected. Header files and incompatibilities between C and C++ **************************************************** To interact with each other, C and C++ must share code through header files: data structures, macros, static functions,... While C and C++ have a large overlap, they're different languages with `known incompatibilities`_. C is not just a C++ subset. Standard levels (e.g.: "C+11") add another level of complexity as new features are often inspired by and copied from the other language but many years later and with subtle differences. Making things more complex, compilers often offer early prototypes of features before they become standardized. Standards can have ambiguities interpreted differently by different compilers. Compilers can have bugs and these may need workarounds. To help with this, many projects restrict themselves to a limited number of toolchains. Zephyr does not. These compatibility issues affect header files dis-proportionally. Not just because they have to be compatible between C and C++, but also because they end up being compiled in a surprisingly high number of other source files due to indirect inclusion and the `lack of structure and headers organization`_ that is typical in real-world projects. So, header files are exposed to a much larger variety of toolchains and project configurations. Adding more constraints, the Zephyr project has demanding policies with respect to code style, compiler warnings, static analyzers and standard compliance (e.g.: MISRA). Put together, all these constraints can make writing header files very challenging. The purpose of this section is to document some best "header practices" and lessons learned in a Zephyr-specific context. While a lot of the information here is not Zephyr-specific, this section is not a substitute for knowledge of C/C++ standards, textbooks and other references. Testing ------- Fortunately, the Zephyr project has an extensive test and CI infrastructure that provides coverage baselines, catches issues early, enforces policies and maintains such combinatorial explosions under some control. The ``tests/lib/cpp/cxx/`` are very useful in this context because their ``testcase.yaml`` configuration lets ``twister`` iterate quickly over a range of ``-std`` parameters: ``-std=c++98``, ``-std=c++11``, etc. Keep in mind unused macros are not compiled. Designated initializers ----------------------- Initialization macros are common in header files as they help reduce boilerplate code. C99 added initialization of ``struct`` and ``union`` types by "designated" member names instead of a list of bare expressions. Some GCC versions support designated initializers even in their C90 mode. When used at a simple level, designated initializers are less error-prone, more readable and more flexible. On the other hand, C99 allowed a surprisingly large and lax set of possibilities: designated initializers can be out of order, duplicated, "nested" (``.a.x =``), various other braces can be omitted, designated initializers and not can be mixed, etc. Twenty years later, C++20 added designated initializers to C++ but in much more restricted way; partly because a C++ ``struct`` is actually a ``class``. As described in the C++ proposal number P0329 (which compares with C) or in any complete C++ reference, a mix is not allowed and initializers must be in order (gaps are allowed). Interestingly, the new restrictions in C++20 can cause ``gcc -std=c++20`` to fail to compile code that successfully compiles with ``gcc -std=c++17``. For example, ``gcc -std=c++17`` and older allow the C-style mix of initializers and bare expressions. This fails to compile with using ``gcc -std=c++20`` with the same GCC version. Recommendation: to maximize compatibility across different C and C++ toolchains and standards, designated initializers in Zephyr header files should follow all C++20 rules and restrictions. Non-designated, pre-C99 initialization offers more compatibility and is also allowed but designated initialization is the more readable and preferred code style. In any case, both styles must never be mixed in the same initializer. Warning: successful compilation is not the end of the incompatibility story. For instance, the evaluation order of initializer expressions is unspecified in C99! It is the (expected) left-to-right order in C++20. Other standard revisions may vary. In doubt, do not rely on evaluation order (here and elsewhere). Anonymous unions ---------------- Anonymous unions (a.k.a. "unnamed" unions) seem to have been part of C++ from its very beginning. They were not officially added to C until C11. As usual, there are differences between C and C++. For instance, C supports anonymous unions only as a member of an enclosing ``struct`` or ``union``, empty lists ``{ }`` have always been allowed in C++ but they require C23, etc. When initializing anonymous members, the expression can be enclosed in braces or not. It can be either designated or bare. For maximum portability, when initializing anonymous unions: - Do not enclose designated initializers with braces. This is required by C++20 and above which perceive such braces as mixing bare expressions with (other) designated initializers and fails to compile. - Do enclose bare expressions with braces. This is required by C. Maybe because C is laxer and allows many initialization possibilities and variations, so it may need such braces to disambiguate? Note C does allow omitting most braces in initializer expressions - but not in this particular case of initializing anonymous unions with bare expressions. Some pre-C11 GCC versions support some form of anonymous unions. They unfortunately require enclosing their designated initializers with braces which conflicts with this recommendation. This can be solved with an ``#ifdef __STDC_VERSION__`` as demonstrated in Zephyr commit `c15f029a7108 <path_to_url`_ and the corresponding code review. .. _`C++ Standard Library`: path_to_url .. _`Standard Template Library (STL)`: path_to_url .. _`known incompatibilities`: path_to_url .. _`lack of structure and headers organization`: path_to_url .. _`gcc commit [C++ PATCH] P0329R4: Designated Initialization`: path_to_url ```	/content/code_sandbox/doc/develop/languages/cpp/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,540
```restructuredtext .. _c_library_common: Common C library code ##################### Zephyr provides some C library functions that are designed to be used in conjunction with multiple C libraries. These either provide functions not available in multiple C libraries or are designed to replace functionality in the C library with code better suited for use in the Zephyr environment Time function *********** This provides an implementation of the standard C function, :c:func:`time`, relying on the Zephyr function, :c:func:`clock_gettime`. This function can be enabled by selecting :kconfig:option:`COMMON_LIBC_TIME`. Dynamic Memory Management *********************** The common dynamic memory management implementation can be enabled by selecting the :kconfig:option:`CONFIG_COMMON_LIBC_MALLOC` in the application configuration file. The common C library internally uses the :ref:`kernel memory heap API <heap_v2>` to manage the memory heap used by the standard dynamic memory management interface functions such as :c:func:`malloc` and :c:func:`free`. The internal memory heap is normally located in the ``.bss`` section. When userspace is enabled, however, it is placed in a dedicated memory partition called ``z_malloc_partition``, which can be accessed from the user mode threads. The size of the internal memory heap is specified by the :kconfig:option:`CONFIG_COMMON_LIBC_MALLOC_ARENA_SIZE`. The default heap size for applications using the common C library is zero (no heap). For other C library users, if there is an MMU present, then the default heap is 16kB. Otherwise, the heap uses all available memory. There are also separate controls to select :c:func:`calloc` (:kconfig:option:`COMMON_LIBC_CALLOC`) and :c:func:`reallocarray` (:kconfig:option:`COMMON_LIBC_REALLOCARRAY`). Both of these are enabled by default as that doesn't impact memory usage in applications not using them. The standard dynamic memory management interface functions implemented by the common C library are thread safe and may be simultaneously called by multiple threads. These functions are implemented in :file:`lib/libc/common/source/stdlib/malloc.c`. ```	/content/code_sandbox/doc/develop/languages/c/common_libc.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	466
```restructuredtext .. _c_library_picolibc: Picolibc ######## `Picolibc`_ is a complete C library implementation written for the embedded systems, targeting `C17 (ISO/IEC 9899:2018)`_ and `POSIX 2018 (IEEE Std 1003.1-2017)`_ standards. Picolibc is an external open source project which is provided for Zephyr as a module, and included as part of the :ref:`toolchain_zephyr_sdk` in precompiled form for each supported architecture (:file:`libc.a`). .. note:: Picolibc is also available for other 3rd-party toolchains, such as :ref:`toolchain_gnuarmemb`. Zephyr implements the API hook functions that are invoked by the C standard library functions in the Picolibc. These hook functions are implemented in :file:`lib/libc/picolibc/libc-hooks.c` and translate the library internal system calls to the equivalent Zephyr API calls. .. _`Picolibc`: path_to_url .. _`C17 (ISO/IEC 9899:2018)`: path_to_url .. _`POSIX 2018 (IEEE Std 1003.1-2017)`: path_to_url .. _c_library_picolibc_module: Picolibc Module =============== When built as a Zephyr module, there are several configuration knobs available to adjust the feature set in the library, balancing what the library supports versus the code size of the resulting functions. Because the standard C++ library must be compiled for the target C library, the Picolibc module cannot be used with applications which use the standard C++ library. Building the Picolibc module will increase the time it takes to compile the application. The Picolibc module can be enabled by selecting :kconfig:option:`CONFIG_PICOLIBC_USE_MODULE` in the application configuration file. When updating the Picolibc module to a newer version, the :ref:`toolchain-bundled Picolibc in the Zephyr SDK <c_library_picolibc_toolchain>` must also be updated to the same version. .. _c_library_picolibc_toolchain: Toolchain Picolibc ================== Starting with version 0.16, the Zephyr SDK includes precompiled versions of Picolibc for every target architecture, along with precompiled versions of libstdc++. The toolchain version of Picolibc can be enabled by de-selecting :kconfig:option:`CONFIG_PICOLIBC_USE_MODULE` in the application configuration file. For every release of Zephyr, the toolchain-bundled Picolibc and the :ref:`Picolibc module <c_library_picolibc_module>` are guaranteed to be in sync when using the :ref:`recommended version of Zephyr SDK <toolchain_zephyr_sdk_compatibility>`. Building Without Toolchain bundled Picolibc ------------------------------------------- For toolchain where there is no bundled Picolibc, it is still possible to use Picolibc by building it from source. Note that any restrictions mentioned in :ref:`c_library_picolibc_module` still apply. To build without toolchain bundled Picolibc, the toolchain must enable :kconfig:option:`CONFIG_PICOLIBC_SUPPORTED`. For example, this needs to be added to the toolchain Kconfig file: .. code-block:: kconfig config TOOLCHAIN_<name>_PICOLIBC_SUPPORTED def_bool y select PICOLIBC_SUPPORTED By enabling :kconfig:option:`CONFIG_PICOLIBC_SUPPORTED`, the build system would automatically build Picolibc from source with its module when there is no toolchain bundled Picolibc. Formatted Output **************** Picolibc supports all standard C formatted input and output functions, including :c:func:`printf`, :c:func:`fprintf`, :c:func:`sprintf` and :c:func:`sscanf`. Picolibc formatted input and output function implementation supports all format specifiers defined by the C17 and POSIX 2018 standards with the following exceptions: * Floating point format specifiers (e.g. ``%f``) require :kconfig:option:`CONFIG_PICOLIBC_IO_FLOAT`. * Long long format specifiers (e.g. ``%lld``) require :kconfig:option:`CONFIG_PICOLIBC_IO_LONG_LONG`. This option is automatically enabled with :kconfig:option:`CONFIG_PICOLIBC_IO_FLOAT`. Printk, cbprintf and friends **************************** When using Picolibc, Zephyr formatted output functions are implemented in terms of stdio calls. This includes: * printk, snprintk and vsnprintk * cbprintf and cbvprintf * fprintfcb, vfprintfcb, printfcb, vprintfcb, snprintfcb and vsnprintfcb When using tagged args (:kconfig:option:`CONFIG_CBPRINTF_PACKAGE_SUPPORT_TAGGED_ARGUMENTS` and :c:macro:`CBPRINTF_PACKAGE_ARGS_ARE_TAGGED`), calls to cbpprintf will not use Picolibc, so formatting of output using those code will differ from Picolibc results as the cbprintf functions are not completely C/POSIX compliant. Math Functions ************ Picolibc provides full C17/`IEEE STD 754-2019`_ support for float, double and long double math operations, except for long double versions of the Bessel functions. .. _`IEEE STD 754-2019`: path_to_url Thread Local Storage **************** Picolibc uses Thread Local Storage (TLS) (where supported) for data which is supposed to remain local to each thread, like :c:macro:`errno`. This means that TLS support is enabled when using Picolibc. As all TLS variables are allocated out of the thread stack area, this can affect stack size requirements by a few bytes. C Library Local Variables ********************* Picolibc uses a few internal variables for things like heap management. These are collected in a dedicated memory partition called :c:var:`z_libc_partition`. Applications using :kconfig:option:`CONFIG_USERSPACE` and memory domains must ensure that this partition is included in any domain active during Picolibc calls. Dynamic Memory Management *********************** Picolibc uses the malloc api family implementation provided by the :ref:`common C library <c_library_common>`, which itself is built upon the :ref:`kernel memory heap API <heap_v2>`. ```	/content/code_sandbox/doc/develop/languages/c/picolibc.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,421
```restructuredtext .. _mac-setup-alts: macOS alternative setup instructions #################################### .. _mac-gatekeeper: Important note about Gatekeeper ******************************* Starting with macOS 10.15 Catalina, applications launched from the macOS Terminal application (or any other terminal emulator) are subject to the same system security policies that are applied to applications launched from the Dock. This means that if you download executable binaries using a web browser, macOS will not let you execute those from the Terminal by default. In order to get around this issue you can take two different approaches: * Run ``xattr -r -d com.apple.quarantine /path/to/folder`` where ``path/to/folder`` is the path to the enclosing folder where the executables you want to run are located. * Open :menuselection:`System Preferences --> Security and Privacy --> Privacy` and then scroll down to "Developer Tools". Then unlock the lock to be able to make changes and check the checkbox corresponding to your terminal emulator of choice. This will apply to any executable being launched from such terminal program. Note that this section does not apply to executables installed with Homebrew, since those are automatically un-quarantined by ``brew`` itself. This is however relevant for most :ref:`toolchains`. .. _macOS Gatekeeper: path_to_url Additional notes for MacPorts users *********************************** While MacPorts is not officially supported in this guide, it is possible to use MacPorts instead of Homebrew to get all the required dependencies on macOS. Note also that you may need to install ``rust`` and ``cargo`` for the Python dependencies to install correctly. ```	/content/code_sandbox/doc/develop/getting_started/installation_mac.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	358
```restructuredtext .. _c_library_newlib: Newlib ###### `Newlib`_ is a complete C library implementation written for the embedded systems. It is a separate open source project and is not included in source code form with Zephyr. Instead, the :ref:`toolchain_zephyr_sdk` includes a precompiled library for each supported architecture (:file:`libc.a` and :file:`libm.a`). .. note:: Other 3rd-party toolchains, such as :ref:`toolchain_gnuarmemb`, also bundle the Newlib as a precompiled library. Zephyr implements the "API hook" functions that are invoked by the C standard library functions in the Newlib. These hook functions are implemented in :file:`lib/libc/newlib/libc-hooks.c` and translate the library internal system calls to the equivalent Zephyr API calls. Types of Newlib ************* The Newlib included in the :ref:`toolchain_zephyr_sdk` comes in two versions: 'full' and 'nano' variants. Full Newlib =========== The Newlib full variant (:file:`libc.a` and :file:`libm.a`) is the most capable variant of the Newlib available in the Zephyr SDK, and supports almost all standard C library features. It is optimized for performance (prefers performance over code size) and its footprint is significantly larger than the nano variant. This variant can be enabled by selecting the :kconfig:option:`CONFIG_NEWLIB_LIBC` and de-selecting the :kconfig:option:`CONFIG_NEWLIB_LIBC_NANO` in the application configuration file. Nano Newlib =========== The Newlib nano variant (:file:`libc_nano.a` and :file:`libm_nano.a`) is the size-optimized version of the Newlib, and supports all features that the full variant supports except the new format specifiers introduced in C99, such as the ``char``, ``long long`` type format specifiers (i.e. ``%hhX`` and ``%llX``). This variant can be enabled by selecting the :kconfig:option:`CONFIG_NEWLIB_LIBC` and :kconfig:option:`CONFIG_NEWLIB_LIBC_NANO` in the application configuration file. Note that the Newlib nano variant is not available for all architectures. The availability of the nano variant is specified by the :kconfig:option:`CONFIG_HAS_NEWLIB_LIBC_NANO`. .. _`Newlib`: path_to_url Formatted Output ************** Newlib supports all standard C formatted input and output functions, including ``printf``, ``fprintf``, ``sprintf`` and ``sscanf``. The Newlib formatted input and output function implementation supports all format specifiers defined by the C standard with the following exceptions: * Floating point format specifiers (e.g. ``%f``) require :kconfig:option:`CONFIG_NEWLIB_LIBC_FLOAT_PRINTF` and :kconfig:option:`CONFIG_NEWLIB_LIBC_FLOAT_SCANF` to be enabled. * C99 format specifiers are not supported in the Newlib nano variant (i.e. ``%hhX`` for ``char``, ``%llX`` for ``long long``, ``%jX`` for ``intmax_t``, ``%zX`` for ``size_t``, ``%tX`` for ``ptrdiff_t``). Dynamic Memory Management ************************* Newlib implements an internal heap allocator to manage the memory blocks used by the standard dynamic memory management interface functions (for example, :c:func:`malloc` and :c:func:`free`). The internal heap allocator implemented by the Newlib may vary across the different types of the Newlib used. For example, the heap allocator implemented in the Full Newlib (:file:`libc.a` and :file:`libm.a`) of the Zephyr SDK requests larger memory chunks to the operating system and has a significantly higher minimum memory requirement compared to that of the Nano Newlib (:file:`libc_nano.a` and :file:`libm_nano.a`). The only interface between the Newlib dynamic memory management functions and the Zephyr-side libc hooks is the :c:func:`sbrk` function, which is used by the Newlib to manage the size of the memory pool reserved for its internal heap allocator. The :c:func:`_sbrk` hook function, implemented in :file:`libc-hooks.c`, handles the memory pool size change requests from the Newlib and ensures that the Newlib internal heap allocator memory pool size does not exceed the amount of available memory space by returning an error when the system is out of memory. When userspace is enabled, the Newlib internal heap allocator memory pool is placed in a dedicated memory partition called ``z_malloc_partition``, which can be accessed from the user mode threads. The amount of memory space available for the Newlib heap depends on the system configurations: * When MMU is enabled (:kconfig:option:`CONFIG_MMU` is selected), the amount of memory space reserved for the Newlib heap is set by the size of the free memory space returned by the :c:func:`k_mem_free_get` function or the :kconfig:option:`CONFIG_NEWLIB_LIBC_MAX_MAPPED_REGION_SIZE`, whichever is the smallest. * When MPU is enabled and the MPU requires power-of-two partition size and address alignment (:kconfig:option:`CONFIG_NEWLIB_LIBC_ALIGNED_HEAP_SIZE` is set to a non-zero value), the amount of memory space reserved for the Newlib heap is set by the :kconfig:option:`CONFIG_NEWLIB_LIBC_ALIGNED_HEAP_SIZE`. * Otherwise, the amount of memory space reserved for the Newlib heap is equal to the amount of free (unallocated) memory in the SRAM region. The standard dynamic memory management interface functions implemented by the Newlib are thread safe and may be simultaneously called by multiple threads. ```	/content/code_sandbox/doc/develop/languages/c/newlib.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	1,280
```restructuredtext .. _installation_linux: Install Linux Host Dependencies ############################### Documentation is available for these Linux distributions: * Ubuntu * Fedora * Clear Linux * Arch Linux For distributions that are not based on rolling releases, some of the requirements and dependencies may not be met by your package manager. In that case please follow the additional instructions that are provided to find software from sources other than the package manager. .. note:: If you're working behind a corporate firewall, you'll likely need to configure a proxy for accessing the internet, if you haven't done so already. While some tools use the environment variables ``http_proxy`` and ``https_proxy`` to get their proxy settings, some use their own configuration files, most notably ``apt`` and ``git``. Update Your Operating System ************************** Ensure your host system is up to date. .. tabs:: .. group-tab:: Ubuntu .. code-block:: console sudo apt-get update sudo apt-get upgrade .. group-tab:: Fedora .. code-block:: console sudo dnf upgrade .. group-tab:: Clear Linux .. code-block:: console sudo swupd update .. group-tab:: Arch Linux .. code-block:: console sudo pacman -Syu .. _linux_requirements: Install Requirements and Dependencies *********************************** .. NOTE FOR DOCS AUTHORS: DO NOT PUT DOCUMENTATION BUILD DEPENDENCIES HERE. This section is for dependencies to build Zephyr binaries, NOT this documentation. If you need to add a dependency only required for building the docs, add it to doc/README.rst. (This change was made following the introduction of LaTeX->PDF support for the docs, as the texlive footprint is massive and not needed by users not building PDF documentation.) Note that both Ninja and Make are installed with these instructions; you only need one. .. tabs:: .. group-tab:: Ubuntu .. code-block:: console sudo apt-get install --no-install-recommends git cmake ninja-build gperf \ ccache dfu-util device-tree-compiler wget \ python3-dev python3-pip python3-setuptools python3-tk python3-wheel xz-utils file \ make gcc gcc-multilib g++-multilib libsdl2-dev libmagic1 .. group-tab:: Fedora .. code-block:: console sudo dnf group install "Development Tools" "C Development Tools and Libraries" sudo dnf install cmake ninja-build gperf dfu-util dtc wget which \ python3-pip python3-tkinter xz file python3-devel SDL2-devel .. group-tab:: Clear Linux .. code-block:: console sudo swupd bundle-add c-basic dev-utils dfu-util dtc \ os-core-dev python-basic python3-basic python3-tcl The Clear Linux focus is on native performance and security and not cross-compilation. For that reason it uniquely exports by default to the :ref:`environment <env_vars>` of all users a list of compiler and linker flags. Zephyr's CMake build system will either warn or fail because of these. To clear the C/C++ flags among these and fix the Zephyr build, run the following command as root then log out and back in: .. code-block:: console echo 'unset CFLAGS CXXFLAGS' >> /etc/profile.d/unset_cflags.sh Note this command unsets the C/C++ flags for all users on the system. Each Linux distribution has a unique, relatively complex and potentially evolving sequence of bash initialization files sourcing each other and Clear Linux is no exception. If you need a more flexible solution, start by looking at the logic in ``/usr/share/defaults/etc/profile``. .. group-tab:: Arch Linux .. code-block:: console sudo pacman -S git cmake ninja gperf ccache dfu-util dtc wget \ python-pip python-setuptools python-wheel tk xz file make CMake ===== A :ref:`recent CMake version <install-required-tools>` is required. Check what version you have by using ``cmake --version``. If you have an older version, there are several ways of obtaining a more recent one: * On Ubuntu, you can follow the instructions for adding the `kitware third-party apt repository <path_to_url`_ to get an updated version of cmake using apt. * Download and install a packaged cmake from the CMake project site. (Note this won't uninstall the previous version of cmake.) .. code-block:: console cd ~ wget path_to_url chmod +x cmake-3.21.1-Linux-x86_64.sh sudo ./cmake-3.21.1-Linux-x86_64.sh --skip-license --prefix=/usr/local hash -r The ``hash -r`` command may be necessary if the installation script put cmake into a new location on your PATH. * Download and install from the pre-built binaries provided by the CMake project itself in the `CMake Downloads`_ page. For example, to install version 3.21.1 in :file:`~/bin/cmake`: .. code-block:: console mkdir $HOME/bin/cmake && cd $HOME/bin/cmake wget path_to_url yes \| sh cmake-3.21.1-Linux-x86_64.sh \| cat echo "export PATH=$PWD/cmake-3.21.1-Linux-x86_64/bin:\$PATH" >> $HOME/.zephyrrc * Use ``pip3``: .. code-block:: console pip3 install --user cmake Note this won't uninstall the previous version of cmake and will install the new cmake into your ~/.local/bin folder so you'll need to add ~/.local/bin to your PATH. (See :ref:`python-pip` for details.) * Check your distribution's beta or unstable release package library for an update. * On Ubuntu you can also use snap to get the latest version available: .. code-block:: console sudo snap install cmake After updating cmake, verify that the newly installed cmake is found using ``cmake --version``. You might also want to uninstall the CMake provided by your package manager to avoid conflicts. (Use ``whereis cmake`` to find other installed versions.) DTC (Device Tree Compiler) ========================== A :ref:`recent DTC version <install-required-tools>` is required. Check what version you have by using ``dtc --version``. If you have an older version, either install a more recent one by building from source, or use the one that is bundled in the :ref:`Zephyr SDK <toolchain_zephyr_sdk>` by installing it. Python ====== A :ref:`modern Python 3 version <install-required-tools>` is required. Check what version you have by using ``python3 --version``. If you have an older version, you will need to install a more recent Python 3. You can build from source, or use a backport from your distribution's package manager channels if one is available. Isolating this Python in a virtual environment is recommended to avoid interfering with your system Python. .. _pyenv: path_to_url Install the Zephyr Software Development Kit (SDK) ************************************************* The Zephyr Software Development Kit (SDK) contains toolchains for each of Zephyr's supported architectures. It also includes additional host tools, such as custom QEMU and OpenOCD. Use of the Zephyr SDK is highly recommended and may even be required under certain conditions (for example, running tests in QEMU for some architectures). The Zephyr SDK supports the following target architectures: * ARC (32-bit and 64-bit; ARCv1, ARCv2, ARCv3) * ARM (32-bit and 64-bit; ARMv6, ARMv7, ARMv8; A/R/M Profiles) * MIPS (32-bit and 64-bit) * Nios II * RISC-V (32-bit and 64-bit; RV32I, RV32E, RV64I) * x86 (32-bit and 64-bit) * Xtensa Follow these steps to install the Zephyr SDK: #. Download and verify the `Zephyr SDK bundle`_: .. parsed-literal:: wget \|sdk-url-linux\| wget -O - \|sdk-url-linux-sha\| \| shasum --check --ignore-missing You can change \|sdk-version-literal\| to another version if needed; the `Zephyr SDK Releases`_ page contains all available SDK releases. If your host architecture is 64-bit ARM (for example, Raspberry Pi), replace ``x86_64`` with ``aarch64`` in order to download the 64-bit ARM Linux SDK. #. Extract the Zephyr SDK bundle archive: .. parsed-literal:: cd <sdk download directory> tar xvf zephyr-sdk- \|sdk-version-trim\| _linux-x86_64.tar.xz #. Run the Zephyr SDK bundle setup script: .. parsed-literal:: cd zephyr-sdk- \|sdk-version-ltrim\| ./setup.sh If this fails, make sure Zephyr's dependencies were installed as described in `Install Requirements and Dependencies`_. If you want to uninstall the SDK, remove the directory where you installed it. If you relocate the SDK directory, you need to re-run the setup script. .. note:: It is recommended to extract the Zephyr SDK bundle at one of the following locations: * ``$HOME`` * ``$HOME/.local`` * ``$HOME/.local/opt`` * ``$HOME/bin`` * ``/opt`` * ``/usr/local`` The Zephyr SDK bundle archive contains the ``zephyr-sdk-<version>`` directory and, when extracted under ``$HOME``, the resulting installation path will be ``$HOME/zephyr-sdk-<version>``. If you install the Zephyr SDK outside any of these locations, you must register the Zephyr SDK in the CMake package registry by running the setup script, or set :envvar:`ZEPHYR_SDK_INSTALL_DIR` to point to the Zephyr SDK installation directory. You can also use :envvar:`ZEPHYR_SDK_INSTALL_DIR` for pointing to a directory containing multiple Zephyr SDKs, allowing for automatic toolchain selection. For example, ``ZEPHYR_SDK_INSTALL_DIR=/company/tools``, where the ``company/tools`` folder contains the following subfolders: * ``/company/tools/zephyr-sdk-0.13.2`` * ``/company/tools/zephyr-sdk-a.b.c`` * ``/company/tools/zephyr-sdk-x.y.z`` This allows the Zephyr build system to choose the correct version of the SDK, while allowing multiple Zephyr SDKs to be grouped together at a specific path. .. _sdkless_builds: Building on Linux without the Zephyr SDK **************************************** The Zephyr SDK is provided for convenience and ease of use. It provides toolchains for all Zephyr target architectures, and does not require any extra flags when building applications or running tests. In addition to cross-compilers, the Zephyr SDK also provides prebuilt host tools. It is, however, possible to build without the SDK's toolchain by using another toolchain as described in the :ref:`toolchains` section. As already noted above, the SDK also includes prebuilt host tools. To use the SDK's prebuilt host tools with a toolchain from another source, you must set the :envvar:`ZEPHYR_SDK_INSTALL_DIR` environment variable to the Zephyr SDK installation directory. To build without the Zephyr SDK's prebuilt host tools, the :envvar:`ZEPHYR_SDK_INSTALL_DIR` environment variable must be unset. To make sure this variable is unset, run: .. code-block:: console unset ZEPHYR_SDK_INSTALL_DIR .. _Zephyr SDK Releases: path_to_url .. _CMake Downloads: path_to_url ```	/content/code_sandbox/doc/develop/getting_started/installation_linux.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,676
```restructuredtext .. _win-setup-alts: Windows alternative setup instructions ###################################### .. _win-wsl: Windows 10 WSL (Windows Subsystem for Linux) ******************************************** If you are running a recent version of Windows 10 you can make use of the built-in functionality to natively run Ubuntu binaries directly on a standard command-prompt. This allows you to use software such as the :ref:`Zephyr SDK <toolchain_zephyr_sdk>` without setting up a virtual machine. .. warning:: Windows 10 version 1803 has an issue that will cause CMake to not work properly and is fixed in version 1809 (and later). More information can be found in :github:`Zephyr Issue 10420 <10420>`. #. `Install the Windows Subsystem for Linux (WSL)`_. .. note:: For the Zephyr SDK to function properly you will need Windows 10 build 15002 or greater. You can check which Windows 10 build you are running in the "About your PC" section of the System Settings. If you are running an older Windows 10 build you might need to install the Creator's Update. #. Follow the Ubuntu instructions in the :ref:`installation_linux` document. .. NOTE FOR DOCS AUTHORS: as a reminder, do NOT put dependencies for building the documentation itself here. .. _Install the Windows Subsystem for Linux (WSL): path_to_url ```	/content/code_sandbox/doc/develop/getting_started/installation_win.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	315
```restructuredtext .. _sparse: Sparse support ############## `Sparse <path_to_url`__ is a static code analysis tool. Apart from performing common code analysis tasks it also supports an ``address_space`` attribute, which allows introduction of distinct address spaces in C code with subsequent verification that pointers to different address spaces do not get confused. Additionally it supports a ``force`` attribute which should be used to cast pointers between different address spaces. At the moment Zephyr introduces a single custom address space ``__cache`` used to identify pointers from the cached address range on the Xtensa architecture. This helps identify cases where cached and uncached addresses are confused. Running with sparse ******************* To run a sparse verification build :ref:`west build <west-building>` should be called with a ``-DZEPHYR_SCA_VARIANT=sparse`` parameter, e.g. .. code-block:: shell west build -d hello -b intel_adsp/cavs25 zephyr/samples/hello_world -- -DZEPHYR_SCA_VARIANT=sparse ```	/content/code_sandbox/doc/develop/sca/sparse.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	226
```restructuredtext .. _getting_started: Getting Started Guide ##################### Follow this guide to: - Set up a command-line Zephyr development environment on Ubuntu, macOS, or Windows (instructions for other Linux distributions are discussed in :ref:`installation_linux`) - Get the source code - Build, flash, and run a sample application .. _host_setup: Select and Update OS ******************** Click the operating system you are using. .. tabs:: .. group-tab:: Ubuntu This guide covers Ubuntu version 20.04 LTS and later. .. code-block:: bash sudo apt update sudo apt upgrade .. group-tab:: macOS On macOS Mojave or later, select System Preferences > Software Update. Click Update Now if necessary. On other versions, see `this Apple support topic <path_to_url`_. .. group-tab:: Windows Select Start > Settings > Update & Security > Windows Update. Click Check for updates and install any that are available. .. _install-required-tools: Install dependencies ******************** Next, you'll install some host dependencies using your package manager. The current minimum required version for the main dependencies are: .. list-table:: :header-rows: 1 * - Tool - Min. Version * - `CMake <path_to_url`_ - 3.20.5 * - `Python <path_to_url`_ - 3.10 * - `Devicetree compiler <path_to_url`_ - 1.4.6 .. tabs:: .. group-tab:: Ubuntu .. _install_dependencies_ubuntu: #. If using an Ubuntu version older than 22.04, it is necessary to add extra repositories to meet the minimum required versions for the main dependencies listed above. In that case, download, inspect and execute the Kitware archive script to add the Kitware APT repository to your sources list. A detailed explanation of ``kitware-archive.sh`` can be found here `kitware third-party apt repository <path_to_url`_: .. code-block:: bash wget path_to_url sudo bash kitware-archive.sh #. Use ``apt`` to install the required dependencies: .. code-block:: bash sudo apt install --no-install-recommends git cmake ninja-build gperf \ ccache dfu-util device-tree-compiler wget \ python3-dev python3-pip python3-setuptools python3-tk python3-wheel xz-utils file \ make gcc gcc-multilib g++-multilib libsdl2-dev libmagic1 #. Verify the versions of the main dependencies installed on your system by entering: .. code-block:: bash cmake --version python3 --version dtc --version Check those against the versions in the table in the beginning of this section. Refer to the :ref:`installation_linux` page for additional information on updating the dependencies manually. .. group-tab:: macOS .. _install_dependencies_macos: #. Install `Homebrew <path_to_url`_: .. code-block:: bash /bin/bash -c "$(curl -fsSL path_to_url" #. After the Homebrew installation script completes, follow the on-screen instructions to add the Homebrew installation to the path. * On macOS running on Apple Silicon, this is achieved with: .. code-block:: bash (echo; echo 'eval "$(/opt/homebrew/bin/brew shellenv)"') >> ~/.zprofile source ~/.zprofile * On macOS running on Intel, use the command for Apple Silicon, but replace ``/opt/homebrew/`` with ``/usr/local/``. #. Use ``brew`` to install the required dependencies: .. code-block:: bash brew install cmake ninja gperf python3 python-tk ccache qemu dtc libmagic wget openocd #. Add the Homebrew Python folder to the path, in order to be able to execute ``python`` and ``pip`` as well ``python3`` and ``pip3``. .. code-block:: bash (echo; echo 'export PATH="'$(brew --prefix)'/opt/python/libexec/bin:$PATH"') >> ~/.zprofile source ~/.zprofile .. group-tab:: Windows .. note:: Due to issues finding executables, the Zephyr Project doesn't currently support application flashing using the `Windows Subsystem for Linux (WSL) <path_to_url`_ (WSL). Therefore, we don't recommend using WSL when getting started. These instructions must be run in a ``cmd.exe`` command prompt terminal window. In modern version of Windows (10 and later) it is recommended to install the Windows Terminal application from the Microsoft Store. The required commands differ on PowerShell. These instructions rely on `Chocolatey`_. If Chocolatey isn't an option, you can install dependencies from their respective websites and ensure the command line tools are on your :envvar:`PATH` :ref:`environment variable <env_vars>`. \|p\| .. _install_dependencies_windows: #. `Install chocolatey`_. #. Open a ``cmd.exe`` terminal window as Administrator. To do so, press the Windows key, type ``cmd.exe``, right-click the :guilabel:`Command Prompt` search result, and choose :guilabel:`Run as Administrator`. #. Disable global confirmation to avoid having to confirm the installation of individual programs: .. code-block:: bat choco feature enable -n allowGlobalConfirmation #. Use ``choco`` to install the required dependencies: .. code-block:: bat choco install cmake --installargs 'ADD_CMAKE_TO_PATH=System' choco install ninja gperf python311 git dtc-msys2 wget 7zip .. warning:: As of November 2023, Python 3.12 is not recommended for Zephyr development on Windows, as some required Python dependencies may be difficult to install. #. Close the terminal window. .. _Chocolatey: path_to_url .. _Install chocolatey: path_to_url .. _get_the_code: .. _clone-zephyr: .. _install_py_requirements: .. _gs_python_deps: Get Zephyr and install Python dependencies **************************************** Next, clone Zephyr and its :ref:`modules <modules>` into a new :ref:`west <west>` workspace named :file:`zephyrproject`. You'll also install Zephyr's additional Python dependencies in a `Python virtual environment`_. .. _Python virtual environment: path_to_url .. tabs:: .. group-tab:: Ubuntu #. Use ``apt`` to install Python ``venv`` package: .. code-block:: bash sudo apt install python3-venv #. Create a new virtual environment: .. code-block:: bash python3 -m venv ~/zephyrproject/.venv #. Activate the virtual environment: .. code-block:: bash source ~/zephyrproject/.venv/bin/activate Once activated your shell will be prefixed with ``(.venv)``. The virtual environment can be deactivated at any time by running ``deactivate``. .. note:: Remember to activate the virtual environment every time you start working. #. Install west: .. code-block:: bash pip install west #. Get the Zephyr source code: .. code-block:: bash west init ~/zephyrproject cd ~/zephyrproject west update #. Export a :ref:`Zephyr CMake package <cmake_pkg>`. This allows CMake to automatically load boilerplate code required for building Zephyr applications. .. code-block:: bash west zephyr-export #. Zephyr's ``scripts/requirements.txt`` file declares additional Python dependencies. Install them with ``pip``. .. code-block:: bash pip install -r ~/zephyrproject/zephyr/scripts/requirements.txt .. group-tab:: macOS #. Create a new virtual environment: .. code-block:: bash python3 -m venv ~/zephyrproject/.venv #. Activate the virtual environment: .. code-block:: bash source ~/zephyrproject/.venv/bin/activate Once activated your shell will be prefixed with ``(.venv)``. The virtual environment can be deactivated at any time by running ``deactivate``. .. note:: Remember to activate the virtual environment every time you start working. #. Install west: .. code-block:: bash pip install west #. Get the Zephyr source code: .. code-block:: bash west init ~/zephyrproject cd ~/zephyrproject west update #. Export a :ref:`Zephyr CMake package <cmake_pkg>`. This allows CMake to automatically load boilerplate code required for building Zephyr applications. .. code-block:: bash west zephyr-export #. Zephyr's ``scripts/requirements.txt`` file declares additional Python dependencies. Install them with ``pip``. .. code-block:: bash pip install -r ~/zephyrproject/zephyr/scripts/requirements.txt .. group-tab:: Windows #. Open a ``cmd.exe`` terminal window as a regular user #. Create a new virtual environment: .. code-block:: bat cd %HOMEPATH% python -m venv zephyrproject\.venv #. Activate the virtual environment: .. code-block:: bat zephyrproject\.venv\Scripts\activate.bat Once activated your shell will be prefixed with ``(.venv)``. The virtual environment can be deactivated at any time by running ``deactivate``. .. note:: Remember to activate the virtual environment every time you start working. #. Install west: .. code-block:: bat pip install west #. Get the Zephyr source code: .. code-block:: bat west init zephyrproject cd zephyrproject west update #. Export a :ref:`Zephyr CMake package <cmake_pkg>`. This allows CMake to automatically load boilerplate code required for building Zephyr applications. .. code-block:: bat west zephyr-export #. Zephyr's ``scripts\requirements.txt`` file declares additional Python dependencies. Install them with ``pip``. .. code-block:: bat pip install -r %HOMEPATH%\zephyrproject\zephyr\scripts\requirements.txt Install the Zephyr SDK ****************** The :ref:`Zephyr Software Development Kit (SDK) <toolchain_zephyr_sdk>` contains toolchains for each of Zephyr's supported architectures, which include a compiler, assembler, linker and other programs required to build Zephyr applications. It also contains additional host tools, such as custom QEMU and OpenOCD builds that are used to emulate, flash and debug Zephyr applications. .. include:: ../toolchains/zephyr_sdk.rst :start-after: toolchain_zephyr_sdk_install_start :end-before: toolchain_zephyr_sdk_install_end .. _getting_started_run_sample: Build the Blinky Sample ******************* .. note:: :zephyr:code-sample:`blinky` is compatible with most, but not all, :ref:`boards`. If your board does not meet Blinky's :ref:`blinky-sample-requirements`, then :ref:`hello_world` is a good alternative. If you are unsure what name west uses for your board, ``west boards`` can be used to obtain a list of all boards Zephyr supports. Build the :zephyr:code-sample:`blinky` with :ref:`west build <west-building>`, changing ``<your-board-name>`` appropriately for your board: .. tabs:: .. group-tab:: Ubuntu .. code-block:: bash cd ~/zephyrproject/zephyr west build -p always -b <your-board-name> samples/basic/blinky .. group-tab:: macOS .. code-block:: bash cd ~/zephyrproject/zephyr west build -p always -b <your-board-name> samples/basic/blinky .. group-tab:: Windows .. code-block:: bat cd %HOMEPATH%\zephyrproject\zephyr west build -p always -b <your-board-name> samples\basic\blinky The ``-p always`` option forces a pristine build, and is recommended for new users. Users may also use the ``-p auto`` option, which will use heuristics to determine if a pristine build is required, such as when building another sample. .. note:: A board may contain one or multiple SoCs, Also, each SoC may contain one or more CPU clusters. When building for such boards it is necessary to specify the SoC or CPU cluster for which the sample must be built. For example to build :zephyr:code-sample:`blinky` for the ``cpuapp`` core on the :ref:`nRF5340DK <nrf5340dk_nrf5340>` the board must be provided as: ``nrf5340dk/nrf5340/cpuapp``. See also :ref:`board_terminology` for more details. Flash the Sample ************ Connect your board, usually via USB, and turn it on if there's a power switch. If in doubt about what to do, check your board's page in :ref:`boards`. Then flash the sample using :ref:`west flash <west-flashing>`: .. code-block:: shell west flash You may need to install additional :ref:`host tools <flash-debug-host-tools>` required by your board. The ``west flash`` command will print an error if any required dependencies are missing. If you're using blinky, the LED will start to blink as shown in this figure: .. figure:: img/ReelBoard-Blinky.png :width: 400px :name: reelboard-blinky Phytec :ref:`reel_board <reel_board>` running blinky Next Steps ******** Here are some next steps for exploring Zephyr: * Try other :ref:`samples-and-demos` * Learn about :ref:`application` and the :ref:`west <west>` tool * Find out about west's :ref:`flashing and debugging <west-build-flash-debug>` features, or more about :ref:`flashing_and_debugging` in general * Check out :ref:`beyond-GSG` for additional setup alternatives and ideas * Discover :ref:`project-resources` for getting help from the Zephyr community .. _troubleshooting_installation: Troubleshooting Installation ************************** Here are some tips for fixing some issues related to the installation process. .. _toolchain_zephyr_sdk_update: Double Check the Zephyr SDK Variables When Updating =================================================== When updating Zephyr SDK, check whether the :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` or :envvar:`ZEPHYR_SDK_INSTALL_DIR` environment variables are already set. See :ref:`gs_toolchain_update` for more information. For more information about these environment variables in Zephyr, see :ref:`env_vars_important`. .. _help: Asking for Help ************* You can ask for help on a mailing list or on Discord. Please send bug reports and feature requests to GitHub. * Mailing Lists: users@lists.zephyrproject.org is usually the right list to ask for help. `Search archives and sign up here`_. * Discord: You can join with this `Discord invite`_. * GitHub: Use `GitHub issues`_ for bugs and feature requests. How to Ask ========== .. important:: Please search this documentation and the mailing list archives first. Your question may have an answer there. Don't just say "this isn't working" or ask "is this working?". Include as much detail as you can about: #. What you want to do #. What you tried (commands you typed, etc.) #. What happened (output of each command, etc.) Use Copy/Paste ============== Please copy/paste text instead of taking a picture or a screenshot of it. Text includes source code, terminal commands, and their output. Doing this makes it easier for people to help you, and also helps other users search the archives. Unnecessary screenshots exclude vision impaired developers; some are major Zephyr contributors. `Accessibility`_ has been recognized as a basic human right by the United Nations. When copy/pasting more than 5 lines of computer text into Discord or Github, create a snippet using three backticks to delimit the snippet. .. _Search archives and sign up here: path_to_url .. _Discord invite: path_to_url .. _GitHub issues: path_to_url .. _Accessibility: path_to_url ```	/content/code_sandbox/doc/develop/getting_started/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	3,809
```restructuredtext .. _gcc: GCC static analysis support ########################### Static analysis was introduced in `GCC <path_to_url`__ 10 and it is enabled with the option ``-fanalyzer``. This option performs a much more expensive and thorough analysis of the code than traditional warnings. Run GCC static analysis *********************** To run GCC static analysis, :ref:`west build <west-building>` should be called with a ``-DZEPHYR_SCA_VARIANT=gcc`` parameter, e.g. .. code-block:: shell west build -b qemu_x86 samples/userspace/hello_world_user -- -DZEPHYR_SCA_VARIANT=gcc ```	/content/code_sandbox/doc/develop/sca/gcc.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	142
```restructuredtext .. _sca: Static Code Analysis (SCA) ########################## Support for static code analysis tools in Zephyr is possible through CMake. The build setting :makevar:`ZEPHYR_SCA_VARIANT` can be used to specify the SCA tool to use. :envvar:`ZEPHYR_SCA_VARIANT` is also supported as :ref:`environment variable <env_vars>`. Use ``-DZEPHYR_SCA_VARIANT=<tool>``, for example ``-DZEPHYR_SCA_VARIANT=sparse`` to enable the static analysis tool ``sparse``. .. _sca_infrastructure: SCA Tool infrastructure ********************* Support for an SCA tool is implemented in a file:`sca.cmake` file. The file:`sca.cmake` must be placed under file:`<SCA_ROOT>/cmake/sca/<tool>/sca.cmake`. Zephyr itself is always added as an :makevar:`SCA_ROOT` but the build system offers the possibility to add additional folders to the :makevar:`SCA_ROOT` setting. You can provide support for out of tree SCA tools by creating the following structure: .. code-block:: none <sca_root>/ # Custom SCA root cmake/ sca/ <tool>/ # Name of SCA tool, this is the value given to ZEPHYR_SCA_VARIANT sca.cmake # CMake code that configures the tool to be used with Zephyr To add ``foo`` under ``/path/to/my_tools/cmake/sca`` create the following structure: .. code-block:: none /path/to/my_tools cmake/ sca/ foo/ sca.cmake To use ``foo`` as SCA tool you must then specify ``-DZEPHYR_SCA_VARIANT=foo``. Remember to add ``/path/to/my_tools`` to :makevar:`SCA_ROOT`. :makevar:`SCA_TOOL` can be set as a regular CMake setting using ``-DSCA_ROOT=<sca_root>``, or added by a Zephyr module in its :file:`module.yml` file, see :ref:`Zephyr Modules - Build settings <modules_build_settings>` .. _sca_native_tools: Native SCA Tool support ********************* The following is a list of SCA tools natively supported by Zephyr build system. .. toctree:: :maxdepth: 1 codechecker sparse gcc cpptest ```	/content/code_sandbox/doc/develop/sca/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	553
```restructuredtext .. _cpptest: Parasoft C/C++test support ########################## Parasoft `C/C++test <path_to_url`__ is a software testing and static analysis tool for C and C++. It is a commercial software and you must acquire a commercial license to use it. Documentation of C/C++test can be found at path_to_url Please refer to the documentation for how to use it. Generating Build Data Files ************************* To use C/C++test, ``cpptestscan`` must be found in your :envvar:`PATH` environment variable. And :ref:`west build <west-building>` should be called with a ``-DZEPHYR_SCA_VARIANT=cpptest`` parameter, e.g. .. code-block:: shell west build -b qemu_cortex_m3 zephyr/samples/hello_world -- -DZEPHYR_SCA_VARIANT=cpptest A ``.bdf`` file will be generated as :file:`build/sca/cpptest/cpptestscan.bdf`. Generating a report file ********************** Please refer to Parasoft C/C++test documentation for more details. To import and generate a report file, something like the following should work. .. code-block:: shell cpptestcli -data out -localsettings local.conf -bdf build/sca/cpptest/cpptestscan.bdf -config "builtin://Recommended Rules" -report out/report You might need to set ``bdf.import.c.compiler.exec``, ``bdf.import.cpp.compiler.exec``, and ``bdf.import.linker.exec`` to the toolchain :ref:`west build <west-building>` used. ```	/content/code_sandbox/doc/develop/sca/cpptest.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	352
```restructuredtext .. _codechecker: CodeChecker support ################### `CodeChecker <path_to_url`__ is a static analysis infrastructure. It executes analysis tools available on the build system, such as `Clang-Tidy <path_to_url`__, `Clang Static Analyzer <path_to_url`__ and `Cppcheck <path_to_url`__. Refer to the analyzer's websites for installation instructions. Installing CodeChecker ******************** CodeChecker itself is a python package available on `pypi <path_to_url`__. .. code-block:: shell pip install codechecker Running with CodeChecker ******************** To run CodeChecker, :ref:`west build <west-building>` should be called with a ``-DZEPHYR_SCA_VARIANT=codechecker`` parameter, e.g. .. code-block:: shell west build -b mimxrt1064_evk samples/basic/blinky -- -DZEPHYR_SCA_VARIANT=codechecker Configuring CodeChecker ******************* To configure CodeChecker or analyzers used, arguments can be passed using the ``CODECHECKER_ANALYZE_OPTS`` parameter, e.g. .. code-block:: shell west build -b mimxrt1064_evk samples/basic/blinky -- -DZEPHYR_SCA_VARIANT=codechecker \ -DCODECHECKER_ANALYZE_OPTS="--config;$CODECHECKER_CONFIG_FILE;--timeout;60" Storing CodeChecker results *********************** If a CodeChecker server is active the results can be uploaded and stored for tracking purposes. Storing is done using the optional ``CODECHECKER_STORE=y`` or ``CODECHECKER_STORE_OPTS="arg;list"`` parameters, e.g. .. code-block:: shell west build -b mimxrt1064_evk samples/basic/blinky -- -DZEPHYR_SCA_VARIANT=codechecker \ -DCODECHECKER_STORE_OPTS="--name;build;--url;localhost:8001/Default" .. note:: If ``--name`` isn't passed to either ``CODECHECKER_ANALYZE_OPTS`` or ``CODECHECKER_STORE_OPTS``, the default ``zephyr`` is used. Exporting CodeChecker reports ************************* Optional reports can be generated using the CodeChecker results, when passing a ``-DCODECHECKER_EXPORT=<type>`` parameter. Allowed types are: ``html,json,codeclimate,gerrit,baseline``. Multiple types can be passed as comma-separated arguments. Optional parser configuration arguments can be passed using the ``CODECHECKER_PARSE_OPTS`` parameter, e.g. .. code-block:: shell west build -b mimxrt1064_evk samples/basic/blinky -- -DZEPHYR_SCA_VARIANT=codechecker \ -DCODECHECKER_EXPORT=html,json -DCODECHECKER_PARSE_OPTS="--trim-path-prefix;$PWD" Failing the build on CodeChecker issues ************************************* By default, CodeChecker identified issues will not fail the build, only generate a report. To fail the build if any issues are found (for example, for use in CI), pass the ``CODECHECKER_PARSE_EXIT_STATUS=y`` parameter, e.g. .. code-block:: shell west build -b mimxrt1064_evk samples/basic/blinky -- -DZEPHYR_SCA_VARIANT=codechecker \ -DCODECHECKER_PARSE_EXIT_STATUS=y ```	/content/code_sandbox/doc/develop/sca/codechecker.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	725
```unknown .. _external_module_<name>: <External Module Name> ####################### Introduction ********** Short intro into the module and how it relates to Zephyr. Usage with Zephyr ************* How to use this module with Zephyr. Provide all the details. Reference ******* External references and links. ```	/content/code_sandbox/doc/develop/manifest/external/external.rst.tmpl	unknown	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	67
```restructuredtext :orphan: .. _west_projects_index: West Projects index ################### See :ref:`external-contributions` for more information about this contributing and review process for imported components. Active Projects/Modules +++++++++++++++++++++++ The projects below are enabled by default and will be downloaded when you call `west update`. Many of the projects or modules listed below are essential for building generic Zephyr application and include among others hardware support for many of the platforms available in Zephyr. To disable any of the active modules, for example a specific HAL, use the following commands:: west config manifest.project-filter -- -hal_FOO west update .. manifest-projects-table:: :filter: active Inactive and Optional Projects/Modules ++++++++++++++++++++++++++++++++++++++ The projects below are optional and will not be downloaded when you call `west update`. You can add any of the projects or modules listed below and use them to write application code and extend your workspace with the added functionality. To enable any of the modules below, use the following commands:: west config manifest.project-filter -- +nanopb west update .. manifest-projects-table:: :filter: inactive External Projects/Modules ++++++++++++++++++++++++++ The projects listed below are external and are not directly imported into the default manifest. To use any of the projects below, you will need to define your own manifest file which includes them. See :ref:`west-manifest-import` for information on recommended ways to do this while still inheriting the mandatory modules from Zephyr's :file:`west.yml`. Use the template :file:`doc/develop/manifest/external/external.rst.tmpl` to add external modules to the list below: .. toctree:: :titlesonly: :maxdepth: 1 :glob: external/* ```	/content/code_sandbox/doc/develop/manifest/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	392
```restructuredtext .. _external_module_dummy: Add Your External Module Here ############################# Introduction ********** Short intro into the module and how it relates to Zephyr. Usage with Zephyr ************* How to use this module with Zephyr. Provide all the details. Reference ******* External references and links. ```	/content/code_sandbox/doc/develop/manifest/external/dummy.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	65
```restructuredtext .. _footprint: Optimizing for Footprint ######################## Stack Sizes ********* Stack sizes of various system threads are specified generously to allow for usage in different scenarios on as many supported platforms as possible. You should start the optimization process by reviewing all stack sizes and adjusting them for your application: :kconfig:option:`CONFIG_ISR_STACK_SIZE` Set to 2048 by default :kconfig:option:`CONFIG_MAIN_STACK_SIZE` Set to 1024 by default :kconfig:option:`CONFIG_IDLE_STACK_SIZE` Set to 320 by default :kconfig:option:`CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE` Set to 1024 by default :kconfig:option:`CONFIG_PRIVILEGED_STACK_SIZE` Set to 1024 by default, depends on userspace feature. Unused Peripherals ************** Some peripherals are enabled by default. You can disable unused peripherals in your project configuration, for example:: CONFIG_GPIO=n CONFIG_SPI=n Various Debug/Informational Options ******************************* The following options are enabled by default to provide more information about the running application and to provide means for debugging and error handling: :kconfig:option:`CONFIG_BOOT_BANNER` This option can be disabled to save a few bytes. :kconfig:option:`CONFIG_DEBUG` This option can be disabled for production builds MPU/MMU Support ************* Depending on your application and platform needs, you can disable MPU/MMU support to gain some memory and improve performance. Consider the consequences of this configuration choice though, because you'll lose advanced stack checking and support. ```	/content/code_sandbox/doc/develop/optimizations/footprint.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	337
```restructuredtext .. _optimizations: Optimizations ############## Guides on how to optimize Zephyr for performance, power and footprint. .. toctree:: :maxdepth: 1 footprint.rst tools.rst ```	/content/code_sandbox/doc/develop/optimizations/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	51
```restructuredtext .. _optimization_tools: Optimization Tools ################## The available optimization tools let you analyse :ref:`footprint_tools` and :ref:`data_structure_tools` using different build system targets. .. _footprint_tools: Footprint and Memory Usage ************************** The build system offers 3 targets to view and analyse RAM, ROM and stack usage in generated images. The tools run on the final image and give information about size of symbols and code being used in both RAM and ROM. Additionally, with features available through the compiler, we can also generate worst-case stack usage analysis. Some of the tools mentioned in this section are organizing their output based on the physical organization of the symbols. As some symbols might be external to the project's tree structure, or might lack metadata needed to display them by name, the following top-level containers are used to group such symbols: * Hidden - The RAM and ROM reports list all processing symbols with no matching mapped files in the Hidden category. This means that the file for the listed symbol was not added to the metadata file, was empty, or was undefined. The tool was unable to get the name of the function for the given symbol nor identify where it comes from. * No paths - The RAM and ROM reports list all processing symbols with relative paths in the No paths category. This means that the listed symbols cannot be placed in the tree structure of the report at an absolute path under one specific file. The tool was able to get the name of the function, but it was unable to identify where it comes from. .. note:: You can have multiple cases of the same function, and the No paths category will list the sum of these in one entry. Build Target: ram_report ======================== List all compiled objects and their RAM usage in a tabular form with bytes per symbol and the percentage it uses. The data is grouped based on the file system location of the object in the tree and the file containing the symbol. Use the ``ram_report`` target with your board, as in the following example. .. zephyr-app-commands:: :tool: all :app: samples/hello_world :board: reel_board :goals: ram_report These commands will generate something similar to the output below:: Path Size % Address ======================================================================================== Root 4637 100.00% - (hidden) 4 0.09% - (no paths) 2748 59.26% - _cpus_active 4 0.09% 0x20000314 _kernel 32 0.69% 0x20000318 _sw_isr_table 384 8.28% 0x00006474 cli.1 16 0.35% 0x20000254 on.2 4 0.09% 0x20000264 poll_out_lock.0 4 0.09% 0x200002d4 z_idle_threads 128 2.76% 0x20000120 z_interrupt_stacks 2048 44.17% 0x20000360 z_main_thread 128 2.76% 0x200001a0 WORKSPACE 184 3.97% - modules 184 3.97% - hal 184 3.97% - nordic 184 3.97% - nrfx 184 3.97% - drivers 184 3.97% - src 184 3.97% - nrfx_clock.c 8 0.17% - m_clock_cb 8 0.17% 0x200002e4 nrfx_gpiote.c 132 2.85% - m_cb 132 2.85% 0x20000060 nrfx_ppi.c 4 0.09% - m_channels_allocated 4 0.09% 0x200000e4 nrfx_twim.c 40 0.86% - m_cb 40 0.86% 0x200002ec ZEPHYR_BASE 1701 36.68% - arch 5 0.11% - arm 5 0.11% - core 5 0.11% - mpu 1 0.02% - arm_mpu.c 1 0.02% - static_regions_num 1 0.02% 0x20000348 tls.c 4 0.09% - z_arm_tls_ptr 4 0.09% 0x20000240 drivers 258 5.56% - ... ... ...% ======================================================================================== 4637 Build Target: rom_report ======================== List all compiled objects and their ROM usage in a tabular form with bytes per symbol and the percentage it uses. The data is grouped based on the file system location of the object in the tree and the file containing the symbol. Use the ``rom_report`` target with your board, as in the following example. .. zephyr-app-commands:: :tool: all :app: samples/hello_world :board: reel_board :goals: rom_report These commands will generate something similar to the output below:: Path Size % Address ======================================================================================== Root 27828 100.00% - ... ... ...% ZEPHYR_BASE 13558 48.72% - arch 1766 6.35% - arm 1766 6.35% - core 1766 6.35% - cortex_m 1020 3.67% - fault.c 620 2.23% - bus_fault.constprop.0 108 0.39% 0x00000749 mem_manage_fault.constprop.0 120 0.43% 0x000007b5 usage_fault.constprop.0 84 0.30% 0x000006f5 z_arm_fault 292 1.05% 0x0000082d z_arm_fault_init 16 0.06% 0x00000951 ... ... ...% boards 32 0.11% - arm 32 0.11% - reel_board 32 0.11% - board.c 32 0.11% - __init_board_reel_board_init 8 0.03% 0x000063e4 board_reel_board_init 24 0.09% 0x00000ed5 build 194 0.70% - zephyr 194 0.70% - isr_tables.c 192 0.69% - _irq_vector_table 192 0.69% 0x00000040 misc 2 0.01% - generated 2 0.01% - configs.c 2 0.01% - _ConfigAbsSyms 2 0.01% 0x00005945 drivers 6282 22.57% - ... ... ...% ======================================================================================== 21652 Build Target: puncover ====================== This target uses a third-party tool called puncover which can be found at path_to_url When this target is built, it will launch a local web server which will allow you to open a web client and browse the files and view their ROM, RAM, and stack usage. Before you can use this target, install the puncover Python module:: pip3 install git+path_to_url --user .. warning:: This is a third-party tool that might or might not be working at any given time. Please check the GitHub issues, and report new problems to the project maintainer. After you installed the Python module, use ``puncover`` target with your board, as in the following example. .. zephyr-app-commands:: :tool: all :app: samples/hello_world :board: reel_board :goals: puncover To view worst-case stack usage analysis, build this with the :kconfig:option:`CONFIG_STACK_USAGE` enabled. .. zephyr-app-commands:: :tool: all :app: samples/hello_world :board: reel_board :goals: puncover :gen-args: -DCONFIG_STACK_USAGE=y .. _data_structure_tools: Data Structures **************** Build Target: pahole ===================== Poke-a-hole (pahole) is an object-file analysis tool to find the size of the data structures, and the holes caused due to aligning the data elements to the word-size of the CPU by the compiler. Poke-a-hole (pahole) must be installed prior to using this target. It can be obtained from path_to_url and is available in the dwarves package in both fedora and ubuntu:: sudo apt-get install dwarves Alternatively, you can get it from fedora:: sudo dnf install dwarves After you installed the package, use ``pahole`` target with your board, as in the following example. .. zephyr-app-commands:: :tool: all :app: samples/hello_world :board: reel_board :goals: pahole Pahole will generate something similar to the output below in the console:: /* Used at: [...]/build/zephyr/kobject_hash.c / / <375> [...]/zephyr/include/zephyr/sys/dlist.h:37 / union { struct _dnode head; /* 0 4 / struct _dnode next; /* 0 4 / }; / Used at: [...]/build/zephyr/kobject_hash.c / / <397> [...]/zephyr/include/zephyr/sys/dlist.h:36 / struct _dnode { union { struct _dnode head; /* 0 4 / struct _dnode next; /* 0 4 / }; / 0 4 / union { struct _dnode tail; /* 4 4 / struct _dnode prev; /* 4 4 / }; / 4 4 / / size: 8, cachelines: 1, members: 2 / / last cacheline: 8 bytes / }; / Used at: [...]/build/zephyr/kobject_hash.c / / <3b7> [...]/zephyr/include/zephyr/sys/dlist.h:41 / union { struct _dnode tail; /* 0 4 / struct _dnode prev; /* 0 4 */ }; ... ... ```	/content/code_sandbox/doc/develop/optimizations/tools.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	2,615
```restructuredtext .. _develop_debug: Debugging ######### .. _application_debugging: Application Debugging ********************* This section is a quick hands-on reference to start debugging your application with QEMU. Most content in this section is already covered in `QEMU`_ and `GNU_Debugger`_ reference manuals. .. _QEMU: path_to_url .. _GNU_Debugger: path_to_url In this quick reference, you'll find shortcuts, specific environmental variables, and parameters that can help you to quickly set up your debugging environment. The simplest way to debug an application running in QEMU is using the GNU Debugger and setting a local GDB server in your development system through QEMU. You will need an :abbr:`ELF (Executable and Linkable Format)` binary image for debugging purposes. The build system generates the image in the build directory. By default, the kernel binary name is :file:`zephyr.elf`. The name can be changed using :kconfig:option:`CONFIG_KERNEL_BIN_NAME`. GDB server ========== We will use the standard 1234 TCP port to open a :abbr:`GDB (GNU Debugger)` server instance. This port number can be changed for a port that best suits the development environment. There are multiple ways to do this. Each way starts a QEMU instance with the processor halted at startup and with a GDB server instance listening for a connection. Running QEMU directly ~~~~~~~~~~~~~~~~~~~~~ You can run QEMU to listen for a "gdb connection" before it starts executing any code to debug it. .. code-block:: bash qemu -s -S <image> will setup Qemu to listen on port 1234 and wait for a GDB connection to it. The options used above have the following meaning: * ``-S`` Do not start CPU at startup; rather, you must type 'c' in the monitor. * ``-s`` Shorthand for :literal:`-gdb tcp::1234`: open a GDB server on TCP port 1234. Running QEMU via :command:`ninja` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Run the following inside the build directory of an application: .. code-block:: console ninja debugserver QEMU will write the console output to the path specified in :makevar:`${QEMU_PIPE}` via CMake, typically :file:`qemu-fifo` within the build directory. You may monitor this file during the run with :command:`tail -f qemu-fifo`. Running QEMU via :command:`west` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Run the following from your project root: .. code-block:: console west build -t debugserver_qemu QEMU will write the console output to the terminal from which you invoked :command:`west`. Configuring the :command:`gdbserver` listening device ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Kconfig option :kconfig:option:`CONFIG_QEMU_GDBSERVER_LISTEN_DEV` controls the listening device, which can be a TCP port number or a path to a character device. GDB releases 9.0 and newer also support Unix domain sockets. If the option is unset, then the QEMU invocation will lack a ``-s`` or a ``-gdb`` parameter. You can then use the :envvar:`QEMU_EXTRA_FLAGS` shell environment variable to pass in your own listen device configuration. GDB client ========== Connect to the server by running :command:`gdb` and giving these commands: .. code-block:: bash $ path/to/gdb path/to/zephyr.elf (gdb) target remote localhost:1234 (gdb) dir ZEPHYR_BASE .. note:: Substitute the correct :ref:`ZEPHYR_BASE <important-build-vars>` for your system. You can use a local GDB configuration :file:`.gdbinit` to initialize your GDB instance on every run. Your home directory is a typical location for :file:`.gdbinit`, but you can configure GDB to load from other locations, including the directory from which you invoked :command:`gdb`. This example file performs the same configuration as above: .. code-block:: none target remote localhost:1234 dir ZEPHYR_BASE Alternate interfaces ~~~~~~~~~~~~~~~~~~~~ GDB provides a curses-based interface that runs in the terminal. Pass the ``--tui`` option when invoking :command:`gdb` or give the ``tui enable`` command within :command:`gdb`. .. note:: The GDB version on your development system might not support the ``--tui`` option. Please make sure you use the GDB binary from the SDK which corresponds to the toolchain that has been used to build the binary. Finally, the command below connects to the GDB server using the :abbr:`DDD (Data Display Debugger)`, a graphical frontend for GDB. The following command loads the symbol table from the ELF binary file, in this instance, :file:`zephyr.elf`. .. code-block:: bash ddd --gdb --debugger "gdb zephyr.elf" Both commands execute :command:`gdb`. The command name might change depending on the toolchain you are using and your cross-development tools. :command:`ddd` may not be installed in your development system by default. Follow your system instructions to install it. For example, use :command:`sudo apt-get install ddd` on an Ubuntu system. Debugging ========= As configured above, when you connect the GDB client, the application will be stopped at system startup. You may set breakpoints, step through code, etc. as when running the application directly within :command:`gdb`. .. note:: :command:`gdb` will not print the system console output as the application runs, unlike when you run a native application in GDB directly. If you just :command:`continue` after connecting the client, the application will run, but nothing will appear to happen. Check the console output as described above. Debug with Eclipse **************** Overview ======== CMake supports generating a project description file that can be imported into the Eclipse Integrated Development Environment (IDE) and used for graphical debugging. The `GNU MCU Eclipse plug-ins`_ provide a mechanism to debug ARM projects in Eclipse with pyOCD, Segger J-Link, and OpenOCD debugging tools. The following tutorial demonstrates how to debug a Zephyr application in Eclipse with pyOCD in Windows. It assumes you have already installed the GCC ARM Embedded toolchain and pyOCD. Set Up the Eclipse Development Environment ========================================== #. Download and install `Eclipse IDE for C/C++ Developers`_. #. In Eclipse, install the `GNU MCU Eclipse plug-ins`_ by opening the menu ``Window->Eclipse Marketplace...``, searching for ``GNU MCU Eclipse``, and clicking ``Install`` on the matching result. #. Configure the path to the pyOCD GDB server by opening the menu ``Window->Preferences``, navigating to ``MCU``, and setting the ``Global pyOCD Path``. Generate and Import an Eclipse Project ====================================== #. Set up a GNU Arm Embedded toolchain as described in :ref:`toolchain_gnuarmemb`. #. Navigate to a folder outside of the Zephyr tree to build your application. .. code-block:: console # On Windows cd %userprofile% .. note:: If the build directory is a subdirectory of the source directory, as is usually done in Zephyr, CMake will warn: "The build directory is a subdirectory of the source directory. This is not supported well by Eclipse. It is strongly recommended to use a build directory which is a sibling of the source directory." #. Configure your application with CMake and build it with ninja. Note the different CMake generator specified by the ``-G"Eclipse CDT4 - Ninja"`` argument. This will generate an Eclipse project description file, :file:`.project`, in addition to the usual ninja build files. .. zephyr-app-commands:: :tool: all :app: %ZEPHYR_BASE%\samples\synchronization :host-os: win :board: frdm_k64f :gen-args: -G"Eclipse CDT4 - Ninja" :goals: build :compact: #. In Eclipse, import your generated project by opening the menu ``File->Import...`` and selecting the option ``Existing Projects into Workspace``. Browse to your application build directory in the choice, ``Select root directory:``. Check the box for your project in the list of projects found and click the ``Finish`` button. Create a Debugger Configuration =============================== #. Open the menu ``Run->Debug Configurations...``. #. Select ``GDB PyOCD Debugging``, click the ``New`` button, and configure the following options: - In the Main tab: - Project: ``my_zephyr_app@build`` - C/C++ Application: :file:`zephyr/zephyr.elf` - In the Debugger tab: - pyOCD Setup - Executable path: :file:`${pyocd_path}\\${pyocd_executable}` - Uncheck "Allocate console for semihosting" - Board Setup - Bus speed: 8000000 Hz - Uncheck "Enable semihosting" - GDB Client Setup - Executable path example (use your ``GNUARMEMB_TOOLCHAIN_PATH``): :file:`C:\\gcc-arm-none-eabi-6_2017-q2-update\\bin\\arm-none-eabi-gdb.exe` - In the SVD Path tab: - File path: :file:`<workspace top>\\modules\\hal\\nxp\\mcux\\devices\\MK64F12\\MK64F12.xml` .. note:: This is optional. It provides the SoC's memory-mapped register addresses and bitfields to the debugger. #. Click the ``Debug`` button to start debugging. RTOS Awareness ============== Support for Zephyr RTOS awareness is implemented in `pyOCD v0.11.0`_ and later. It is compatible with GDB PyOCD Debugging in Eclipse, but you must enable CONFIG_DEBUG_THREAD_INFO=y in your application. Debugging I2C communication ************************* There is a possibility to log all or some of the I2C transactions done by the application. This feature is enabled by the Kconfig option :kconfig:option:`CONFIG_I2C_DUMP_MESSAGES`, but it uses the ``LOG_DBG`` function to print the contents so the :kconfig:option:`CONFIG_I2C_LOG_LEVEL_DBG` option must also be enabled. The sample output of the dump looks like this:: D: I2C msg: io_i2c_ctrl7_port0, addr=50 D: W len=01: 00 D: R Sr P len=08: D: contents: D: 43 42 41 00 00 00 00 00 \|CBA..... The first line indicates the I2C controller and the target address of the transaction. In above example, the I2C controller is named ``io_i2c_ctrl7_port0`` and the target device address is ``0x50`` .. note:: the address, length and contents values are in hexadecimal, but lack the ``0x`` prefix Next lines contain messages, both sent and received. The contents of write messages is always shown, while the content of read messages is controlled by a parameter to the function ``i2c_dump_msgs_rw``. This function is available for use by user, but is also called internally by ``i2c_transfer`` API function with read content dump enabled. Before the length parameter, the header of the message is printed using abbreviations: - W - write message - R - read message - Sr - restart bit - P - stop bit The above example shows one write message with byte ``0x00`` representing the address of register to read from the I2C target. After that the log shows the length of received message and following that, the bytes read from the target ``43 42 41 00 00 00 00 00``. The content dump consist of both the hex and ASCII representation. Filtering the I2C communication dump ==================================== By default, all I2C communication is logged between all I2C controllers and I2C targets. It may litter the log with unrelated devices and make it difficult to effectively debug the communication with a device of interest. Enable the Kconfig option :kconfig:option:`CONFIG_I2C_DUMP_MESSAGES_ALLOWLIST` to create an allowlist of I2C targets to log. The allowlist of devices is configured using the devicetree, for example:: / { i2c { display0: some-display@a { ... }; sensor3: some-sensor@b { ... }; }; i2c-dump-allowlist { compatible = "zephyr,i2c-dump-allowlist"; devices = < &display0 >, < &sensor3 >; }; }; The filters nodes are identified by the compatible string with ``zephyr,i2c-dump-allowlist`` value. The devices are selected using the ``devices`` property with phandles to the devices on the I2C bus. In the above example, the communication with device ``display0`` and ``sensor3`` will be displayed in the log. .. _Eclipse IDE for C/C++ Developers: path_to_url .. _GNU MCU Eclipse plug-ins: path_to_url .. _pyOCD v0.11.0: path_to_url ```	/content/code_sandbox/doc/develop/debug/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	3,004
```restructuredtext .. _toolchain_armclang: Arm Compiler 6 ############## #. Download and install a development suite containing the `Arm Compiler 6`_ for your operating system. #. :ref:`Set these environment variables <env_vars>`: - Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``armclang``. - Set :envvar:`ARMCLANG_TOOLCHAIN_PATH` to the toolchain installation directory. #. The Arm Compiler 6 needs the :envvar:`ARMLMD_LICENSE_FILE` environment variable to point to your license file or server. For example: .. code-block:: bash # Linux, macOS, license file: export ARMLMD_LICENSE_FILE=/<path>/license_armds.dat # Linux, macOS, license server: export ARMLMD_LICENSE_FILE=8224@myserver .. code-block:: batch # Windows, license file: set ARMLMD_LICENSE_FILE=c:\<path>\license_armds.dat # Windows, license server: set ARMLMD_LICENSE_FILE=8224@myserver #. If the Arm Compiler 6 was installed as part of an Arm Development Studio, then you must set the :envvar:`ARM_PRODUCT_DEF` to point to the product definition file: See also: `Product and toolkit configuration <path_to_url`_. For example if the Arm Development Studio is installed in: ``/opt/armds-2020-1`` with a Gold license, then set :envvar:`ARM_PRODUCT_DEF` to point to ``/opt/armds-2020-1/gold.elmap``. .. note:: The Arm Compiler 6 uses ``armlink`` for linking. This is incompatible with Zephyr's linker script template, which works with GNU ld. Zephyr's Arm Compiler 6 support Zephyr's CMake linker script generator, which supports generating scatter files. Basic scatter file support is in place, but there are still areas covered in ld templates which are not fully supported by the CMake linker script generator. Some Zephyr subsystems or modules may also contain C or assembly code that relies on GNU intrinsics and have not yet been updated to work fully with ``armclang``. .. _Arm Compiler 6: path_to_url ```	/content/code_sandbox/doc/develop/toolchains/arm_compiler.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	504
```restructuredtext .. _toolchain_gnuarmemb: GNU Arm Embedded ################ #. Download and install a `GNU Arm Embedded`_ build for your operating system and extract it on your file system. .. note:: On Windows, we'll assume for this guide that you install into the directory :file:`C:\\gnu_arm_embedded`. You can also choose the default installation path used by the ARM GCC installer, in which case you will need to adjust the path accordingly in the guide below. .. warning:: On macOS Catalina or later you might need to :ref:`change a security policy <mac-gatekeeper>` for the toolchain to be able to run from the terminal. #. :ref:`Set these environment variables <env_vars>`: - Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``gnuarmemb``. - Set :envvar:`GNUARMEMB_TOOLCHAIN_PATH` to the toolchain installation directory. #. To check that you have set these variables correctly in your current environment, follow these example shell sessions (the :envvar:`GNUARMEMB_TOOLCHAIN_PATH` values may be different on your system): .. code-block:: console # Linux, macOS: $ echo $ZEPHYR_TOOLCHAIN_VARIANT gnuarmemb $ echo $GNUARMEMB_TOOLCHAIN_PATH /home/you/Downloads/gnu_arm_embedded # Windows: > echo %ZEPHYR_TOOLCHAIN_VARIANT% gnuarmemb > echo %GNUARMEMB_TOOLCHAIN_PATH% C:\gnu_arm_embedded .. warning:: On macOS, if you are having trouble with the suggested procedure, there is an unofficial package on brew that might help you. Run ``brew install gcc-arm-embedded`` and configure the variables - Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``gnuarmemb``. - Set :envvar:`GNUARMEMB_TOOLCHAIN_PATH` to the brew installation directory (something like ``/usr/local``) .. _GNU Arm Embedded: path_to_url ```	/content/code_sandbox/doc/develop/toolchains/gnu_arm_embedded.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	467
```restructuredtext .. _custom_cmake_toolchains: Custom CMake Toolchains ####################### To use a custom toolchain defined in an external CMake file, :ref:`set these environment variables <env_vars>`: - Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to your toolchain's name - Set ``TOOLCHAIN_ROOT`` to the path to the directory containing your toolchain's CMake configuration files. Zephyr will then include the toolchain cmake files located in the :file:`TOOLCHAIN_ROOT` directory: - :file:`cmake/toolchain/<toolchain name>/generic.cmake`: configures the toolchain for "generic" use, which mostly means running the C preprocessor on the generated :ref:`devicetree` file. - :file:`cmake/toolchain/<toolchain name>/target.cmake`: configures the toolchain for "target" use, i.e. building Zephyr and your application's source code. Here <toolchain name> is the same as the name provided in :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` See the zephyr files :zephyr_file:`cmake/modules/FindHostTools.cmake` and :zephyr_file:`cmake/modules/FindTargetTools.cmake` for more details on what your :file:`generic.cmake` and :file:`target.cmake` files should contain. You can also set ``ZEPHYR_TOOLCHAIN_VARIANT`` and ``TOOLCHAIN_ROOT`` as CMake variables when generating a build system for a Zephyr application, like so: .. code-block:: console west build ... -- -DZEPHYR_TOOLCHAIN_VARIANT=... -DTOOLCHAIN_ROOT=... .. code-block:: console cmake -DZEPHYR_TOOLCHAIN_VARIANT=... -DTOOLCHAIN_ROOT=... If you do this, ``-C <initial-cache>`` `cmake option`_ may useful. If you save your :makevar:`ZEPHYR_TOOLCHAIN_VARIANT`, :makevar:`TOOLCHAIN_ROOT`, and other settings in a file named :file:`my-toolchain.cmake`, you can then invoke cmake as ``cmake -C my-toolchain.cmake ...`` to save typing. Zephyr includes :file:`include/toolchain.h` which again includes a toolchain specific header based on the compiler identifier, such as ``__llvm__`` or ``__GNUC__``. Some custom compilers identify themselves as the compiler on which they are based, for example ``llvm`` which then gets the :file:`toolchain/llvm.h` included. This included file may though not be right for the custom toolchain. In order to solve this, and thus to get the :file:`include/other.h` included instead, add the set(TOOLCHAIN_USE_CUSTOM 1) cmake line to the generic.cmake and/or target.cmake files located under :file:`<TOOLCHAIN_ROOT>/cmake/toolchain/<toolchain name>/`. When :makevar:`TOOLCHAIN_USE_CUSTOM` is set, the :file:`other.h` must be available out-of-tree and it must include the correct header for the custom toolchain. A good location for the :file:`other.h` header file, would be a directory under the directory specified in ``TOOLCHAIN_ROOT`` as :file:`include/toolchain`. To get the toolchain header included in zephyr's build, the :makevar:`USERINCLUDE` can be set to point to the include directory, as shown here: .. code-block:: console west build -- -DZEPHYR_TOOLCHAIN_VARIANT=... -DTOOLCHAIN_ROOT=... -DUSERINCLUDE=... .. _cmake option: path_to_url#options ```	/content/code_sandbox/doc/develop/toolchains/custom_cmake.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	829
```restructuredtext .. _toolchain_intel_oneapi_toolkit: Intel oneAPI Toolkit #################### #. Download `Intel oneAPI Base Toolkit <path_to_url`_ #. Assuming the toolkit is installed in ``/opt/intel/oneApi``, set environment using:: # Linux, macOS: export ONEAPI_TOOLCHAIN_PATH=/opt/intel/oneapi source $ONEAPI_TOOLCHAIN_PATH/compiler/latest/env/vars.sh # Windows: > set ONEAPI_TOOLCHAIN_PATH=C:\Users\Intel\oneapi To setup the complete oneApi environment, use:: source /opt/intel/oneapi/setvars.sh The above will also change the python environment to the one used by the toolchain and might conflict with what Zephyr uses. #. Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``oneApi``. ```	/content/code_sandbox/doc/develop/toolchains/intel_oneapi_toolkit.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	190
```restructuredtext .. _toolchains: Toolchains ########## Guides on how to set up toolchains for Zephyr development. .. toctree:: :maxdepth: 1 zephyr_sdk.rst arm_compiler.rst cadence_xcc.rst designware_arc_mwdt.rst gnu_arm_embedded.rst intel_oneapi_toolkit.rst crosstool_ng.rst host.rst other_x_compilers.rst custom_cmake.rst ```	/content/code_sandbox/doc/develop/toolchains/index.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	118
```restructuredtext .. _host_toolchains: Host Toolchains ############### In some specific configurations, like when building for non-MCU x86 targets on a Linux host, you may be able to reuse the native development tools provided by your operating system. To use your host gcc, set the :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` :ref:`environment variable <env_vars>` to ``host``. To use clang, set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``llvm``. ```	/content/code_sandbox/doc/develop/toolchains/host.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	110
```restructuredtext .. _toolchain_cadence_xcc: Cadence Tensilica Xtensa C/C++ Compiler (XCC) ############################################# #. Obtain Tensilica Software Development Toolkit targeting the specific SoC on hand. This usually contains two parts: * The Xtensa Xplorer which contains the necessary executables and libraries. * A SoC-specific add-on to be installed on top of Xtensa Xplorer. * This add-on allows the compiler to generate code for the SoC on hand. #. Install Xtensa Xplorer and then the SoC add-on. * Follow the instruction from Cadence on how to install the SDK. * Depending on the SDK, there are two set of compilers: * GCC-based compiler: ``xt-xcc`` and its friends. * Clang-based compiler: ``xt-clang`` and its friends. #. Make sure you have obtained a license to use the SDK, or has access to a remote licensing server. #. :ref:`Set these environment variables <env_vars>`: * Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``xcc`` or ``xt-clang``. * Set :envvar:`XTENSA_TOOLCHAIN_PATH` to the toolchain installation directory. * Set :envvar:`XTENSA_CORE` to the SoC ID where application is being targeting. * Set :envvar:`TOOLCHAIN_VER` to the Xtensa SDK version. #. For example, assuming the SDK is installed in ``/opt/xtensa``, and using the SDK for application development on ``intel_adsp_cavs15``, setup the environment using: .. code-block:: console # Linux export ZEPHYR_TOOLCHAIN_VARIANT=xcc export XTENSA_TOOLCHAIN_PATH=/opt/xtensa/XtDevTools/install/tools/ export XTENSA_CORE=X6H3SUE_RI_2018_0 export TOOLCHAIN_VER=RI-2018.0-linux #. To use Clang-based compiler: * Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``xt-clang``. * Note that the Clang-based compiler may contain an old LLVM bug which results in the following error: .. code-block:: console /tmp/file.s: Assembler messages: /tmp/file.s:20: Error: file number 1 already allocated clang-3.9: error: Xtensa-as command failed with exit code 1 If this happens, set :envvar:`XCC_NO_G_FLAG` to ``1``. * For example: .. code-block:: console # Linux export XCC_NO_G_FLAG=1 ```	/content/code_sandbox/doc/develop/toolchains/cadence_xcc.rst	restructuredtext	2016-05-26T17:54:19	2024-08-16T18:09:06	zephyr	zephyrproject-rtos/zephyr	10,307	591

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.