commit | 118389fc8ec58cc0c929216831c63297f82ee673 | [log] [tgz] |
---|---|---|
author | Wyatt Hepler <hepler@pigweed.infra.roller.google.com> | Thu Aug 01 00:39:11 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 01 00:39:11 2024 +0000 |
tree | 9d24fe4f6def6dd0af2d709557275c1c02bd30aa | |
parent | b9d2283862460dffda5fac8eb7567440a3179e52 [diff] |
roll: pigweed, pw_toolchain: pw_tokenizer: decode_optionally_tokenized without a Detokenizer Make the Detokenizer optional for decode_optionally_tokenized. This makes handling optionally tokenized fields simpler and more consistent when a token database isn't loaded. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/226727 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 280aeccf0bef690..55c5087185c0ff3 Roller-URL: https://ci.chromium.org/b/8740850216371365553 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I079ed6ec6e51ca5006fa22ccbb9c5c1fe4dbe6c3 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226902 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!