Hi:
If CPU is in secure state, and calling the none-secure world method. Dose this allowed or it will generat a security fault
Hello,
If you are changing secure OS, you can do that. You might need to map the normal world functions to secure world.
However, in general, this is not recommended because a malicious function can be executed with secure world privilege, which will compromise the secure world.
Hi Grent:
Thanks for you reply.
One thing want to know is that, If calling NS world method directly (which is in none-secure memory setup by SAU), for example using BL not BLNS to branch to a none-secure method address, will this leading to secure fault.
I didn’t realize that the question was about trustzone on v8-m. On v8-a, it is doable as long as the region is set as executable for both worlds by TZASC.