| commit | 85df4fc4e6ffaf198d971746e84e2c4753bbd238 | [log] [tgz] |
|---|---|---|
| author | David Rees <drees@pigweed.infra.roller.google.com> | Sat Jun 22 06:41:49 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jun 22 06:41:49 2024 +0000 |
| tree | d84deafee5125b59a6d36f260aa2c38d639e0454 | |
| parent | cf2a1309a85256e7183e95ace00846b636a8b2b5 [diff] |
roll: pigweed, pw_toolchain: docs: Add emboss to packages installed for build_docs Allows building size for projects that use emboss. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216893 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 1edcc733fe2cec8..99dfabfb6139412 Roller-URL: https://ci.chromium.org/b/8744451283657425265 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I7f992d3613fc6931e5629121d98b2dc4d976ce54 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217553 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!