Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a7987e39c4a816f14e27804827fe7b410126d40a
commita7987e39c4a816f14e27804827fe7b410126d40a[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jul 01 20:41:11 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 01 20:41:11 2024 +0000
treed2c2fc68f5c7a57a2403b0995922e78c6a366908
parent449fe0aca03a2ad7baadd43d4b166b4f3d71fc84 [diff]
roll: pigweed, pw_toolchain 3 commits

324824be015681a pw_bluetooth: Format emboss files
9324fd3b8eec8bb pw_bluetooth_sapphire: Add CIS events and commands
4fd97f5fc4ae5dc pw_bluetooth_sapphire: Retrieve sleep clock accura

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 194c43b97cef496..324824be015681a
Roller-URL: https://ci.chromium.org/b/8743583487009997009
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I4ccb723405a41a8179c11f648a3ee9cdd7dc39f4
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/219432
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: d2c2fc68f5c7a57a2403b0995922e78c6a366908
  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!