commit | 444d420e0ca935a1012c7e64aa6e5c94b14cb053 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Apr 24 18:55:55 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 24 18:55:55 2024 +0000 |
tree | a875149893cb779c67bdd846464f2e54f3c3b6ed | |
parent | 213b66c1d478c8f3aab909594b42a86bdbb4290a [diff] |
[third_party/pigweed] Roll 4 commits 96dee917b1ede10 SEED-0124: Getting Used Size from Multisink 4dad2cbb2bd183c pw_bluetooth_proxy: Add some emboss helper functio d55154afdb9d9a3 pw_bluetooth_proxy: Template test emboss packet cr c7f27e2026d681c .bazelversion: Add file https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 6f9099b2b688bf6..96dee917b1ede10 Roller-URL: https://ci.chromium.org/b/8749750331150149633 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I9ea7af0a3b6db56b569c4a0b50e6f92247ef8da2 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206212 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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!