Google Git
Sign in
pigweed / pigweed / quickstart / bazel / fd96f986d9f2d5140e931d24eee7edabb951e1f8
commitfd96f986d9f2d5140e931d24eee7edabb951e1f8[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Aug 07 23:09:40 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 07 23:09:40 2024 +0000
tree184e0667f69f0443a7cea66b962003176a643743
parentc66ede4a5f4c4548d2c95d9f6f3e39e35c953c84 [diff]
roll: pigweed, pw_toolchain 5 commits

28d16ef6f95b032 pw_ide: Show progress bar on manual refreshes
fcb5ead44b10d2c pw_ide: Detect manual target change in settings
a5271e92732267f third_party/icu: Remove ICU
2dd66edd629aee6 pw_web: Add resize handler to message col
e004f5f292dd9d6 pw_allocator: Fix bucketed block corruption

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: e6af48396fd8c94..28d16ef6f95b032
Roller-URL: https://ci.chromium.org/b/8740221700637032881
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I2b7231924e1c284d303b3bb3adbe31f1698d90a1
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/228339
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: 184e0667f69f0443a7cea66b962003176a643743
  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!