| commit | 0121807c50fe1b30752671d920fa330767e7ee3b | [log] [tgz] |
|---|---|---|
| author | Austin Foxley <afoxley@pigweed.infra.roller.google.com> | Tue Apr 30 07:00:23 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 30 07:00:23 2024 +0000 |
| tree | 1ee49ca355d83058a5b3334b2a037859d34c411e | |
| parent | 70a80c8afc8c65bfba2508e848800fe11c062912 [diff] |
[roll third_party/pigweed] pw_stream_uart_mcuxpresso: Add interrupt safe write-only uart stream Suitable for use in interrupt or fault handlers, it uses the blocking UART api which spins while tx fifo is drained. Also tested to be able to take over a UART that was already initialized elsewhere in the case of a fault handler. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/207414 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 4d23123c37a3363..5f043974e7207fb Roller-URL: https://ci.chromium.org/b/8749251763131447953 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Iaf3a65b114ba9af38e0154f7d15fe9c48c6a3238 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207530 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!