Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1b4a1f275d6771484965cabf60cde1f98f4ab98f
commit1b4a1f275d6771484965cabf60cde1f98f4ab98f[log] [tgz]
authorCarlos Chinchilla <cachinchilla@pigweed.infra.roller.google.com>Fri May 10 19:09:40 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 10 19:09:40 2024 +0000
tree7161af6eb012e598fae6359d1c3330dc5aef4885
parente44e996649df448904de30408a5f042186b6d0f1 [diff]
[roll third_party/pigweed] pw_log: Make TODO actionable

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/209571
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 47018e2757e4c2c..4d868e624a68d16
Roller-URL: https://ci.chromium.org/b/8748299924207945121
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic6f0e02c7164e2059db9f54e6645621a4fc83952
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209552
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: 7161af6eb012e598fae6359d1c3330dc5aef4885
  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!