Google Git
Sign in
pigweed / pigweed / quickstart / bazel / c820598dcee8155a26072c2553cdb31a646e43bb
commitc820598dcee8155a26072c2553cdb31a646e43bb[log] [tgz]
authorTed Pudlik <tpudlik@pigweed.infra.roller.google.com>Thu Jul 25 22:23:39 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 25 22:23:39 2024 +0000
tree6e66a4f20bc48333b6c12edf25210f5bfce46f85
parentb9e5a4932155fec2691345bc0057efd50578d3fb [diff]
roll: pigweed, pw_toolchain: roll: FreeRTOS for upstream

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: a7a84b2e1150d89..0792e045ef9cc27
Roller-URL: https://ci.chromium.org/b/8741402335622225649
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I550895af4c54fadd28f0e67f0dfe4a8fe6501f35
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226041
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: 6e66a4f20bc48333b6c12edf25210f5bfce46f85
  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!