Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 01cfe4d0d986dcd372dfc51c601fd01c85e754db
commit01cfe4d0d986dcd372dfc51c601fd01c85e754db[log] [tgz]
authorTed Pudlik <tpudlik@pigweed.infra.roller.google.com>Fri Jun 28 23:46:11 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 28 23:46:11 2024 +0000
treee5dbe68263ebed368e7a3e98b360da703de42889
parent1361330f9e315a06bcdc065455967ae87a912404 [diff]
roll: pigweed, pw_toolchain: pw_sys_io: Remove multiplexer, constraints

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: f588ba91c9de167..8b8ad3820dff2e6
Roller-URL: https://ci.chromium.org/b/8743843296180308161
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I9076f782bc30a402653dc4519488d26f1e485c72
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218784
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: e5dbe68263ebed368e7a3e98b360da703de42889
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!