roll: third_party/pigweed pw_kernel: Add ARMv7-M architecture support Add PMSAv7 MPU support alongside existing PMSAv8 for ARMv8-M: - Split MPU registers into arch-specific modules (mpu_v7, mpu_v8) - Split CONTROL register definitions (msr_v7, msr_v8) - Add protection_v7.rs for PMSAv7 region configuration - Rename armv8m_app.ld.jinja to cortex_m_app.ld.jinja for shared ARMv7-M/ARMv8-M use - Update system generator for ARMv7-M targets - Fix ELF section address preservation in system assembler The PMSAv7 implementation uses sub-region disable bits for fine-grained memory protection within power-of-two aligned regions. Tested on MPS2-AN505 (Cortex-M33). Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/374432 Original-Revision: e6a6bcc12dc0096feace2be1d08e9d002d6e8aea Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: b91d195484aba8..e6a6bcc12dc009 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8686240251665359857 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: If17252e3d8c33d6b3c36a072bec9581fd3d11c66 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/390452
This repository outlines the recommended way of using Pigweed in a new or existing project. Feel free to fork this repository, or read it as a reference.
For more information see the Pigweed Getting started guide.
Check back for more complex examples and features coming soon!
Make sure you've set up Pigweed's prerequisites.
If you're on Windows, you can automate the initial setup by downloading the first-time setup script from cmd.exe:
curl https://pigweed.googlesource.com/pigweed/examples/+/main/tools/setup_windows_prerequisites.bat?format=TEXT > setup_pigweed_prerequisites.b64 && certutil -decode -f setup_pigweed_prerequisites.b64 setup_pigweed_prerequisites.bat && del setup_pigweed_prerequisites.b64
Then you can run the script with the following command in cmd.exe:
setup_pigweed_prerequisites.bat
Note: You may see a few UAC prompts as the script installs Git, Python, and enables developer mode.
Once that is done, you can clone this project with the following command:
git clone https://pigweed.googlesource.com/pigweed/examples
Pigweed uses a local development environment for most of its tools. This means tools are not installed to your machine, and are instead stored in a directory inside your project (Note: git ignores this directory). The tools are temporarily added to the PATH of the current shell session.
To make sure the latest tooling has been fetched and set up, run the bootstrap command for your operating system:
Windows
bootstrap.bat
Linux & Mac
source ./bootstrap.sh
After tooling updates, you might need to run bootstrap again to ensure the latest tools.
After the initial bootstrap, you can use use the activate scripts to configure the current shell for development without doing a full update.
Windows
activate.bat
Linux & Mac
source ./activate.sh
All of these commands must be run from inside an activated developer environment. See Environment setup
To build the project, documentation, and tests, run the following command in an activated environment:
pw build
Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:
pw watch
When you pull latest repository changes, run bootstrap:
source ./bootstrap.sh
If you're just launching a new shell session, you can activate instead:
source ./activate.sh
and rebuild with:
pw build
Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.