Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 8e132cc8dc7d64363ec29d4fc0a36f6d691f8491
commit8e132cc8dc7d64363ec29d4fc0a36f6d691f8491[log] [tgz]
authorTed Pudlik <tpudlik@pigweed.infra.roller.google.com>Thu Jul 18 17:56:33 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 18 17:56:33 2024 +0000
tree470760a893075b780a8d185f8fcd9529e2d4835f
parentb07c9e967e261d16ab8af80a698bb7cb397ca75d [diff]
roll: pigweed, pw_toolchain 2 commits

a17b318ce670eae bazel: Use Python toolchain in custom rules
9215cef0494c61f docs: Minor changelog update

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: d7f4cfe88a34541..a17b318ce670eae
Roller-URL: https://ci.chromium.org/b/8742053329168711041
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I895d5db5f4a44ec478ad27d92ff07170a7f60efd
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/224331
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 470760a893075b780a8d185f8fcd9529e2d4835f
  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!