Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 149e26632a6991121f26b613f7400e0959e0fdb1
commit149e26632a6991121f26b613f7400e0959e0fdb1[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Apr 25 00:56:03 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 25 00:56:03 2024 +0000
tree1782a9e20f707f5361f126cab7c0ced2b7ac0cf8
parent0647475b5960dc06dec83ee77700d7681956081d [diff]
[third_party/pigweed] Roll 3 commits

32ff69e60cb8ad6 pw_allocator: Clean up LibCAllocatorTest
c50cd3d84714aa6 pw_allocator: Move block allocators to separate fi
4613447f11e0513 pw_presubmit: Save 'bazel info output_base'

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