Google Git
Sign in
pigweed / pigweed / quickstart / bazel / bb8b5a76ed927a2ace9f37cf78c7e3bde5a8e014
commitbb8b5a76ed927a2ace9f37cf78c7e3bde5a8e014[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jul 25 01:55:46 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 25 01:55:46 2024 +0000
tree8c3569cc5d5f19ad5f30236bbd98ea0d50f0ce4f
parentef3f74e607a17f82df8367cc9ed6220cf0e5e80f [diff]
roll: pigweed, pw_toolchain 5 commits

d04920d78848a69 pw_async2: Add Coro::Empty
1c308d70f947c93 emboss: Run python with optimization on
2cd7928833a7590 pw_web: Add repl intro message and title param
319b183d63d4cd0 pw_ide: Use vendored Bazelisk in recommended confi
c369d01270042fc pw_ide: Improve VSC settings interface

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 54b1551fabecd43..d04920d78848a69
Roller-URL: https://ci.chromium.org/b/8741479579435354449
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iee943be8d5695a7d2f3321c7e881d2bbd8281261
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226012
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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: 8c3569cc5d5f19ad5f30236bbd98ea0d50f0ce4f
  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!