Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a79516a5f698dd179edb65efe378e0731a433a2b
commita79516a5f698dd179edb65efe378e0731a433a2b[log] [tgz]
authorWyatt Hepler <hepler@pigweed.infra.roller.google.com>Thu May 09 19:08:28 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 09 19:08:28 2024 +0000
treeabf8a28725cbdf0748dd5bccb56ef75483738ed6
parent8c5dc2e8480a9420c876a80db6ec105d8eb5054e [diff]
[roll third_party/pigweed] pw_rpc: Update docs for channel ID remapping

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/209431
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 56b3cbf0ec8010a..12fda3bfe435881
Roller-URL: https://ci.chromium.org/b/8748390580424859537
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I87d6661c965cf5b0593e47744173115559644b47
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209079
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: abf8a28725cbdf0748dd5bccb56ef75483738ed6
  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!