| commit | 61de2cf65fd906de5a077ca6823fab61c96093a9 | [log] [tgz] |
|---|---|---|
| author | Jonathon Reinhart <jrreinhart@pigweed.infra.roller.google.com> | Sat May 11 01:09:55 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat May 11 01:09:55 2024 +0000 |
| tree | 2b3811730805882b6ace3261c92b899f5cd9d1ff | |
| parent | 42d8362e03ef7103f5f6e5178aaebd1cc72bb0ae [diff] |
[roll third_party/pigweed] pw_digital_io_linux: Add test_utils.h for ASSERT_OK and friends This is temporary until b/338094795 officially adds these to the light testing framework. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/209592 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 56f740f4aa97088..eed9f3c4cb733f7 Roller-URL: https://ci.chromium.org/b/8748277262046147505 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I905978c78045ebcf55be42a9417168ae992e12af Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209562 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!