| commit | 7c5ec29b6da0d7153db18e75b6d829573148b276 | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Thu Mar 28 06:33:45 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 28 06:33:45 2024 +0000 |
| tree | 32dd886aded772c3c248e8f500f70a8f2705f9b5 | |
| parent | 4750266cfe7cd9c986aeab0145fe447bb08455a3 [diff] |
[roll third_party/pigweed] pw_presubmit: Update buildifier invocation Buildifier is removing some linter warnings (by merging them into the default formatting process), see https://github.com/bazelbuild/buildtools/pull/1244. This change will prevent a breakage from occurring when we roll a buildifier update that contains this PR. Internally see also g/copybara-users/c/Jkgv3DH-lyk Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/200350 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 917b5b7db5b6bba..15303ba92faa0dd Roller-URL: https://ci.chromium.org/b/8752243179647794689 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I0d408a0e3d9a021c5598a163a46382ce315675d3 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200688 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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!