Google Git
Sign in
pigweed / pigweed / quickstart / bazel / b61fe5b97738b180351744ba1a9ff6e2a565b05d
commitb61fe5b97738b180351744ba1a9ff6e2a565b05d[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 17 16:16:33 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 17 16:16:33 2024 +0000
tree96e1e4808506c18af431102f26ee80b88759c648
parented60e48e10fb6b9932fdd05108734e8e2f390904 [diff]
roll: pigweed, pw_toolchain 3 commits

110886b36198cfe pw_bluetooth_sapphire: Use pw_bytes for endianness
8874d47ccfa465d pw_bluetooth_sapphire: Reorganize test_packets.h/.
721173ca9019b69 pw_bluetooth_sapphire: Cleanup WriteInquiryScanAct

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 63a1dce944a0fbe..110886b36198cfe
Roller-URL: https://ci.chromium.org/b/8742150247002385025
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1b858b19170fa4cf9dec4841b3880e9ae74d0be8
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223814
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 96e1e4808506c18af431102f26ee80b88759c648
  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!