Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 50be15e7154d5fafdc22a8a234ec1b3498341911
commit50be15e7154d5fafdc22a8a234ec1b3498341911[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat May 18 01:14:51 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat May 18 01:14:51 2024 +0000
treed52579f4ee6e8b4c5650220871dffc8dbc3db545
parenta96c1c7ce856462ac5bd7ee7878bc5218617e235 [diff]
[third_party/pigweed] Roll 2 commits

efcc36b25be8339 targets/rp2040: Increase device_detector verbosity
d8d48ae0cbd9574 docs: Update changelog

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 9c7d87957171705..efcc36b25be8339
Roller-URL: https://ci.chromium.org/b/8747642754616621713
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I580dc5add6fa0e828fe8431b9ae7bf691aa80dbf
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210361
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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: d52579f4ee6e8b4c5650220871dffc8dbc3db545
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!