| commit | ec1ce5beaafa351ea476eb2994f80791f4ff312c | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Jul 16 04:39:33 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 16 04:39:33 2024 +0000 |
| tree | 9c452a63a31bf5b6dbaeec01e8e9455d3ff07a1e | |
| parent | 98d463fab310bf17a0f53caf1b264e411dba817a [diff] |
roll: pigweed, pw_toolchain: pw_{kvs,stream}: Update bazel config
Bazel build targets that require file operations are not
compatible with MCUs. Excluding them from MCU builds.
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/223171
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 8f327bb620173a2..789f3ef5abc6b6e
Roller-URL: https://ci.chromium.org/b/8742284649291575825
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ia0a2996c329362a3f147680f4c9a8289a22206aa
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223242
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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!