| commit | 65ef76f7049621262124f4d3bcff49b326ef5fd4 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Jun 04 21:13:43 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 04 21:13:43 2024 +0000 |
| tree | b5306a8cb3794317adeb8a9098f85ed8cda1f7e0 | |
| parent | 69c30ba31aa3105708fb26a30474e4f4988eae7b [diff] |
[third_party/pigweed] Roll 7 commits 0f2537e5f13d9fd third_party: Add probe-rs ad079700b6f69ef pw_async2: Fix location of backends in sitenav 4be3dbc86c04e9d pw_presubmit: Remove shellcheck from lintformat pr 81b6bdb4fd457de pigweed.json: Add config for Bazel builders 2c8183903bf9b6e docs: Update homepage tagline 76902e6d4a7fa3c rp2040: Support bazel wildcard build on rp2040 dea891ac18bee92 pw_bluetooth_proxy: Fix compilation errors https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 5f164749a2bb256..0f2537e5f13d9fd Roller-URL: https://ci.chromium.org/b/8746027192268056785 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I080043b5e1dfe3839bcb0f4e6f079e0a70adde0c Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213880 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!