Google Git
Sign in
pigweed / pigweed / quickstart / gn / dc438d4dfe34fb1a391898e9b304b1d369c6e39f
commitdc438d4dfe34fb1a391898e9b304b1d369c6e39f[log] [tgz]
authorFaraaz Sareshwala <fsareshwala@pigweed.infra.roller.google.com>Thu Apr 18 15:50:44 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 18 15:50:44 2024 +0000
treea0357828c9cee29aa36ed8518d06ca855fdce0a1
parent5a0b2abc02b04e6e37f04c625634de0bb1a5e28c [diff]
[roll third_party/pigweed] pw_bluetooth: LEGetVendorCapabilitiesCommandCompleteEvent v1.04 fields

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/204198

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 0f2396924cd89a6..bc019dca4f4f1a3
Roller-URL: https://ci.chromium.org/b/8750305571357853905
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I141766d964d559142fef9f5b0a87cd9f44fc2328
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204490
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: a0357828c9cee29aa36ed8518d06ca855fdce0a1
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!