| commit | ce37fc5d58000c52ad515a3491ec90b697e9adb0 | [log] [tgz] |
|---|---|---|
| author | Austin Foxley <afoxley@pigweed.infra.roller.google.com> | Wed Jun 19 00:26:01 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 19 00:26:01 2024 +0000 |
| tree | 3ede96bab619718bbf7759bf74d8f883bc568b91 | |
| parent | a7548a2f11a95b42ebacb4b5d4b0411b7d19d5e4 [diff] |
roll: pw_toolchain, pw_toolchain: python: Add python targets for pw_i2c, pw_digital_io protos Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216736 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pw_toolchain, pw_toolchain Rolled-Commits: 0af21c49fa7f692..2c8b44aa6836dd3 Roller-URL: https://ci.chromium.org/b/8744746769573194801 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I71a6773c4e48bf813a6205285e4c80a05010ca1b Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/216820 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!