Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 0d6c78eede189413cc9fe3303df69daf2296916c
commit0d6c78eede189413cc9fe3303df69daf2296916c[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri May 17 01:14:09 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 17 01:14:09 2024 +0000
tree710aa1ce3b0e51bb9cc6f0ee436d124c55b8f554
parente4e6822993dbec8d60fa6cef8892fce1e0c0f31e [diff]
[third_party/pigweed] Roll 2 commits

770fffc2d741fc5 pw_transfer: End active transfers when RPC stream
3a93dbec943d0aa pw_config_loader: Add missing types dep

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: fe3b300897488d8..770fffc2d741fc5
Roller-URL: https://ci.chromium.org/b/8747733404805155553
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iee7a8ba632bb18fbf9e0df94df54c51f5f7a426f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210279
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: 710aa1ce3b0e51bb9cc6f0ee436d124c55b8f554
  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!