Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 7058d9d183096efa6d7b0680b8f87b3c3d8931ef
commit7058d9d183096efa6d7b0680b8f87b3c3d8931ef[log] [tgz]
authorJimmy Chen <jimmycmchen@pigweed.infra.roller.google.com>Wed Jul 10 02:53:50 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 10 02:53:50 2024 +0000
treef0921280d79448f467b2e7bb1b38cf2ed749d9f3
parent3ae7f6f82741f5f51ac5d4a2469a76d4d05ed6ed [diff]
roll: pigweed, pw_toolchain: pw_malloc_freertos: Fix typo

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 1154e3a6281e5ce..73623f58298ca29
Roller-URL: https://ci.chromium.org/b/8742835282794742385
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I57fc359cfad5cf836a8352a5121b756c98804c63
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/221192
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: f0921280d79448f467b2e7bb1b38cf2ed749d9f3
  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!