Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 73373c9b79b8ad76d73c874d87e239de26011b82
commit73373c9b79b8ad76d73c874d87e239de26011b82[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Mar 26 21:37:52 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Mar 26 21:37:52 2024 +0000
treee1a666722c3e1f3443b7b6f1d6af43105ef7205b
parent17558f3cfc5eeeb66c4456b519f918232887ec7a [diff]
[third_party/pigweed] Roll 7 commits

e0abef00c07545a pw_multibuf: Define as cc_static_library
cb32298c56d1b71 pw_log_null: Define as cc_static_library
7cffdd83bfd413c pw_thread: Follow Soong guidance
7682e4abe456481 pw_allocator: Add allocation detail storage to Tra
ebcc8c717f3980d pw_channel: Add loopback channel
72a1d6f484ecbd1 pw_toolchain: Remove unusued source set
16d3c47ab5a6d45 pw_status: Add StatusWithSize::size_or

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 55b88ef80fc2403..e0abef00c07545a
Roller-URL: https://ci.chromium.org/b/8752367827875210609
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I357d7e743825a58c6290d6a77d73585519eb624a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200154
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: e1a666722c3e1f3443b7b6f1d6af43105ef7205b
  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/example/echo

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!