Google Git
Sign in
pigweed / pigweed / quickstart / bazel / ed164f498cd5d695037e8b5a3ac6df5b4e1d5454
commited164f498cd5d695037e8b5a3ac6df5b4e1d5454[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed May 01 01:00:49 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 01 01:00:49 2024 +0000
treeb4c0d453867393273b3a4e61857495d4b7d1e81f
parent8e545af9b770d9dd0b163ee4d5d52e331bb156e5 [diff]
[third_party/pigweed] Roll 3 commits

26f064159c278b2 pw_bluetooth_proxy: Delete policies functionality
e3a20766f69442f pw_bluetooth: Sync with recent APCF changes
aa6b152d30aa3cc pw_rpc: Add private method for sending internal::P

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 299330f742b9c86..26f064159c278b2
Roller-URL: https://ci.chromium.org/b/8749183779239748433
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I48b52c88ad91c537d85525a574afb17c95443dcf
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207634
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: b4c0d453867393273b3a4e61857495d4b7d1e81f
  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!