commit | 3b1a47d27b7beb6edf6408068eb80ea4431ed8fd | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue May 07 22:06:54 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 07 22:06:54 2024 +0000 |
tree | 6f3a4be9cd15dd7cae93071da286c4e7ec8d785e | |
parent | e9a25d60c252728ee22f3110abb4e3200d633dbf [diff] |
[third_party/pigweed] Roll 2 commits 6942dd5c53c11b4 pw_format: Refactor format string parsing for bett 2d4292592c08ffd *: Run clang-format https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: ef655533be05a36..6942dd5c53c11b4 Roller-URL: https://ci.chromium.org/b/8748560543994859617 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia7fc85d2664f992395dbcd40b6506c8d1b73ca13 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208874 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!