Google Git
Sign in
pigweed / pigweed / quickstart / bazel / c7fe00c26a29474bb3d643865d2eb273d3616d73
commitc7fe00c26a29474bb3d643865d2eb273d3616d73[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jun 03 19:27:20 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 03 19:27:20 2024 +0000
tree9519861c0f2b02ad4664b517d91299b16d54ceb2
parent7509a7b4f39bbcb0169c92b58c88d14472a79c54 [diff]
[third_party/pigweed] Roll 2 commits

35450d745f54bdd pw_rpc: Fix hyperlink
61203e8e2b2f9d4 pw_bluetooth: Add HCI StatusCode values

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 04079093944aab1..35450d745f54bdd
Roller-URL: https://ci.chromium.org/b/8746124465398087137
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I9d1e31cd584c3b687dc22984d33e4eead07ff78e
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213633
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: 9519861c0f2b02ad4664b517d91299b16d54ceb2
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!