| commit | 03a5bd0841e0061c62dcfba1e1fa7fb27e2f4976 | [log] [tgz] |
|---|---|---|
| author | Dave Roth <davidroth@pigweed.infra.roller.google.com> | Wed Jul 24 02:33:46 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 24 02:33:46 2024 +0000 |
| tree | 5043599f8822e799011696376ce0f0bc92822e0d | |
| parent | d6afa4611024792ff95bf4e039400ab4e2c6830c [diff] |
roll: pigweed, pw_toolchain: pw_system: Add crash handling and device service - setup custom exception handler & assert_trap on rp2040 - add new device_service - populate the crash snapshot with metadata, cpu_state & logs - add device.get_crash_snapshots() to download crash snapshot from the console. Original-Fixes: pwbug.dev/350807773 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/224299 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: c67d79552acb924..4224d6d0c23cfd4 Roller-URL: https://ci.chromium.org/b/8741567848955910993 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I5928412571736bdc541ba17824c32691a3f07449 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225639 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!