Google Git
Sign in
pigweed / pigweed / quickstart / bazel / bbeb221896c9f1a4b252bd89248ae1b48266610e
commitbbeb221896c9f1a4b252bd89248ae1b48266610e[log] [tgz]
authorAmy Hu <amyhu@pigweed.infra.roller.google.com>Tue Jul 02 23:55:03 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 02 23:55:03 2024 +0000
treedb3038312531ef31aa77f8cafd6fa4dc21e5938a
parent82e1b75bab8611c165782938bb502f93a49a2eff [diff]
roll: pigweed, pw_toolchain: pw_web: Fix columns on first load

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 3bce472d07ecae8..5c3289c29896ea2
Roller-URL: https://ci.chromium.org/b/8743480304970738865
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ide1a0b8728a1010a58594575b0ae4e72684a3a2b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/219676
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: db3038312531ef31aa77f8cafd6fa4dc21e5938a
  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!