Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 878eead5bd80c768458d9ff98cfa15fa9b1f44cc
commit878eead5bd80c768458d9ff98cfa15fa9b1f44cc[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Apr 02 00:36:58 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 02 00:36:58 2024 +0000
treee80dfb871c4ff198da4fba001b3800337b52a2ee
parentf76650dc3fcfb725c41525a767fb19c548eadb2b [diff]
[third_party/pigweed] Roll 3 commits

035f292d35a6918 docs: Organize the documentation style guides
2262ec0a0be4690 pw_allocator: Remove Layout from Deallocate and Re
f6d9544b2895948 pw_bytes: Add example to docs of using _b suffix

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 18442a7e69a5b1c..035f292d35a6918
Roller-URL: https://ci.chromium.org/b/8751812613482528305
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I04a0df218ad513e8ba5300b126f67979295ae0ce
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201411
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: e80dfb871c4ff198da4fba001b3800337b52a2ee
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!