Board support
The Bridle provides board definitions for all TiaC Systems devices. In addition, you can define custom boards.
Board names
The following tables list all boards and build targets for TiaC Systems hardware platforms.
Boards included in tiac-zephyr
The following boards are defined in the zephyr/boards/ folder.
Also see the Supported Boards and Shields section in the Zephyr Project documentation.
Bridle provides some standard board extensions. For more details, see
the Supported Extensions section in this documentation.
Hardware platform |
Board name |
Build target |
|---|---|---|
Native |
native_simnative_sim/native/64 |
|
Emulator |
qemu_x86qemu_x86_64 |
|
|
||
|
||
|
||
ARM Cortex-A9 Emulation |
|
|
|
||
|
||
|
||
|
||
qemu_riscv32qemu_riscv32_xip |
||
|
||
qemu_xtensa_dc233cqemu_xtensa_dc233c_mmu |
||
|
||
|
||
Virtualization |
|
|
ATSAMD21G18A |
|
|
|
||
i.MX RT1010 |
|
|
i.MX RT1060 |
mimxrt1060_evk/mimxrt1062/hyperflashmimxrt1060_evk@A/mimxrt1062/qspimimxrt1060_evk@B/mimxrt1062/qspimimxrt1060_evk@C/mimxrt1062/qspi |
|
i.MX RT1170 (CM7) |
mimxrt1170_evk/mimxrt1176/cm4mimxrt1170_evk/mimxrt1176/cm7mimxrt1170_evk@B/mimxrt1176/cm4mimxrt1170_evk@B/mimxrt1176/cm7 |
|
nRF52840 |
|
|
|
||
nRF9160 |
nrf9160dk/nrf9160nrf9160dk/nrf9160/ns |
|
RP2040 |
rpi_picorpi_pico/rp2040/w |
|
STM32F303RE |
|
|
STM32F401RE |
|
|
STM32F413ZH |
|
|
STM32F746ZG |
|
|
STM32F767ZI |
|
|
STM32L496ZG |
|
Boards included in tiac-bridle
The following boards are defined in the bridle/boards/ folder.
Also see the Supported Boards section in this documentation.
Hardware platform |
Board name |
Build target |
|---|---|---|
APM32F103Cx |
weact_bluepillplus_apm32f103c8weact_bluepillplus_apm32f103cb |
|
ATSAMD21G18A |
|
|
|
||
|
||
|
||
CH32F103Cx |
weact_bluepillplus_ch32f103c6weact_bluepillplus_ch32f103c8 |
|
CH32V103Cx |
weact_bluepillplus_ch32v103c6weact_bluepillplus_ch32v103c8 |
|
CH32V203Cx |
weact_bluepillplus_ch32v203c6weact_bluepillplus_ch32v203c8 |
|
GD32F103Cx |
weact_bluepillplus_gd32f103c8weact_bluepillplus_gd32f103cb |
|
GD32F303CC |
weact_bluepillplus_gd32f303cc |
|
nRF52840 |
|
|
RP2040 |
cytron_maker_nano_rp2040cytron_maker_pi_rp2040 |
|
mini_usb_rp2040/rp2040mini_usb_rp2040@16mb/rp2040mini_usb_rp2040@chipled/rp2040 |
||
picoboy/rp2040picoboy_color/rp2040 |
||
waveshare_rp2040_onewaveshare_rp2040_zerowaveshare_rp2040_matrixwaveshare_rp2040_tinywaveshare_rp2040_ethwaveshare_rp2040_lcd_0_96waveshare_rp2040_pluswaveshare_rp2040_plus@16mbwaveshare_rp2040_geek |
||
RP2350 |
mini_usb_rp2350/rp2350mini_usb_rp2350@16mb/rp2350 |
|
|
||
STM32F030C8 |
vccgnd_bluepill_stm32f030c8 |
|
STM32F051C8 |
vccgnd_bluepill_stm32f051c8 |
|
STM32F072Cx |
vccgnd_bluepill_stm32f072c8vccgnd_bluepill_stm32f072cb |
|
STM32F103Cx |
vccgnd_bluepill_stm32f103c8vccgnd_bluepill_stm32f103cb |
|
weact_bluepillplus_stm32f103c8weact_bluepillplus_stm32f103cb |
||
STM32F777NI |
|
Shield names
The following tables list all shields and build targets for TiaC Systems hardware platforms.
Shields included in tiac-bridle
The following shields are defined in the bridle/boards/shields/ folder.
Also see the Supported Shields section in this documentation.
Hardware platform |
Shield name |
Build target |
|---|---|---|
Common for testing |
loopback_testloopback_test_tmph |
|
Common for (new) chip support |
cjmcu_750_i2ccjmcu_750_i2c_noirqcjmcu_750_spicjmcu_750_spi_noirqcjmcu_752_i2ccjmcu_752_i2c_noirqcjmcu_752_spicjmcu_752_spi_noirq |
|
|
||
|
||
|
||
tcs_604_ardtcs_604_x_grove_testbed |
||
|
||
|
||
|
||
|
||
|
||
|
||
grove_sens_bme280grove_sens_bmp280grove_sens_dps310 |
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
Snippet names
The following tables list all snippets and build targets for TiaC Systems hardware platforms.
Snippets included in tiac-bridle
The following snippets are defined in the bridle/snippets/ folder.
Also see the Supported Snippets section in this documentation.
Hardware platform |
Snippet name |
Build target |
|---|---|---|
Common for usage |
Delete Default Devicetree Aliases Snippet (del-default-aliases) |
|
Common for usage |
|
|
Common for usage |
|
|
Common for testing |
|
|
Common for testing |
|
|
Common for testing |
Build all Display drivers test adjustments (tstdrv-bldall-display-adj) |
|
Common for testing |
Build all GPIO drivers test adjustments (tstdrv-bldall-gpio-adj) |
|
Common for testing |
Build all I2C drivers test adjustments (tstdrv-bldall-i2c-adj) |
|
Common for testing |
Build all MFD drivers test adjustments (tstdrv-bldall-mfd-adj) |
|
Common for testing |
Build all RTC drivers test adjustments (tstdrv-bldall-rtc-adj) |
|
Common for testing |
Build all Sensor drivers test adjustments (tstdrv-bldall-sensor-adj) |
|
Common for testing |
Build all UART drivers test adjustments (tstdrv-bldall-uart-adj) |
|
Tweak for setups |
|
Custom boards and shields
Defining your own board or shield is a very common step in application development, since applications are typically designed to run on boards that are not directly supported by Zephyr Project or Bridle, given that they are typically custom designs and not available publicly. To define your own board or shield, you can use the following Zephyr Project guides as reference, since boards are defined in Bridle just as they are in the Zephyr Project:
Custom Board, Devicetree and SOC Definitions is a guide to adding your own custom board to the Zephyr build system.
Shields is a complete guide to integrate your own modules as shields.
Board Porting Guide is a complete guide to porting Zephyr to your own board.
SoC Porting Guide is a complete guide to porting Zephyr to your own SoC.
Architecture Porting Guide is a complete guide to porting Zephyr to your own architecture.