commit | 874d405f2b5a3b912a4b1086f5b39a2490deac0b | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Sun Apr 28 21:59:26 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Apr 28 21:59:26 2024 +0000 |
tree | 439c2f3becacfb2afc952d35defc2bb3b3aac02f | |
parent | 8e3338630727fd237ef9184b013e730d8ce15aaf [diff] |
[roll third_party/pigweed] roll: gn From: git_revision:155c53952ec2dc324b0438ce5b9bd4a286577d25 To: git_revision:f284b6b47039a2d7edfcbfc51f52664f82b5a789 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/206859 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: ab83b349da5c2fd..ccc5241d8133cd2 Roller-URL: https://ci.chromium.org/b/8749376396765567617 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ie225b5f4f2f3ed89d8f151006a97a11bed391d24 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207013 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!