commit | 023bb977d297994e552737bed76ab2053045b851 | [log] [tgz] |
---|---|---|
author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Tue May 28 22:23:01 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 28 22:23:01 2024 +0000 |
tree | 867c41da2b4ef91c56e37a9d8700817f8a5f054b | |
parent | 634ecf1d4566a8b4dc5056dad69b42ed709d452c [diff] |
[roll third_party/pigweed] pw_toolchain: Add manual tag to Rust toolchains Test: bazel build --config=stm32f429i //pw_toolchain/rust/... Test: bazel build --platforms=/pw_build/platforms:lm3s6965evb //pw_rust/examples/embedded_hello:hello Original-Bug: 342695883 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/211934 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: eb97b4508f6e0ca..c2915194debfc14 Roller-URL: https://ci.chromium.org/b/8746656997792217441 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I89ee2ae54c8f7b0a39d42735d7efdb96b712cb6b Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/211938 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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!