| commit | d47b2ab5c778cf3585e2948c89ef577e7411d5fd | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Mon Jul 01 20:47:51 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 01 20:47:51 2024 +0000 |
| tree | 9397bf075e4094f2dad1327db585f17de963eadd | |
| parent | a7987e39c4a816f14e27804827fe7b410126d40a [diff] |
roll: pigweed, pw_toolchain: bazel: Introduce incompatible_with_mcu Also provide one example of using it: mark //pw_stream:socket_stream incompatible_with_mcu (unless the platform declares compatibility through a module-specific constraint value). Original-Bug: 348008794 Original-Fixed: 343481391 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216851 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 324824be015681a..947d85d964b002e Roller-URL: https://ci.chromium.org/b/8743582714397112081 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia86fc7ffbd5704a7df8c7accc8f667c15a711262 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/219433 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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!