Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a20c2c0792aae45ffc41eed1d28c67df106b8c3f
commita20c2c0792aae45ffc41eed1d28c67df106b8c3f[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Jun 28 02:32:07 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 28 02:32:07 2024 +0000
treeb9eccfbbddca089c3c8181816b87c091bf900091
parentfb2b1da307ca80059b024461b0ac4a0719e88a5b [diff]
roll: pigweed, pw_toolchain 3 commits

77630d60f4d98ff pw_bluetooth_sapphire: Fix typo in comment
1a6e58dd3709e38 pw_bluetooth_sapphire: Move LegacyLowEnergyScanner
2dd1d3048799f2f pw_bluetooth_sapphire: Revert "remove now unnecess

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 07994af5927683a..77630d60f4d98ff
Roller-URL: https://ci.chromium.org/b/8743923422406589297
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3d2c36da64a12f9d8cfacd73dd700d4f78b56546
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218776
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: b9eccfbbddca089c3c8181816b87c091bf900091
  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!