Google Git
Sign in
pigweed / pigweed / quickstart / bazel / aedfa15be8f6a5324e6bf9050f6c073742176f39
commitaedfa15be8f6a5324e6bf9050f6c073742176f39[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat Jul 27 00:47:48 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Jul 27 00:47:48 2024 +0000
tree87c51d4702d568a8a3dbb42c87b01b04fba3c4df
parentf905d011d79364216b0ddcd1f2969f6c832655a6 [diff]
roll: pigweed, pw_toolchain 2 commits

6503ea83db78a47 pw_symbolizer: Get llvm-symbolizer path from Bazel
08c4ea4df5a3d2b docs: Update changelog

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 542cb9290ee366a..6503ea83db78a47
Roller-URL: https://ci.chromium.org/b/8741302650770702769
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I2b3b8ad61e59a3cb14034bf3e4b18161fd7c3d0d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226293
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: 87c51d4702d568a8a3dbb42c87b01b04fba3c4df
  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!