Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
PSA: PSoC 6 Correct TRNG behaviour #10025
On PSA targets the TRNG should be accessible from the secure-side only.
Relevant tests passed
Pull request type
For me, removing TRNG device from CM4_PSA target (as it was before) looks more logical, than a simple NV_SEED disabling. If there are no TRNG device - than nobody can work with it. If only one feature that needs TRNG is disabled, somebody can try to work with TRNG via another feature. In case anybody tries to work with TRNG (HW PSoC6 block) from CM4, it causes a CM4 HardFault.
if a user will try to access the TRNG from the M4 core on a PSA target, the user will get into HardFault.
the HRNG API relies on the platform having TRNG macro, that is why we add