Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 877e5c55c64306414d690958c070224535ee0d9c
commit877e5c55c64306414d690958c070224535ee0d9c[log] [tgz]
authorAsad Memon <asadmemon@pigweed.infra.roller.google.com>Fri Jul 19 02:42:34 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jul 19 02:42:34 2024 +0000
treeed05b4950c525a0f8929e9d11af2873696dbe7e1
parent95a93a6fed461f91aba42d8501384467d06b5510 [diff]
roll: pigweed, pw_toolchain: pw_web: Fix bug in code editor to not eval empty snippet

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: a0bc30225ae7058..e3076ba724ed431
Roller-URL: https://ci.chromium.org/b/8742020229069949249
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ifa669182a3ce76776a1397dacb5d0baee059fcd4
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/224571
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: ed05b4950c525a0f8929e9d11af2873696dbe7e1
  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!