| commit | c5148031dcc653b02dc6ebd5363175ff7a3f098e | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Sun Apr 07 21:41:57 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Apr 07 21:41:57 2024 +0000 |
| tree | 83ba36b10118ad9994ace2c80feddaee52c96797 | |
| parent | e33b1d3948656e282d75071d10255695d586d693 [diff] |
[roll third_party/pigweed] roll: gn From: git_revision:93ee9b91423c1f1f53fb5f6cba7b8eef6247a564 To: git_revision:415b3b19e094cd4b6982147693485df65037f942 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/202230 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 1cbf2352b3e0b5e..7ca22fc66b3aa3c Roller-URL: https://ci.chromium.org/b/8751280038747082577 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: If538f4720cb3cb49bcaca25ce1817165bf9d06b1 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/202250 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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!