| commit | d2abe3a8e1ab1fa2e0d8e0067f186e6c28014771 | [log] [tgz] |
|---|---|---|
| author | Chad Norvell <chadnorvell@pigweed.infra.roller.google.com> | Fri Jul 26 18:57:17 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 26 18:57:17 2024 +0000 |
| tree | 91eea2115e8e6c53edceae0d990167c471cd6ccb | |
| parent | 94ffb84fc8ce3c6463965725e96bd679920ffa9b [diff] |
roll: pigweed, pw_toolchain: pw_ide: VSC extension refactoring This is almost entirely a refactor, at least in spirit, if not completely by the book Embrace the Visual Studio code event system: Remove some redundant event handling in favor of leaning into the VSC event system, except for the refresh manager, which needs to remain editor-agnostic, but nonetheless needs a bridge to connect it to the VSC event system. Standardize on disposable class instances: There was a melange of different ways of initializing components and linking them together. Now we standardize on disposable class instances and an ad hoc constructor dependency injection system, plus event subscriptions in each component's constructor, reducing coupling. This should make things a lot clearer. Standardize import formatting Fix a bad dependency import Add pre-release build commands Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/226059 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: f73ddb4d76eb9df..84803f3af2d56dc Roller-URL: https://ci.chromium.org/b/8741324721322295809 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I145a976644f45d6830be9dfab3b4897c485e644f Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226049 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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!