| commit | 3371a5753d3dcc9c82af04f399418856915c603f | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@pigweed.infra.roller.google.com> | Fri Jun 28 21:58:32 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 28 21:58:32 2024 +0000 |
| tree | db1812acc1e85c74838ed52eb0af6aa71e807515 | |
| parent | a049fb4a62f59cf469b1cc74fcc9d40ced19d944 [diff] |
roll: pigweed, pw_toolchain: pw_system: Remove IPython from pw_system console - Remove the --ipython option from the pw_system console, since IPython is not well optimized for Pigweed. - Describe how to embed IPython in the pw_console docs. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218882 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: d6d285ab73303e4..d36dcb9fedb7b88 Roller-URL: https://ci.chromium.org/b/8743855439834445873 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I0c8cdcb6a5f09f7bda7db5ccfe4ada16343f61de Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218800 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!