| commit | 51fe0137be680e63cefce7d5323c6ec578fa2526 | [log] [tgz] |
|---|---|---|
| author | Austin Foxley <afoxley@pigweed.infra.roller.google.com> | Fri Jun 21 20:19:02 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 21 20:19:02 2024 +0000 |
| tree | 216d3f0a824b08e6e33b67b6b953539a6ef6c52c | |
| parent | 8be72876b81b56cd44e301871e13fafa3e554902 [diff] |
roll: pw_toolchain, pw_toolchain: pw_env_setup: Suppress error message when running outside git repo When doing pw_env_setup from a directory that is not a git repo, the cipd wrapper would log a 'fatal error' but continue on when determining which useragent to send with request. Suppress it the same way we suppress the other git call in this file. Write stderr to /dev/null. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/217216 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pw_toolchain, pw_toolchain Rolled-Commits: 144113cb55fa118..81b9531df0d3fcb Roller-URL: https://ci.chromium.org/b/8744490778677189681 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I27a32e97d1ba9812ae3f048ec06066355720c840 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217491 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!