Google Git
Sign in
pigweed / pigweed / quickstart / bazel / b7de634e5d594fef0cc784ccd876e26b526d1034
commitb7de634e5d594fef0cc784ccd876e26b526d1034[log] [tgz]
authorAndrei Cornescu <andreicornescu@pigweed.infra.roller.google.com>Wed May 22 07:18:02 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 22 07:18:02 2024 +0000
tree28a51a2032809e5236789f1edd8938735bf23365
parent06acc10b9fdb33cc2e5fbe677084ee3fe3760415 [diff]
[roll third_party/pigweed] pw_uart: Add pw_uart to CMakeLists

Fix pw_uart import by adding to root CMakeLists.txt

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/210731
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 506466d72aa5cbf..83644e88fe7aa51
Roller-URL: https://ci.chromium.org/b/8747257523240905953
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I6724b9a3cb7adffce49f2cdab98a4740a274280c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210891
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: 28a51a2032809e5236789f1edd8938735bf23365
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!