Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 279e9575302d13aa7fb147921c5e0afd083b4147
commit279e9575302d13aa7fb147921c5e0afd083b4147[log] [tgz]
authorChad Norvell <chadnorvell@pigweed.infra.roller.google.com>Wed Jul 17 08:02:17 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 17 08:02:17 2024 +0000
tree1c8d7ac6810c852aece0c9240cc86e4142d5ef0d
parentae51a271fdcfc19c8bd022218dbe4f6449d13295 [diff]
roll: pigweed, pw_toolchain: pw_ide: Fix VSC troubleshooting links

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 1e6e5c51a80a41a..29715742befb0a6
Roller-URL: https://ci.chromium.org/b/8742183777562915121
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ibc5f6b6d3cf7f109fcaa4ced62b305c3c1682cc6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223565
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: 1c8d7ac6810c852aece0c9240cc86e4142d5ef0d
  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!