Merge branch 'raspberrypi:master' into pioasm-wrap-dot-word

Author: magy00

.bazelignore

@@ -4,3 +4,7 @@ common --host_per_file_copt=external/.*@-w
 
 # Produce useful output when the build fails.
 common --verbose_failures
+
+# Silence warnings about old bazel_dep pins. Bazel 8 brings along newer ones,
+# but we can support Bazel 7 (for now).
+common --check_direct_dependencies=off

.bazelrc

@@ -1 +1 @@
-7.2.1
+8.1.0

.bazelversion

@@ -0,0 +1,27 @@
+name: Check Board Headers
+
+on:
+  push:
+    paths:
+      - 'src/boards/include/boards/**'
+      - 'tools/check_board_header.py'
+      - 'tools/check_all_board_headers.sh'
+      - '.github/workflows/check_board.yml'
+  pull_request:
+    paths:
+      - 'src/boards/include/boards/**'
+      - 'tools/check_board_header.py'
+      - 'tools/check_all_board_headers.sh'
+      - '.github/workflows/check_board.yml'
+
+jobs:
+  check-board-headers:
+    if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name != github.event.pull_request.base.repo.full_name
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Check Board Headers
+        run: |
+          tools/check_all_board_headers.sh

.github/workflows/check_board.yml

@@ -0,0 +1,33 @@
+name: Check Configs
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  check-configs:
+    if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name != github.event.pull_request.base.repo.full_name
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Check Build Defines
+        if: always()
+        run: |
+          tools/extract_build_defines.py .
+
+      - name: Check CMake Configs
+        if: always()
+        run: |
+          tools/extract_cmake_configs.py .
+      
+      - name: Check CMake Functions
+        if: always()
+        run: |
+          tools/extract_cmake_functions.py .
+
+      - name: Check Configs
+        if: always()
+        run: |
+          tools/extract_configs.py .

.github/workflows/check_configs.yml

@@ -2,5 +2,4 @@
 <packages>
   <package id="gcc-arm-embedded" version="10.2.1" />
   <package id="mingw" version="12.2.0" />
-  <package id="ninja" version="1.12.1" />
 </packages>

.github/workflows/choco_packages.config

@@ -0,0 +1,28 @@
+name: Make sure PRs target the develop branch
+
+on:
+  pull_request_target:
+
+# By default, pull_request_target gets write permissions to the repo - this prevents that
+permissions:
+  pull-requests: write
+
+jobs:
+  check-branch:
+    if: github.event.pull_request.base.ref == 'master'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Add comment
+        uses: actions/github-script@v7
+        with:
+          script: |
+            github.rest.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: 'Please do not submit against `master`, use `develop` instead'
+            })
+      - name: Throw error
+        run: |
+          echo "::error title=wrong-branch::Please do not submit against 'master', use 'develop' instead"
+          exit 1

.github/workflows/pr-check.yml

@@ -1,12 +1,12 @@
 module(
     name = "pico-sdk",
-    version = "2.1.2-develop",
+    version = "2.2.0",
 )
 
 bazel_dep(name = "platforms", version = "0.0.9")
 bazel_dep(name = "bazel_skylib", version = "1.6.1")
 bazel_dep(name = "rules_python", version = "0.36.0")
-bazel_dep(name = "picotool", version = "2.1.1")
+bazel_dep(name = "picotool", version = "2.2.0")
 bazel_dep(name = "rules_cc", version = "0.0.10")
 
 http_archive = use_repo_rule("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

MODULE.bazel

@@ -177,12 +177,11 @@ instructions for other platforms, and just in general, we recommend you see [Ras
 1. Setup a CMake build directory.
       For example, if not using an IDE:
       ```
-      $ mkdir build
-      $ cd build
-      $ cmake ..
-      ```   
+      $ cmake -S . -B build
+      ```
+      > The cmake -S flag indicates the source directory, and the -B flag tells cmake the name of the output-directory to create. This doesn't have to be named "build", you can call it whatever you want.
    
-   When building for a board other than the Raspberry Pi Pico, you should pass `-DPICO_BOARD=board_name` to the `cmake` command above, e.g. `cmake -DPICO_BOARD=pico2 ..` or `cmake -DPICO_BOARD=pico_w ..` to configure the SDK and build options accordingly for that particular board.
+   When building for a board other than the Raspberry Pi Pico, you should pass `-DPICO_BOARD=board_name` to the `cmake` command above, e.g. `cmake -S . -B build -DPICO_BOARD=pico2` or `cmake -S . -B build -DPICO_BOARD=pico_w` to configure the SDK and build options accordingly for that particular board.
 
    Specifying `PICO_BOARD=<boardname>` sets up various compiler defines (e.g. default pin numbers for UART and other hardware) and in certain 
    cases also enables the use of additional libraries (e.g. wireless support when building for `PICO_BOARD=pico_w`) which cannot
@@ -193,11 +192,32 @@ instructions for other platforms, and just in general, we recommend you see [Ras
 
 1. Make your target from the build directory you created.
       ```sh
-      $ make hello_world
+      $ cmake --build build --target hello_world
       ```
+      > The directory-name supplied to the `--build` flag needs to match the directory-name that was passed to the `-B` flag in the earlier cmake command.
 
 1. You now have `hello_world.elf` to load via a debugger, or `hello_world.uf2` that can be installed and run on your Raspberry Pi Pico-series device via drag and drop.
 
 # RISC-V support on RP2350
 
 See [Raspberry Pi Pico-series C/C++ SDK](https://rptl.io/pico-c-sdk) for information on setting up a build environment for RISC-V on RP2350.
+
+## RISC-V quick start
+
+The [pico-sdk-tools](https://github.com/raspberrypi/pico-sdk-tools/releases) repository contains some prebuilt versions of the RISC-V compiler.
+
+You can use these to get a working RISC-V compiler on Raspberry Pi OS for example.
+
+```
+wget https://github.com/raspberrypi/pico-sdk-tools/releases/download/v2.0.0-5/riscv-toolchain-14-aarch64-lin.tar.gz
+sudo mkdir -p /opt/riscv/riscv-toolchain-14
+sudo chown $USER /opt/riscv/riscv-toolchain-14
+tar xvf riscv-toolchain-14-aarch64-lin.tar.gz -C /opt/riscv/riscv-toolchain-14
+```
+
+To use the RISC-V compiler to build code you need to set a couple of environment variables and run cmake from fresh.
+
+```
+export PICO_TOOLCHAIN_PATH=/opt/riscv/riscv-toolchain-14/
+export PICO_PLATFORM=rp2350-riscv
+```

README.md

@@ -0,0 +1,10 @@
+ignore_directories(
+    [
+        # Don't accidentally pick up external CMake deps with Bazel build files.
+        "cmake-*",
+        "build",
+        "build-*",
+        # Don't treat submodules as part of this project.
+        "lib",
+    ],
+)