Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 7509a7b4f39bbcb0169c92b58c88d14472a79c54
commit7509a7b4f39bbcb0169c92b58c88d14472a79c54[log] [tgz]
authorAlan Rosenthal <alanrosenthal@pigweed.infra.roller.google.com>Mon Jun 03 16:27:44 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 03 16:27:44 2024 +0000
tree7ab9e8da7675c3ef05933236ffd603d12705583f
parentc3ae64a2e5036f0fe85d6487e877e9f7bce1472d [diff]
[roll third_party/pigweed] zephyr: Fix typo

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

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: b0b4108bd83aa5a..04079093944aab1
Roller-URL: https://ci.chromium.org/b/8746135797925176113
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iba254d09e10c1e16d2bb798d8afb3b497327364d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213531
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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: 7ab9e8da7675c3ef05933236ffd603d12705583f
  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!