You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sw/device/silicon_creator/rom_ext/doc/ownership.md
+28-4Lines changed: 28 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -732,6 +732,14 @@ See the definition in [datatypes.h](../../lib/ownership/datatypes.h).
732
732
### Rescue Configuration
733
733
734
734
The rescue configuration describes the owner's desired configuration of the ROM\_EXT rescue protocol.
735
+
- The owner may configure desired rescue protocol: Xmodem, USB-DFU or SPI-DFU.
736
+
- The owner may configure desired rescue trigger: UART break, Strapping combination or GPIO pin.
737
+
- When the trigger is UART break, at least 350us of the break condition must be observed on the UART RX line to trigger the rescue protocol.
738
+
- When the trigger is a strapping combination, the desired strap pattern must be configured (e.g. a value 0-61).
739
+
- When the trigger is a GPIO pin, the desired IO pin as well as the sense of the pin and whether or not to enable the internal pull-up/down resistor must be configured.
740
+
- The owner may configure rescue to be triggered by failure to boot an owner payload.
741
+
- The owner may configure rescue to be triggered by a watchdog timeout as the reset reason.
742
+
- The owner may configure rescue to automatically exit after a specific timeout of no activity.
735
743
- The owner may configure the region of flash to be erased and reprogrammed during firmware rescue.
736
744
- The owner may configure the allowed interactions with the rescue protocol.
737
745
- Allowed rescue modes permit whether the rescue client can upload firmware or interact with the boot log and boot services.
0 commit comments