| commit | 048c93aec34692745e47c69b45e7222dc5ca7393 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed May 01 19:02:10 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 01 19:02:10 2024 +0000 |
| tree | a80da7c246d3d7b37c4b89f10e66e510171b3142 | |
| parent | f8607cc38903afc65b8bd1c29ced57f7141a986d [diff] |
[third_party/pigweed] Roll 8 commits 71017480adf7fb1 boringssl: Add cmake integration 63e6774b2b84f81 pw_bluetooth: Add header alias in command complete 58a80c6548797d2 pw_bluetooth_proxy: Rename ProcessH4* to HandleH4* e0a6e32b38b20eb pw_bluetooth_proxy: Rename passthrough_test.cc to ac1d46f720ff626 roll: clang-next b890f6af0b74e9a pw_web: Fix icons in packaged version 74efe356798f1e7 pw_tls_client: Add cmake facades 08d5e68858f9e26 pw_grpc: Support fragmented gRPC messages if an al https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: b572538413b3dcc..71017480adf7fb1 Roller-URL: https://ci.chromium.org/b/8749115794631732865 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I15bdba031cb69fe36424b06b15f85c4e66f25161 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207577 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!