Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 8d0ca2e3d8840e8786a01d536deb6e5d68709ef3
commit8d0ca2e3d8840e8786a01d536deb6e5d68709ef3[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jul 08 14:40:00 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 08 14:40:00 2024 +0000
treeaed8b8367d837299643232b8f2fbb15a1a3ed65c
parent69f35f42af049a59457e8c9f529b968623fb543f [diff]
roll: pigweed, pw_toolchain: roll: go

From: version:2@1.22.4
To: version:3@1.22.5
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/220471
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 434ae75c94cbd00..a5f72ef6f5e0e78
Roller-URL: https://ci.chromium.org/b/8742971655075062145
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I39729fdfe13a574c94a1ed1a869bb5dab4c0af44
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/220491
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: aed8b8367d837299643232b8f2fbb15a1a3ed65c
  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!