Google Git
Sign in
pigweed / pigweed / quickstart / bazel / e046dd28b3e60f327b816d6fd7e96560670ac0e0
commite046dd28b3e60f327b816d6fd7e96560670ac0e0[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri May 03 04:02:56 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 03 04:02:56 2024 +0000
tree18aef11d4244f662938d014df16f9388a02ad8cc
parentc9058e66b10d3907cf5050e505a6c4b55103e70f [diff]
[third_party/pigweed] Roll 2 commits

5b96d29bb8a6ff0 pw_digital_io_linux: Refactor test
e59fb801bd8584c pw_build: Fix type hint

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 9cbecdc781e3706..5b96d29bb8a6ff0
Roller-URL: https://ci.chromium.org/b/8748991132301972641
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If8e1b4e3d787b16a40e44541aa34be3413dd69f8
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208022
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 18aef11d4244f662938d014df16f9388a02ad8cc
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!