Bridle 3.7.0 Release Notes (Working draft)

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

  • NOT YET, tbd.

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

v3.7-branch

v3.7.0
tiac-ubxlib
(u-blox-ubxlib)
geographiclib
tiacsys/main
(main)
tiac-zephyr
(zephyr-core)
acpica
liblc3
loramac-node
lvgl
mcuboot
open-amp
openthread
picolibc
hal : cmsis
hal : hal_altera
hal : hal_ambiq
hal : hal_atmel
hal : hal_espressif
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_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/v3.7-branch
(v3.7-branch)

v3.7.0

Supported boards

NOT YET, tbd.

  • Arduino/Genuino Zero

  • PicoBoy Mini-Handheld

  • Cytron Maker Nano RP2040

  • Cytron Maker Pi RP2040

  • NXP MIMXRT1010-EVK

  • NXP MIMXRT1060-EVK

  • Raspberry Pi Pico and Pico W

  • Seeeduino Cortex-M0+

  • Seeeduino Lotus Cortex-M0+

  • ST Nucleo F2xxxx

  • ST Nucleo F3xxxx / L4xxxx

  • ST Nucleo F6xxxx

  • 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

NOT YET, tbd.

  • Seeed Studio Grove Interconnect Shields

  • Grove Button Shields

  • Grove LED 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

Supported snippets

NOT YET, tbd.

  • USB Console Snippet (usb-console)

  • PWM Servomotor Preset Snippet (pwm-servo)

  • CAN timing adjustments (can-timing-adj)

  • Watchdog timing adjustments (wdt-timing-adj)

Change log

NOT YET, tbd.

  • tbd.

  • tbd.

  • tbd.

  • Allow users to still specify any old board name, and let Bridel together with the Zephyr build system (board validation) to select the new board name.

  • Rename board tiac_magpie to magpie_f777ni and mark the old name as deprecated.

  • Adapt new identifier from Hardware Model v2 for snippets, tests and samples.

The following sections provide detailed lists of changes by component.

Build Infrastructure

Take over the new build principles from Zephyr:

NOT YET, tbd.

  • tbd.

  • tbd.

  • tbd.

  • Use the new upstream MIPI DBI driver class for all ST7735R based displays.

  • Use the new upstream MIPI DBI driver class for all ST7789V based displays.

  • Convert all Bridle boards and SoCs to the new Hardware Model v2.

  • Hook up board.cmake in Bridle’s board extension folder.

  • Hook up Kconfig.defconfig in Bridle’s board extension folder.

  • With the new Kconfig.defconfig hookup in the Bridle board extension folder, all static configurations can be removed and Kconfig can work more sensitively, e.g. only influence the log level in the USB subsystem if the USB stack is really activated.

  • Add the Ambiq Micro HAL to support the new Apollo 4 SoC in Zephyr upstream with Bridle’s common test suite bridle/tests/bridle/common.

  • Add the Intel HAL and the ACPI Component Architecture library to support Bridle’s common test suite bridle/tests/bridle/common also for most of the Intel boards found in Zephyr upstream.

  • Adoption of patch and compliance checks from Zephyr upstream for the new Hardware Model v2 with slight adjustments for Bridle:

    • BRIDLE_BASE as an additional magic string <bridle-base>

    • Bridle with additional external module handling (MODULE_EXT_ROOT)

    • use Bridle’s checkpatch.pl and .checkpatch.conf

    • use Bridle’s spelling.txt and typedefsfile

    • use Bridle’s .gitlint

    • use Bridle’s .yamllint

Documentation

NOT YET, tbd.

  1. Export ZEPHYR_BASE as environment variable to make the Sphinx extension autodoc for the pytest-twister-harness happy.

  2. Update all output messages in documentation to be in sync with the upcoming Bridle version v3.7.0, based on Zephyr v3.7 (samples and tests).