Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d898801f9f95ac48c129ca98a9af9107e08f3122
commitd898801f9f95ac48c129ca98a9af9107e08f3122[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jun 26 22:56:16 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 26 22:56:16 2024 +0000
treefb033c4b42d051edd7305f926021ce2d5e069547
parent6500e5b108c9eb98e4fd3d3623cd41f28352fd53 [diff]
roll: pigweed, pw_toolchain 3 commits

a8bf99f2bf19e83 pw_hex_dump: Remove pw prefix from log_bytes
2e092bc815ef30c BUILD.bazel: Remove unnecessary @pigweed reference
ae4cc140ba3da39 pw_i2c: Handle unaligned buffer reads in register_

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 5a8f064e15304d6..a8bf99f2bf19e83
Roller-URL: https://ci.chromium.org/b/8744027634382936449
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I82a49ab44378ede58cd6aef3c623e40e719c0473
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218494
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: fb033c4b42d051edd7305f926021ce2d5e069547
  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!