Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 5f56f69bda2e48cf6b424a1ba315d9f2f921c632
commit5f56f69bda2e48cf6b424a1ba315d9f2f921c632[log] [tgz]
authorLulu Wang <luluwang@pigweed.infra.roller.google.com>Fri Jun 21 20:25:24 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 21 20:25:24 2024 +0000
tree2e6361a818cbe35ace48edefe94e9d0072e51201
parent51fe0137be680e63cefce7d5323c6ec578fa2526 [diff]
roll: pw_toolchain, pw_toolchain: pw_bluetooth: Add PinCodeRequestNegativeReplyCommand Emboss struct

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

https://pigweed.googlesource.com/pigweed/pigweed
pw_toolchain, pw_toolchain Rolled-Commits: 81b9531df0d3fcb..3eb5b9bc5991940
Roller-URL: https://ci.chromium.org/b/8744490097479651313
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I7d3e3c2d2f8201d75d45921e33a2c8600d982763
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217492
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: 2e6361a818cbe35ace48edefe94e9d0072e51201
  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!