commit | 194a3cba2148b5ce5e6572d05b0fc6a1b23349b5 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri May 31 22:25:26 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 31 22:25:26 2024 +0000 |
tree | 574b66196a5aa96e0bf87c441225cb3c45565e4d | |
parent | 481656ef8e5886d09dae884c9c606a5b369299a2 [diff] |
[third_party/pigweed] Roll 10 commits 93fa287dc5010cf targets/rp2040: Add pico/debug probe filtering fla bdc50b62ca4c11a pw_log_string: Set default log backend da28a3e5e0b0048 pw_stream_uart_mcuxpresso: InterruptSafeWriter exa 1aa9d51028fcbc3 pw_stream_uart_mcuxpresso: Stream example a9a64a72393ed20 pw_stream_uart_mcuxpresso: Use clock tree 57310630f125c37 pw_clock_tree: Introduce ElementController class 1a672e2605ac5a4 pw_clock_tree_mcuxpresso: Fix source set name and 1d491c30feb54ee pw_clock_tree: Fix source set name and visibility aaa553c8693be3d pw_stream_uart_mcuxpresso: DMA stream example e8dcc48f4c5e8aa mimxrt595: Upgrade to SDK_2_14_0_EVK-MIMXRT59 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 1f6ad3a910c7cb0..93fa287dc5010cf Roller-URL: https://ci.chromium.org/b/8746385066242180129 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Idf23c1e04acdc42cea2e83988c77ad9bb39eea17 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213091 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!