Device tree for Orin NX in L4T R36.3 missing nodes for tegra-se

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
,
1

I noticed on my Orin NX unit the HW crypto (tegra-se) driver wasn’t being activated, and it turns out it’s because the necessary device tree nodes are missing for that SKU but present for all others. Copying those nodes causes the HW crypto to be loaded and used.

Was this an oversight or is there a reason why these nodes are missing?

4

hello stephen.segal,

please see-also developer guide, Security.
may I know what’s the Jetson security function you would like to enable?

5

I was trying to enable the HW crypto engine. The device tree nodes to report the existence of the hardware to Linux are missing from tegra234-p3768-0000+p3767-xxxx-nv-common.dtsi but are present in the other similar files for other SKUs:

                       crypto@15810000 {
                               status = "okay";
                       };

                       crypto@15820000 {
                               status = "okay";
                       };

                       crypto@15840000 {
                               status = "okay";
                       };

Adding this causes the HW crypto to be available. Why were these lines missing?

6

hello stephen.segal,

may I know which Orin NX SKU you’re working with?
you may check the flashing logs,
for instance,
Board ID(3767) version(300) sku(0005) revision(K.2)
Chip SKU(00:00:00:D5) ramcode(00:00:00:02) fuselevel(fuselevel_production) board_FAB(300)
or… you may using $ i2cdump -f -y 0 0x50 to check the module EEPROM,

8

Board ID 3767
Board SKU 0001
revision N.2
Chip SKU is 00:00:00:D4

9

FYI, it’s cryptsetup utility for using Security Engine (SE) hardware for data encryption and decryption.

10

In this case, the driver is isn’t being activated, so cryptsetup will just end up using software encryption.

11

hello stephen.segal,

to be more specific,
although crypto engine is set to disabled, security function will use software mechanism for encryption and decryption. it does not have any functional impact.

we’ve code update to enable crypto accelerators, (i.e. crypto@15820000, crypto@15840000), crypto@15810000 has removed since it is not valid for Orin NX/Nano.
hence, for your use-case,
you may enable them from device tree manually. please expect next JP-6 public release will include those changes as well.

13

Hi @JerryChang, could you tell me if the crypto accelerators are in use in JetPack 5.1.2? If not, is there a 5.X.X release that supports them?

14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.