Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 8b732c4806c1ee9c5280402f18aa19ac21e4a627
commit8b732c4806c1ee9c5280402f18aa19ac21e4a627[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu May 02 19:02:35 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 02 19:02:35 2024 +0000
treedef6f6e3099cb4d407d39150270d9c510efaffe4
parentb6ff14c87854629448bb96825cde98b9e34998e3 [diff]
[third_party/pigweed] Roll 4 commits

7b7d2fd94a5d29c pw_build: Add chipset constraint for imxrt500 fami
07d564b6cd7e9cd pw_presubmit: reST format end-of-file formatting
618d59adc376e67 pw_bluetooth: Add HCI informational commands
0a8168cbf0c950d pw_thread: Fix remaining compilability issues

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: aa19504faca0b72..7b7d2fd94a5d29c
Roller-URL: https://ci.chromium.org/b/8749025141018235937
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I9e852c7fcc4a69142f3baa455d55ff5a4f078321
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208111
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: def6f6e3099cb4d407d39150270d9c510efaffe4
  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!