| commit | 22e5cdb331bedbc76c334726714ac7b4720f778e | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@pigweed.infra.roller.google.com> | Mon Jul 08 20:47:20 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 08 20:47:20 2024 +0000 |
| tree | c8692d233a88c6a2c2d1cfd71c4e1904fce19ff8 | |
| parent | f3b10f2f8b025dbc4995837d3d22f89f5ad55322 [diff] |
roll: pigweed, pw_toolchain: pw_presubmit: Don't automatically use exclusions Don't automatically apply the exclusions from pigweed.json to every presubmit check. Original-Bug: b/347274642 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216355 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 0a4a217f91f65fb..40ced78e4ae4490 Roller-URL: https://ci.chromium.org/b/8742948598578906945 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I2bbca95358d051f1b05af455a08f8802e1e333ba Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/220652 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!