Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a0af8177e5221eb63673c77553749ae0fbfd34bf
commita0af8177e5221eb63673c77553749ae0fbfd34bf[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri May 03 19:03:54 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 03 19:03:54 2024 +0000
treedfdd59aaabff9d017f066598bf4cb2600af6d9f1
parente046dd28b3e60f327b816d6fd7e96560670ac0e0 [diff]
[third_party/pigweed] Roll 2 commits

89c90454a256760 pw_toolchain: Add no-canonical-system-headers
59bc1cdc76fbc59 pw_allocator: Use singletons for stateless allocat

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 5b96d29bb8a6ff0..89c90454a256760
Roller-URL: https://ci.chromium.org/b/8748934472295267873
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie6e6fef0eaf8eb80820325d4d80893137634211f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208026
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: dfdd59aaabff9d017f066598bf4cb2600af6d9f1
  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!