commit | 32f75e1a20fdc978cfbff656ead41ab309e90a4c | [log] [tgz] |
---|---|---|
author | Erik Gilling <konkers@pigweed.infra.roller.google.com> | Sat Jun 22 21:50:42 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jun 22 21:50:42 2024 +0000 |
tree | cab7d207bb37136377dd5e9049b86fb71f5d40dc | |
parent | 9cf46c287642abcc986de1034d29f256dafd9e77 [diff] |
roll: pigweed, pw_toolchain: rust: Fix clippy lints Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/217136 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 880f40d3709839d..7ad2bee3e541072 Roller-URL: https://ci.chromium.org/b/8744394233704695601 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia3ba82513e30f6516d0aea8df32f2ea0bdb3f4c4 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217167 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!