Changes between Version 1 and Version 2 of venice/edgelock

Timestamp:

08/12/2025 06:53:19 PM (3 days ago)

Author:

Ryan Erbstoesser

Comment:

add notes for veniceflex

venice/edgelock

@@ -2 +2 @@
 
 = NXP !EdgeLock Secure Enclave
-While the i.MX8M does have its own internal !EdgeLock Secure Enclave it only allows up to FIPS level 2 and in some cases level 3 is required (which requires the keys are stored in a different IC).
+
+Gateworks has added the NXP EdgeLock SEO52F Secure Element with FIPS 140-3 Level 3 Certification to VeniceFLEX and Catalina SBCs. 
+
+While the i.MX8M processor used on the SBCs does have its own internal !EdgeLock Secure Enclave it only allows up to FIPS level 2 and in some cases level 3 is required (which requires the keys are stored in a different IC).
 
 The SE05x speaks SCP03 on top of I2C and can co-exist with other I2C devices. It is often used within OPTEE with a trampoline driver that hooks into Linux with an SMC call to allow Linux owning the I2C bus but OPTEE still allowed controlled access
@@ -24 +27 @@
 The following Gateworks boards have a SE05x chip on-board:
 ||= Family =||= Board =||= Chip =||= bus/address =||= reset =||
-|| Venice   || GW8201-C+ || SE052F || I2C2@0x48 || N/A ||
+|| VeniceFLEX   || GW8201-C+ || SE052F || I2C2@0x48 || N/A ||
+
+* Note, the SE052F is not available on standard Venice, only VeniceFLEX
 
 
@@ -35 +40 @@
 Valid chip addresses: 48
 }}}
-  - the valid chip address above confirms SCL/SDA/VDD_3V3/GND are wired correctly and powered
+  - The valid chip address above confirms SCL/SDA/VDD_3V3/GND are wired correctly and powered
 
 Because there is no U-Boot or Linux kernel driver there does not need to be any device-tree node for the device.
@@ -42 +47 @@
 
 === NXP Plug & Trust Middleware
-The NXP Plug & Trust middleware communicates with the SE05x directly in userspace via the I2C device file (e.g., /dev/i2c-1). It uses the Linux I2C userspace interface (ioctl calls) to send T1oI2C APDUs, bypassing the need for a dedicated kernel driver. The middleware handles all protocol details, including authentication (e.g., SCP03) and command formatting. Because this is in userspace there is no dt entry needed as long as the I2C bus is enabled.
+The NXP Plug & Trust middleware communicates with the SE05x directly in userspace via the I2C device file (e.g., /dev/i2c-1). It uses the Linux I2C userspace interface (ioctl calls) to send T1oI2C APDUs, bypassing the need for a dedicated kernel driver. The middleware handles all protocol details, including authentication (e.g., SCP03) and command formatting. Because this is in userspace there is no device-tree entry needed as long as the I2C bus is enabled.
 
 There are multiple flavors of the NXP Plug & Trust Middleware below are very minimal examples of getting it up and running by building software on the target board itself.
@@ -50 +55 @@
 
 Notes:
- - example apps take a 'port' argument identifying the bus and address via <busdev>:<slaveaddr> (ie '/dev/i2c-1:0x48' for GW8201). Note that while the busdev is a Linux path that exists the ':0x48' will not exist in a device path)
- - the ssscli ssscli tool isnt' a standalone binary; its a python based CLI installed via setup.py after building the middleware libraries.
- - there are fairly detailed HTML docs within the docs directory 
+ - Example apps take a 'port' argument identifying the bus and address via <busdev>:<slaveaddr> (ie '/dev/i2c-1:0x48' for GW8201). Note that while the busdev is a Linux path that exists the ':0x48' will not exist in a device path)
+ - The ssscli ssscli tool isnt' a standalone binary; its a python based CLI installed via setup.py after building the middleware libraries.
+ - There are fairly detailed HTML docs within the docs directory 
 
 Building:
@@ -255 +260 @@
 
 Example:
- * build
+ * Build
 {{{#!bash
 # install pre-requisites
 apt update && apt install -y build-essential git cmake python3 python3-pip python3-setuptools python3-wheel libssl-dev libusb-1.0-0-dev pkg-config unzip wget
 
-# fetch code
+# Fetch code
 git clone https://github.com/NXPPlugNTrust/nano-package
 cd nano-package
 
-# configure
+# Configure
 cd examples/se05x_GetInfo/linux
 mkdir build
@@ -270 +275 @@
 cmake ../
 
-# build
+# Build
 make
 }}}