commit | 3758d1d406fd39989ba33c2c390e30cdd68f9695 | [log] [tgz] |
---|---|---|
author | Darren Chan <chandarren@pigweed.infra.roller.google.com> | Sat Mar 30 06:34:48 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Mar 30 06:34:48 2024 +0000 |
tree | de14ce88da38ede9fe45c8545905d8fb4bc29f0f | |
parent | 425c84f0e004d9529bcf600691feded073ecde7f [diff] |
[roll third_party/pigweed] pw_bluetooth_sapphire: Fuchsia testing support Add support for testing on Fuchsia by performing the following: 1. Introduces the fuchsia-infra-bazel-rules repository as @fuchsia_infra, allowing us to use `fuchsia_test_group` to run all target tests under the scope of a provisioned emulator. 2. Uprrev @com_google_googletest (gtest for Bazel) to contain 3b6d48e8d5c1d9b3f9f10ac030a94008bfaf032bb. This is needed to realize the upstream changes necessary to build gtests that run against a Fuchsia target. Original-Bug: 331692493, 42178254 Original-Fixed: 321267689 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/198270 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 16c27d8785cb548..314a6228d8b6aa8 Roller-URL: https://ci.chromium.org/b/8752061886392018753 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ifb79225c6fbf86fa696836348f6879d6a4d7c0b1 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201005 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
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.
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
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.
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!