Google Git
Sign in
pigweed / pigweed / quickstart / bazel / ed7b9951d9394094362f30f3cf05c702181c4453
commited7b9951d9394094362f30f3cf05c702181c4453[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue May 14 19:12:36 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 14 19:12:36 2024 +0000
tree33b2e46a156567de0f1a49f015cd77b8be271bb4
parent9dd245485245f99d9cba4ff7c2aaa6ad529a5b30 [diff]
[third_party/pigweed] Roll 3 commits

077ce0610af5305 third_party/perfetto: Add third party perfetto rep
042145933488ae0 pw_async2: Add Coro<T> coroutine API
bfcaab8edf331e4 third_party/perfetto: Copybara import

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 170ad30163fb5ab..077ce0610af5305
Roller-URL: https://ci.chromium.org/b/8747937344029260273
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I6976c78278a5f2a75c6e6c4401928125c3c944dd
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209874
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 33b2e46a156567de0f1a49f015cd77b8be271bb4
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!