Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 59f93eb8df87f5a924d9dce716240670a60401d7
commit59f93eb8df87f5a924d9dce716240670a60401d7[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Apr 09 18:43:33 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 09 18:43:33 2024 +0000
tree2ff77dfdf1fc287e564c08405d9b1a3e2f89c6c9
parent15324b99e8a35bf02de03828b55ec871c2e33a58 [diff]
[third_party/pigweed] Roll 2 commits

fb7782c0299f501 pw_tls_client: Only include <sys/time.h> if availa
fb1c6c223a457a8 SEED-0117: pw_i3c

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 6987287d186eef8..fb7782c0299f501
Roller-URL: https://ci.chromium.org/b/8751110083650933137
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I14be9563cc8ca33456dc8ec3db04ad67be6b4d35
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/202792
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: 2ff77dfdf1fc287e564c08405d9b1a3e2f89c6c9
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!