Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d7fd36caf107acb90d36e6e0bf5cb3a9024b6e65
commitd7fd36caf107acb90d36e6e0bf5cb3a9024b6e65[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Apr 04 00:38:32 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 04 00:38:32 2024 +0000
treed9020cb4d9fb2797158628604ac9dbe65b7de034
parentce264a3d2cef8929a43c7efceb18ee83b9d7987b [diff]
[third_party/pigweed] Roll 2 commits

f54d93143ffd79c pw_async2: Fix TSAN for dispatcher_thread_test
d54f6c446cd85ec mbedtls: Avoid the use of unsupported libc functio

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: c3dfc3987262a43..f54d93143ffd79c
Roller-URL: https://ci.chromium.org/b/8751631315372497601
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I50d6f50f30888c1e6105115307ca73c6b5e4c688
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201871
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: d9020cb4d9fb2797158628604ac9dbe65b7de034
  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!