Google Git
Sign in
pigweed / pigweed / quickstart / bazel / c7ed2c61343e3b9eb917b16bd0680f9279eb36a2
commitc7ed2c61343e3b9eb917b16bd0680f9279eb36a2[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed May 01 22:02:15 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 01 22:02:15 2024 +0000
tree1453874a54e131216ec74da07a7ee2228ad00fe3
parent048c93aec34692745e47c69b45e7222dc5ca7393 [diff]
[third_party/pigweed] Roll 2 commits

5bda8d1632020bd pw_digital_io_linux: Move OwnedFd to its own heade
6fb2433c30e6733 pw_cpu_exception_cortex_m: Add util_test to tests

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 71017480adf7fb1..5bda8d1632020bd
Roller-URL: https://ci.chromium.org/b/8749104459185879409
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie8a5df01fb7330e102bc9c09ee7432655e3d75f0
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207580
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: 1453874a54e131216ec74da07a7ee2228ad00fe3
  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!