TPM module integration with Colibri iMX6ULL

Technical Support
, ,
1

I need some information about which model TPM can be used. somebody can help me?

2

Hi @fxtsupport ,

Welcome to the community! :tada:

Which OS are you using?

Can you elaborate on your use-case? Where are you planing to use the TPM? On U-Boot level or kernel level?

Best Regards
Kevin

3

Hi @kevin.tx , sorry for delay.

I will use Yocto.
My device is a client that communicate with a server using crypto E2E.
I need to use the TPM to store the key pairs.

Which TPM module it is recommended? (I think to use IRIDIUM SLM 9670 TPM2.0)

https://www.infineon.com/cms/en/product/evaluation-boards/iridium-slm-9670-tpm2.0/

How integrate it with BSP?

Thanks

4

Can you give me something information how use tpm2 ?

5

Hello @fxtsupport ,
Here you have a post where the customer managed to do some tests with a similar module, maybe this helps:

Best regards,
Josep

6

Hello @fxtsupport ,
Do you have any updates on this topic?

Best regards,
Josep

7

I’m tryng.
My current setup is Iris + Infineon-Iridium_1-0_9670 but I have difficult on SPI to active correctly.

8

Hello @fxtsupport

Could you give us more details on that issue? (error messages, logs, etc…)

Best regards,
Josep

9

I reset all.

I need the correct sequence to apply for link tpm module SLI9670.

Can you help me?

I connect the module (see attached the PDF) like this:

SIGNAL SLI 9670 iM6xULL Colibrì IRIS X16
PWR 1 - 33
GND 6 - 36
CS 26 86 9
MOSI 19 92 11
MISO 21 90 10
SCLK 23 88 8

But I have problem to modify dtb.

Infineon-Iridium_1-0_9670_HD-AdditionalTechnicalInformation-v01_01-EN.pdf (763.3 KB)

10

Hi @fxtsupport !

Could you please share what and how you tried?

We can try to help you from your starting point.

Best regards,

11

I have activated on kernel the INFINEON and SPI module; see attached devconfig.

But when started the dmesg write:
…
5.788643] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 6.038975] systemd-journald[113]: Received client request to flush runtime journal.
[ 8.546683] caam-snvs 20cc000.caam-snvs: violation handlers armed - init state
[ 8.849837] spi_imx 2008000.spi: probed
[ 8.891945] imx-sdma 20ec000.sdma: loaded firmware 3.5
[ 10.817597] crng init done
[ 10.822038] random: 3 urandom warning(s) missed due to ratelimiting
[ 12.613366] CAN device driver interface
[ 13.667597] mcp251x spi0.0: MCP251x didn’t enter in conf mode after reset
[ 13.676304] mcp251x spi0.0: Probe failed, err=16
[ 13.769242] mcp251x: probe of spi0.0 failed with error -16
[ 13.964807] Bluetooth: Core ver 2.22
[ 13.990458] NET: Registered protocol family 31
…

Under /sys/bus/spi/drivers i found:
at25 mcp251x spidev st33zp24-spi tpm_tis_spi

How I must change the device tree?

defconfig (133.0 KB)

12

Hi @fxtsupport!

Could you please share the output of tdx-info?

Best regards,

14

I modify my dtb using the patch attached.

Can you help me to investigate what’s happens?
0001-configurazione-device-tpm.patch (1.7 KB)
imx6ull-colibri-eval-v3.dtsi (3.3 KB)

15

see on attached

tdx_info.txt (2.7 KB)

16

Hello @fxtsupport ,
Maybe these topics from the NXP community might help you. They are not for iMX6ULL specifically but can give some ideas where the problem could be. https://community.nxp.com/t5/i-MX-Processors/Interface-TPM-2-0-SLB9670-with-IMX8M-processor/m-p/1430035
https://community.nxp.com/t5/i-MX-Processors/i-MX8MP-SPI-connection-with-TPM-SLB9670/m-p/1612460
TPM SLB9670 with IMX6-UL - NXP Community

this is also the overlay for Raspberry linux/tpm-slb9670-overlay.dts at rpi-6.1.y · raspberrypi/linux · GitHub
The “official” board for this TPM supported by Infineon

tpm-slb9670-overlay.dts


/*
* Device Tree overlay for the Infineon SLB9670 Trusted Platform Module add-on
* boards, which can be used as a secure key storage and hwrng.
* available as "Iridium SLB9670" by Infineon and "LetsTrust TPM" by pi3g.
*/

/dts-v1/;
/plugin/;

/ {
compatible = "brcm,bcm2835";

fragment@0 {
target = [&spi0];
__overlay__ {
status = "okay";
};
};

fragment@1 {
target = [&spidev1];
__overlay__ {
status = "disabled";
};
};

fragment@2 {
target = [&spi0];
__overlay__ {
/* needed to avoid dtc warning */
#address-cells = [1];
#size-cells = [0];
slb9670: slb9670@1 {
compatible = "infineon,slb9670";
reg = [1]; /* CE1 */
#address-cells = [1];
#size-cells = [0];
spi-max-frequency = [32000000];
status = "okay";
};

};
};
};