Google Git
Sign in
pigweed / pigweed / quickstart / bazel / b2826e24d2afd9e9bfb439ca306794e293b54f55
commitb2826e24d2afd9e9bfb439ca306794e293b54f55[log] [tgz]
authorWyatt Hepler <hepler@pigweed.infra.roller.google.com>Thu May 30 19:24:20 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 30 19:24:20 2024 +0000
tree29528707ef6e346ab278e9ff2cc02cd1e3c910de
parent285f70032c52b4b6c14b5879fa460823b972d715 [diff]
[third_party/pigweed] Roll 2 commits

9913b3beb9551d4 pw_channel: Only open read/write if channel is rea
ed678303dec5a41 pw_thread: Fix thread snapshot service test

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: e07a08914d79ea1..9913b3beb9551d4
Roller-URL: https://ci.chromium.org/b/8746487043944172561
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I2f447fe899d84e3e358a59907fedc97ff9650927
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/212371
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: 29528707ef6e346ab278e9ff2cc02cd1e3c910de
  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!