Home
last modified time | relevance | path

Searched refs:PSP (Results 1 – 8 of 8) sorted by relevance

/trusted-firmware-m-3.4.0/platform/ext/common/
Dexception_info.c15 uint32_t PSP; /* (Secure) PSP. */ member
123 SPMLOG_DBGMSGVAL(" PSP: ", ctx->PSP); in dump_exception_info()
219 ctx->PSP = PSP_in; in store_and_dump_context()
220 ctx->EXC_FRAME = get_exception_frame(ctx->EXC_RETURN, ctx->MSP, ctx->PSP); in store_and_dump_context()
/trusted-firmware-m-3.4.0/docs/releases/
D1.6.1.rst8 - Correctly apply the stack sealing for the PSP stack in library mode
/trusted-firmware-m-3.4.0/platform/ext/target/cypress/psoc64/Device/Source/gcc/
Dstartup_psoc64_s.S293 mrs r0, PSP
Dstartup_psoc64_ns.S456 mrs r0, PSP
/trusted-firmware-m-3.4.0/platform/ext/target/cypress/psoc64/Device/Source/armclang/
Dstartup_psoc64_ns.s294 mrs r0, PSP
/trusted-firmware-m-3.4.0/platform/ext/target/cypress/psoc64/Device/Source/iar/
Dstartup_psoc64_ns.s292 mrs r0, PSP
/trusted-firmware-m-3.4.0/docs/technical_references/design_docs/
Dtfm_physical_attack_mitigation.rst597 - Bypass the setting of the PSP limit register. Otherwise, a stack overflow
598 exception will happen. Because the secure PSP will be overwritten by the
Dcode_sharing.rst158 | Stack (PSP) |