commit | eb009eff18e89a9122e80313137262ce06765ba7 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Jul 18 00:37:11 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 18 00:37:11 2024 +0000 |
tree | 66bdda76d8d53f5fa2ef5d2b22923b04ff62f9b5 | |
parent | 5d7c5e67bcbaa8f5fb570f7270869f0931fd8804 [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Cleanup WriteLocalNameResponse to shared file Test: fx test bt-host-gap-tests Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1075499 GitOrigin-RevId: 12088a80adb621e4ddd5bb96050564ec146a3324 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/224094 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Lint: Eric Rahm <erahm@google.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 5592c7588a11a66..f5bb47bd0316e6a Roller-URL: https://ci.chromium.org/b/8742118744677972993 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I153dce03eda1b89dac25b17633c849e2061aadbf Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223801 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>
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!