| commit | 094d6090b42c8882c1ca94b7e729b7f2c766a2e6 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Jun 28 05:45:05 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 28 05:45:05 2024 +0000 |
| tree | 1da70492cbb326800d21751b1fc04a14cd597a82 | |
| parent | ba56b5249f9f5e51737e73a16badd07c2f44b10e [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Use Write instead of UncheckedWrite This reverts commit 87c346ab57a17eb746012398a3fcadec8dfdc0b6. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/983481 GitOrigin-RevId: 4e543d23c87b1ef5e692048954f79177f8280d1d Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/214675 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 4c71a9ac34f0607..14b2e4c65d8b10d Roller-URL: https://ci.chromium.org/b/8743911300444438833 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I7ecaf83688e0252f3da45733913c23f10848aede Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218795 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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!