Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a49379e9dd7a60af4f9709d2a27000308d1d9d9d
commita49379e9dd7a60af4f9709d2a27000308d1d9d9d[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Apr 26 00:57:14 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Apr 26 00:57:14 2024 +0000
tree76b6797dc5edf32638318d13ceee2665f8553e59
parentf2f04d8c7af36709541d8f9790e56fbdc7ab549a [diff]
[third_party/pigweed] Roll 2 commits

5a8cde71ecadfd8 pw_rust: Fix Rust tokenized logging example
144ac20a8cbfa3f pw_module: Include :authors: in generated SEED fil

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 55f718e19c789f7..5a8cde71ecadfd8
Roller-URL: https://ci.chromium.org/b/8749637020583979345
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If2a8c8e031eb6b55112b1987ff0a2606e36b3281
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206692
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 76b6797dc5edf32638318d13ceee2665f8553e59
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!