commit | 9d4bb20db0cd4913751d53b89000387b5d75664d | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Jul 11 23:43:22 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 11 23:43:22 2024 +0000 |
tree | dff05dfbf370b65a79c167cb8eb4fe1fa884c573 | |
parent | 47c8718ffd1c34f10db0b1e559197c76a04f4f83 [diff] |
roll: pigweed, pw_toolchain 6 commits b9de0f451197083 pw_env_setup: Use full paths for proj action impor 41a0140c8ece3f4 third_party/googletest: Fix the docs b041517545b70d1 bazel: Add missing dependencies 9b979cb0cbec695 pw_bluetooth_sapphire: Add Bazel build files to li 932c44e8e5c240e pw_system: Add web console option 7eb32bb61f56148 pw_web: Set min width for message https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: b4987e47aef3696..b9de0f451197083 Roller-URL: https://ci.chromium.org/b/8742665714362914801 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I8040d47da1bf763869b2a52c13b47ee744a9e673 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222635 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!