Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 9cf46c287642abcc986de1034d29f256dafd9e77
commit9cf46c287642abcc986de1034d29f256dafd9e77[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat Jun 22 21:43:16 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Jun 22 21:43:16 2024 +0000
tree14264b8ec295ae3735d41d9128412ef0cdf7985f
parent85df4fc4e6ffaf198d971746e84e2c4753bbd238 [diff]
roll: pigweed, pw_toolchain 2 commits

880f40d3709839d roll: cmake
ba4a1747954de39 pw_format: Fix and enable disabled Rust tests

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 99dfabfb6139412..880f40d3709839d
Roller-URL: https://ci.chromium.org/b/8744394634346489665
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I99ec8f1d8dfa89b9437765aade9c09fe9a34a4c5
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217555
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>
1 file changed
tree: 14264b8ec295ae3735d41d9128412ef0cdf7985f
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  13. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

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.

Building

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

Flashing

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.

Communicating

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!