| commit | afbf8d13b255e741eaefd4ece85f99925b2a57a9 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Mar 27 18:33:05 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 27 18:33:05 2024 +0000 |
| tree | a7352032a3239615da03541eeb044df5bcf21889 | |
| parent | 41e03d9180f56de6b74066d0e47aeb65bd1a460a [diff] |
[third_party/pigweed] Roll 7 commits 130b688924ea31a pw_bluetooth_proxy: Use emboss OpCode enum 82c19ed1527c398 pw_bluetooth: Add opcode_full field to emboss HCI b548637dd52cd3c pw_bluetooth: Add enum for opcodes 69d666a1346461d pw_transfer: Make numerous logging adjustments 7fb4c2175d65dfe pw_build_android: Define rule with static libs 12c8670b26f1ec1 pw_bluetooth: Update cmake targets to be consisten 479644ebbce49bf pw_bluetooth: Update build files to be consistent https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 93558a01ab8e995..130b688924ea31a Roller-URL: https://ci.chromium.org/b/8752288505528218929 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I1a1eda82db8fad59d5de71e61c08e692dc2f0568 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200731 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
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.
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
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.
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!