Google Git
Sign in
pigweed/pigweed/quickstart/bazel/370a694cab87834fc3b671e25d02cc96c2072f46
commit
370a694cab87834fc3b671e25d02cc96c2072f46
[log]
author
Josh Conner <joshconner@pigweed.infra.roller.google.com>
Fri Jul 19 23:27:26 2024 +0000
committer
CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri Jul 19 23:27:26 2024 +0000
tree
30f7bb1c2350fade4408f15863afd0a54cb6a876
parent
d761c36b22b9835c0742db169b29a96297532dc0 [diff]
roll: pigweed, pw_toolchain: pw_bluetooth: Add generic HCI command definition

Add a generic HCI command definition, to support the creation of
arbitrary command packets in emboss. One immediate use case for
this is the generation of vendor-specific commands.

Original-Bug: b/42167863
Test: pw presubmit --step gn_chre_googletest_nanopb_sapphire_build
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/224931
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: d39a9561840c8fe..44e7233eced4907
Roller-URL: https://ci.chromium.org/b/8741941887816936065
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I8c19b5449ad8d6f502ad02a01ca7ac7c90e92fd7
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225132
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: 30f7bb1c2350fade4408f15863afd0a54cb6a876
  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!