Bridle 4.0.0 Release Notes

This project demonstrate the integration of TiaC Systems support in open source projects, like the Zephyr RTOS, with libraries and source code for applications. It is not yet intended or supported by TiaC Systems for product development.

Highlights

  • Bridle is now in sync and align to the latest Zephyr upstream V4 landscape.

  • Simplify Zephyr SDK location.

Note

See the changelog and readme files in the component repositories for a detailed description of changes.

Repositories

For more details, see: Repositories and revisions.

Component

Group : Imports

Branch

Tag

tiac-bridle

v4.0-branch

v4.0.0
tiac-ubxlib
(u-blox-ubxlib)
geographiclib
62c0021cbf079b43cdd9a219e9b10b49ea616e19
(master)
tiac-zephyr
(zephyr-core)
acpica
liblc3
loramac-node
lvgl
mcuboot
open-amp
openthread
picolibc
hal : cmsis
hal : hal_adi
hal : hal_altera
hal : hal_ambiq
hal : hal_atmel
hal : hal_espressif
hal : hal_ethos_u
hal : hal_gigadevice
hal : hal_infineon
hal : hal_intel
hal : hal_microchip
hal : hal_nordic
hal : hal_nuvoton
hal : hal_nxp
hal : hal_openisa
hal : hal_quicklogic
hal : hal_renesas
hal : hal_rpi_pico
hal : hal_silabs
hal : hal_st
hal : hal_stm32
hal : hal_telink
hal : hal_ti
hal : hal_wurthelektronik
hal : hal_xtensa
hal : libmetal
fs : fatfs
fs : littlefs
tee : trusted-firmware-a
tee : trusted-firmware-m
crypto : mbedtls
crypto : tinycrypt
debug : mipi-sys-t
debug : segger
tools : edtt
tools : net-tools
optional : canopennode
optional : chre
optional : psa-arch-tests
optional : tf-m-tests
tiacsys/v4.0-branch
(v4.0-branch)

v4.0.0

Supported boards

  • Arduino/Genuino Zero

  • PicoBoy Mini-Handheld

  • Cytron Maker Nano RP2040

  • Cytron Maker Pi RP2040

  • NXP MIMXRT1010-EVK

  • NXP MIMXRT1060-EVK

  • NXP MIMXRT1170-EVK/EVKB (CM7)

  • Nordic nRF52840 DK

  • Nordic nRF9160 DK

  • Raspberry Pi Pico and Pico W

  • Seeeduino Cortex-M0+

  • Seeeduino Lotus Cortex-M0+

  • ST Nucleo F2xxxx

  • ST Nucleo F3xxxx / L4xxxx

  • ST Nucleo F4xxxx

  • ST Nucleo F6xxxx

  • ST Nucleo F7xxxx

  • TiaC Magpie F777NI (former TiaC Magpie STM32F777NIHx)

  • Waveshare RP2040 (series of mini and pico sized boards)

  • XIAO SAMD21 (former Seeed Studio XIAO SAMD21), also known as Seeeduino XIAO

Supported shields

  • Seeed Studio Grove Interconnect Shields

  • Grove Button Shields

  • Grove LED Shields

  • Grove Sensor Shields

  • Raspberry Pi Pico Clock Shields

  • Raspberry Pi Pico LCD Shields

  • Raspberry Pi Pico LED Shields

  • Raspberry Pi Pico TEST Shields

  • Waveshare LCD Modules

  • Waveshare Pico 10-DOF IMU Sensor

  • Waveshare Pico Environment Sensor

  • SC16IS75x Breakout Boards

  • NXP SC18IS604-EVB

  • TiaC SC18IS604 Arduino

Supported snippets

  • USB Console Snippet (usb-console)

  • PWM Servomotor Preset Snippet (pwm-servo)

  • Delete Default Devicetree Aliases Snippet (del-default-aliases)

  • BME280 Sensor Sample Tweaks (samples-sensor-bme280-tweaks)

  • CAN timing adjustments (can-timing-adj)

  • Watchdog timing adjustments (wdt-timing-adj)

  • Build all Display drivers test adjustments (tstdrv-bldall-display-adj)

  • Build all GPIO drivers test adjustments (tstdrv-bldall-gpio-adj)

  • Build all I2C drivers test adjustments (tstdrv-bldall-i2c-adj)

  • Build all MFD drivers test adjustments (tstdrv-bldall-mfd-adj)

  • Build all RTC drivers test adjustments (tstdrv-bldall-rtc-adj)

  • Build all Sensor drivers test adjustments (tstdrv-bldall-sensor-adj)

  • Build all UART drivers test adjustments (tstdrv-bldall-uart-adj)

Change log

  • Simplify Zephyr SDK location.

  • Rename DTS bindings:

  • Rename drivers:

  • Add more shields:

    • Grove Button Shields:

      • Grove Dual Button V1.0 (Sep 2019) by Seeed Studio

      • Grove LED Button V1.0 (Jun 2018) by Seeed Studio

    • Grove LED Shields:

      • Grove LED Button V1.0 (Jun 2018) by Seeed Studio

The following sections provide detailed lists of changes by component.

Build Infrastructure

Take over the new build principles from Zephyr:

  • Bridle now fully relies on the find_package CMake script provided by Zephyr to locate at least the required or a valid Zephyr SDK version.

  • ci: github: qa-integration: Use Zephyr CI container v0.27.4 and Zephyr SDK v0.17.0 which is now required.

  • ci: github: qa-integration: The self-hosted GitHub action runner for executing the integration tests on targets (HiL) requires an explicitly activated virtual Python 3.12 environment for the time being. The machine used as HiL gateway (RPi4) has an Ubuntu 20.04 LTS system installation with the Python 3.12 packages from the Deadsnake PPA. Python 3.12 is now required.

  • ci: github: qa-integration: In the hardware map file, the name of the board was renamed from magpie_f777ni to the fully qualified HWMv2 name magpie_f777ni/stm32f777xx. Also a more meaningful product name and name for the unique serial console device file was set.

  • The SoC stm32f777xx of the stm32/stm32f7 family/series is now an independent Kconfig symbol and no longer falls back to the mostly compatible SoC stm32f767xx of this family/series. The number of interrupts CONFIG_NUM_IRQS and the FPU type CONFIG_CPU_HAS_FPU_DOUBLE_PRECISION have been adopted one-to-one from the stm32f767xx SoC. At CMake level, the start and initialization code from Zephyr upstream is completely reused, but can also be extended if necessary. A notice is issued at build time.

  • Copy and own the always removed Sphinx extension zephyr.warnings_filter as bridle.warnings_filter. Since Bridle have to rebuild different documentation sets by a split strategy (apartly the document inventory first and then the other documents at all that dependent to other inventories), Bridle have to expect and tolerate warnings of unknown or invalid references to “other” inter-Sphinx documents. In the past it was a good practice to filter out such expected warnings explicitly by the warnings_filter.

Documentation

  1. Upgrade to Sphinx v8.1 and thus adapt the TSN theme to be compatible to the new underlayed RDT theme v3.0.

  2. Present the Sphinx copy button on all literal parsed and code blocks.

  3. Revise all inter-Sphinx links and apply the valid official syntax, a very big move forward to be compatible for the future.

  4. Update all output messages in documentation to be in sync with the upcoming Bridle version v4.0.0, based on Zephyr v4.0 (samples and tests).