Google Git
Sign in
pigweed / pigweed / quickstart / bazel / cf362fa216d33146eff8171c1974bdbc3e6cb082
commitcf362fa216d33146eff8171c1974bdbc3e6cb082[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jul 16 01:38:19 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 16 01:38:19 2024 +0000
tree8e165bf3c34c15516a47f11429328a272fa281cd
parenteb35c9e4a0e21484a991b7e48c6cdd9a5687c600 [diff]
roll: pigweed, pw_toolchain 5 commits

28772428574c752 pw_web: Change repl keybinding to eval
6e2747685b1938f pw_web: Bundle console.ts, fix log source handlers
56eeafc862a5d9f pw_log: Log decoder timestamp cleanup
e3c08d776ad308d pw_ide: Integrate Bazelisk in VSC
dd427e3d26f5247 pw_trace_tokenized: Fix bazel build

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 103f6fd7aa5f55c..28772428574c752
Roller-URL: https://ci.chromium.org/b/8742296082588303313
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib0e6acbd9d08a0b751aa2b86981f1e99b5398a4c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223239
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: 8e165bf3c34c15516a47f11429328a272fa281cd
  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!