Google Git
Sign in
pigweed / pigweed / quickstart / gn / ee1ee69019049d37e29cb6c686ef04a1652298bb
commitee1ee69019049d37e29cb6c686ef04a1652298bb[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Apr 29 22:05:25 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 29 22:05:25 2024 +0000
tree3f1d97accc4901f141852a72613ad536eeee887a
parentec107bd81875124e8fb00896054b81f782727f21 [diff]
[third_party/pigweed] Roll 3 commits

fa1938a64124d21 pw_assert: Fix support for print_and_abort in Baze
4f13eae7187e8ba pw_build: Add a `test_main` param to `pw_cc_test`
5e4e82bec8288b7 pw_thread_threadx: Remove unused dependency

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 51572a37f0c380b..fa1938a64124d21
Roller-URL: https://ci.chromium.org/b/8749285751530312689
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I729dcf514bdfe9d5b2e0d7fbffd083ed6820a6e5
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207432
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: 3f1d97accc4901f141852a72613ad536eeee887a
  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!