Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds ST_NUCLEO144_F767ZI #226

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

Adds ST_NUCLEO144_F767ZI #226

wants to merge 13 commits into from

Conversation

networkfusion
Copy link
Member

@networkfusion networkfusion commented Oct 31, 2023

Description

Adds new firmware for - ST_NUCLEO144_F767ZI
Replaces nanoframework/nf-interpreter#2762 (apart from pwm config nanoframework/nf-interpreter#2804)

Targets affected

  • BrainPad2
  • GHI_FEZ_CERB40_NF
  • GHI_FEZ_CERBERUS_NF
  • I2M_ELECTRON_NF
  • I2M_OXYGEN_NF
  • MBN_QUAIL
  • NESHTEC_NESHNODE_V1
  • NETDUINO3_WIFI
  • PybStick2x
  • ST_NUCLEO64_F401RE_NF
  • ST_NUCLEO64_F411RE_NF
  • ST_STM32F411_DISCOVERY
  • ST_NUCLEO144_F412ZG_NF
  • ST_NUCLEO144_F746ZG
  • ST_NUCLEO144_F767ZI
  • ST_STM32F4_DISCOVERY
  • ST_NUCLEO144_F439ZI
  • WEACT_F411CE
  • TI_CC1352P1_LAUNCHXL_868
  • TI_CC1352P1_LAUNCHXL_915
  • LilygoTWatch2020
  • LilygoTWatch2021
  • BUILD ALL

Motivation and Context

Adds new target

How Has This Been Tested?

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Config and build (change in the configuration and build system, has no impact on code or features)
  • Dependencies (update dependencies and changes associated, has no impact on code or features)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Summary by CodeRabbit

  • New Features

    • Introduced full support for the ST NUCLEO144 F767ZI board with comprehensive build configurations.
    • Added enhanced debugging setups for nanoBooter and nanoCLR applications.
    • Expanded the CI/CD pipeline to include a dedicated build job for the new target board.
    • Added new configuration and build presets for the ST NUCLEO144 F767ZI platform.
  • Bug Fixes

    • Ensured correct inclusion of source files and configurations across various project components.

@Ellerbach
Copy link
Member

@networkfusion do you still want to move this PR forward? It's open for more than 1.5 years :-)

@networkfusion
Copy link
Member Author

@networkfusion do you still want to move this PR forward? It's open for more than 1.5 years :-)

I think so, but need to dig out the board again 😅

Copy link

coderabbitai bot commented Feb 13, 2025

Warning

Rate limit exceeded

@networkfusion has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 13 minutes and 11 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between c537224 and 9945ef0.

📒 Files selected for processing (1)
  • azure-pipelines.yml (1 hunks)

Walkthrough

This pull request integrates support for the ST_NUCLEO144_F767ZI board into the ChibiOS project. New CMake configurations, presets, and CMakeLists files for board-specific targets (including nanoBooter and nanoCLR) have been added. Debug configurations and a dedicated Azure Pipelines job have been introduced to manage the build and debugging processes for the new hardware configuration.

Changes

File(s) Change Summary
CMakePresets.json
ChibiOS/.../CMakePresets.json
Added a new include entry in the root preset file and introduced a board-specific CMake preset defining both configuration and build presets for ST_NUCLEO144_F767ZI.
ChibiOS/ST_NUCLEO144_F767ZI/CMakeLists.txt
ChibiOS/ST_NUCLEO144_F767ZI/common/CMakeLists.txt
ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/CMakeLists.txt
ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/CMakeLists.txt
Introduced board-specific CMake build configurations including new functions (nf_setup_target_build, nf_generate_bin_package), added copyright notices, appended source files, and marked project source variables as global.
ChibiOS/ST_NUCLEO144_F767ZI/launch.json Added new debugging configurations for nanoBooter and nanoCLR, specifying debugger settings, remote target connection, and flash commands.
azure-pipelines.yml Added a new CI/CD job (Build_ST_NUCLEO144_F767ZI) to build for the ST_NUCLEO144_F767ZI board, including steps for source checkout, environment setup, building, and publishing artifacts.

Sequence Diagram(s)

sequenceDiagram
    participant P as Azure Pipeline (Build_ST_NUCLEO144_F767ZI)
    participant C as Code Checkout
    participant M as CMake (Configuration)
    participant B as Build System
    participant X as Package Manager

    P->>C: Checkout source code & templates
    C->>M: Provide CMake presets and CMakeLists files
    M->>B: Execute build configuration (nf_setup_target_build)
    B->>M: Process build type (Debug/RelWithDebInfo)
    B->>X: Invoke nf_generate_bin_package
    X->>P: Publish binaries and artifacts
Loading
sequenceDiagram
    participant D as Debugger
    participant L as launch.json Config
    participant T as Target Board

    D->>L: Read debug configuration (nanoBooter/nanoCLR)
    L->>T: Connect via OpenOCD with flash and reset commands
    T-->>D: Establish debug session
Loading

Suggested reviewers

  • josesimoes

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (2)
azure-pipelines.yml (2)

1434-1453: 🛠️ Refactor suggestion

Add ST_NUCLEO144_F767ZI to build failure reporting dependencies.

The new job Build_ST_NUCLEO144_F767ZI should be added to the list of dependencies for the build failure reporting job.

Add the following line to the list of dependencies:

   dependsOn:
   - Build_MBN_QUAIL
   - Build_BrainPad2
   - Build_GHI_FEZ_CERB40_NF
   - Build_I2M_ELECTRON_NF
   - Build_I2M_OXYGEN_NF
   - Build_WEACT_F411CE
   - Build_ST_NUCLEO64_F401RE_NF
   - Build_ST_NUCLEO64_F411RE_NF
   - Build_ST_STM32F411_DISCOVERY
   - Build_ST_NUCLEO144_F412ZG_NF
   - Build_ST_NUCLEO144_F746ZG
   - Build_ST_STM32F4_DISCOVERY
   - Build_ST_NUCLEO144_F439ZI
   - Build_TI_CC1352P1_LAUNCHXL_868
   - Build_TI_CC1352P1_LAUNCHXL_915
   - Build_PybStick2x
   - Build_LilygoTWatch2020
   - Build_LilygoTWatch2021
   - Build_NETDUINO3_WIFI
+  - Build_ST_NUCLEO144_F767ZI
🧰 Tools
🪛 YAMLlint (1.35.1)

[warning] 1435-1435: wrong indentation: expected 4 but found 2

(indentation)


1457-1476: 🛠️ Refactor suggestion

Add ST_NUCLEO144_F767ZI to build failure conditions.

The new job Build_ST_NUCLEO144_F767ZI should be added to the list of conditions for the build failure reporting job.

Add the following line to the list of conditions:

   condition: >-
     or(
       failed('Build_MBN_QUAIL'),
       failed('Build_BrainPad2'),
       failed('Build_GHI_FEZ_CERB40_NF'),
       failed('Build_I2M_ELECTRON_NF'),
       failed('Build_I2M_OXYGEN_NF'),
       failed('Build_WEACT_F411CE'),      
       failed('Build_ST_NUCLEO64_F401RE_NF'),
       failed('Build_ST_NUCLEO64_F411RE_NF'),
       failed('Build_ST_STM32F411_DISCOVERY'),
       failed('Build_ST_NUCLEO144_F412ZG_NF'),
       failed('Build_ST_NUCLEO144_F746ZG'),
       failed('Build_ST_STM32F4_DISCOVERY'),
       failed('Build_ST_NUCLEO144_F439ZI'),
       failed('Build_TI_CC1352P1_LAUNCHXL_868'),
       failed('Build_TI_CC1352P1_LAUNCHXL_915'),
       failed('Build_PybStick2x'),
       failed('Build_LilygoTWatch2020'),
       failed('Build_LilygoTWatch2021'),
       failed('Build_NETDUINO3_WIFI')    
+      failed('Build_ST_NUCLEO144_F767ZI')
     )
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 1463-1463: trailing spaces

(trailing-spaces)


[error] 1476-1476: trailing spaces

(trailing-spaces)

🧹 Nitpick comments (2)
ChibiOS/ST_NUCLEO144_F767ZI/CMakeLists.txt (1)

37-49: Remove duplicated binary package generation code.

The binary package generation code is identical for both Debug/RelWithDebInfo and other build types. The conditional block can be simplified.

Apply this diff to remove the duplication:

-    if(CMAKE_BUILD_TYPE MATCHES Debug OR CMAKE_BUILD_TYPE MATCHES RelWithDebInfo)
-        nf_generate_bin_package(
-            ${CMAKE_SOURCE_DIR}/build/${NANOBOOTER_PROJECT_NAME}.bin
-            ${CMAKE_SOURCE_DIR}/build/${NANOCLR_PROJECT_NAME}.bin
-            10000
-            ${CMAKE_SOURCE_DIR}/build/nanobooter-nanoclr.bin)
-    else()
-        nf_generate_bin_package(
-            ${CMAKE_SOURCE_DIR}/build/${NANOBOOTER_PROJECT_NAME}.bin
-            ${CMAKE_SOURCE_DIR}/build/${NANOCLR_PROJECT_NAME}.bin
-            10000
-            ${CMAKE_SOURCE_DIR}/build/nanobooter-nanoclr.bin)
-    endif()
+    nf_generate_bin_package(
+        ${CMAKE_SOURCE_DIR}/build/${NANOBOOTER_PROJECT_NAME}.bin
+        ${CMAKE_SOURCE_DIR}/build/${NANOCLR_PROJECT_NAME}.bin
+        10000
+        ${CMAKE_SOURCE_DIR}/build/nanobooter-nanoclr.bin)
azure-pipelines.yml (1)

923-924: Fix formatting issues.

There are indentation and trailing spaces issues in the file:

  • Line 923: Remove trailing spaces
  • Line 924: Fix indentation (should be 4 spaces)
  • Line 932: Remove trailing spaces
  • Line 941: Fix indentation (should be 4 spaces)

Apply this diff to fix the formatting:

-  dependsOn: 
-  - Check_Code_Style
+    dependsOn:
+        - Check_Code_Style

-  pool: 
+    pool:

Also applies to: 932-932, 941-941

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 923-923: trailing spaces

(trailing-spaces)


[warning] 924-924: wrong indentation: expected 4 but found 2

(indentation)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 980c31a and e37454e.

⛔ Files ignored due to path filters (51)
  • .github/PULL_REQUEST_TEMPLATE.md is excluded by !**/*.md and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/README.md is excluded by !**/*.md and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/board.c is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/board.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/common/Device_BlockStorage-DEBUG.c is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/common/Device_BlockStorage.c is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/common/serialcfg.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/common/targetHAL_ConfigurationManager.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/managed_helpers/README.md is excluded by !**/*.md and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/managed_helpers/ST_NUCLEO144_F767ZI.Adc.cs is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/managed_helpers/package.nuspec is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/mbedtls_config.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/STM32F76xx_booter-DEBUG.ld is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/STM32F76xx_booter.ld is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/chconf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/halconf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/halconf_nf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/main.c is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/mcuconf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/mcuconf_nf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/target_board.h.in is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/STM32F76xx_CLR-DEBUG.ld is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/STM32F76xx_CLR.ld is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/chconf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/halconf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/halconf_nf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/main.c is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/mcuconf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/mcuconf_nf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/nanoHAL.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/target_board.h.in is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/stm32f7xx_hal_conf.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_BlockStorage.c is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_BlockStorage.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_common.c is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_common.h.in is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_external_memory.c is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_lwip_sntp_opts.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_lwipopts.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_nf_dev_onewire_config.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_nf_dev_onewire_config.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_nf_device_can_config.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_nf_device_can_config.h is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_system_device_adc_config.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_system_device_dac_config.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_system_device_i2c_config.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_system_device_pwm_config.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_system_device_spi_config.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_system_io_ports_config.cpp is excluded by none and included by none
  • ChibiOS/ST_NUCLEO144_F767ZI/target_system_io_ports_config.h is excluded by none and included by none
  • README.md is excluded by !**/*.md and included by none
📒 Files selected for processing (8)
  • CMakePresets.json (1 hunks)
  • ChibiOS/ST_NUCLEO144_F767ZI/CMakeLists.txt (1 hunks)
  • ChibiOS/ST_NUCLEO144_F767ZI/CMakePresets.json (1 hunks)
  • ChibiOS/ST_NUCLEO144_F767ZI/common/CMakeLists.txt (1 hunks)
  • ChibiOS/ST_NUCLEO144_F767ZI/launch.json (1 hunks)
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/CMakeLists.txt (1 hunks)
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/CMakeLists.txt (1 hunks)
  • azure-pipelines.yml (1 hunks)
✅ Files skipped from review due to trivial changes (3)
  • CMakePresets.json
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoBooter/CMakeLists.txt
  • ChibiOS/ST_NUCLEO144_F767ZI/nanoCLR/CMakeLists.txt
🧰 Additional context used
🪛 YAMLlint (1.35.1)
azure-pipelines.yml

[error] 923-923: trailing spaces

(trailing-spaces)


[warning] 924-924: wrong indentation: expected 4 but found 2

(indentation)


[error] 932-932: trailing spaces

(trailing-spaces)


[warning] 941-941: wrong indentation: expected 4 but found 2

(indentation)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Community-Targets (Check_Code_Style)
  • GitHub Check: Community-Targets (Check_Build_Options)
  • GitHub Check: Community-Targets (Get_Commit_Message)
🔇 Additional comments (3)
ChibiOS/ST_NUCLEO144_F767ZI/CMakePresets.json (1)

1-58: LGTM!

The CMake presets configuration is well-structured and correctly configures all necessary settings for the ST_NUCLEO144_F767ZI board.

ChibiOS/ST_NUCLEO144_F767ZI/launch.json (2)

43-43: Verify OpenOCD configuration file.

The current configuration uses stm32f769i-disco.cfg, but this is for the F769I board. Consider using a configuration file specific to the F767ZI board.

Please verify if stm32f769i-disco.cfg is compatible with the ST_NUCLEO144_F767ZI board or if a more appropriate configuration file should be used.


8-9: Replace placeholder paths.

The configuration contains placeholder paths that need to be replaced with actual paths:

  • <absolute-path-to-the-toolchain-folder-mind-the-forward-slashes>
  • <path-to-the-repo-root-mind-the-forward-slash>

Please ensure these placeholder paths are replaced with actual paths before using the launch configuration.

Also applies to: 23-24, 26-27

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (1)
azure-pipelines.yml (1)

1415-1434: ⚠️ Potential issue

Add ST_NUCLEO144_F767ZI to build failure reporting.

The new job needs to be added to the Report_Build_Failure job's dependencies to ensure build failures are properly reported.

Add the new job to the dependencies:

    dependsOn:
    - Build_MBN_QUAIL
    - Build_BrainPad2
    - Build_GHI_FEZ_CERB40_NF
    - Build_I2M_ELECTRON_NF
    - Build_I2M_OXYGEN_NF
    - Build_WEACT_F411CE
    - Build_ST_NUCLEO64_F401RE_NF
    - Build_ST_NUCLEO64_F411RE_NF
    - Build_ST_STM32F411_DISCOVERY
    - Build_ST_NUCLEO144_F412ZG_NF
    - Build_ST_NUCLEO144_F746ZG
+   - Build_ST_NUCLEO144_F767ZI
    - Build_ST_STM32F4_DISCOVERY

Also add the job to the failure condition:

    condition: >-
        or(
            failed('Build_MBN_QUAIL'),
            failed('Build_BrainPad2'),
            failed('Build_GHI_FEZ_CERB40_NF'),
            failed('Build_I2M_ELECTRON_NF'),
            failed('Build_I2M_OXYGEN_NF'),
            failed('Build_WEACT_F411CE'),      
            failed('Build_ST_NUCLEO64_F401RE_NF'),
            failed('Build_ST_NUCLEO64_F411RE_NF'),
            failed('Build_ST_STM32F411_DISCOVERY'),
            failed('Build_ST_NUCLEO144_F412ZG_NF'),
            failed('Build_ST_NUCLEO144_F746ZG'),
+           failed('Build_ST_NUCLEO144_F767ZI'),
            failed('Build_ST_STM32F4_DISCOVERY'),
🧰 Tools
🪛 YAMLlint (1.35.1)

[warning] 1416-1416: wrong indentation: expected 4 but found 2

(indentation)

🧹 Nitpick comments (1)
azure-pipelines.yml (1)

911-915: Fix indentation for consistency.

The indentation should be 4 spaces instead of 2 spaces to match the rest of the file.

Apply this diff to fix the indentation:

-  dependsOn: 
-  - Check_Code_Style
+    dependsOn: 
+    - Check_Code_Style

-  pool:
-    vmImage: 'windows-latest'
+    pool:
+        vmImage: 'windows-latest'
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 911-911: trailing spaces

(trailing-spaces)


[warning] 912-912: wrong indentation: expected 4 but found 2

(indentation)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e37454e and c537224.

📒 Files selected for processing (3)
  • ChibiOS/ST_NUCLEO144_F767ZI/CMakePresets.json (1 hunks)
  • ChibiOS/ST_NUCLEO144_F767ZI/common/CMakeLists.txt (1 hunks)
  • azure-pipelines.yml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • ChibiOS/ST_NUCLEO144_F767ZI/common/CMakeLists.txt
  • ChibiOS/ST_NUCLEO144_F767ZI/CMakePresets.json
🧰 Additional context used
🪛 YAMLlint (1.35.1)
azure-pipelines.yml

[error] 911-911: trailing spaces

(trailing-spaces)


[warning] 912-912: wrong indentation: expected 4 but found 2

(indentation)


[error] 920-920: trailing spaces

(trailing-spaces)


[warning] 928-928: wrong indentation: expected 4 but found 2

(indentation)

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Community-Targets (Build_ST_NUCLEO144_F767ZI)
  • GitHub Check: Community-Targets (Check_Code_Style)
  • GitHub Check: Community-Targets (Check_Build_Options)
  • GitHub Check: Community-Targets (Get_Commit_Message)
🔇 Additional comments (2)
azure-pipelines.yml (2)

898-909: LGTM! The job condition is consistent with other jobs.

The condition block correctly checks for the target board in commit messages and build variables, following the established pattern in the pipeline.


927-949: LGTM! The build steps are consistent with other STM32 jobs.

The job correctly uses all the required templates for building STM32 targets, including:

  • Clone and build preparations
  • Git versioning
  • ARM GCC toolchain and Ninja installation
  • Build, package and publish steps
🧰 Tools
🪛 YAMLlint (1.35.1)

[warning] 928-928: wrong indentation: expected 4 but found 2

(indentation)

(just incase).
@networkfusion
Copy link
Member Author

@networkfusion do you still want to move this PR forward? It's open for more than 1.5 years :-)

steped the commits forward to match the repo changes. (untested on the target for the moment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants