| commit | c66ede4a5f4c4548d2c95d9f6f3e39e35c953c84 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Aug 07 20:40:26 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 07 20:40:26 2024 +0000 |
| tree | 3a8961839039d04af06f7a809a3abcb0c7c2fddc | |
| parent | 23badfd8209e0081d998b57af6e15ab6b6e1c92a [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Handle switch warning with pigweed This switches over to using `pw_preproccesor` to annotate and disable switch related warnings. This fixes non-clang builds Original-Bug: b/355511476 Test: fx test //src/connectivity/bluetooth/core/bt-host Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1092485 GitOrigin-RevId: 3ec33d398c866760859f0891a04f1bff8b55f923 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/227044 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 17a6be9e3c21fcb..e6af48396fd8c94 Roller-URL: https://ci.chromium.org/b/8740231103396971761 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I3a829f8420e4ce364fd63a7885a7bcf270254ebc Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/228335 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> 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!