Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 4b836fac808ceeff8315044a64faf38896712d78
commit4b836fac808ceeff8315044a64faf38896712d78[log] [tgz]
authorJonathon Reinhart <jrreinhart@pigweed.infra.roller.google.com>Tue Jul 30 16:23:12 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 30 16:23:12 2024 +0000
tree5e302a93b1bf1575b1292891dc30c8d7f115ee3a
parent0f0a778462a98157de0edb851d9159d93ff4fcd0 [diff]
roll: pigweed, pw_toolchain: pw_digital_io_linux: Set log level to INFO

Specifically, this avoids the debug message on each GPIO event.

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: dbd8c53b25ddf3b..f513cf21c32c28e
Roller-URL: https://ci.chromium.org/b/8740972018641698785
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ia07ff5f7b90bef0e4bc9a5e5c009cc9692b8e1dc
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226511
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 5e302a93b1bf1575b1292891dc30c8d7f115ee3a
  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!