Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 918d9f8d491bb5c1286676648ca442c2ca69035b
commit918d9f8d491bb5c1286676648ca442c2ca69035b[log] [tgz]
authorAli Saeed <saeedali@pigweed.infra.roller.google.com>Mon Jun 24 09:43:54 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 24 09:43:54 2024 +0000
treeac9129130aab2678d3e322fee8c07a9e1f37b84c
parent32f75e1a20fdc978cfbff656ead41ab309e90a4c [diff]
roll: pigweed, pw_toolchain: pw_bluetooth: Add att.emb

Introduce Emboss definitions for the Attribute Protocol.

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 7ad2bee3e541072..c510c7e8e49153d
Roller-URL: https://ci.chromium.org/b/8744258673358366513
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I063e2112ffd9dbcf19f255088b11016d4af13539
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217674
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: ac9129130aab2678d3e322fee8c07a9e1f37b84c
  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!