Google Git
Sign in
pigweed / pigweed / quickstart / bazel / ba56b5249f9f5e51737e73a16badd07c2f44b10e
commitba56b5249f9f5e51737e73a16badd07c2f44b10e[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Jun 28 05:38:23 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 28 05:38:23 2024 +0000
tree0a9b0a7a3edfc198c60bfb72d8c425e7c6a65702
parentdb9c6129ddf82ca9ab0aa271be9a2c9fd464bce4 [diff]
roll: pigweed, pw_toolchain 3 commits

4c71a9ac34f0607 pw_bluetooth_proxy: Prevent crash in GattNotifyTes
bd7063ab2ecc84a pw_bluetooth_sapphire: Remove now unnecessary use
305dfea3e54f7cf pw_bluetooth_sapphire: Expose connection role to l

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: dbf80df17b1f1a5..4c71a9ac34f0607
Roller-URL: https://ci.chromium.org/b/8743912090578350417
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1cbdb376985a8233db27d3f393d06e5b07ef7b9f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218794
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: 0a9b0a7a3edfc198c60bfb72d8c425e7c6a65702
  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!