Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 3c68ed1f4dede449fa7fa6b205d94fc763a5de28
commit3c68ed1f4dede449fa7fa6b205d94fc763a5de28[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat Apr 20 21:52:44 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Apr 20 21:52:44 2024 +0000
tree6cf0dd3116f052b0e1da326a4cb1df22a7bacd84
parent95dd58e75b2a213c546619e14ec11862df07c74e [diff]
[third_party/pigweed] Roll 2 commits

4ab4b220f23f968 roll: sysroot
2de4acb67e7e38d roll: cmake

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 98a790ed35ba482..4ab4b220f23f968
Roller-URL: https://ci.chromium.org/b/8750101600228013329
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I90192c22dc7c935dc82a2eb126e8c0cd36326ba3
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205174
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 6cf0dd3116f052b0e1da326a4cb1df22a7bacd84
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!