Search results

Jump to navigation Jump to search
  • | 1 || Mode 2 - Alternative Secure? | 2 || Mode 4 - Non-secure?
    3 KB (537 words) - 21:58, 1 May 2023
  • ...ializes ARM [[TrustZone]] (ARM Secure kernel) through [[SKBL]] and ARM Non-secure kernel through [[NSKBL]]. ...nto DRAM and resets the ARM CPU. The stage at this point would have set up DRAM and the [[eMMC]] driver. There is no Virtual Memory Addressing at this poin
    6 KB (918 words) - 04:43, 1 May 2023
  • ...s higher privileges that the normal [[Kernel]]. On the Vita, it seems that secure world has only a few tasks, which is facilitating communication with the [[ ...ial thing is that Tzs libraries exports are only accessible to Tzs, so non-secure kernel modules cannot import them. For that reason, Tzs [[SceExcpmgr]] regi
    6 KB (860 words) - 00:18, 19 January 2024
  • A Secure Module, abbreviated as SM, is a module running in the [[Secure Block]] of the PS Vita. A SM is a SELF targetting the [[CMeP]] processor. B = Secure Modules List =
    3 KB (398 words) - 19:17, 20 September 2023
  • Syscon powers up and sets up DRAM, sets up boot context buffer, turns on the [[Kermit|KERMIT SOC]] which even ...tZone for execution in both a non-secure world and a sandboxed [[TrustZone|Secure World]]. However it is not the first processor to run on boot.
    12 KB (1,757 words) - 08:24, 9 August 2023
  • | 512MiB DRAM. | 1GiB DRAM for Development Kit.
    31 KB (4,305 words) - 19:50, 22 February 2024
  • ...w power state where the main application processor is turned off. The main DRAM state is preserved so upon resume, the kernel does not have to be reloaded. ...nfo at <code>0x1F001800</code>, [[Suspend#SKBL Resume code|then enters Non-secure state at <code>0x1F000000</code>]].
    12 KB (1,871 words) - 04:36, 19 June 2022
  • ...o SKBL text segment base address. See [[Physical_Memory#Secure_DRAM|Secure DRAM]].
    7 KB (780 words) - 21:59, 1 May 2023
  • | <code>PERVASIVE_SYS_SBEATB</code> - Pervasive Secure Bus Error Attribute | <code>PERVASIVE_SYS_SBEADR</code> - Pervasive Secure Bus Error Address
    27 KB (3,223 words) - 00:05, 1 February 2024
  • ...the data directly into the shared DRAM. After clearing the cache, the non-secure kernel has access to the data. Cmep will not decrypt if anything fails in i === Non-secure Kernel ===
    6 KB (1,004 words) - 08:27, 4 August 2023
  • ...enerator code many times, and to implement the generation code in the most secure layer: second_loader (excluding first_loader but that's because first_loade | 0x60 || 0x4 || second_loader || DRAM base paddr (0x40000000)
    33 KB (4,849 words) - 19:57, 30 March 2024
  • | Secure Modules ...command 0xD0. AES-128-ECB key used to encrypt/decrypt the content of Ernie secure packets. If (ernieVersion < 0x90903 && (ernieDLVersion & 0xffffff) < 0x3600
    15 KB (2,128 words) - 09:51, 18 March 2024
  • | Non-secure kernel bootloader mapping. This is unmapped after boot. | Debug PA Dram kernel mapping. If you have dipsw 0xD4, This is mapped.
    37 KB (4,938 words) - 05:51, 2 September 2023
  • | 0.940-3.60 || Non-secure || Kernel ...[[SceKernelModulemgr#SceModulemgrForKernel|SceModulemgrForKernel]] || Non-secure || Kernel || 0xC445FA63
    91 KB (11,099 words) - 06:25, 11 November 2023
  • ...ng material is a cmep payload that is constantly updating a CTR counter in DRAM. cmep state is verified by checking if this CTR counter is updated. secure-kernel failed to load and is stuck at "wait 2".
    173 KB (30,646 words) - 01:40, 23 February 2022