| commit | 70a80c8afc8c65bfba2508e848800fe11c062912 | [log] [tgz] |
|---|---|---|
| author | Armando Montanez <amontanez@pigweed.infra.roller.google.com> | Tue Apr 30 04:00:27 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 30 04:00:27 2024 +0000 |
| tree | a683712531dfd47857e42df38b694e35897eed80 | |
| parent | efa4a69b3d831fc0ca0240a9efaaf70d539927d3 [diff] |
[roll third_party/pigweed] npm: Update package-lock.json Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/207336 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 33d6d7e04508964..4d23123c37a3363 Roller-URL: https://ci.chromium.org/b/8749263083770605665 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I447e0130c92d697ba483742d1ea4493030bd6ac6 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207435 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!