Google Git
Sign in
pigweed / pigweed / quickstart / bazel / abb6999830c9e39314f088cc72734bf8dd4aa761
commitabb6999830c9e39314f088cc72734bf8dd4aa761[log] [tgz]
authorDavid Rees <drees@pigweed.infra.roller.google.com>Fri Jul 19 17:19:52 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jul 19 17:19:52 2024 +0000
tree19c6259fcd00fec6a18fe47322aecf1b67268d77
parentf558f6e3de9c89d205ff48fbf199ef114c6b3fb5 [diff]
roll: pigweed, pw_toolchain 3 commits

f3a52277083c515 pw_bluetooth_proxy: Do not pass on NOCP events wit
a3dac2f97ae68a9 pw_bluetooth_proxy: Have functions handle passing
2e8949d2187a7e5 pw_bluetooth_proxy: Update tests to verify number

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: e45ec8f7c2d1e77..f3a52277083c515
Roller-URL: https://ci.chromium.org/b/8741965058605339729
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3a3b7f2df3f9aeb315d12c5ca9cc6a05ed644c0f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/224771
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: 19c6259fcd00fec6a18fe47322aecf1b67268d77
  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!