Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 3716867aa2d1947d47a84856ebed0f5abc3c9342
commit3716867aa2d1947d47a84856ebed0f5abc3c9342[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jul 29 22:51:27 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 29 22:51:27 2024 +0000
tree3a1fd0068b82085e4d7020e182bc723884f318c7
parent64ff78f20f31cc3c06f6df046107aabfe12210c5 [diff]
roll: pigweed, pw_toolchain 3 commits

262f3ce7028d220 pw_bluetooth_proxy: Only log disconnect events for
c9e99bb603446a8 pw_system: Save snapshots to /tmp
d6d9edae2f8faf4 pw_system: Make crash detection logs louder

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 7bbbec8a98bcf12..262f3ce7028d220
Roller-URL: https://ci.chromium.org/b/8741038221197568481
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1fbc4d7c0ec62e079fe7c5970aedd5ac276320e3
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226413
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: 3a1fd0068b82085e4d7020e182bc723884f318c7
  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!