Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 6c045eba674c3acd8c6ad96f67f872914528bef1
commit6c045eba674c3acd8c6ad96f67f872914528bef1[log] [tgz]
authorAnthony DiGirolamo <tonymd@pigweed.infra.roller.google.com>Thu Apr 04 03:38:33 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 04 03:38:33 2024 +0000
treeb64213b5baa6454986db3619c09859d64b2076ef
parentd7fd36caf107acb90d36e6e0bf5cb3a9024b6e65 [diff]
[roll third_party/pigweed] pw_module: Overwrite prompt with diff display

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/201851

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: f54d93143ffd79c..83816fda4ae0793
Roller-URL: https://ci.chromium.org/b/8751619979353204001
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic7ca4955ee77e2d7e1b5826db5ab207ddd2b87ce
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201873
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: b64213b5baa6454986db3619c09859d64b2076ef
  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!