Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 5d7c5e67bcbaa8f5fb570f7270869f0931fd8804
commit5d7c5e67bcbaa8f5fb570f7270869f0931fd8804[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jul 18 00:31:09 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 18 00:31:09 2024 +0000
tree23fd03d6b45e7b89820a38b7c24409ab66bd39ad
parent98bb169af76cdfaed538abdaae0fd5bf45d6de6c [diff]
roll: pigweed, pw_toolchain 2 commits

5592c7588a11a66 pw_bluetooth_sapphire: Fix camel case for CIS acro
6f990918d3f2ee6 pw_bluetooth_sapphire: Cleanup Inquiry command pac

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 003bbe28674612a..5592c7588a11a66
Roller-URL: https://ci.chromium.org/b/8742119135659436625
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id00d5a8078c3092cc3d9e5ae5acbd87104e89622
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223972
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: 23fd03d6b45e7b89820a38b7c24409ab66bd39ad
  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!