commit | 136dcf4aba0c7d21e8f430bf24d93161190b4109 | [log] [tgz] |
---|---|---|
author | Jason Graffius <jgraff@pigweed.infra.roller.google.com> | Sat Jul 13 21:02:54 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jul 13 21:02:54 2024 +0000 |
tree | f3825a29e59d965e3d5da9bbe6d6e0f6ef99a884 | |
parent | 2ae48537def16653a69809bc24d48b002018e58c [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Fix all available lint errors This change is to help familiarize myself with the sapphire commit flow. Test: fx test //src/connectivity/bluetooth/core/bt-host Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1023552 GitOrigin-RevId: b078575a6e19a53d5dfdfcce8db867eb1af5ae26 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/221171 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: d20ce7ca399f68e..8bb5fb62c3b4ced Roller-URL: https://ci.chromium.org/b/8742494582165080145 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Iad6860c9427ac50256390047cda50d66eeff2ecb Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222952 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!