Google Git
Sign in
pigweed / pigweed / quickstart / gn / ec107bd81875124e8fb00896054b81f782727f21
commitec107bd81875124e8fb00896054b81f782727f21[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Apr 29 19:00:07 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 29 19:00:07 2024 +0000
tree73dbaadd443189024004de2e05185ced0528fdff
parent874d405f2b5a3b912a4b1086f5b39a2490deac0b [diff]
[third_party/pigweed] Roll 4 commits

51572a37f0c380b pw_env_setup: Update default sysroot version
e0492ee7eaed1f4 roll: clang
73d4ddb4cb33de4 pw_allocator: Add missing return statement
a1faba5d2d569a1 SEED-0129: Claim SEED number

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