| commit | 999f4c4aed12cb834e39ae493dbdf97f2db3ae2c | [log] [tgz] |
|---|---|---|
| author | Jordan Brauer <jtbrauer@pigweed.infra.roller.google.com> | Tue Jul 30 19:24:53 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 30 19:24:53 2024 +0000 |
| tree | ed409b587be8f208e1e98cca8806be1228441a55 | |
| parent | ec87df86af72b160054d4cdcc40b75c6acec51b7 [diff] |
roll: pigweed, pw_toolchain: pw_transfer: Use initial timeout when resending start chunks A start chunk may timeout the initial timeout, but when it is resent after that timeout, we use the typical chunk timeout. If that chunk was dropped and the transfer not started on the server side, the initial needs to be used again. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/226452 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: cbd04b9968e997f..cb0686574d879d8 Roller-URL: https://ci.chromium.org/b/8740960585325158577 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I99b4c60f5b68be4d05543a08d7a1bfc840c2e142 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226493 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!