Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 44eb8c703512b18a1f1fc9b6781dd4bad4b67bf6
commit44eb8c703512b18a1f1fc9b6781dd4bad4b67bf6[log] [tgz]
authorJiacheng Lu <lujc@pigweed.infra.roller.google.com>Thu Aug 01 03:28:51 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Aug 01 03:28:51 2024 +0000
tree8d7ac289ff4fcb9dc3d2d0879457c89b8821a6c1
parent118389fc8ec58cc0c929216831c63297f82ee673 [diff]
roll: pigweed, pw_toolchain 3 commits

61f6e54585a0e81 pw_rust: Add no_std build to basic_executable
79f0dd143867866 pw_rust: Rename host_executable
9d49c47bb21b0cc pw_env_setup: Add rustc thumbv7m target

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 55c5087185c0ff3..61f6e54585a0e81
Roller-URL: https://ci.chromium.org/b/8740839602029451233
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iab2f29dfb831b73b1dc95439ccdf3241b95125e1
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226903
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: 8d7ac289ff4fcb9dc3d2d0879457c89b8821a6c1
  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!