| commit | 1ce33e6410009dd376aefe731e4ad479a10bd9c9 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Jul 09 20:52:12 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 09 20:52:12 2024 +0000 |
| tree | eeaa82d8423a098aca6139df3292ddebe1e12e0c | |
| parent | 510fb6734ebe973e890013ad0201bb13676548ea [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Add packet filtering consts to vendor protocol Original header: Add advertising packet filtering packet constants to vendor protocol Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/983023 GitOrigin-RevId: e542cb53235024b3ea521e0afccf5c38cf59a05b Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218978 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: a4580add7631db4..ebb087cf8898715 Roller-URL: https://ci.chromium.org/b/8742857926309221889 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I3ff2e565c2d177a6f7a3596c8b2890d1e900bc2c Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/220855 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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!