| commit | 25f8042cdf008ad055880f268753ee8af69247e2 | [log] [tgz] |
|---|---|---|
| author | Jiacheng Lu <lujc@pigweed.infra.roller.google.com> | Thu Aug 01 03:40:24 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 01 03:40:24 2024 +0000 |
| tree | ce38203e07c2886261e9bb7d103fdd180dc9592e | |
| parent | 4be2d1c6b442ae649cc5034ca9493dd0774a7bbc [diff] |
roll: pigweed, pw_toolchain: pw_toolchain: Rustc cross compile to qemu-clang Original-Bug: 343111481 Support rustc GN toolchain cross compile to cortex-m3 targets. Cross compiling requires specifying target triple and target specific linker flags. Both triple and linker flags are propagated using rustflags defined in config. Adding more supported targets requires walking through related config declaration in pigweed codebase which defines linker flags and target triple, and populating corresponding rustflags. This change has been validated by building and running pw_rust/examples/basic_executable:hello on lm3s6965evb_qemu target. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/211994 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 2bccf25ed3d181d..ddcc251bcac0c2c Roller-URL: https://ci.chromium.org/b/8740838818238157361 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I4dc6bfebb1fd3b66a481b9d2136c8125744350de Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226905 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!