-
Notifications
You must be signed in to change notification settings - Fork 0
double trouble ?
HannesH_Dev edited this page Feb 26, 2021
·
22 revisions
fear no more !
- project-> clean -> all
- build secure
- build nonsecure
Problemlösungen zeigen
stell sicher, dass du den Link, der dir per eMail geschickt wurde, in derselben Browserinstanz geöffnet wird, in welcher du den Download angefordert hast.
Problemlösungen zeigen
- erst Secure bauen dann nichtsecure, siehe Brechstange
Problemlösungen zeigen
- Stell sicher, dass dein USB-Kabel Datenübertragung unterstützt#
- Das soll so sein wenn du auf "run" statt auf "debug" drückst
- einmal den schwarzen Reset-Knopf drücken
Problemlösungen zeigen
If TrustZone is enabled it is not possible to disable it without activating the Read Out Protection and boot to RSS (Root Security Service), which boots the core in an unsecure state. However, before one should enable TrustZone and the Read Out Protection there are some important things to be checked:
- NEVER use Read Out Protection Level 2, once activated, the board will be locked forever
- Before enabling Read Out Protection Level 0.5 or 1, make sure to check the following options in the STM32CubeProgrammer:
- The BOOT LOCK Bit has to be set to 0
- The nSWBOOT0 has to be set to 1
- Also in the STM32CubeProgrammer, at the adresse 0x0BF97FFE, the Value should not be 0x00D0 Once these options have been checked, you may proceed to set the RDP Level to 0.5 or 1. Once you have raised the Level of the Read Out Protection you will not be able to connect yout device with the STM32CubeProgrammer, at least not until you boot to RSS. RSS can be booted by connecting Pin 5 and 7 at C11. Once these Pins are connected, you can reset the device. If the blue and red LED are turned on, you have sucessfully bootes to RSS. Now you can connect with the STM32CubeProgrammer and disable the Read Out Protection and TrustZone (TZEN Bit). After another reset, the device should be fully accessible and TrustZone is diabled
Ist hier keine Lösung für euer Problem zu finden, ihr denkt aber wir sind daran schuld, dann meldet euch gerne! Vielleicht findet ihr ja aber auch schon eine Lösung in den Issues denen wir schon begegnet sind.