I’m trying to understand how the Nvidia Platform Security Controller (PSC) can be configured to set peripherals as secure for use by TrustZone’s secure world.
According to the Jetson Orin Nano data sheet, it has the PSC which supports TrustZone peripheral security:
Dedicated Platform Security Controller (PSC) for critical security use-cases, including secure boot and key management. Two dedicated NIST-compliant Security Engines (SE) for hashing, symmetric/public key cryptographic algorithms, key derivation, and random number generation.
• TrustZone technology support for DRAM and peripherals
I’ve checked out the miscellaneous configuration guide on the developer page which references psc features but it doesn’t mention anything about peripheral security or how this can be configured.
Could someone explain how the PSC can be used to isolate peripherals to the TrustZone secure world?
*** Please note that this reply is generated by LLM automatically ***
The Nvidia Platform Security Controller (PSC) is a critical component in the Jetson Orin Nano series, responsible for managing the security of peripherals and ensuring that sensitive data is protected. To configure the PSC to set peripherals as secure for use by TrustZone’s secure world, you’ll need to follow these steps:
Understand the PSC features: The PSC supports TrustZone peripheral security, which allows you to isolate peripherals to the TrustZone secure world. This feature is essential for ensuring that sensitive data is protected from unauthorized access.
Configure the PSC: To configure the PSC, you’ll need to use the miscellaneous configuration guide on the developer page. Although the guide doesn’t explicitly mention peripheral security, it provides information on how to configure the PSC features.
Use the Device Tree: The Device Tree is a data structure that describes the hardware components of the system. You can use the Device Tree to configure the PSC and set peripherals as secure. Specifically, you’ll need to modify the nvidia,psc node in the Device Tree to enable TrustZone peripheral security.
Set the peripheral security bits: To isolate peripherals to the TrustZone secure world, you’ll need to set the peripheral security bits in the PSC. This can be done by writing to the PSC_PERIPH_SEC register. The specific bits to set will depend on the peripheral you want to secure.
Verify the configuration: Once you’ve configured the PSC and set the peripheral security bits, you’ll need to verify that the configuration is correct. You can do this by checking the PSC status registers and ensuring that the peripherals are indeed isolated to the TrustZone secure world.
Comparison with other Jetson Orin series:
Jetson Orin NX: The Jetson Orin NX series also supports TrustZone peripheral security, but the configuration process may differ slightly. You’ll need to consult the Jetson Orin NX documentation for specific instructions.
Jetson AGX Orin: The Jetson AGX Orin series also supports TrustZone peripheral security, but the configuration process may differ significantly. You’ll need to consult the Jetson AGX Orin documentation for specific instructions.
In summary, configuring the PSC to set peripherals as secure for use by TrustZone’s secure world on the Jetson Orin Nano series requires a good understanding of the PSC features, the Device Tree, and the peripheral security bits. By following these steps, you can ensure that sensitive data is protected and that peripherals are isolated to the TrustZone secure world.
Here is some sample code to get you started:
#include <linux/device-tree.h>
#include <linux/psc.h>
// Get the PSC device node
struct device_node *psc_node = of_find_compatible_node(NULL, "nvidia,psc");
// Get the PSC device handle
struct psc_device *psc_dev = psc_get_device(psc_node);
// Set the peripheral security bits
psc_write(psc_dev, PSC_PERIPH_SEC, 0x1);
// Verify the configuration
uint32_t psc_status = psc_read(psc_dev, PSC_STATUS);
if (psc_status & PSC_PERIPH_SEC_BIT) {
printk(KERN_INFO "Peripheral security enabled\n");
} else {
printk(KERN_ERR "Peripheral security not enabled\n");
}
Note that this is just sample code and may not work as-is. You’ll need to modify it to suit your specific use case and ensure that it’s compatible with your system configuration.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
the code suggests configuring TrustZone security from within the Linux kernel? how is that secure. I was thinking it has to do with firewalls, so basically doing the changes before flashing since everything happens when booting.
The code isn’t actually suggesting that, the code it is showing is a (likely made up but close to the actual) configuration file for the jetson firmware, specifically the security configuration.
The configuration would mean that it would be flashed once and not modifiable from the Linux kernel since as you rightly pointed out would be insecure.
My quarrel is that the LLM generated response is making fields and values up, the platform security controller does have this capability but it’s unclear on how to make use of it.
The additional challenge which is separate from securing the peripheral is actually using the peripheral in the secure world. You’d need a driver for the peripheral compatible with OP-TEE which isn’t straight forward because OP-TEE doesn’t boot a full Linux kernel so development becomes bespoke to some degree.