Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 4c27db01690e2fee528cd44cb345262847a78218
commit4c27db01690e2fee528cd44cb345262847a78218[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat Jul 13 02:44:18 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Jul 13 02:44:18 2024 +0000
treee4be332d52b5d9f53e0a5f3b4b355c507f502380
parent84398c6f6399775b95a9da2caec0366ad6429c67 [diff]
roll: pigweed, pw_toolchain 3 commits

dea5d4d8115fcd6 pw_bluetooth_sapphire: Add Bazel build files
8e469505d647384 pw_system: Add synchronization to pw::System alloc
a27a7371c69cb58 docs: Update changelog

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 990ed9bb2f16bec..dea5d4d8115fcd6
Roller-URL: https://ci.chromium.org/b/8742563737548735505
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I88edb51fee02a68009b72a76b2e729ffcd62414d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222856
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: e4be332d52b5d9f53e0a5f3b4b355c507f502380
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!