Google Git
Sign in
pigweed / pigweed / quickstart / bazel / aa045664b1a285c1a7b0b30cb048bd3ee06e34ae
commitaa045664b1a285c1a7b0b30cb048bd3ee06e34ae[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 31 01:10:05 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 31 01:10:05 2024 +0000
tree7984cfb0229fa09d17b5baa5ea5f548994777180
parent12585b60aae1d668fb849126930cc91a54a2bc87 [diff]
roll: pigweed, pw_toolchain 3 commits

ac59830dcdbd32c pw_system: Add console device aliases for common R
b0153387ffcae11 pw_clock_tree_mcuxpresso: Introduce ClockMcuxpress
ed88d9b037da70c pw_presubmit: Allow fxbug.dev and crbug.com TODOs

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 513f5005834264d..ac59830dcdbd32c
Roller-URL: https://ci.chromium.org/b/8740938912957067889
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id26f6a89a4288cfc36ee7397e0b8e1c799dafe2b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226633
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 7984cfb0229fa09d17b5baa5ea5f548994777180
  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!