Google Git
Sign in
pigweed / pigweed / quickstart / bazel / b07c9e967e261d16ab8af80a698bb7cb397ca75d
commitb07c9e967e261d16ab8af80a698bb7cb397ca75d[log] [tgz]
authorChad Norvell <chadnorvell@pigweed.infra.roller.google.com>Thu Jul 18 06:20:47 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 18 06:20:47 2024 +0000
tree8ce1ea335a278e4cfc48e73a6f68232e94b3bbcb
parentd48e7429b3bcbb7ce8974e58d817f9f07d95c72c [diff]
roll: pigweed, pw_toolchain: pw_ide: VSC extension 1.0.0 release

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 37bbd5f8e53c1cf..d7f4cfe88a34541
Roller-URL: https://ci.chromium.org/b/8742097070674495041
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie4984bfe7562c00bac3e3f9d5fb6b95dcf33d645
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223808
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: 8ce1ea335a278e4cfc48e73a6f68232e94b3bbcb
  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!