| commit | 5a0b2abc02b04e6e37f04c625634de0bb1a5e28c | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Apr 18 03:50:13 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 18 03:50:13 2024 +0000 |
| tree | 2af936a9c488da322eb6e523a75fefd087af98aa | |
| parent | 6cd8afced58b8ec21921151a079597474188013f [diff] |
[roll third_party/pigweed] pw_env_setup: clang From: git_revision:b81bb0e1d0acc3db64557ed699ccba751b8b511a To: git_revision:8ccf1c117b0dc08f7e9c24fe98f45ebe32e95cd1 Original-Bug: b/333448202 Docs: N/A Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/202591 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: c0fdef4a7e8c34c..0f2396924cd89a6 Roller-URL: https://ci.chromium.org/b/8750350892613390993 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ibf475f042e905579abc44aec76e7f9234d55f929 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204410 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!