| commit | 9156f74791346f4abcce25a8d4f94c162aa805bd | [log] [tgz] |
|---|---|---|
| author | David Rees <drees@pigweed.infra.roller.google.com> | Wed Jun 19 18:25:49 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 19 18:25:49 2024 +0000 |
| tree | d4aa78e82828d904598100701a4550f3ea75036c | |
| parent | 5b151b9ce94819965560e4c86c65c743ec0b744c [diff] |
roll: pw_toolchain, pw_toolchain: pw_bluetooth_proxy: Move to using H4Packet wrapper classes Use wrapper class rather than wrapper struct. This will make it easier to use mix of H4-based and HCI-based packets. It also will provide the location for releasing of buffers after container send. Original-Bug: 326499764 Original-Bug: 326497489 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/215222 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pw_toolchain, pw_toolchain Rolled-Commits: c6f3a9eeb718be6..e6c5165547f3054 Roller-URL: https://ci.chromium.org/b/8744678783291751073 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ifca044668da106b9f887a070739b85005499a25d Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/216931 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!