Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 8cabe6a97ad4d63fc24846f59623a93f8242f7e5
commit8cabe6a97ad4d63fc24846f59623a93f8242f7e5[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue May 21 01:16:57 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 21 01:16:57 2024 +0000
tree44c99dd772831096ab8ec5996df35b52e58ba637
parentc899c94d61cb99b4cf3905b3ca1e4b06ce9d137b [diff]
[third_party/pigweed] Roll 5 commits

4d84714f44de7d6 pw_cpu_exception_cortex_m: Fix checks for ARMv8
bb558ed3c239189 rp2040: Raise minimal stack size to 1KB
dc5c87c532e5c75 pw_system: Simplify pw_system usage in Bazel
eeec5566194948d targets/rp2040: Refresh target docs
905d4268e336ff1 pw_clock_tree: Generic clock tree management

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: de0813bee2778fe..4d84714f44de7d6
Roller-URL: https://ci.chromium.org/b/8747370830667539105
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iaebecde72d16f6ef6d35770843c625ccd6c87c49
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210632
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: 44c99dd772831096ab8ec5996df35b52e58ba637
  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!