Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 71de5015442753dbff0f9fd11f666a6181d4306f
commit71de5015442753dbff0f9fd11f666a6181d4306f[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jul 15 22:42:32 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 15 22:42:32 2024 +0000
tree1c6f7ad5cce9d6c1bc89b53a5027b6fc76fbfc3c
parent7160681b43c064e819b36441c66e092926c38ee0 [diff]
roll: pigweed, pw_toolchain 3 commits

4a53a922de3b28d pw_ide: Bazel comp DB management in VSC
96a846ccf24428d pw_log: Fix log_decoder timestamp formatting
74c9cc4f1eea0d5 pw_ide: VSC/JS project management

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: a02745cb13e02e4..4a53a922de3b28d
Roller-URL: https://ci.chromium.org/b/8742307113088594097
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I8d27c4a9fb2ea27105ca2cfbbf7d1016efd05d7d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223233
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: 1c6f7ad5cce9d6c1bc89b53a5027b6fc76fbfc3c
  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!