commit | 854af14b862c898e9b0dffda39b05f08f386686a | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@pigweed.infra.roller.google.com> | Thu Apr 25 03:56:11 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 25 03:56:11 2024 +0000 |
tree | 8c3898a0d4cd5fd4ade96be5423d22f24b2e7ece | |
parent | 149e26632a6991121f26b613f7400e0959e0fdb1 [diff] |
[roll third_party/pigweed] pw_presubmit: Separate 'bazel info' stderr Separate stdout and stderr of 'bazel info output_base'. Original-Bug: b/332357274 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/206350 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 32ff69e60cb8ad6..54558a97edeb5ab Roller-URL: https://ci.chromium.org/b/8749716337089271233 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I28e90c39450632c36aacb3e6c2eb97d82205a54a Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206410 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!