commit | e44e996649df448904de30408a5f042186b6d0f1 | [log] [tgz] |
---|---|---|
author | Scott James Remnant <keybuk@pigweed.infra.roller.google.com> | Fri May 10 04:08:56 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 10 04:08:56 2024 +0000 |
tree | 103c7cc4350efde1f232f52382e3d8dbde196eff | |
parent | 24fb840b24f90922a1bb853ff2701ae1ab8238f9 [diff] |
[roll third_party/pigweed] pw_boot_cortex_m: Emit pw_boot_Entry without prologue As the startup function, pw_boot_Entry must not have a stack frame, since its jobs include setting the stack pointer and limit. Original-Bug: b/339107121 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/208931 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: d533f317b8719a8..47018e2757e4c2c Roller-URL: https://ci.chromium.org/b/8748356581157445713 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ifeee339eec483624b3affa37dbdf36eb0f5b98f0 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209457 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!