| commit | 2521fce7bdcc911a7ed0dc0c8ebf2a3ea05d3102 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Apr 17 00:48:52 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 17 00:48:52 2024 +0000 |
| tree | 469153fc1b90a6c618e824a34fca676fd30ad54e | |
| parent | 0bbe2e72c3e7e5546610ebfd9c86ffeef268b8fb [diff] |
[third_party/pigweed] Roll 8 commits
5b8b84f452c9ced pw_snapshot: Process snapshots based on CPU archit
cfd57d8453d3291 pw_thread_freertos: Use TCB for running stack poin
343cadc83c5ea36 pw_cli: Fix subprocess runner arg concatenation
287a6a668c70176 pw_{presubmit,cli}: Move FileFilter
4ae73f61b725990 pw_{containers,hdlc,build,rpc,transfer}: Iterators
7c73477c547ec68 pw_cpu_exception_risc_v: Add initial backend struc
7ab7b73a3786fc2 pw_presubmit: Add bthost_package step
221767c03aacd1e pw_presubmit: Don't overwrite Bazel stdout files
https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 09c9355f6493ad0..5b8b84f452c9ced
Roller-URL: https://ci.chromium.org/b/8750452892090810193
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I54528fc6d4f507a979681ebaa445b80f68bef939
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204070
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!