Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 2578c8e267c3b0dd7cb741dfaf6da6c211fdc39e
commit2578c8e267c3b0dd7cb741dfaf6da6c211fdc39e[log] [tgz]
authorAsad Memon <asadmemon@pigweed.infra.roller.google.com>Thu Jul 11 00:05:11 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 11 00:05:11 2024 +0000
treefa35e81761d192f9a58a711401e35b51727dc6bd
parent7877175e440118369fe2b2f3fb0f981545554f55 [diff]
roll: pigweed, pw_toolchain: pw_console: Headless mode with web/ws server running

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

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