Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 0125c852adeae254dfa25ae0391d6c3514dfa8ab
commit0125c852adeae254dfa25ae0391d6c3514dfa8ab[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jul 25 02:02:07 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 25 02:02:07 2024 +0000
tree9c7507d1bce5697bcb7b16c9da68e7c24779c147
parentbb8b5a76ed927a2ace9f37cf78c7e3bde5a8e014 [diff]
roll: pigweed, pw_toolchain 4 commits

e82bb11ee931b92 pw_console: Fix RPC autocompletion in web kernel
4d38f4611153ced emboss: Update emboss repo to v2024.0718.173957
a158415a5c07e71 pw_system: Enable crash handler in async system
4b3e53050bbc33c pw_ide: Update vendored tools on extension update

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: d04920d78848a69..e82bb11ee931b92
Roller-URL: https://ci.chromium.org/b/8741479183322680193
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie255e8ee227dca0b0bddc321fad1d635c9410c1b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226013
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 9c7507d1bce5697bcb7b16c9da68e7c24779c147
  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!