All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Tricca <philip.b.tricca at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] Problem with Infineon Iridium SLB 9670 TPM2.0
Date: Sun, 18 Mar 2018 22:07:37 -0700	[thread overview]
Message-ID: <20180319050737.GE8769@intel.com> (raw)
In-Reply-To: trinity-6e000144-63dc-4e2f-b8d1-cd689dbbc4a3-1521378255578@3c-app-gmx-bs78

[-- Attachment #1: Type: text/plain, Size: 2994 bytes --]

Hey there madprops,

On Sun, Mar 18, 2018 at 02:04:15PM +0100, madprops(a)gmx.net wrote:
> <html><head>
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
> <div class="signature">
> <div class="signature">
> <div>I'm trying to get an &quot;Infineon Iridium SLB 9670 TPM 2.0 SPI Board&quot; run on my Raspberry Pi 3. I have downloaded, compiled and installed the latest versions of tpm2-abrmd, tpm2-tss and tpm2-tools. I started tpm2-abrmd as root, hoping that I can then interact with the Infineon TPM using tpm2-tools. &quot;tpm2_pcrlist&quot; and all other tpm2_* commands, however, return error &quot;ERROR: Failed to initialize tcti context: 0x1&quot;.</div>
> 

Can you please provide some more info about your configuration?
Specifically:
- the version of the TSS2 libraries you're using
- the version of the tabrmd you're using
- the configuration options you're passing to each

A log file from the tabrmd with logging dialed all the way up would be
helpful. Since tabrmd uses glib and it's logging infrastructure you dial
up the debug output all the way by setting `G_MESSAGES_DEBUG=all` in the
daemon's environment.

> <div>&nbsp;</div>
> 
> <div>Any ideas? Thanks!</div>

The most common issue we've seen people run into when installing from
source is that the default value for the `prefix` and some other
installation directories aren't what most expect.

Still, if you're running the daemon as root you shouldn't have any
issues w/r to permissions on the /dev/tpm0 device node so I wonder if
this node even exists on your platform. You may want to check to see if
`/dev/tpm0` is even present on your system. You're on an ARM platform
which means the kernel will only be aware of the TPM2 device you've
added if you configure the device tree properly.

Regards,
Philip

> <div>pi(a)raspberrypi:~/TPM/tpm2-abrmd $ uname -a<br>
> Linux raspberrypi 4.4.50-v7&#43; #1 SMP Wed Mar 14 14:01:00 PDT 2018 armv7l GNU/Linux (&lt;== includes patch provided by Infineon)</div>
> 
> <div>&nbsp;</div>
> 
> <div>pi(a)raspberrypi:~/TPM/tpm2-abrmd $ dmesg | grep tpm<br>
> [&nbsp;&nbsp;&nbsp; 3.700384] tpm_spi_tis spi0.1: 2.0 TPM (device-id 0xB6BC, rev-id 16)</div>
> 
> <div>&nbsp;</div>
> 
> <div>pi(a)raspberrypi:/etc $ cat /etc/os-release<br>
> PRETTY_NAME=&quot;Raspbian GNU/Linux 9 (stretch)&quot;<br>
> NAME=&quot;Raspbian GNU/Linux&quot;<br>
> VERSION_ID=&quot;9&quot;<br>
> VERSION=&quot;9 (stretch)&quot;<br>
> ID=raspbian<br>
> ID_LIKE=debian<br>
> HOME_URL=&quot;http://www.raspbian.org/&quot;<br>
> SUPPORT_URL=&quot;http://www.raspbian.org/RaspbianForums&quot;<br>
> BUG_REPORT_URL=&quot;http://www.raspbian.org/RaspbianBugs&quot;</div>
> </div>
> </div>
> </div></div></body></html>

> _______________________________________________
> tpm2 mailing list
> tpm2(a)lists.01.org
> https://lists.01.org/mailman/listinfo/tpm2


             reply	other threads:[~2018-03-19  5:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19  5:07 Philip Tricca [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-28 17:40 [tpm2] Problem with Infineon Iridium SLB 9670 TPM2.0 Philip Tricca
2018-03-28 15:51 Trevor Woerner
2018-03-23 20:42 Roberts, William C
2018-03-23 20:11 madprops
2018-03-23 19:58 Roberts, William C
2018-03-20 19:19 Philip Tricca
2018-03-19 20:17 madprops
2018-03-19 15:31 Philip Tricca
2018-03-19 10:49 Javier Martinez Canillas
2018-03-18 13:04 madprops

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=20180319050737.GE8769@intel.com \
    --to=tpm2@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.