| commit | 66c41963adfbdc550d4f34f076c7db880c8de20c | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Apr 15 21:47:51 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 15 21:47:51 2024 +0000 |
| tree | a8ca0b3d0957a6cae6cc4f9361b2b010f8916195 | |
| parent | 104e5c7e3fd9cce3b9c0b9b4f5a644fd0bc26cc4 [diff] |
[third_party/pigweed] Roll 2 commits 53e8f63714ca67b pw_web: Fix string manipulation in download logs 4152b6754ca7a74 pw_allocator: Add missing soong deps https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: e3c8e94cbffee47..53e8f63714ca67b Roller-URL: https://ci.chromium.org/b/8750554873833126785 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I1ab755a17e66fa0b6ad52ff6fb963e79aa70760d Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/203710 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!