Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 9cf21738869bffb3382b9bbee888636c11d39cc7
commit9cf21738869bffb3382b9bbee888636c11d39cc7[log] [tgz]
authorDavid Rees <drees@pigweed.infra.roller.google.com>Wed May 08 22:13:57 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 08 22:13:57 2024 +0000
tree063f2297130a993ebc05528972aa5db28d085952
parentfcf98356a6590e0b9879457498d84a91d064522c [diff]
[roll third_party/pigweed] pw_bluetooth_proxy: Removing trailing comma in PW_LOG call

Original-Bug: 326499611
Test: CQ
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/209231
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 84853afa7c9be8e..e6d8fb860af22d8
Roller-URL: https://ci.chromium.org/b/8748469502413690017
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I52a07637e2e54612706227c103279b1822108c28
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209074
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: 063f2297130a993ebc05528972aa5db28d085952
  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!