Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 7d28ede7f709f854b487fa8efc8cce067a1b5aab
commit7d28ede7f709f854b487fa8efc8cce067a1b5aab[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Apr 10 21:44:20 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 10 21:44:20 2024 +0000
treef3977cba7424a84ff0baec7a9397ecd8b35d6c45
parent084394795a308f007a4c1655b1e0e779a10ae2d0 [diff]
[third_party/pigweed] Roll 2 commits

262a9aaf40ddbe6 pw_log_zephyr: Tokenize Zephyr shell fprintf
111df21a5bc108e pw_presubmit: Fix copy/paste bug in _value()

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: e1fa7dc22ad709d..262a9aaf40ddbe6
Roller-URL: https://ci.chromium.org/b/8751008103385416961
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id3a2f4b38daa8df4da24ced9b6f8a7f937a77884
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/202950
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: f3977cba7424a84ff0baec7a9397ecd8b35d6c45
  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!