| commit | 5e6ddf5e5ee3a2ad9aff8d5d460afb3e799c0863 | [log] [tgz] |
|---|---|---|
| author | Chad Norvell <chadnorvell@pigweed.infra.roller.google.com> | Tue Jul 23 17:54:36 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 23 17:54:36 2024 +0000 |
| tree | e727e26e50940d55c169a6beb64547c79add3988 | |
| parent | f0fd25b9ded9665fe2547a8202ad2c16508521c1 [diff] |
roll: pigweed, pw_toolchain: pw_ide: Don't unnecessarily infer working dir We only need to infer the working dir if a project root isn't explicitly provided. In uncommon use cases, the right way to deal with our inability to infer the working dir is to manually specify the project root, so a working dir inference failure is counterproductive. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/224572 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 95347e0199c0427..6afbf6deaa1d762 Roller-URL: https://ci.chromium.org/b/8741600453416304257 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I315183916364f504cc4acbad29e08835da273e08 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225635 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!