Google Git
Sign in
pigweed / pigweed / quickstart / bazel / fd09669a92ecea9612848052c0b76bbf6b55ca06
commitfd09669a92ecea9612848052c0b76bbf6b55ca06[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Aug 07 23:16:03 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 07 23:16:03 2024 +0000
treeb11593d17ffabf869db0b8eb690ebcd0fda6dc7c
parentfd96f986d9f2d5140e931d24eee7edabb951e1f8 [diff]
roll: pigweed, pw_toolchain 2 commits

1d487225d2e5fc6 pw_ide: VSC extension 1.3.2 release
10d538fee6ed808 docs: Start Sense tutorial

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 28d16ef6f95b032..1d487225d2e5fc6
Roller-URL: https://ci.chromium.org/b/8740221285782058945
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I656923a2d2638ab16d0d6c5de44304da5cd16bc6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/228340
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: b11593d17ffabf869db0b8eb690ebcd0fda6dc7c
  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!