| commit | bbaf989c9e19ab0f7053d33255582d56bde12796 | [log] [tgz] |
|---|---|---|
| author | Armando Montanez <amontanez@pigweed.infra.roller.google.com> | Fri May 24 16:19:41 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 24 16:19:41 2024 +0000 |
| tree | 155407456bcc312abda2872280ba9270c7f7554b | |
| parent | 89cbe787e0e253210a507e94ae84d7a0d5d5d6eb [diff] |
[roll third_party/pigweed] bazel: Explicitly load rules_python in BUILD.bazel files Some Bazel build files were not explicitly using Python rules from rules_python, which will soon cause breakages when rules_python is updated. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/211361 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: e0af1981782a05e..b658add873a975a Roller-URL: https://ci.chromium.org/b/8747042242368644529 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I6ff53630f2de906e50cc55d53d211b6201d18d75 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/211540 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
git clone --recursive https://pigweed.googlesource.com/pigweed/quickstart/bazel
If you already cloned but forgot to include --recursive, run git submodule update --init to pull all submodules.
TODO: b/300695111 - Don't require submodules for this example.
We‘ll assume you already have Bazel on your system. If you don’t, the recommended way to get it is through Bazelisk.
To build the entire project (including building the application for both the host and the STM32 Discovery Board), run
bazel build //...
To run the application locally on your machine, run,
bazel run //src:echo
To flash the firmware to a STM32F429 Discovery Board connected to your machine, run,
bazel run //tools:flash
Note that you don't need to build the firmware first: Bazel knows that the firmware images are needed to flash the board, and will build them for you. And if you edit the source of the firmware or any of its dependencies, it will get rebuilt when you flash.
Run,
bazel run //tools:miniterm -- /dev/ttyACM0 --filter=debug
to communicate with the board. When you transmit a character, you should get the same character back!