Google Git
Sign in
pigweed / pigweed / quickstart / bazel / fbc00c5d6f051d33a7f8fa393742298b032c1eb4
commitfbc00c5d6f051d33a7f8fa393742298b032c1eb4[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jul 11 20:44:02 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 11 20:44:02 2024 +0000
tree5dea36a4c5c482b0f29ebb04474bc4af9a0f2d81
parent56a517ea5eddce980bdedad1c490f644f5313576 [diff]
roll: pigweed, pw_toolchain 4 commits

a10dc77e7bf9af0 pw_system: Add missing work queue thread
dbda0e98bd7b9b7 pw_system: Clean up pw_system/threads.cc
cd7e34bbe9e8dcb pw_function: Dynamic allocation for upstream host
61c6b9a2ed03145 pw_web: Implement console-level split panels

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