Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1361330f9e315a06bcdc065455967ae87a912404
commit1361330f9e315a06bcdc065455967ae87a912404[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Jun 28 23:40:41 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 28 23:40:41 2024 +0000
treeead2544254a75b2876ef68917f7ada248bd48665
parentf6296b5d344eb6e1edda18358670bcc69b43abd0 [diff]
roll: pigweed, pw_toolchain 4 commits

f588ba91c9de167 pw_unit_test: Fix CMake test runner argument forwa
cbd621a85af48c3 pw_digital_io_rp2040: Remove manual tags
93f268c644dd869 pw_system: RunOnce function for work queue functio
11aebdc3411c93b pw_thread: Remove backend multiplexers

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: e12c9358911b3b2..f588ba91c9de167
Roller-URL: https://ci.chromium.org/b/8743844105167495281
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I6f8ba90a632231e8b8253bfe9c630b0c66a264e2
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218783
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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: ead2544254a75b2876ef68917f7ada248bd48665
  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!