Google Git
Sign in
pigweed / pigweed / quickstart / bazel / e9a25d60c252728ee22f3110abb4e3200d633dbf
commite9a25d60c252728ee22f3110abb4e3200d633dbf[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue May 07 19:06:56 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 07 19:06:56 2024 +0000
tree5465695a389f039121f2206d66b04293a33a601b
parentaf207253f3c025644e89b7ccd7727d61978f92a6 [diff]
[third_party/pigweed] Roll 2 commits

ef655533be05a36 SEED-0116: Set status to On Hold
1dc4b07e46688fe pw_sys_io_stm32cube: Fix build for f1xx family

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 51bf763e5a99803..ef655533be05a36
Roller-URL: https://ci.chromium.org/b/8748571874595433105
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I786b27571fc723a63f75ff1a0cc110d4cbc5797b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208793
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: 5465695a389f039121f2206d66b04293a33a601b
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!