| commit | ca0918ad0ae09ea6250f0327d8ee1d913b30854e | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Apr 18 21:51:31 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 18 21:51:31 2024 +0000 |
| tree | fa90028af3e964a55ab8ebea0b995b7f97f4f231 | |
| parent | d47a460b2d297e94fa383348d5bc7c125a155892 [diff] |
[third_party/pigweed] Roll 2 commits
463dca050a46608 pw_web: Support creating client without using prot
2ea6211c76a8666 pw_{rpc,protobuf}: Access raw proto values; change
https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: a82ae449503ad71..463dca050a46608
Roller-URL: https://ci.chromium.org/b/8750282909785320305
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I2f6fcd405dae5659ebc04889b75a8c4e993d0d68
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204610
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!