| commit | 7160681b43c064e819b36441c66e092926c38ee0 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Jul 15 19:47:10 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 15 19:47:10 2024 +0000 |
| tree | 1054f3b418a3ba927fffd6e44332b719a826da49 | |
| parent | cd58f88daea54b318f3fd00782de1467548a9da4 [diff] |
roll: pigweed, pw_toolchain 8 commits a02745cb13e02e4 pw_ide: Create VSC settings interface cab84ef685196d2 pw_ide: Use VSC output panel for logging a830caebe3879e4 pw_ide: VSC extension cleanup 85f14eaec1d87a2 pw_thread: Add TestThreadContext for FreeRTOS f0ca09b6b258e75 pw_multibuf: Add more context on chunk regions d2185bd9f929dba pw_web: Save state on input change and adjust filt d984de91b2907d0 pw_rpc: Pass .proto files to compiler in Soong cf9b87778d83764 pw_transfer: Fix initial timeout and missing start https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: f81694520583467..a02745cb13e02e4 Roller-URL: https://ci.chromium.org/b/8742318155047200801 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia6a63d88c1070f4b91bb0173c1c8f0f8319869a5 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223153 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: 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!