commit | 3812d07bc6aefbca165d7ac08f2bf46e7ffe1e95 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Jul 12 00:06:59 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 12 00:06:59 2024 +0000 |
tree | 0323a8bc0fd27666efca3957e7ff4e8baa51a049 | |
parent | e05e9154e0a42b1c6ce48761bfa7c5099d20872d [diff] |
roll: pigweed, pw_toolchain: pw_toolchain_bazel: Add native binary for clang-tidy Original-Bug: 352343585 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/221471 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: f2e580ecbc81acb..a047c412171136c Roller-URL: https://ci.chromium.org/b/8742664224273181745 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ic163e8b5c7be441a2043e3966654b45995a6a4e0 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222659 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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!