Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 2c3240dcb247db57c434bcbb5cece92b68dd6220
commit2c3240dcb247db57c434bcbb5cece92b68dd6220[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat Jul 13 17:57:22 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Jul 13 17:57:22 2024 +0000
tree0486efc974d58e9f0abce28152e85e411cec29e4
parentf52285d7854486f0ab936050f0601cf86a7dce02 [diff]
roll: pigweed, pw_toolchain 3 commits

b216eb7fb3a472d pw_bluetooth_sapphire: Pass hci::AdvertisingInterv
505638596e1ea63 pw_bluetooth_sapphire: Shorten pw::bluetooth::embo
071670f2a8e7309 pw_bluetooth_sapphire: Pass extended_pdu booleans

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 351c9a45b2099b6..b216eb7fb3a472d
Roller-URL: https://ci.chromium.org/b/8742506694415286225
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib0663cc126b9ecde3ddbb369000b4952204426e8
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222647
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: 0486efc974d58e9f0abce28152e85e411cec29e4
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!