Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 4f71bc9a15e78957ff9cce4abe44157c9fe45815
commit4f71bc9a15e78957ff9cce4abe44157c9fe45815[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Aug 07 20:26:16 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 07 20:26:16 2024 +0000
tree706b537e71f6bf8e345d69106a4648a235d45df3
parent0397ae9440cebbae2ce199c458f1bc38699115d9 [diff]
roll: pigweed, pw_toolchain 3 commits

9e1ed90cd304c1b pw_bluetooth_sapphire: Handle switch warning with
d3dbe8c29f5acf9 pw_bluetooth_sapphire: Write Variable PIN Type for
5142577e6a89912 pw_bluetooth_sapphire: Add LegacyPairingState to B

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 4034273a4c9ddf0..9e1ed90cd304c1b
Roller-URL: https://ci.chromium.org/b/8740231939733014209
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic0a3fb1dfe4ac922fea573726055cd54b6a18d7f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/228334
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 706b537e71f6bf8e345d69106a4648a235d45df3
  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!