| commit | ec87df86af72b160054d4cdcc40b75c6acec51b7 | [log] [tgz] |
|---|---|---|
| author | Eric Rahm <erahm@pigweed.infra.roller.google.com> | Tue Jul 30 19:19:28 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 30 19:19:28 2024 +0000 |
| tree | bb5faf1662531f36ef62723762e10d2cc5e6d79f | |
| parent | 4b836fac808ceeff8315044a64faf38896712d78 [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Remove manufacturer list As of this CL, `GetManufacturerName(...)` will return a string containing the hexadecimal representation of the value provided, rather than looking up a full name in the table. Call sites of this function will likely be refactored and removed in a future CL. Test: pw presubmit Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/226472 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: f513cf21c32c28e..cbd04b9968e997f Roller-URL: https://ci.chromium.org/b/8740960983277316065 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Iaab08023027f5ba43fe37a26cef78c62e4dedc79 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226492 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!