commit | e05e9154e0a42b1c6ce48761bfa7c5099d20872d | [log] [tgz] |
---|---|---|
author | Jason Graffius <jgraff@pigweed.infra.roller.google.com> | Fri Jul 12 00:00:08 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 12 00:00:08 2024 +0000 |
tree | f6086afa564e1f421e65824bc70b86f0d592ca4e | |
parent | 2e9c5d9089813cf7f45a2315ad4623de3ce65dac [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Remove modulo operator from asserts Because the assert macros can use format strings in some configurations, there must not be any `%` characters within the macro argument. This change fixes the one instance of this in pw_bluetooth_sapphire. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/222233 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: cca41e3e720679b..f2e580ecbc81acb Roller-URL: https://ci.chromium.org/b/8742664930028044097 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ie5fb7cbe48040cd1331cee7f68b46bb926f5b630 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222657 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!