Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 02994a562161fd3ddb78eedf08eb1166e9dec484
commit02994a562161fd3ddb78eedf08eb1166e9dec484[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri May 31 19:34:55 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 31 19:34:55 2024 +0000
treefb55dc5f01980d2005779b2ca7b0b0ed41f760cf
parent2b50580d03398da6b46322559f4da43bcca1af3d [diff]
[third_party/pigweed] Roll 3 commits

1f6ad3a910c7cb0 pw_multibuf: SimpleAllocatorForTest
7bb5a76cced7e77 docs: Update changelog
201c503d9d3f066 pw_build: Add pw_elf_to_bin rule

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