Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 7fcddb74c9fd3ab88614bc11ebbf603dd02ae4f3
commit7fcddb74c9fd3ab88614bc11ebbf603dd02ae4f3[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Apr 26 18:57:30 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Apr 26 18:57:30 2024 +0000
tree0f23aeb2010ff6b4413e29a834650516a6f2263f
parenta49379e9dd7a60af4f9709d2a27000308d1d9d9d [diff]
[third_party/pigweed] Roll 3 commits

87126e11b80d206 pw_transfer: Assume a minimum window size when res
2593707a02b0c21 pw_toolchain: Add clang-tidy suggestion
b2c733596a777c5 pw_transfer: Attempt to recover when receiving inv

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 5a8cde71ecadfd8..87126e11b80d206
Roller-URL: https://ci.chromium.org/b/8749569041153596321
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ibcf58a14be71b9e00004ca4f2079ec45bf8d8fc2
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206874
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 0f23aeb2010ff6b4413e29a834650516a6f2263f
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!