Google Git
Sign in
pigweed / pigweed / quickstart / bazel / f0fd25b9ded9665fe2547a8202ad2c16508521c1
commitf0fd25b9ded9665fe2547a8202ad2c16508521c1[log] [tgz]
authorRob Mohr <mohrr@pigweed.infra.roller.google.com>Tue Jul 23 17:48:04 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 23 17:48:04 2024 +0000
treeaf94efeb54912f0ec5fd512e1153f93618cfd156
parentb61544b9bbd4eb08bbd4b0254fcc77cdc6921935 [diff]
roll: pigweed, pw_toolchain: pw_presubmit: Add attributes to docstring

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 8a4ae70355cd135..95347e0199c0427
Roller-URL: https://ci.chromium.org/b/8741600952136608529
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I31c5d70f6c8c31edc66fc06828690cd0d724f575
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225634
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: af94efeb54912f0ec5fd512e1153f93618cfd156
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!