Google Git
Sign in
pigweed / pigweed / quickstart / bazel / f3d420a6f6b4e0e73816d887b6f8a68b976afa46
commitf3d420a6f6b4e0e73816d887b6f8a68b976afa46[log] [tgz]
authorChad Norvell <chadnorvell@pigweed.infra.roller.google.com>Mon Jul 22 21:25:24 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 22 21:25:24 2024 +0000
tree6ddba486b7c780701b119d33fa41362e389ddef1
parenta70404bf22c771063911f61ba2bcd2a40560a0a5 [diff]
roll: pigweed, pw_toolchain: pw_ide: VSC extension 1.1.1 release

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 6d21be2f13d7f84..4f0412dae17b20a
Roller-URL: https://ci.chromium.org/b/8741677790652058417
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iba0ab00022fdbf38d3873288c80bc170c5b27437
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225432
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: 6ddba486b7c780701b119d33fa41362e389ddef1
  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!