Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 104e5c7e3fd9cce3b9c0b9b4f5a644fd0bc26cc4
commit104e5c7e3fd9cce3b9c0b9b4f5a644fd0bc26cc4[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Apr 15 18:48:10 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 15 18:48:10 2024 +0000
treeadb321fc3eb105b5f586d06c79d9feb090af6a26
parent17661f9d937d7163df84a60592164a3397da093d [diff]
[third_party/pigweed] Roll 2 commits

e3c8e94cbffee47 pw_transfer: Implement adaptive windowing in Pytho
79c1f24e16c01c3 pw_web: Use existing col data when adding new View

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 3fbcf41574028ef..e3c8e94cbffee47
Roller-URL: https://ci.chromium.org/b/8750566208270930785
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I99415854413d0b65ba8eea9a063c898b91b015ca
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/203633
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: adb321fc3eb105b5f586d06c79d9feb090af6a26
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!