| commit | f881dddf5c5ca8e5ddc11103013949e4d9027822 | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Fri Jul 19 00:08:23 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 19 00:08:23 2024 +0000 |
| tree | 9dab25d72ad24e6d80ace5e209b946b252d41b98 | |
| parent | 07d1ef65cd7485b7927fb6a4fcb63029b48d2764 [diff] |
roll: pigweed, pw_toolchain: pw_build: Introduce pw_py_binary This is a followup to http://pwrev.dev/215258: mark all Pigweed Python binaries as incompatible with MCU devices. Except for the changes to pw_build/python.bzl and pw_build/bazel.rst, this CL was generated by running, /usr/bin/buildozer 'set kind pw_py_binary' //...:%py_binary /usr/bin/buildozer 'new_load //pw_build:python.bzl pw_py_binary' //...:__pkg__ /usr/bin/buildozer 'fix unusedLoads' //...:__pkg__ Original-Bug: 258836641 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/224296 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 4ce00e68e47e917..acbc017cab7db9b Roller-URL: https://ci.chromium.org/b/8742029901600408833 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Id2baf4a03558ad1634eb1094ae626f8dd92eac72 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/224511 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!