tiacsys / bridle Goto Github PK

Bridle and kite line for embedded systems based on Zephyr.

Home Page: https://bridle.tiac-systems.net

License: Apache License 2.0

CMake 16.68% C 39.46% Shell 0.16% Gnuplot 0.04% Python 11.69% Dockerfile 0.20% Nix 0.83% Perl 30.93%

setup-zephyr zephyr-documentation zephyr-source doc-zephyr kconfig zephyr iot microcontroller operating-system real-time

bridle's People

Contributors

Stargazers

Watchers

Forkers

marekmatej ecoapi jilaypandya

bridle's Issues

[FER] docs: Switch from 'breathe' to 'docleaf' for API documentation generation

Is your enhancement proposal related to a problem? Please describe.

Following the Zephyr upstream PR zephyrproject-rtos/zephyr#59570 and switches the Bridle documentation from using Breathe to using Docleaf for generating API documentation from Doxygen XML output. For more details, see the referred Zephyr upstream PR above.

Describe the solution you'd like

The switch should be done in two separated steps:

Stay on Breath for the time being. Extend Bridle's Python requirements for documentation with the latest Breath version that Zephyr has used.
Switch from Breath to Docleaf in same way as Zephyr has done.

Describe alternatives you've considered
Non.

Additional context
Non.

[BUG] Nightly QA integration test fails (convert to stm32-bxcan)

Describe the bug
Because of Zephyr upstream PR zephyrproject-rtos/zephyr#61494 (renames CAN driver stm32-can to stm32-bxcan) and zephyrproject-rtos/zephyr#62816 (deprecated DTS properties for this CAN driver) the PR and nightly build fails.

To Reproduce
Use Bridle main branch for standard West workspace setup. Then:

west twister --verbose --jobs 4 \
  --outdir twister-out --no-clean --inline-logs \
  --enable-size-report --platform-reports \
  --device-testing --extra-args SHIELD=can_timing_adj \
  --hardware-map bridle/.github/qa-target-integration/map-tiac_magpie.yml \
  --testsuite-root zephyr/tests/drivers/can

Expected behavior
QA integration test do not fail.

Impact
Showstopper.

Logs and console output

devicetree error: 'prop-seg' is marked as deprecated in 'properties:' in .../bridle/bridle/workspace/zephyr/dts/bindings/can/st,stm32-bxcan.yaml for node /soc/can@40006400.

Screenshots
None.

Development Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK 0.16.1
Commit SHA 1cf63ac

Additional context
None.

[FER] Provide USB console by snippets instead of specific board revision

Is your enhancement proposal related to a problem? Please describe.
Boards maintained by Bridle with USB device capability providing the specific board revision @usbcons to swap the standard in-/output from the default UART to a USB CDC-ACM console. Since upstream Zephyr 3.4 provides the concept of snippets it would be more comfortable to use a central place for this swapping. This makes it more general purpose, even when a board has not (yet) OEM specific vendor and product identifier or descriptions for the USB Request Block.

Describe the solution you'd like
The Kconfig and DTS overly files related to board revision @usbcons of the following boards will be abandoned and splitted (converted) to a common and a board specific part in the new snipped folder usb-console. The Zephyr build system variables EXTRA_CONF_FILE and EXTRA_DTC_OVERLAY_FILE must be used in proper way, see: https://github.com/zephyrproject-rtos/zephyr/blob/main/snippets/xen_dom0/snippet.yml

Boards are:

Describe alternatives you've considered
Non.

Additional context
Non.

Can't rebuild documentation

Exception occurred:
  File "/home/runner/.local/lib/python3.8/site-packages/west/manifest.py", line 1417, in get_projects
    raise ValueError(unknown, uncloned)
ValueError: (['bridle'], [])
The full traceback has been saved in /tmp/sphinx-err-6o4drt8w.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
FAILED: CMakeFiles/bridle-html-all /home/runner/work/bridle/bridle/workspace/build/CMakeFiles/bridle-html-all

[BUG] Upgrade to Sphinx 5.x

Describe the bug
With nRF-SDK v2.0.2 @gmarull reports a the following PR on the Zephyr project: zephyrproject-rtos/zephyr#48947

The nRF-SDK hot-fix is: nrfconnect/sdk-nrf@9db3cf0

To Reproduce
not yet possible or happen

Expected behavior
not yet

Impact
nothing

Logs and console output
not possible

Screenshots
not possible

Development Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK v0.14.x
Bridle v3.x-next

Additional context
Evaluate the recommended and implemented upgrade to Sphinx 5.x and breathe 4.34 (required).

[FCR] Integrate the Trinamic Motion Control (TMC) API

Is your feature request related to a problem? Please describe.

I as an firmware developer wants to see any kind of integration of the TMC-API as Zephyr module with a common accessible Zephyr API based on Zephyr system calls, similar to the Sensor API. I think we can start with the name Actuator API.

Describe the solution you'd like

Drive stepper motors by Trinamic Chips connected over UART, SPI or a simple Step/Direction (S/D) interface.

Describe alternatives you've considered

No alternatives. Zephyr doesn't know anything about FOC or stepper motors, servo motors only. Maybe that the servo motors can also supported by the upcoming Actuator API.

Additional context

This will implement two different things:

Driver support for Trinamic chips, beginning with TMC2130 (simple driver) over S/D and SPI. That also integrates the TMC-API as Zephyr module.
Integration of the new Actuator API, beginning on downstream in Bridle, later contribute to upstream Zephyr.

[HW] Seeeduino Lotus Cortex-M0+ board support

Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe.

I need support for the Seeeduino Lotus Cortex-M0+.

Describe why you are asking for this support?

I've prepared a changeset for PR. I'll maintain the new board for Bridle and later contribute and maintain to/in Zephyr upstream.

Additional context

The new board support will coming together with Grove connector support as currently provided by Bridle only.

[BUG] Bridle Common (core) Testing fails since v3.4

Describe the bug
The execution of Bridle Common Testing runs into several Cmake / Build failure errors.

To Reproduce
Steps to reproduce the behavior:

following Installing Bridle manually for Linux
Cloning the repositories from v3.4-branch
use Twister to execute the tests:
west twister --jobs 4 --verbose --inline-logs --testsuite-root bridle/tests/bridle/common
See error

Expected behavior
All tests should be green.

Impact
Minor impact, no showstopper.

Logs and console output

INFO -  62/578 gd32vf103c_starter        ERROR Cmake build failure (build)
INFO -  69/578 gd32vf103v_eval           ERROR Cmake build failure (build)
INFO -  71/578 longan_nano               ERROR Cmake build failure (build)
INFO -  73/578 longan_nano_lite          ERROR Cmake build failure (build)

       zephyr/boards/riscv/gd32vf103c_starter/gd32vf103c_starter-pinctrl.dtsi:6:10:
       zephyr/boards/riscv/gd32vf103v_eval/gd32vf103v_eval-pinctrl.dtsi:6:10:
       zephyr/boards/riscv/longan_nano/longan_nano-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32vf103c(b-8)xx-pinctrl.h: No such file or directory

INFO -  67/578 rv32m1_vega_ri5cy         ERROR Build failure (build)
INFO -  68/578 rv32m1_vega_zero_riscy    ERROR Build failure (build)

       zephyr/soc/riscv/openisa_rv32m1/soc.h:12:10:
       fatal error: fsl_device_registers.h: No such file or directory

INFO -  72/578 tlsr9518adk80d            ERROR Build failure (build)

       zephyr/soc/riscv/riscv-privileged/telink_b91/soc.c:7:10:
       fatal error: sys.h: No such file or directory

INFO - 140/578 gd32f350r_eval            ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32f350r_eval/gd32f350r_eval-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32f350r(8-b)xx-pinctrl.h: No such file or directory

INFO - 173/578 gd32e507v_start           ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32e507v_start/gd32e507v_start-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32e507v(e-c)xx-pinctrl.h: No such file or directory

INFO - 206/578 gd32a503v_eval            ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32a503v_eval/gd32a503v_eval-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32a503v(b-c-d)xx-pinctrl.h: No such file or directory

INFO - 240/578 gd32e507z_eval            ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32e507z_eval/gd32e507z_eval-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32e507z(e-c)xx-pinctrl.h: No such file or directory

INFO - 246/578 gd32f403z_eval            ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32f403z_eval/gd32f403z_eval-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32f403z(k-i-g-e-c-b)xx-pinctrl.h: No such file or directory

INFO - 286/578 gd32e103v_eval            ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32e103v_eval/gd32e103v_eval-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32e103v(b-8)xx-pinctrl.h: No such file or directory

INFO - 314/578 gd32f450z_eval            ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32f450z_eval/gd32f450z_eval-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32f450z(e-g-i-k)xx-pinctrl.h: No such file or directory

INFO - 370/578 gd32f450i_eval            ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32f450i_eval/gd32f450i_eval-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32f450i(g-i-k)xx-pinctrl.h: No such file or directory

INFO - 380/578 gd32f407v_start           ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32f407v_start/gd32f407v_start-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32f405z(e-g-k)xx-pinctrl.h: No such file or directory

INFO - 470/578 gd32f470i_eval            ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32f470i_eval/gd32f470i_eval-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32f470i(g-i-k)xx-pinctrl.h: No such file or directory

INFO - 475/578 gd32f450v_start           ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32f450v_start/gd32f450v_start-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32f450v(e-g-i-k)xx-pinctrl.h: No such file or directory

INFO - 508/578 gd32l233r_eval            ERROR Cmake build failure (build)

       zephyr/boards/arm/gd32l233r_eval/gd32l233r_eval-pinctrl.dtsi:6:10:
       fatal error: dt-bindings/pinctrl/gd32l233r(b-c)xx-pinctrl.h: No such file or directory

INFO - 143/578 cc1352r_sensortag         ERROR Build failure (build)
INFO - 167/578 cc26x2r1_launchxl         ERROR Build failure (build)
INFO - 181/578 cc1352r1_launchxl         ERROR Build failure (build)
INFO - 317/578 cc1352p1_launchxl         ERROR Build failure (build)

       zephyr/soc/arm/ti_simplelink/cc13x2_cc26x2/soc.c:9:10:
       fatal error: driverlib/setup.h: No such file or directory

       zephyr/soc/arm/ti_simplelink/cc13x2_cc26x2/ccfg.c:26:10:
       fatal error: startup_files/ccfg.c: No such file or directory

INFO - 312/578 cc3220sf_launchxl         ERROR Build failure (build)
INFO - 405/578 cc3235sf_launchxl         ERROR Build failure (build)

       zephyr/soc/arm/ti_simplelink/cc32xx/soc.h:10:10:
       fatal error: inc/hw_types.h: No such file or directory

INFO - 329/578 msp_exp432p401r_launchxl  ERROR Build failure (build)

       zephyr/soc/arm/ti_simplelink/msp432p4xx/soc.h:6:10:
       fatal error: ti/devices/msp432p4xx/inc/msp.h: No such file or directory

INFO - 500/578 beagleconnect_freedom     ERROR Build failure (build)

       zephyr/soc/arm/ti_simplelink/cc13x2x7_cc26x2x7/soc.c:9:10:
       fatal error: driverlib/setup.h: No such file or directory

INFO - 147/578 da1469x_dk_pro            ERROR Build failure (build)

       zephyr/soc/arm/renesas_smartbond/da1469x/soc.h:14:10:
       fatal error: DA1469xAB.h: No such file or directory

INFO - 160/578 efr32bg27_brd2602a        ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efr32bg27/soc.h:14:10:
       fatal error: em_common.h: No such file or directory

INFO - 162/578 efr32bg22_brd4184a        ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efr32bg22/soc.h:18:10:
       fatal error: em_common.h: No such file or directory

INFO - 170/578 efm32wg_stk3800           ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efm32wg/soc.h:20:10:
       fatal error: em_bus.h: No such file or directory

INFO - 215/578 efm32gg_slwstk6121a       ERROR Build failure (build)
INFO - 249/578 efm32gg_stk3701a          ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efm32gg11b/soc.h:25:10:
       fatal error: em_bus.h: No such file or directory

INFO - 230/578 efr32xg24_dk2601b         ERROR Build failure (build)
INFO - 337/578 efr32_radio_brd4187c      ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efr32mg24/soc.h:20:10:
       fatal error: em_common.h: No such file or directory

INFO - 233/578 efm32pg_stk3401a          ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efm32pg1b/soc.h:20:10:
       fatal error: em_bus.h: No such file or directory

INFO - 271/578 efm32pg_stk3402a_jg       ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efm32jg12b/soc.h:20:10:
       fatal error: em_bus.h: No such file or directory

INFO - 273/578 efm32pg_stk3402a          ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efm32pg12b/soc.h:20:10:
       fatal error: em_bus.h: No such file or directory

INFO - 333/578 efr32_radio_brd4255a      ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efr32fg13p/soc.h:20:10:
       fatal error: em_bus.h: No such file or directory

INFO - 334/578 efr32_radio_brd4104a      ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efr32bg13p/soc.h:20:10:
       fatal error: em_common.h: No such file or directory

INFO - 338/578 efr32_radio_brd4250b      ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efr32fg1p/soc.h:20:10:
       fatal error: em_bus.h: No such file or directory

INFO - 339/578 efr32_radio_brd4180a      ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efr32mg21/soc.h:20:10:
       fatal error: em_common.h: No such file or directory

INFO - 441/578 efr32mg_sltb004a          ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efr32mg12p/soc.h:20:10:
       fatal error: em_common.h: No such file or directory

INFO - 443/578 efm32hg_slstk3400a        ERROR Build failure (build)

       zephyr/soc/arm/silabs_exx32/efm32hg/soc.h:20:10:
       fatal error: em_common.h: No such file or directory

INFO - 219/578 quick_feather             ERROR Build failure (build)
INFO - 284/578 qomu                      ERROR Build failure (build)

       zephyr/soc/arm/quicklogic_eos_s3/soc.h:11:10:
       fatal error: eoss3_dev.h: No such file or directory

INFO - 268/578 mec2016evb_assy6797       ERROR Build failure (build)

       zephyr/soc/arm/microchip_mec/mec1701/soc.h:14:10:
       fatal error: MCHP_MEC1701.h: No such file or directory

INFO - 418/578 mec1501modular_assy6885   ERROR Build failure (build)
INFO - 461/578 mec15xxevb_assy6853       ERROR Build failure (build)

       zephyr/soc/arm/microchip_mec/mec1501/soc.h:14:10:
       fatal error: MEC1501hsz.h: No such file or directory

INFO - 330/578 nuvoton_pfm_m487          ERROR Cmake build failure (build)

       zephyr/boards/arm/nuvoton_pfm_m487/nuvoton_pfm_m487-pinctrl.dtsi:7:10:
       fatal error: nuvoton/numicro/M48x-pinctrl.h: No such file or directory

INFO - 414/578 xmc47_relax_kit           ERROR Build failure (build)
INFO - 505/578 xmc45_relax_kit           ERROR Build failure (build)

       zephyr/soc/arm/infineon_xmc/4xxx/soc.h:9:10:
       fatal error: xmc_device.h: No such file or directory

INFO - 178/578 cy8cproto_063_ble         ERROR Cmake build failure (build)
INFO - 485/578 cy8cproto_062_4343w       ERROR Cmake build failure (build)

       warning: USE_INFINEON_UART (defined at modules/hal_infineon/Kconfig:51) has direct
       dependencies (SOC_FAMILY_PSOC6 || SOC_FAMILY_INFINEON_CAT1) && 0 with value n, but
       is currently being y-selected by the following symbols:
        - UART_INFINEON_CAT1 (defined at drivers/serial/Kconfig.ifx_cat1:7), with value y,
          direct dependencies DT_HAS_INFINEON_CAT1_UART_ENABLED && SERIAL (value: y), and
          select condition DT_HAS_INFINEON_CAT1_UART_ENABLED && SERIAL (value: y)

       error: Aborting due to Kconfig warnings

INFO - 289/578 cy8ckit_062_wifi_bt_m4    ERROR Cmake build failure (build)
INFO - 291/578 cy8ckit_062_wifi_bt_m0    ERROR Cmake build failure (build)
INFO - 359/578 [email protected]  ERROR Cmake build failure (build)
INFO - 360/578 cy8ckit_062_ble_m4        ERROR Cmake build failure (build)
INFO - 362/578 [email protected]  ERROR Cmake build failure (build)
INFO - 363/578 [email protected]  ERROR Cmake build failure (build)
INFO - 364/578 cy8ckit_062_ble_m0        ERROR Cmake build failure (build)

       warning: USE_INFINEON_UART (defined at modules/hal_infineon/Kconfig:51) has direct
       dependencies (SOC_FAMILY_PSOC6 || SOC_FAMILY_INFINEON_CAT1) && 0 with value n, but
       is currently being y-selected by the following symbols:
        - UART_PSOC6 (defined at drivers/serial/Kconfig.psoc6:7), with value y,
          direct dependencies DT_HAS_CYPRESS_PSOC6_UART_ENABLED && SERIAL (value: y), and
          select condition DT_HAS_CYPRESS_PSOC6_UART_ENABLED && SERIAL (value: y)

       error: Aborting due to Kconfig warnings

INFO - 204/578 nrf9161dk_nrf9161_ns      ERROR Cmake build failure (build)
INFO - 228/578 bl5340_dvk_cpuapp_ns      ERROR Cmake build failure (build)
INFO - 397/578 mps2_an521_ns             ERROR Cmake build failure (qemu)
INFO - 410/578 nrf5340dk_nrf5340_cpuapp_ns ERROR Cmake build failure (build)
INFO - 449/578 nrf9160dk_nrf9160_ns      ERROR Cmake build failure (build)

       CMake Error at zephyr/cmake/reports/CMakeLists.txt:34 (add_custom_target):
         Error evaluating generator expression:

           $<TARGET_PROPERTY:tfm,TFM_S_ELF_FILE>

         Target "tfm" not found.

INFO - 570/578 fvp_base_revc_2xaemv8a_smp_ns ERROR Cmake build failure (build)

       warning: BUILD_WITH_TFA (defined at modules/trusted-firmware-a/Kconfig:7)
       was assigned the value 'y' but got the value 'n'. Check these unsatisfied
       dependencies: 0 (=n). See
       http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_BUILD_WITH_TFA
       and/or look up BUILD_WITH_TFA in the menuconfig/guiconfig interface. The
       Application Development Primer, Setting Configuration Values, and Kconfig
       - Tips and Best Practices sections of the manual might be helpful too.

       CMake Error at zephyr/cmake/emu/armfvp.cmake:47 (message):
         Please specify ARMFVP_BL1_FILE in environment or with
         -DARMFVP_BL1_FILE=</path/to/bl1.bin>

INFO - 1 test scenarios (578 test instances) selected, 32 configurations skipped (26 by static filter, 6 at runtime).
INFO - 479 of 578 test configurations passed (87.73%), 0 failed, 67 errored, 32 skipped with 0 warnings in 3954.66 seconds
INFO - In total 546 test cases were executed, 32 skipped on 578 out of total 580 platforms (99.66%)
INFO - 35 test configurations executed on platforms, 511 test configurations were only built.

Screenshots
Non.

Development Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK 0.16.1
Version: v3.4-branch

Additional context
It seems we still missing some 3rd party hardware abstraction layer, detailed:

[FER] replace whitelist/blacklist with allowlist/blocklist

Is your enhancement proposal related to a problem? Please describe.
Per zephyrproject-rtos/west#440 and in common https://twitter.com/dhh/status/1032050325513940992, I'd like for Bridle to use the correct keywords in west.yml file.

Describe the solution you'd like
West 0.9 is the minimum version, we can use 'allowlist' or 'blocklist'. Set manifest requires west 0.10 or later to cache potential fixes, use the new keywords, the submodules feature, also be prepared for the new 'filter' keyword..

Describe alternatives you've considered
Non.

Additional context
Non.

[FCR] Support NXP HAL

Is your feature request related to a problem? Please describe.
Current manifest in west.yml doesn't support the NXP HAL, so I'm unable to build anything for e.g. the NXP MIMXRT1060-EVK development hardware.

Describe the solution you'd like
Add hal_nxp to the allowlist.

Describe alternatives you've considered
Non.

Additional context
Non.

[FCR] Support Raspberry Pi Pico HAL

Is your feature request related to a problem? Please describe.
Current manifest in west.yml doesn't support the Raspberry Pi Pico, so I'm unable to build anything for e.g. the Raspberry Pi Pico development hardware.

Describe the solution you'd like
Add hal_rpi_pico to the allowlist.

Describe alternatives you've considered
Non.

Additional context
Non.

[BUG] Zephyr counter driver test fails

Describe the bug
Since tiacsys/zephyr@51f452b the RTC (counter) test runs into timeout. Thus the qa-integration workflow fails since a couple of days.

To Reproduce
Steps to reproduce the behavior:

following https://bridle.tiac-systems.net/doc/latest/bridle/gs_installing.html
west twister --device-testing --hardware-map bridle/.github/qa-integration/map-tiac_magpie.yml --board-root bridle/boards --testsuite-root zephyr/tests/drivers/counter

Expected behavior
The original Zephyr test for RTC (counter) on STM32 should be successfully run without hacks. But sadly, it seems Zephyr have never used this test for RTC, only counter and only on selected boards.

Impact
It is an showstopper. Our QA workflow is broken.

Logs and console output

INFO    - Using Ninja..
INFO    - Zephyr version: zephyr-v3.3.0-1683-g7e5349a33581
INFO    - Using 'zephyr' toolchain.
INFO    - Building initial testsuite list...
INFO    - Writing JSON report twister-out/testplan.json

Device testing on:

| Platform    | ID       | Serial device   |
|-------------|----------|-----------------|
| tiac_magpie | DT04ATV0 | /dev/ttyUSB0    |

INFO    - JOBS: 4
INFO    - Adding tasks to the queue...
INFO    - Added initial list of jobs to queue
INFO    - 26/47 tiac_magpie               tests/drivers/spi/dt_spec/drivers.spi.dt_spec      PASSED (device 14.033s)
INFO    - 27/47 tiac_magpie               tests/drivers/can/shell/drivers.can.shell          PASSED (device 13.979s)
INFO    - 28/47 tiac_magpie               tests/drivers/spi/spi_loopback/drivers.spi.loopback.internal SKIPPED (runtime filter)
INFO    - 29/47 tiac_magpie               tests/drivers/spi/spi_loopback/drivers.spi.loopback PASSED (device 8.452s)
INFO    - 30/47 tiac_magpie               tests/drivers/gpio/gpio_get_direction/peripheral.gpio.get_direction PASSED (device 6.206s)
INFO    - 31/47 tiac_magpie               tests/drivers/can/timing/drivers.can.timing        PASSED (device 5.942s)
INFO    - 32/47 tiac_magpie               tests/drivers/can/api/drivers.can.api              PASSED (device 7.069s)
INFO    - 33/47 tiac_magpie               tests/drivers/gpio/gpio_basic_api/drivers.gpio.2pin PASSED (device 27.412s)
INFO    - 34/47 tiac_magpie               tests/drivers/hwinfo/api/drivers.hwinfo.api        PASSED (device 6.589s)
INFO    - 35/47 tiac_magpie               tests/drivers/gpio/gpio_api_1pin/peripheral.gpio.1pin PASSED (device 11.960s)
INFO    - 36/47 tiac_magpie               tests/drivers/watchdog/wdt_basic_api/drivers.watchdog SKIPPED (runtime filter)
INFO    - 37/47 tiac_magpie               tests/drivers/entropy/api/drivers.entropy.psa_crypto SKIPPED (runtime filter)
INFO    - 38/47 tiac_magpie               wdt_basic_api/drivers.watchdog.stm32iwdg.tiac_magpie PASSED (device 9.774s)
INFO    - 39/47 tiac_magpie               tests/crypto/rand32/drivers.rand32.random_psa_crypto SKIPPED (runtime filter)
INFO    - 40/47 tiac_magpie               tests/drivers/counter/counter_basic_api/drivers.counter.basic_api  FAILED Timeout (device 605.294s)
ERROR   - *** Booting Zephyr OS build zephyr-v3.3.0-1683-g7e5349a33581 ***
Running TESTSUITE counter_basic
===================================================================
START - test_all_channels
Testing rtc@40002800
PASS - test_all_channels in 3.103 seconds
===================================================================
START - test_cancelled_alarm_does_not_expire
Skipped for rtc@40002800
PASS - test_cancelled_alarm_does_not_expire in 0.103 seconds
===================================================================
START - test_late_alarm
Skipped for rtc@40002800
PASS - test_late_alarm in 0.103 seconds
===================================================================
START - test_late_alarm_error
Skipped for rtc@40002800
PASS - test_late_alarm_error in 0.103 seconds
===================================================================
START - test_multiple_alarms
Skipped for rtc@40002800
PASS - test_multiple_alarms in 0.103 seconds
===================================================================
START - test_set_top_value_with_alarm
Skipped for rtc@40002800
PASS - test_set_top_value_with_alarm in 0.103 seconds
===================================================================
START - test_short_relative_alarm
Testing rtc@40002800

Development Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK 0.15.2
Version: main (tiacsys/zephyr@6898094)

[BUG] Bridle CMake Package not usable in Freestanding mode

Describe the bug
When I try to use find_package(Bridle REQUIRED) in a standalone "freestanding" CMake application project the following errors occurs:

CMake Error at .../workspace/bridle/cmake/modules/bridle/version.cmake:39 (include):
  include could not find requested file:

    /cmake/hex.cmake
Call Stack (most recent call first):
  .../workspace/bridle/share/bridle-package/cmake/BridleConfigVersion.cmake:108 (include)
  CMakeLists.txt:6 (find_package)

CMake Error at .../workspace/bridle/cmake/modules/bridle/version.cmake:88 (to_hex):
  Unknown CMake command "to_hex".
Call Stack (most recent call first):
  .../workspace/bridle/share/bridle-package/cmake/BridleConfigVersion.cmake:108 (include)
  CMakeLists.txt:6 (find_package)

To Reproduce
Steps to reproduce the behavior:

Following Bridle's Getting Starting Guide, install a full featured Bridle workspace and export the Zephyr and Bridle CMake Packages:
```
west zephyr-export
west bridle-export
```
Create the new project folder hello_world for the standalone "freestanding" CMake application project with a simple "Hello World!" C Application and the following content in the CMakeLists.txt:
```
cmake_minimum_required(VERSION 3.20.0)
set(BOARD native_posix_64)
find_package(Bridle REQUIRED)
project(hello_world)
target_sources(app PRIVATE src/main.c)
```
Activate (source) the Python Virtual Environment from the Bridle workspace.
Execute: cmake -Bbuild -GNinja hello_world
See error above.

Expected behavior
Bridle's boilerplate should be load without error and catch the Zephyr boilerplate properly.

Impact

It is not really a showstopper. Workaround would be to use find_package(Zephyr REQUIRED). But from the perspective of a System Architect the hard coded dependency to Bridle for a "Bridle application" would be the goal of Bridle's own CMake Package. Currently it is only work properly internal, inside the Bridle workspace, in "default mode" not "Freestanding mode".

Logs and console output

See error above.

With the workaround (find_package(Zephyr REQUIRED) in CMakeLists.txt the following session works without errors:

rm -rf build

cmake -Bbuild -GNinja hello_world

Loading Zephyr default modules (Freestanding).
-- Application: .../bridle-apps/hello_world
-- CMake version: 3.26.4
Loading Bridle default modules (Freestanding).
-- Bridle version: 3.3.1 (.../workspace/bridle)
-- Bridle is trying to locate Zephyr SDK 0.15.2.
-- Using Zephyr SDK 0.15.2 for building Bridle. (/opt/zephyr-sdk-0.15.2)
-- Found Python3: .../workspace/.venv/bin/python3 (found suitable exact version "3.8.10") found components: Interpreter 
-- Cache files will be written to: /home/user/.cache/zephyr
-- Zephyr version: 3.3.0 (.../workspace/zephyr)
-- Found west (found suitable version "1.0.1", minimum required is "0.7.1")
-- Board: native_posix_64
-- Found host-tools: zephyr 0.15.2 (/opt/zephyr-sdk-0.15.2)
-- Found toolchain: host (gcc/ld)
-- Found Dtc: /opt/zephyr-sdk-0.15.2/sysroots/x86_64-pokysdk-linux/usr/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6") 
-- Found BOARD.dts: .../workspace/zephyr/boards/posix/native_posix/native_posix_64.dts
-- Generated zephyr.dts: .../bridle-apps/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: .../bridle-apps/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: .../bridle-apps/build/zephyr/dts.cmake
Parsing .../workspace/zephyr/Kconfig
Loaded configuration '.../workspace/zephyr/boards/posix/native_posix/native_posix_64_defconfig'
Merged configuration '.../bridle-apps/hello_world/prj.conf'
Configuration saved to '.../bridle-apps/build/zephyr/.config'
Kconfig header saved to '.../bridle-apps/build/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 9.4.0
-- The CXX compiler identification is GNU 9.4.0
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/gcc
-- Configuring done (3.0s)
-- Generating done (0.0s)
-- Build files have been written to: .../bridle-apps/build

ninja -Cbuild

ninja: Entering directory `build'
[1/97] Preparing syscall dependency handling
[2/97] Generating include/generated/version.h
-- Zephyr version: 3.3.0 (.../workspace/zephyr), build: zephyr-v3.3.0-51-g7ea0860e376d
[3/97] Generating ../../zephyr/include/generated/version_bridle.h
-- Bridle version: 3.3.1 (.../workspace/bridle), build: bridle-v3.3.1
[93/97] Linking C executable zephyr/zephyr_pre0.elf
[97/97] Linking C executable zephyr/zephyr.elf

./build/zephyr/zephyr.exe --stop_at=1

*** Booting Zephyr OS build zephyr-v3.3.0-51-g7ea0860e376d ***
Hello World! native_posix_64

Stopped at 1.010s

Screenshots

non

Development Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK 0.15.2
Version: 3.3.1

Additional context

non

[FCR] Support Grove System Shields

Is your feature request related to a problem? Please describe.
I as an user need an abstraction for the Grove System Shields. At least I wants to build and run Zephyr's LED (blinky/fade) and Button samples against the Arduino Sensor Kit - Base without any further expensive device tree overlaying or Kconfig hacking in my own application folder. I wants to use different boards, e.g. Nucleo F3/F4/F7, Raspberry Pi Pico, NXP i.MX RT10xx, ...

Describe the solution you'd like
Create new shield folder for all Grove interconnection shields, the Seeed Grove Base Shield V1/V2 and the Seeed Grove Shield for Pi Pico. Create additional shields for different Grove modules, start with the Button and LED module.

Describe alternatives you've considered
non.

Additional context
Find out a way to (re-)map PWM signal lines over the device tree nexus construct, similar to common GPIO signal lines. Respect the needs to manipulate different pin controls (board specifics).

[FCR] Bump to Zephyr (bleeding edge) main line

Is your feature request related to a problem? Please describe.
I'd like to work with Zephyr bleeding edge to see failures as soon as possible.

Describe the solution you'd like
Change the manifest in west.yml file. Qualify Bridle against new Zephyr version and fix all errors and warnings that happens.

Describe alternatives you've considered
Non.

Additional context
Non.

[FCR] Bump to Zephyr v3.4

Is your feature request related to a problem? Please describe.
I'd like to work with Zephyr v3.4 as soon as it is released.

Describe the solution you'd like
Change the manifest in west.yml file. Qualify Bridle against new Zephyr version and fix all errors and warnings that happens.

Describe alternatives you've considered
Non.

Additional context
Non.

[BUG] Nightly QA integration test fails

Describe the bug
Because of the C and C++ standards violation that type of main is suspicious Bridle's samples "button" and "halloshell" fails since last night.

To Reproduce
Use Bridle main branch for standard West workspace setup. Then:

west twister --verbose --jobs 4 \
  --outdir twister-out --no-clean --inline-logs \
  --enable-size-report --platform-reports \
  --testsuite-root bridle/samples/button \
  --testsuite-root bridle/samples/helloshell

Expected behavior
QA integration test do not fail.

Impact
No showstopper.

Logs and console output

.../workspace/bridle/samples/button/src/init.c:37:6: error: return type of 'main' is not 'int' [-Werror=main]
   37 | void main(void) {}
      |      ^~~~
cc1: all warnings being treated as errors

.../workspace/bridle/samples/helloshell/src/main.c:11:6: error: return type of 'main' is not 'int' [-Werror=main]
   11 | void main(void)
      |      ^~~~
cc1: all warnings being treated as errors

Screenshots
Non.

Development Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK 0.16.1
Commit SHA 11cbf83

Additional context
Non.

STM32F7: PWM loopback test fails

investigate the reason for Operation pin_configure_capture not defined for driver instance

*** Booting Zephyr OS version 2.5.0  ***
Running test suite pwm_loopback_test
===================================================================
START - test_pulse_capture
Testing PWM capture @ 15000000/100000000 nsec
E: syscall z_vrfy_pwm_pin_capture_cycles failed check: Operation pin_configure_capture not defined for driver instance 0x8010514
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000000
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20020100 (unknown)
E: Halting system

Missing TiaC Magpie STM32F777NIHx

The Magpie board made by Three is a Company (TiaC) and based on STM32F777NIHx provide an affordable and flexible way for users to build prototypes and try out new concepts target communication systems.

Status:

configured (DTS/Kconfig):
- User LED 1/2
- UART 7 TX/RX/RTS/CTS
- ETH MII/MDIO
- USB OTG FS DM/DP (device)
- USB OTG HS DM/DP (host/hub)
- CAN 1 TX/RX
- CAN 2 RX/TX
- I2C 2 SDA/SCL
- TiaC MAGPIE Pin Header
- TiaC MAGPIE Pin Header : USART 3 TX/RX
- TiaC MAGPIE Pin Header : UART 4 TX/RX
- TiaC MAGPIE Pin Header : UART 5 TX/RX
- TiaC MAGPIE Pin Header : UART 8 TX/RX/RTS/CTS
- TiaC MAGPIE Pin Header : I2C 3 SCL/SDA
- TiaC MAGPIE Pin Header : I2C 4 SCL/SDA
- TiaC MAGPIE Pin Header : SPI 4 MOSI/NSS/SCK/MISO
- TiaC MAGPIE Pin Header : SPI 5 MOSI/NSS/SCK/MISO
- TiaC MAGPIE Pin Header : PWM TIM 8 CH1/2/3/4
- TiaC MAGPIE Pin Header : ADC 3 IN9/IN14/IN15
manual tested:
- JTAG(SWD) TMS/TCK/TDI/TDO/TRST : ST-Link, OpenOCD
- UART 7 : Zephyr Shell Console
- ETH : DHCPv4 Client, Telnet Server, HTTP Web Server
- USB OTG FS (device) : USB Mass Storage (RAM/FATFS)
- USB OTG HS (host/hub) : Only USB device function is supported in Zephyr at the moment
- CAN 1 : t.b.d.
- CAN 2 : Simultaneous use of CAN_1 and CAN_2 not supported yet
- I2C 2 : Zephyr Shell Console (i2cdetect)
- TiaC MAGPIE Pin Header (for Shields)
- TiaC MAGPIE Pin Header : USART 3 : t.b.d.
- TiaC MAGPIE Pin Header : UART 4 : t.b.d.
- TiaC MAGPIE Pin Header : UART 5 : t.b.d.
- TiaC MAGPIE Pin Header : UART 8 : t.b.d.
- TiaC MAGPIE Pin Header : I2C 3 : Zephyr Shell Console (i2cdetect)
- TiaC MAGPIE Pin Header : I2C 4 : Zephyr Shell Console (i2cdetect)
- TiaC MAGPIE Pin Header : SPI 4 : SPI Loopback
- TiaC MAGPIE Pin Header : SPI 5 : SPI Loopback
- TiaC MAGPIE Pin Header : PWM TIM 8 : Zephyr Shell Console (pwm)
- TiaC MAGPIE Pin Header : ADC 3 : Zephyr Shell Console (adc)
automated test:
- Zephyr : kernel
- ARM : IRQ, NMI, TZ Wrap, Thread Swap, System Call / SW Vector
- ARM Cortex-M7 : MPU and Stack Protection
- ARM Cortex-M7 : RTC on LSE
- ARM Cortex-M7 : IWDG as Watchdog
- ARM Cortex-M7 : WWDG as Watchdog
- ARM Cortex-M7 : RNG for Entropy
- ARM Cortex-M7 : CRC for Hash (Zephyr has not yet any framework to access HW accelerated CRC/HASH units)
- Hardware Info-API
- User LED 1/2
- UART 7
- ETH
- USB OTG FS (device)
- USB OTG HS (host/hub)
- CAN 1
- CAN 2
- I2C 2
- TiaC MAGPIE Pin Header : USART 3 & 4 (not yet)
- TiaC MAGPIE Pin Header : I2C 4 & 3 (FAIL)
- TiaC MAGPIE Pin Header : SPI 4
- TiaC MAGPIE Pin Header : PWM TIM 8 (FAIL)
- TiaC MAGPIE Pin Header : ADC 3 (not yet)

[FER] Snippets

Is your enhancement proposal related to a problem? Please describe.
As Zephyr v3.4 will have support for "Snippets" we want to prepare Bridle for that too.

Describe the solution you'd like
Do the same thing that Zephyr did, see: zephyrproject-rtos/zephyr#53640

Describe alternatives you've considered
Non.

Additional context
Non.

[FER] Provide CAN timing tweak for TiaC Magpie by snippets instead of a shield

Is your enhancement proposal related to a problem? Please describe.
Since the beginning, the adjustments of the CAN timing for the board TiaC Magpie STM32F777NIHx as a shield was more a workaround than a clean and correct abstraction of this problem. With the introduction of snippets as part of the Zephyr build process, this way over a shield can now be abandoned and a general-purpose snippet can be used instead.

Describe the solution you'd like
The Kconfig and DTS overly files from shield can_timing_adj will be abandoned and splitted (converted) to a common and a board specific part in the new snipped folder can-timing-adj. The Zephyr build system variables EXTRA_CONF_FILE and EXTRA_DTC_OVERLAY_FILE must be used in proper way, see: https://github.com/zephyrproject-rtos/zephyr/blob/main/snippets/xen_dom0/snippet.yml

Describe alternatives you've considered
Non.

Additional context
Non.

Improve documentation environment

For the Sphinx documentation not all artifacts will be copied from the source tree to build tree, also the notation in doc/CMakeLists.txt target lpnb-content, command LPNB_EXTRACT_CONTENT_COMMAND has invalid and useless copy rules. Further we missing entries into the board documentation that will be supported and/or developed by LP/N Bridle.

Change all copyright strings from Li-Pro.Net to TiaC Systems

Since the repository was moved from Li-Pro.Net to TiaC we now have to change the namespace.

related to issue #5

Zephyr does not know F777

Support the Zephyr project with new support for the SM32F777 family that is similar to the STM32F767 with the exception of an additional crypto unit.

[HW] Waveshare RP2040

Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe.
I need support for Waveshare's RP2040 boards. The following boards should be supported:

In this early first stage the Zephyr upstream samples "LED blinky" and "Shell on serial console" should be usable.

Describe why you are asking for this support?
With this support the board variation for RP2040 based systems will scaling up.

I'm preparing a changeset for PR. I'll maintain the new board for Bridle and later contribute and maintain to/in Zephyr upstream.

Additional context
The new board support will coming together with Grove connector support as currently provided by Bridle only.

[HW] Grove Interconnect Shields for Arduino/Genuino Zero

Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe.

I need support for the Seeed Studio Grove Interconnect Shields on the Arduino/Genuino Zero.

Describe why you are asking for this support?

Only Bridle has the Grove Interconnect Shields integrated. Thus the shield overlays needs extensions for the Arduino/Genuino Zero too on Bridle downstream level. Later, when the shield would be contributed upstream to Zephyr, the support for Arduino/Genuino Zero is always qualified.

Additional context

non

[HW] Grove Interconnect Shields for Seeeduino XIAO

Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe.

I need support for the Seeed Studio Grove Interconnect Shields on the Seeeduino XIAO.

Describe why you are asking for this support?

Only Bridle has the Grove Interconnect Shields integrated. Thus the shield overlays needs extensions for the Seeeduino XIAO too on Bridle downstream level. Later, when the shield would be contributed upstream to Zephyr, the support for Seeeduino XIAO is always qualified.

Additional context

non

Missing CI build and test for all supported boards

Add https://buildkite.com/ configuration to build and run tests for all board that will be supported and maintain by LP/N Bridle.

Also it would be nice to have an self-hosted action runner for integration test on target.

[FCR] Support Renesas HAL

Is your feature request related to a problem? Please describe.
Current manifest in west.yml doesn't support the Renesas HAL, so I'm unable to build anything for e.g. the Arduino UNO R4 Minima development hardware.

Describe the solution you'd like
Add hal_renesas to the allowlist.

Describe alternatives you've considered
Non.

Additional context
Non.

[FCR] Bump to Zephyr v3.3

Is your feature request related to a problem? Please describe.
I'd like to work with Zephyr v3.3 as soon as it is released.

Describe the solution you'd like
Change the manifest in west.yml file. Qualify Bridle against new Zephyr version and fix all errors and warnings that happens.

Describe alternatives you've considered
Non.

Additional context
Non.

[BUG] QA Integration Test fails

Describe the bug
Because of Zephyr upstream PR zephyrproject-rtos/zephyr#59842 and commit zephyrproject-rtos/zephyr@7f9215d the nightly build fails. Zephyr has moved requirements into doc folder.

To Reproduce
See, e.g.: https://github.com/tiacsys/bridle/actions/runs/5988314710/job/16243362039

Expected behavior
Nightly builds w/o failures.

Impact
Showstopper.

Logs and console output
See, e.g.: https://github.com/tiacsys/bridle/actions/runs/5988314710/job/16243362039

Screenshots
None.

Development Environment (please complete the following information):
See, e.g.: https://github.com/tiacsys/bridle/actions/runs/5988314710/job/16243362039

Additional context
None.

[FCR] Bump to Zephyr v3.0

Is your feature request related to a problem? Please describe.
I'd like to work with Zephyr v3.0.

Describe the solution you'd like
Change the manifest in west.yml file. Qualify Bridle against new Zephyr version and fix all errors and warnings that happens.

Describe alternatives you've considered
Non.

Additional context
Non.

[FCR] .config information available from binary artifact at runtime

When analysing output from firmware information about how the FW was configured is missing
Currently only the version number is reported by the Firmware which helps to identify at which revision the code base was, when the particular binary artifact got created. However, Zephyr also allows for quite elaborate compile time configuration options by means of KConfig control files. All set config options are collected at runtime in a .config file within the build directory. When the binary artifact is shared this information gets lost and there is currently no way to retrieve that information from the binary artifact alone.

Describe the solution you'd like
Bridle should provide an API by which the .config options used for this particular build could be retrieved an runtime. This is similar to how the Linux kernel works where this information can be retrieved at runtime from within the /proc pseudo filesystem.

One solution might be to return this simply as a string or as an array of string elements which are automatically retrieved from the .config file at compile time.

Describe alternatives you've considered
Rather than putting the .config content in a string (or array of strings) it might also be interesting to simply place the .config in a flash partition using Zephyrs built-in fs capabilities and offer the content of this file through an API

[FCR] Support ST HAL

Is your feature request related to a problem? Please describe.
Current manifest in west.yml doesn't support the ST HAL, so I'm unable to build anything for e.g. the Thingy:52 development hardware with MEMS Temperature and Humidity Monitor HTS221 by STMicro.

Describe the solution you'd like
Add hal_st to the allowlist.

Describe alternatives you've considered
Non.

Additional context
Non.

[FCR] Bump to Zephyr v3.2

Is your feature request related to a problem? Please describe.
I'd like to work with Zephyr v3.2 as soon as it is released.

Describe the solution you'd like
Change the manifest in west.yml file. Qualify Bridle against new Zephyr version and fix all errors and warnings that happens.

Describe alternatives you've considered
Non.

Additional context
Non.

[FCR] support Nordic HAL

Is your feature request related to a problem? Please describe.
Current manifest in west.yml doesn't support the Nordic HAL, so I'm unable to build anything for Nordic development hardware.

Describe the solution you'd like
Add 'hal_nordic' to the 'allowlist'.

Describe alternatives you've considered
Non.

Additional context
Non.

[BUG] Grove Shields DTS Binding test suites fail for seeeduino_lotus@usbcons

Describe the bug
The execution of following test suites running into Cmake build failure errors for board seeeduino_lotus@usbcons:

Grove Interconnect Shields DTS Binding
Grove Button Shields DTS Binding
[Grove LED Shields DTS Binding(https://bridle.tiac-systems.net/doc/3.4/bridle/tests/shields/grove_led/dts_bindings/README.html)

To Reproduce
Steps to reproduce the behavior:

following Installing Bridle manually for Linux
Cloning the repositories from v3.4-branch
use Twister to execute the tests (each about 4 to 12 hours):
- west twister --jobs 4 --verbose --inline-logs --testsuite-root bridle/tests/shields/grove/dts_bindings
- west twister --jobs 4 --verbose --inline-logs --testsuite-root bridle/tests/shields/grove_btn/dts_bindings
- west twister --jobs 4 --verbose --inline-logs --testsuite-root bridle/tests/shields/grove_led/dts_bindings
See error

Expected behavior
All tests should be green.

Impact
Minor impact, no showstopper.

Logs and console output
Grove Interconnect Shields DTS Binding:

INFO - 6740/6936 seeeduino_lotus@usbcons   grove.base.v1   ERROR Cmake build failure (build)
INFO - 6837/6936 seeeduino_lotus@usbcons   grove.base.v2   ERROR Cmake build failure (build)

       devicetree error:
       Label 'grove_uart_header' appears on /grove-d0-connector and on /grove-uart-connector

INFO - 12 test scenarios (6936 test instances) selected, 6705 configurations skipped (6701 by static filter, 4 at runtime).
INFO - 229 of 6936 test configurations passed (99.13%), 0 failed, 2 errored, 6705 skipped with 0 warnings in 1690.19 seconds
INFO - In total 2 test cases were executed, 6934 skipped on 578 out of total 580 platforms (99.66%)
INFO - 0 test configurations executed on platforms, 231 test configurations were only built.

Grove Button Shields DTS Binding:

INFO - 45568/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d28   ERROR Cmake build failure (build)
INFO - 45569/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d29   ERROR Cmake build failure (build)
INFO - 45570/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d30   ERROR Cmake build failure (build)
INFO - 45571/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d31   ERROR Cmake build failure (build)
INFO - 45572/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d26   ERROR Cmake build failure (build)
INFO - 45573/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d27   ERROR Cmake build failure (build)
INFO - 45574/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d24   ERROR Cmake build failure (build)
INFO - 45575/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d25   ERROR Cmake build failure (build)
INFO - 45576/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d22   ERROR Cmake build failure (build)
INFO - 45577/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d23   ERROR Cmake build failure (build)
INFO - 45578/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d20   ERROR Cmake build failure (build)
INFO - 45579/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d21   ERROR Cmake build failure (build)
INFO - 45590/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d13   ERROR Cmake build failure (build)
INFO - 45591/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d12   ERROR Cmake build failure (build)
INFO - 45592/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d11   ERROR Cmake build failure (build)
INFO - 45593/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d10   ERROR Cmake build failure (build)
INFO - 45594/49130 seeeduino_lotus@usbcons   grove.connectors.grove_btn.gpio.d9    ERROR Cmake build failure (build)

       devicetree error:
       child specifier for <Node /grove_btns/grove-btn-d9 …>
       child specifier for <Node /grove_btns/grove-btn-d10 …>
       child specifier for <Node /grove_btns/grove-btn-d11 …>
       child specifier for <Node /grove_btns/grove-btn-d12 …>
       child specifier for <Node /grove_btns/grove-btn-d13 …>
       child specifier for <Node /grove_btns/grove-btn-d20 …>
       child specifier for <Node /grove_btns/grove-btn-d21 …>
       child specifier for <Node /grove_btns/grove-btn-d22 …>
       child specifier for <Node /grove_btns/grove-btn-d23 …>
       child specifier for <Node /grove_btns/grove-btn-d24 …>
       child specifier for <Node /grove_btns/grove-btn-d25 …>
       child specifier for <Node /grove_btns/grove-btn-d26 …>
       child specifier for <Node /grove_btns/grove-btn-d27 …>
       child specifier for <Node /grove_btns/grove-btn-d28 …>
       child specifier for <Node /grove_btns/grove-btn-d29 …>
       child specifier for <Node /grove_btns/grove-btn-d30 …>
       child specifier for <Node /grove_btns/grove-btn-d31 …>
       does not appear in  <Property 'gpio-map' at '/grove-laced-if-lotus' …>

INFO - 45636/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d19      ERROR Cmake build failure (build)
INFO - 45733/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d19      ERROR Cmake build failure (build)
INFO - 45830/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d18      ERROR Cmake build failure (build)
INFO - 45927/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d18      ERROR Cmake build failure (build)
INFO - 46024/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d17      ERROR Cmake build failure (build)
INFO - 46121/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d17      ERROR Cmake build failure (build)
INFO - 46218/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d16      ERROR Cmake build failure (build)
INFO - 46315/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d16      ERROR Cmake build failure (build)
INFO - 46412/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d15      ERROR Cmake build failure (build)
INFO - 46509/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d15      ERROR Cmake build failure (build)
INFO - 46606/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d14      ERROR Cmake build failure (build)
INFO - 46703/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d14      ERROR Cmake build failure (build)
INFO - 46800/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d13      ERROR Cmake build failure (build)
INFO - 46897/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d12      ERROR Cmake build failure (build)
INFO - 46994/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d11      ERROR Cmake build failure (build)
INFO - 47091/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d10      ERROR Cmake build failure (build)
INFO - 47188/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d9       ERROR Cmake build failure (build)
INFO - 47285/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d9       ERROR Cmake build failure (build)
INFO - 47382/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d8       ERROR Cmake build failure (build)
INFO - 47479/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d8       ERROR Cmake build failure (build)
INFO - 47576/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d7       ERROR Cmake build failure (build)
INFO - 47673/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d7       ERROR Cmake build failure (build)
INFO - 47770/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d6       ERROR Cmake build failure (build)
INFO - 47867/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d6       ERROR Cmake build failure (build)
INFO - 47964/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d5       ERROR Cmake build failure (build)
INFO - 48061/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d5       ERROR Cmake build failure (build)
INFO - 48158/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d4       ERROR Cmake build failure (build)
INFO - 48255/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d4       ERROR Cmake build failure (build)
INFO - 48352/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d3       ERROR Cmake build failure (build)
INFO - 48449/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d3       ERROR Cmake build failure (build)
INFO - 48546/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d2       ERROR Cmake build failure (build)
INFO - 48643/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d2       ERROR Cmake build failure (build)
INFO - 48740/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d1       ERROR Cmake build failure (build)
INFO - 48837/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d1       ERROR Cmake build failure (build)
INFO - 48934/49130 seeeduino_lotus@usbcons   grove.base.v1.grove_btn.gpio.d0       ERROR Cmake build failure (build)
INFO - 49031/49130 seeeduino_lotus@usbcons   grove.base.v2.grove_btn.gpio.d0       ERROR Cmake build failure (build)

       devicetree error:
       Label 'grove_uart_header' appears on /grove-d0-connector and on /grove-uart-connector

INFO - 85 test scenarios (49130 test instances) selected, 45576 configurations skipped (45567 by static filter, 9 at runtime).
INFO - 3501 of 49130 test configurations passed (98.51%), 0 failed, 53 errored, 45576 skipped with 0 warnings in 29628.31 seconds
INFO - In total 53 test cases were executed, 49077 skipped on 578 out of total 580 platforms (99.66%)
INFO - 0 test configurations executed on platforms, 3554 test configurations were only built.

Grove LED Shields DTS Binding:

INFO - 84695/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d29    ERROR Cmake build failure (build)
INFO - 84696/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d28    ERROR Cmake build failure (build)
INFO - 84697/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d30    ERROR Cmake build failure (build)
INFO - 84698/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d31    ERROR Cmake build failure (build)
INFO - 84699/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d27    ERROR Cmake build failure (build)
INFO - 84700/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d25    ERROR Cmake build failure (build)
INFO - 84701/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d24    ERROR Cmake build failure (build)
INFO - 84702/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d26    ERROR Cmake build failure (build)
INFO - 84703/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d20    ERROR Cmake build failure (build)
INFO - 84704/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d21    ERROR Cmake build failure (build)
INFO - 84705/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d23    ERROR Cmake build failure (build)
INFO - 84706/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d22    ERROR Cmake build failure (build)
INFO - 84707/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d18    ERROR Cmake build failure (build)
INFO - 84708/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d16    ERROR Cmake build failure (build)
INFO - 84709/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d17    ERROR Cmake build failure (build)
INFO - 84710/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d19    ERROR Cmake build failure (build)
INFO - 84711/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d12    ERROR Cmake build failure (build)
INFO - 84712/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d15    ERROR Cmake build failure (build)
INFO - 84713/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d13    ERROR Cmake build failure (build)
INFO - 84714/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d14    ERROR Cmake build failure (build)
INFO - 84715/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d9     ERROR Cmake build failure (build)
INFO - 84716/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d11    ERROR Cmake build failure (build)
INFO - 84717/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d10    ERROR Cmake build failure (build)
INFO - 84718/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d8     ERROR Cmake build failure (build)
INFO - 84729/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d1     ERROR Cmake build failure (build)
INFO - 84731/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.pwm.d0     ERROR Cmake build failure (build)

       devicetree error:
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d0 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d1 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d8 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d9 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d10 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d11 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d12 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d13 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d14 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d15 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d16 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d17 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d18 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d19 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d20 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d21 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d22 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d23 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d24 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d25 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d26 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d27 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d28 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d29 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d30 …>
       child specifier for <Node /grove_pwm_leds/grove-pwm-led-d31 …>
       does not appear in  <Property 'pwm-map' at '/grove-laced-if-lotus' …>

INFO - 84733/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d31   ERROR Cmake build failure (build)
INFO - 84734/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d30   ERROR Cmake build failure (build)
INFO - 84735/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d29   ERROR Cmake build failure (build)
INFO - 84736/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d28   ERROR Cmake build failure (build)
INFO - 84737/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d27   ERROR Cmake build failure (build)
INFO - 84738/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d26   ERROR Cmake build failure (build)
INFO - 84739/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d25   ERROR Cmake build failure (build)
INFO - 84740/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d24   ERROR Cmake build failure (build)
INFO - 84741/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d23   ERROR Cmake build failure (build)
INFO - 84742/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d22   ERROR Cmake build failure (build)
INFO - 84743/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d21   ERROR Cmake build failure (build)
INFO - 84744/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d20   ERROR Cmake build failure (build)
INFO - 84745/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d19   SKIPPED (runtime filter)
INFO - 84746/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d18   SKIPPED (runtime filter)
INFO - 84747/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d17   SKIPPED (runtime filter)
INFO - 84748/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d16   SKIPPED (runtime filter)
INFO - 84749/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d14   SKIPPED (runtime filter)
INFO - 84750/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d15   SKIPPED (runtime filter)
INFO - 84751/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d12   ERROR Cmake build failure (build)
INFO - 84752/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d13   ERROR Cmake build failure (build)
INFO - 84753/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d11   ERROR Cmake build failure (build)
INFO - 84754/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d10   ERROR Cmake build failure (build)
INFO - 84755/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d9    ERROR Cmake build failure (build)
INFO - 84757/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d8    SKIPPED (runtime filter)
INFO - 84770/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d1    SKIPPED (runtime filter)
INFO - 84772/88434 seeeduino_lotus@usbcons   grove.connectors.grove_led.gpio.d0    SKIPPED (runtime filter)

       devicetree error:
       child specifier for <Node /grove_leds/grove-led-d9 …>
       child specifier for <Node /grove_leds/grove-led-d10 …>
       child specifier for <Node /grove_leds/grove-led-d11 …>
       child specifier for <Node /grove_leds/grove-led-d12 …>
       child specifier for <Node /grove_leds/grove-led-d13 …>
       child specifier for <Node /grove_leds/grove-led-d20 …>
       child specifier for <Node /grove_leds/grove-led-d21 …>
       child specifier for <Node /grove_leds/grove-led-d22 …>
       child specifier for <Node /grove_leds/grove-led-d23 …>
       child specifier for <Node /grove_leds/grove-led-d24 …>
       child specifier for <Node /grove_leds/grove-led-d25 …>
       child specifier for <Node /grove_leds/grove-led-d26 …>
       child specifier for <Node /grove_leds/grove-led-d27 …>
       child specifier for <Node /grove_leds/grove-led-d28 …>
       child specifier for <Node /grove_leds/grove-led-d29 …>
       child specifier for <Node /grove_leds/grove-led-d30 …>
       child specifier for <Node /grove_leds/grove-led-d31 …>
       does not appear in  <Property 'gpio-map' at '/grove-laced-if-lotus' …>

INFO - 84940/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d19   ERROR Cmake build failure (build)
INFO - 85037/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d19   ERROR Cmake build failure (build)
INFO - 85134/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d18   ERROR Cmake build failure (build)
INFO - 85231/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d18   ERROR Cmake build failure (build)
INFO - 85328/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d17   ERROR Cmake build failure (build)
INFO - 85425/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d17   ERROR Cmake build failure (build)
INFO - 85522/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d16   ERROR Cmake build failure (build)
INFO - 85619/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d16   ERROR Cmake build failure (build)
INFO - 85716/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d15   ERROR Cmake build failure (build)
INFO - 85813/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d15   ERROR Cmake build failure (build)
INFO - 85910/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d14   ERROR Cmake build failure (build)
INFO - 86007/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d14   ERROR Cmake build failure (build)
INFO - 86104/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d13   ERROR Cmake build failure (build)
INFO - 86201/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d12   ERROR Cmake build failure (build)
INFO - 86298/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d11   ERROR Cmake build failure (build)
INFO - 86395/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d10   ERROR Cmake build failure (build)
INFO - 86492/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d9    ERROR Cmake build failure (build)
INFO - 86589/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d9    ERROR Cmake build failure (build)
INFO - 86686/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d8    ERROR Cmake build failure (build)
INFO - 86783/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d8    ERROR Cmake build failure (build)
INFO - 86880/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d7    ERROR Cmake build failure (build)
INFO - 86977/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d7    ERROR Cmake build failure (build)
INFO - 87074/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d6    ERROR Cmake build failure (build)
INFO - 87171/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d6    ERROR Cmake build failure (build)
INFO - 87268/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d5    ERROR Cmake build failure (build)
INFO - 87365/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d5    ERROR Cmake build failure (build)
INFO - 87462/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d4    ERROR Cmake build failure (build)
INFO - 87559/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d4    ERROR Cmake build failure (build)
INFO - 87656/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d3    ERROR Cmake build failure (build)
INFO - 87753/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d3    ERROR Cmake build failure (build)
INFO - 87850/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d2    ERROR Cmake build failure (build)
INFO - 87947/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d2    ERROR Cmake build failure (build)
INFO - 88044/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d1    ERROR Cmake build failure (build)
INFO - 88141/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d1    ERROR Cmake build failure (build)
INFO - 88238/88434 seeeduino_lotus@usbcons   grove.base.v1.grove_led.gpio.d0    ERROR Cmake build failure (build)
INFO - 88335/88434 seeeduino_lotus@usbcons   grove.base.v2.grove_led.gpio.d0    ERROR Cmake build failure (build)

       devicetree error:
       Label 'grove_uart_header' appears on /grove-d0-connector and on /grove-uart-connector

INFO - 153 test scenarios (88434 test instances) selected, 84708 configurations skipped (84694 by static filter, 14 at runtime).
INFO - 3647 of 88434 test configurations passed (97.88%), 0 failed, 79 errored, 84708 skipped with 0 warnings in 28009.98 seconds
INFO - In total 79 test cases were executed, 88355 skipped on 578 out of total 580 platforms (99.66%)
INFO - 0 test configurations executed on platforms, 3726 test configurations were only built.

Screenshots
Non.

Development Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK 0.16.1
Version: v3.4-branch

Additional context
It seems the serial output switch will not respect by the test suit properly, detailed:

board with UART serial output has no test case – WHY?
- west twister -vi -p seeeduino_lotus -T bridle/tests/shields/grove/dts_bindings
board with USB serial output FAILS – WHY?
- west twister -vi -p seeeduino_lotus@usbcons -T bridle/tests/shields/grove/dts_bindings
- west twister -vi -p seeeduino_lotus@usbcons -T bridle/tests/shields/grove_btn/dts_bindings
- west twister -vi -p seeeduino_lotus@usbcons -T bridle/tests/shields/grove_led/dts_bindings
GOOD CASES for Seeeduino Lotus (seeeduino_lotus)
- west twister -vi -p seeeduino_lotus -T bridle/tests/shields/grove_btn/dts_bindings
- west twister -vi -p seeeduino_lotus -T bridle/tests/shields/grove_led/dts_bindings
GOOD CASES for Arduino Zero (arduino_zero and arduino_zero@usbcons)
- west twister -vi -p arduino_zero -T bridle/tests/shields/grove/dts_bindings
- west twister -vi -p arduino_zero@usbcons -T bridle/tests/shields/grove/dts_bindings
- west twister -vi -p arduino_zero -T bridle/tests/shields/grove_btn/dts_bindings
- west twister -vi -p arduino_zero@usbcons -T bridle/tests/shields/grove_btn/dts_bindings

[FCR] Bump to Zephyr v3.1

Is your feature request related to a problem? Please describe.
I'd like to work with Zephyr v3.1.

Describe the solution you'd like
Change the manifest in west.yml file. Qualify Bridle against new Zephyr version and fix all errors and warnings that happens.

Describe alternatives you've considered
Non.

Additional context
Non.

[FER] Bridle version definition

Is your enhancement proposal related to a problem? Please describe.
At the moment there is no version for Bridle. This needs to be changed.

Describe the solution you'd like
The include file "version.h" should define a valid Bridle version in addition to the Zephyr kernel version. This should also be used in the documentation and accessible by a new shell command set over an internal system API.

Describe alternatives you've considered
There are no alternatives possible.

Additional context
nothing

[BUG] reduced setup time in workflow "QA Integration Test" because of clang-format

Describe the bug
With Zephyr v3.2 the Python package clang-format will be installed within our "QA Integration Test" workflow. Reson is the follwoing line:

pip3 install --upgrade --requirement zephyr/scripts/requirements-extras.txt

--> https://github.com/zephyrproject-rtos/zephyr/blob/ed05fdf0e532d5a9747abde8a830872f3726badd/scripts/requirements-extras.txt#L13

Now, unfortunately, the ARM 64 bit architecture is not (yet) supported on PyPi with a wheel. So on a Raspberry Pi 4 this means an extremely long installation time, because a native C++ compile has to build the wheel from the sdist package first.

Do we really need all the extra Python packages for our "QA Integration Test" workflow?

To Reproduce
Steps to reproduce the behavior:

mkdir build; cd build
python3 -m venv --clear --copies --prompt="$(basename $(pwd))[$(python3 --version)]" .env
source .env/bin/activate
pip3 install --upgrade pip
pip3 install --upgrade setuptools
pip3 install clang-format
And now wait multiple hours ... :-(

Expected behavior
Either we can skip Zephyr's extra packages or PyPi will provide an manylinux-aarch64 wheel in near future. As long the last choice will not happen we can only handle our Python cache carefully.

Monitor issue ssciwr/clang-format-wheel#64

Development Environment (please complete the following information):

OS: Linux on ARM 64 bit
Zephyr v3.2
Bridle next branch

Additional context
Non.

STM32F7: I2C loopback test fails

investigate the reason for .../zephyr/tests/drivers/i2c/i2c_slave_api/src/main.c:55: run_full_read: (ret not equal to 0) -- could be an interrupt handling issue in the I2C slave driver of STM32F7 / HAL_ST

*** Booting Zephyr OS version 2.5.0  ***
Running test suite test_eeprom_slave
===================================================================
START - test_eeprom_slave
Found EP0 EEPROM_0 on I2C Master device I2C_3 at addr 54
Found EP1 EEPROM_1 on I2C Master device I2C_4 at addr 56
Testing single-role
Testing full read: Master: I2C_4, address: 0x54
Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/i2c/i2c_slave_api/src/main.c:55: run_full_read: (ret not equal to 0)
Failed to read EEPROM
FAIL - test_eeprom_slave
===================================================================
Test suite test_eeprom_slave failed.
===================================================================
PROJECT EXECUTION FAILED

[FCR] Bump to Zephyr v2.7

Is your feature request related to a problem? Please describe.
I'd like to work with Zephyr v2.7.

Describe the solution you'd like
Change the manifest in west.yml file. Qualify Bridle against new Zephyr version and fix all errors and warnings that happens.

Describe alternatives you've considered
Non.

Additional context
Non.

[BUG] Twister can not handle duplicate platform identifier

Describe the bug

Whenever I try to execute a test suit against a Bridle downstream board that already exist in Zephyr upstream repository, e.g. here the "Arduino Zero", Twister will run into an exception error.

current workaround:

Remove the upstream board description:

rm zephyr/boards/arm/arduino_zero/arduino_zero.yaml

... and then, after test session, revert back to the original YAML file:

git -C zephyr restore boards/arm/arduino_zero/arduino_zero.yaml

To Reproduce

Steps to reproduce the behavior:

Clone Bridle v3.3 branch
Init and update west workspace (clone Zephyr modules)
Setup Python Virtual Environment based on Zephyr's and Bridle's requirements

Execute a simple test suite against Bridle's board "Arduino Zero":

west twister \
     --jobs 4 \
     --verbose \
     --inline-logs \
     --board-root bridle/boards \
     --platform arduino_zero \
     --testsuite-root bridle/tests/shields/grove/dts_bindings

Expected behavior

Just as Zephyr's CMake extensions respect the availability of boards with the exact same platform identifier in a downstream repository and use this to build examples and tests, Twister as a test framework must also have this behavior and must not generate an exception error. At least this behavior must be possible to switch on as a command line argument.

Impact

I am not able to run test suites on downstream boards with the exact same platform identifier that already exists in Zephyr's upstream repository.

Logs and console output

INFO    - Using Ninja..
INFO    - Zephyr version: zephyr-v3.3.0-39-gc5e8a3d10ecc
INFO    - Using 'zephyr' toolchain.
ERROR   - Duplicate platform arduino_zero in /.../workspace/bridle/boards/arm/arduino_zero/arduino_zero.yaml
Traceback (most recent call last):
  File "/.../workspace/.env/bin/west", line 8, in <module>
    sys.exit(main())
  File "/.../workspace/.env/lib/python3.8/site-packages/west/app/main.py", line 866, in main
    app.run(argv or sys.argv[1:])
  File "/.../workspace/.env/lib/python3.8/site-packages/west/app/main.py", line 111, in run
    self.run_command(argv)
  File "/.../workspace/.env/lib/python3.8/site-packages/west/app/main.py", line 385, in run_command
    self.run_extension(args.command, argv)
  File "/.../workspace/.env/lib/python3.8/site-packages/west/app/main.py", line 467, in run_extension
    self.cmd.run(args, unknown, self.topdir, manifest=self.manifest,
  File "/.../workspace/.env/lib/python3.8/site-packages/west/commands.py", line 194, in run
    self.do_run(args, unknown)
  File "/.../workspace/zephyr/scripts/west_commands/twister_cmd.py", line 60, in do_run
    ret = main(options)
  File "/.../workspace/zephyr/scripts/pylib/twister/twisterlib/twister_main.py", line 120, in main
    tplan.discover()
  File "/.../workspace/zephyr/scripts/pylib/twister/twisterlib/testplan.py", line 125, in discover
    self.add_configurations()
  File "/.../workspace/zephyr/scripts/pylib/twister/twisterlib/testplan.py", line 367, in add_configurations
    raise Exception(f"Duplicate platform identifier {platform.name} found")
Exception: Duplicate platform identifier arduino_zero found

Screenshots

non

Development Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK 0.15.2
v3.3-branch

Additional context

non

[FER] Need a fancy blinky example for novice developer

Is your enhancement proposal related to a problem? Please describe.

I as an project maintainer wants to provide any new novice developer a more fancier blinky example than the original from Zephyr. This should provides feature toggles on Kconfig level to switch between polling and event driven operation mode and also shows the usage of CMake to split the source code in as small pieces as possible and remove the main() entry completely.

Describe the solution you'd like

Take over our private results from hackathon2022 and create a new well named sample folder.

Describe alternatives you've considered

Training and pait programing, but this will become time intensive in future.

Additional context

non

[FCR] Support Atmel HAL

Is your feature request related to a problem? Please describe.
Current manifest in west.yml doesn't support the Atmel HAL, so I'm unable to build anything for e.g. the Seeeduino XIAO development hardware.

Describe the solution you'd like
Add hal_atmel to the allowlist.

Describe alternatives you've considered
Non.

Additional context
Non.

[FCR] Bump to Zephyr v2.6

Is your feature request related to a problem? Please describe.
I'd like to work with Zephyr v2.6.

Describe the solution you'd like
Change the manifest in west.yml file. Qualify Bridle against new Zephyr version and fix all errors and warnings that happens.

Errors that have to fix:

-- west build: running target build-all: documentation early fails because of wrong integration since Zephyr v2.6
create and use our own Sphinx theme PyPi package, fork from: https://pypi.org/project/sphinx-ncs-theme/
boot banner shouldn't show Git SHA1 of TiaC add-on commits: *** Booting Zephyr OS build 3f8d752d33b0 ***

Warnings that have to fix:

Deprecated: Please use device tree for STM32 clock_control configuration

Execute all samples and tests on TiaC Magpie manually, check output and adjust documentation:

Describe alternatives you've considered
Non.

Additional context
Non.

[FER] Backporting new feature enhancements to v3.0

Is your enhancement proposal related to a problem? Please describe.
non

Describe the solution you'd like
I like to see the new feature enhancements to the build and documentaion system with CMake, Sphinx, and Doxygen in v3.1-branch also in v3.0-branch.

Describe alternatives you've considered
non

Additional context
non

[HW] ST STM32F7308-DK Discovery Kit

Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe.

I need support for the STM32F7308-DK Discovery Kit by STMicroelectronics.

Describe why you are asking for this support?

I've prepared a changeset for PR. I'll maintain the new board for Bridle and later contribute and maintain to/in Zephyr upstream.

Additional context

The new board support will coming together with Grove connector support as currently provided by Bridle only.

[FER] Use sub-manifests for 3rd party projects

Is your enhancement proposal related to a problem? Please describe.
Not a problem or show stopper, more a refactoring request. In preparation of more features that should supported by Bridle in near future we expect to add more than only on single project entry in the West manifest file. That will increase the size of the current single point manifest description quickly.

Describe the solution you'd like
Start to refactor the West manifest and lay out the Zephyr project entry to its own sub-manifest file.

Describe alternatives you've considered
Stay with the current single point West manifest description and except the growing file size.

Additional context
Non.

[BUG] Documentation Publish is broken

Describe the bug
Since bump to actions/github-script@v6 in Documentation Publish we can't publish the documentation anymore.

To Reproduce
see: https://github.com/tiacsys/bridle/actions/runs/3244220989/jobs/5320091332

TypeError: Cannot read properties of undefined (reading 'listWorkflowRunArtifacts')
    at eval (eval at callAsyncFunction (/home/runner/work/_actions/actions/github-script/v6/dist/index.js:13355:16), <anonymous>:3:38)
    at callAsyncFunction (/home/runner/work/_actions/actions/github-script/v6/dist/index.js:13356:12)
    at main (/home/runner/work/_actions/actions/github-script/v6/dist/index.js:13451:26)
    at Module.858 (/home/runner/work/_actions/actions/github-script/v6/dist/index.js:13428:1)
    at __webpack_require__ (/home/runner/work/_actions/actions/github-script/v6/dist/index.js:24:31)
    at startup (/home/runner/work/_actions/actions/github-script/v6/dist/index.js:43:19)
    at /home/runner/work/_actions/actions/github-script/v6/dist/index.js:49:18
    at Object.<anonymous> (/home/runner/work/_actions/actions/github-script/v6/dist/index.js:52:10)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
Error: Unhandled error: TypeError: Cannot read properties of undefined (reading 'listWorkflowRunArtifacts')

Expected behavior
Build artefact doc.zip from Documentation Build have to pick up, extract and upload to WEB server.

Impact
Can' deliver release or latest documentation. Can't remove old documentation on WEB server.

Logs and console output
non

Screenshots
non

Development Environment (please complete the following information):

GitHub action runner (workflow)

Additional context
non

tiacsys / bridle Goto Github PK

bridle's People

Contributors

Stargazers

Watchers

Forkers

bridle's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs