Google Git
Sign in
pigweed / pigweed / quickstart / bazel / f8607cc38903afc65b8bd1c29ced57f7141a986d
commitf8607cc38903afc65b8bd1c29ced57f7141a986d[log] [tgz]
authorDavid Rees <drees@pigweed.infra.roller.google.com>Wed May 01 04:01:04 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 01 04:01:04 2024 +0000
tree17ac702826d84e80cc06443b75243b884d083aa2
parented164f498cd5d695037e8b5a3ac6df5b4e1d5454 [diff]
[third_party/pigweed] Roll 4 commits

b572538413b3dcc pw_bluetooth: Add Event Codes to emboss
de89ebf66fe51fa pw_bluetooth: Add opcode_enum to command and respo
e84673095f8d862 pw_bluetooth_proxy: Move ProxyHost methods to .cc
5c47f7009f66838 pw_bluetooth_proxy: Rename HciProxy to ProxyHost

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 26f064159c278b2..b572538413b3dcc
Roller-URL: https://ci.chromium.org/b/8749172448451709681
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iec86a1a5baf902be30a07bb06df0524f931112c7
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207574
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: 17ac702826d84e80cc06443b75243b884d083aa2
  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!