Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 92d6d1aa5208b2071b5580da1e6f0ced23600752
commit92d6d1aa5208b2071b5580da1e6f0ced23600752[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Apr 04 21:39:25 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 04 21:39:25 2024 +0000
tree236b59ae9d8f52645d3dadcf50ff0cd83dcaab25
parente737dc1cbd43f711a0e5a01912910d3336c5d8f2 [diff]
[third_party/pigweed] Roll 2 commits

3f89c18fdffd43f pw_module: Jinja template refactor
6222b1097d11fb1 docs: Update reST style guide

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