Google Git
Sign in
pigweed / pigweed / quickstart / bazel / af86d9d212f2c954ce752249267345348f072566
commitaf86d9d212f2c954ce752249267345348f072566[log] [tgz]
authorYuval Peress <peress@pigweed.infra.roller.google.com>Wed Apr 17 15:49:47 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 17 15:49:47 2024 +0000
tree293b61b98964263b119148ceb8f3cdf34ac0657d
parent2521fce7bdcc911a7ed0dc0c8ebf2a3ea05d3102 [diff]
[third_party/pigweed] Roll 2 commits

a4dd94c7fc90cf4 pw_sensor: Add attribute support to sensor-desc CL
44ad59124c1a191 pw_sensor: Create a sensor-desc CLI

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 5b8b84f452c9ced..a4dd94c7fc90cf4
Roller-URL: https://ci.chromium.org/b/8750396229175531553
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I775e3cd764b0c0b9b72c70fd4754c660ae9f01ab
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204093
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: 293b61b98964263b119148ceb8f3cdf34ac0657d
  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!