STM32 based exercises#302
Open
jonathanpallant wants to merge 7 commits into
Open
Conversation
Deploying ferrous-systems-rust-exercises with
|
| Latest commit: |
b1086c3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://684a4309.ferrous-systems-rust-exercises.pages.dev |
| Branch Preview URL: | https://stm32-exercises.ferrous-systems-rust-exercises.pages.dev |
jonathanpallant
force-pushed
the
stm32-exercises
branch
3 times, most recently
from
July 22, 2026 10:50
1c0cdce to
6d0a08e
Compare
The extra comments are mostly to stop rustfmt reformatting that block inconsistently. But also they are helpful I think.
jonathanpallant
force-pushed
the
stm32-exercises
branch
from
July 22, 2026 10:53
6d0a08e to
cc8e78b
Compare
jonathanpallant
marked this pull request as ready for review
July 22, 2026 10:53
skade
reviewed
Jul 22, 2026
|
|
||
| ## Secure Watermark | ||
|
|
||
| Another part of the option bytes controls the "Secure Watermark" - that is, which pages in Flash are readable from Nonsecure mode. |
Contributor
There was a problem hiding this comment.
NIT. Is it "Nonsecure Mode" or "nonsecure mode"? Unsure about my English skills here though.
skade
reviewed
Jul 22, 2026
| @@ -0,0 +1,237 @@ | |||
| # Changing to Nonsecure Mode | |||
|
|
|||
| We got secure-mode running in the previous chapter. But we also want to run a | |||
Contributor
There was a problem hiding this comment.
Nit: secure-mode, nonsecure mode...
skade
reviewed
Jul 22, 2026
| * Call the BSP function to program the SAU. | ||
| * Call the BSP function to program the Global TrustZone Controller's Memory | ||
| Protection Controller for SRAM3 | ||
| * Use the `cortex-m` library function to bootstrap the Nonsecure application |
skade
reviewed
Jul 22, 2026
|
|
||
| No! | ||
|
|
||
| The point of TrustZone is to keep things in Secure mode (like encryption keys) a |
Contributor
There was a problem hiding this comment.
Nit: The paragraph above capitalises both: "Secure Mode", same with "Nonsecure Mode".
skade
reviewed
Jul 22, 2026
| secret from Nonsecure mode (which might get hacked when processing untrusted | ||
| input). | ||
|
|
||
| Secure mode has is more trusted, and has more permissions that Nonsecure mode. |
I'm not sure why the "STM32 Introduction and Preparation" link didn't work when outlined, but it works inline so that's fine.
I'm trying to consistently stick with nonsecure, not the hyphenated version, because that's what I mostly see in the Arm docs (although they are not consistent at all).
Secure Mode and Nonsecure Mode are specific terms of art, and get written in title case. But nonsecure SRAM, secure SCB - they get lower case. I also tried to use Nonsecure Mode binary rather than nonsecure app (although the example binary is still called 'nonsecure-app')
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding some exercises for the STM32 NUCLEO-U5A5ZJ board.
Unlike the nRF52840-DK we normally use, this board has a Cortex-M33 and supports TrustZone.