From: Miquel Raynal <miquel.raynal@bootlin.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Issue enabling TPM 2.0 on RPI
Date: Mon, 17 Jun 2019 10:44:52 +0200 [thread overview]
Message-ID: <20190617104452.4bac57d1@xps13> (raw)
In-Reply-To: <7890E00D-0F97-45F3-B728-41E8F377B4E0@gmail.com>
Hi Elena,
Elena Unix <elenaunix01@gmail.com> wrote on Fri, 14 Jun 2019 09:43:46
+0200:
> Hello,
>
> I am trying to enable the TPM 2.0 SLB9670 in U-Boot for a Raspberry Pi 3 B+. More precisely, the TPM is on an add-on board, the IRIDIUM SLB9670.
> The communication between the RPI and the TPM is ensured by SPI so I enabled the software spi driver (spi-gpio) in U-Boot because the bcm28x spi driver is not available in U-Boot.
>
> CONFIG_SPI=y
> CONFIG_DM_SPI=y
> CONFIG_SOFT_SPI=y
Are you sure the SPI bus is correctly driven? Can you connect anything
else and ensure it works? You may also probe all the GPIO lines (using
an oscilloscope) and check each of them is clocked correctly.
>
> Then, I enabled the TPM support in U-Boot.
>
> CONFIG_CMD_TPM_V2=y
> CONFIG_CMD_TPM=y
If you use TPM V2, CMD_TPM is not needed. But that's not your problem.
> CONFIG_TPM_V2=y
> CONFIG_TPM2_TIS_SPI=y
> CONFIG_TPM=y
Looks fine.
>
> Finally, I updated my Device Tree.
> /dts-v1/
> / {
> ...
> aliases {
> spi0 = &soft_spi;
> };
>
> soft_spi: soft-spi {
> compatible = "spi-gpio";
> pinctrl-names = "default";
> pinctrl-0 = <&spi0_gpio7>;
> status = "okay";
> gpio-sck = <&gpio 11 0>;
> gpio-mosi = <&gpio 10 0>;
> gpio-miso = <&gpio 9 0>;
> cs-gpios = <&gpio 7 1>;
> #address-cells = <1>;
> #size-cells = <0>;
>
> slb9670: slb9670 at 0 {
> compatible = "tis,tpm2-spi";
> reg = <1>;
> #address-cells = <1>;
> #size-cells = <0>;
> spi-max-frequency = <32000000>;
You might want to slow down a bit this frequency, try it with 1MHz,
just for testing (and see something meaningful with the scope).
> status = "okay";
> };
> };
>
> spio0_gpio7: spio0_gpio7 {
> brcm,pins = <7 8 9 10 11>;
> brcm,function = <4>;
If you bit-bang the SPI bus, I suppose you must use the GPIO function
on each pin, is <4> the GPIO function or the SPI function?
> };
> ...
> };
>
> But, when I try to execute the following command :
> U-Boot> tpm2 init
>
> I have the following response :
>
> tpm_tis_spi_probe : missing reset GPIO
This is indeed harmless, just a warning.
> tpm_tis_spi_request_locality : Timeout getting locality : -2
This usually means you cannot talk to the chip.
> tpm_tis_spi_probe : could not request locality 0
> Could not find TPM (ret=-2)
>
> The Iridium board contains a reset circuit on board, which pulls the reset line of the TPM to GND after VCC becomes available, so the reset GPIO is not needed I think.
>
> I don’t see what is wrong with my setup, a little help would be very appreciated.
>
> Thank you in advance,
> Elena
> ___________
Good luck,
Miquèl
next prev parent reply other threads:[~2019-06-17 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 7:43 [U-Boot] Issue enabling TPM 2.0 on RPI Elena Unix
2019-06-17 8:44 ` Miquel Raynal [this message]
2019-06-17 9:06 ` Miquel Raynal
2019-06-17 13:54 ` Elena Unix
2019-06-17 13:46 ` Elena Unix
2019-06-17 14:28 ` Miquel Raynal
2019-06-20 10:39 ` Hecht, Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190617104452.4bac57d1@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox