| commit | 7f572d6c69c9b8e061c3775426835b61b2ed4708 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri May 03 22:03:42 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 03 22:03:42 2024 +0000 |
| tree | 005df8bc3249d0887e0277dbb0e543000573048d | |
| parent | a0af8177e5221eb63673c77553749ae0fbfd34bf [diff] |
[third_party/pigweed] Roll 7 commits c3d2877b7aa6c78 pw_rpc: Fix macro name in docs and comments d0ff89e952d68de pw_toolchain: Fix CMake build on macOS d5f3adeb5cafd73 pw_protobuf_compiler: Fix bazel failure if proto d fc8d0557e06a367 pw_protobuf_compiler: Add a no_prefix test ac388e7bdae6d03 pw_ide: Raise specific error on bad settings file 6920d0bb3b6898a pw_protobuf_compiler: Tests fail to build under cm 3aa838ba32d99bb pw_allocator: Improve namespacing https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 89c90454a256760..c3d2877b7aa6c78 Roller-URL: https://ci.chromium.org/b/8748923141497958545 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I57d68867741eca292a3d65ebc2436fd0c97b47d9 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208029 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!