Google Git
Sign in
pigweed / pigweed / quickstart / bazel / e1789129959394327fdaf9bb574372956a9877a6
commite1789129959394327fdaf9bb574372956a9877a6[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Jul 26 01:18:54 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jul 26 01:18:54 2024 +0000
treec8b3be14c951d91d303eee4701226afb940f1984
parent98ba1d3b9d6e41fb7d325b38fa609b48ef5062b1 [diff]
roll: pigweed, pw_toolchain 3 commits

7744b8c3d5710dd bazel: Remove @pigweed from bzl files
a99ccb3f20f2d5d emboss: Disable using pw_python_action
050ea7fb96c7f94 bazel: Remove stray @pigweed in load statement

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: cb5ee68a68c2c3c..7744b8c3d5710dd
Roller-URL: https://ci.chromium.org/b/8741391301923435041
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I2e53b76ff7135d99772bdda0820fdd0e826713fe
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226023
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: c8b3be14c951d91d303eee4701226afb940f1984
  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!