Lines Matching full:hs

28 Falcons can run in Non-secure (NS), Light Secure (LS), or Heavy Secure (HS)
31 Heavy Secured (HS) also known as Privilege Level 3 (PL3)
33 HS ucode is the most trusted code and has access to pretty much everything on
34 the chip. The HS binary includes a signature in it which is verified at boot.
37 GSP in HS mode. FRTS, which involves setting up and loading content into the WPR
38 (Write Protect Region), has to be done by the HS ucode and cannot be done by the
43 These modes are less secure than HS. Like HS, the LS or NS ucode binary also
45 Falcon, another Falcon needs to be running in HS mode, which also establishes the
47 ucode in HS mode on the SEC2 Falcon, which then authenticates and runs the
61 BROM and DMA registers to trigger the Falcon to load the HS ucode from the system
62 memory into the Falcon's IMEM/DMEM. Once the HS ucode is loaded, it is verified
65 Once the verified HS code is running on a Falcon, it can verify and load other
67 verification is the same as HS; just in this case, the hardware (BROM) doesn't
68 compute the signature, but the HS ucode does.
71      Hardware (Boot ROM running on the Falcon) -> HS ucode -> LS/NS ucode.
75           HS ucode (Booter running on the SEC2) ->
79      While the CPU can load HS ucode onto a Falcon microcontroller and have it
82      HS ucode. For example, on an Ampere GPU, after the Booter ucode runs on the
83      SEC2 in HS mode and loads the GSP-RM binary onto the GSP, it needs to run
87      temporarily made to run HS ucode (which is itself loaded by the CPU via