Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 69c30ba31aa3105708fb26a30474e4f4988eae7b
commit69c30ba31aa3105708fb26a30474e4f4988eae7b[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jun 04 18:13:15 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 04 18:13:15 2024 +0000
treefb25268879c48779cdffbecb568f21f800cb01d6
parent19e920dc229588ea00991adc63332de8ea67f2ca [diff]
[third_party/pigweed] Roll 3 commits

5f164749a2bb256 pw_web: Fix last column filling space in log table
9c5ff32b8a7e995 pw_bluetooth_proxy: Pass H4 as event type plus an
ee2ddb543cc45ec pw_bluetooth_proxy: Tweak CreateNonInteractingToHo

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 6618a7d3265639b..5f164749a2bb256
Roller-URL: https://ci.chromium.org/b/8746038523625014865
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ibe8f3865d9e7c207b972ae678d594f0d9b92b28c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213871
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: fb25268879c48779cdffbecb568f21f800cb01d6
  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. pigweed.json
  14. README.md
  15. requirements.in
  16. requirements_lock.txt
  17. 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!