Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 3aaa18d1f2f174acae71c4923b7628550d9a0b29
commit3aaa18d1f2f174acae71c4923b7628550d9a0b29[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu May 16 01:13:28 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 16 01:13:28 2024 +0000
treef8b65f7319781292b9b5f18fd59108d2cd9a22a7
parent73a3ee3eb7160eb2d79c961978bb7cc0a94e7186 [diff]
[third_party/pigweed] Roll 5 commits

843bd1cf3b198a4 pw_transfer: Add tests for GetResourceStatus
44c6eb538a67ad6 pw_env_setup: Bazel support for config_file
137e8b7fe7ade32 bazel: Ignore reformatting change in git blame
8c39d4026adc12f pw_presubmit: Auto fix unsorted-dict-items
6b1323857437a22 third_party/perfetto: Rename proto targets

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 7c4acea38d79a7f..843bd1cf3b198a4
Roller-URL: https://ci.chromium.org/b/8747824047310455633
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ida532153be55785e67c6b00e7e09d75f056d9a2c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210123
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>
1 file changed
tree: f8b65f7319781292b9b5f18fd59108d2cd9a22a7
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  13. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

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.

Building

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

Flashing

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.

Communicating

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!