Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 231bede341edf435430b53d549c163a13cfef403
commit231bede341edf435430b53d549c163a13cfef403[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 17 21:29:34 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 17 21:29:34 2024 +0000
tree6358833e5ca50c15b916c726246c05bbb9016244
parent7295a3246e5f066c101f96a75591a4ea4a8c6229 [diff]
roll: pigweed, pw_toolchain 3 commits

ee443d56579423e pw_stream_uart_mcuxpresso: Check init state in Dei
95951f4f88891c1 bazel: Modernize pip deps style
9c64c8d1cd1cec4 pw_cpu_exception_cortex_m: Make PC LR optional

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