commit | 926107435ead137a6dedb6b6b7ff6049e427f8a9 | [log] [tgz] |
---|---|---|
author | Anthony DiGirolamo <tonymd@pigweed.infra.roller.google.com> | Mon Aug 05 21:28:02 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 05 21:28:02 2024 +0000 |
tree | 8e0b76e9024f9f2bc80d65a0364e4b41720e044b | |
parent | ce55914ca808bcf8bd9b9ba6aabd616f53f08ca5 [diff] |
roll: pigweed, pw_toolchain: pw_system: Separate host and device console log levels - Add --host-log-level and --device-log-level for finer grain control over logging levels. - Set default level for host to INFO and device to DEBUG. - The old --verbose option now modifies the host log level only. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/227599 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 38133403fcbccb0..6cd58e15a9a5c86 Roller-URL: https://ci.chromium.org/b/8740409272709138913 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I9583607e9436d5e05dd0e35827324d9f0f37c729 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/227694 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!