| commit | d56f4bee270bede41eb3f4ccab8d8aa1cda7fd67 | [log] [tgz] |
|---|---|---|
| author | Asad Memon <asadmemon@pigweed.infra.roller.google.com> | Wed Jul 31 18:54:51 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 31 18:54:51 2024 +0000 |
| tree | fb3501f41808ff6d6d0b69fd2be0eae4cbb726c3 | |
| parent | 13fb0844169d4d8e018480ac53e7b03c669327b0 [diff] |
roll: pigweed, pw_toolchain: pw_console: Bump version of console js, add titles to log panes Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/226831 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 8f276075de78ca5..93c2ec369ab5a18 Roller-URL: https://ci.chromium.org/b/8740871916104892801 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I5a7d6d0223f4bfdbb165806f29a0e3e168843763 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226893 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!