Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 41e03d9180f56de6b74066d0e47aeb65bd1a460a
commit41e03d9180f56de6b74066d0e47aeb65bd1a460a[log] [tgz]
authorAndrei Cornescu <andreicornescu@pigweed.infra.roller.google.com>Wed Mar 27 15:47:49 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Mar 27 15:47:49 2024 +0000
tree214601a149884f87ec0fc2b75470548d759226d5
parentac835835be224ccba0615da1a323e187fe49b448 [diff]
[roll third_party/pigweed] pw_uart: Added UART interface

Added `Uart` interface that proves a set of basic methods for
performing UART communication.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/181710

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: d595cc8bc24ce2e..93558a01ab8e995
Roller-URL: https://ci.chromium.org/b/8752299841888000385
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I5d07e290d90a17461cbf63af8c40135a1e7f3c58
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200673
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 214601a149884f87ec0fc2b75470548d759226d5
  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!