Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a3db8b66ab517a0263550c3308cb889e683208b9
commita3db8b66ab517a0263550c3308cb889e683208b9[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon May 13 22:11:41 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon May 13 22:11:41 2024 +0000
tree574b110527a3fb6f0c405df7b012355683d4c8b0
parente6b031468f71f73f3b342baa549e881b3fa2e017 [diff]
[third_party/pigweed] Roll 2 commits

158200d25a8562f pw_spi_mcuxpresso: Add responder implementation
b6a1c89349d9ee5 pw_dma_mcuxpresso: Module for working with NXP DMA

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 07f748073e5aa65..158200d25a8562f
Roller-URL: https://ci.chromium.org/b/8748016665705520353
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I7c1bd956975e2b45d11f14e551a1251d56f17282
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209702
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: 574b110527a3fb6f0c405df7b012355683d4c8b0
  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!