linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Niewöhner" <linux@mniewoehner.de>
To: Ken Goldman <kgold@linux.ibm.com>, linux-integrity@vger.kernel.org
Subject: Re: [BUG] Nuvoton NCPT650 TPM 2.0 mode not working
Date: Wed, 28 Nov 2018 16:04:58 +0100	[thread overview]
Message-ID: <660e6a212c9048a6a9660722f2468406b70acb1c.camel@mniewoehner.de> (raw)
In-Reply-To: <010f0d36-66b1-0202-543b-d579db4b2d93@linux.ibm.com>

On Tue, 2018-11-27 at 17:31 -0500, Ken Goldman wrote:
> On 11/26/2018 2:15 PM, Michael Niewöhner wrote:
> > Hi again,
> > 
> > after some experiments I finally found a solution...
> > There seems to be a bug in TPM2.0 firmware version (1.3.1.0) included in
> > Lenovos
> > UEFI image but they do not provide an update.
> > 
> > I have extracted the firmware version 1.3.2.8 from Dell's XPS15 TPM2.0
> > firmware
> > update and used this to replace the firmware in my Lenovo UEFI image.
> > After flashing this version via UEFI Setup the TPM2.0 gets detected and now
> > is
> > fully working. WTF.
> > 
> > For anyone having the same problem: binwalk, uefi-firmware-parser, uefipatch
> > and
> > flashrom are your friends ;-)
> 
> Just to make sure I understand it, do I have this right?
> 
> 1.3.2.8 is Nuvoton's TPM firmware.  It was embedded in Dell's firmware 
> (UEFI?).  You extracted it from Dell and inserted it into Lenovo. 
> (UEFI?).  Then you flashed the TPM firmware.
> 

Exactly. The Lenovo UEFI Setup has the ability to switch between TPM1.2 and
TPM2.0 by flashing the appropriate Firmware. Lenovo has v1.3.1.0 for TPM in
their latest P320 UEFI image. I dumped the SPI flash rom, replaced the firmware
with UEFIPatch and flashed the image back. Then I had to select TPM1.2 to be
able to reflash TPM2.0 firmware as a second step.



  reply	other threads:[~2018-11-28 15:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-11 17:55 [BUG] Nuvoton NCPT650 TPM 2.0 mode not working Michael Niewöhner
2018-11-11 18:24 ` James Bottomley
2018-11-11 18:50   ` Michael Niewöhner
2018-11-11 18:57     ` James Bottomley
2018-11-11 20:09       ` Michael Niewöhner
2018-11-11 20:29         ` James Bottomley
2018-11-11 20:34           ` Michael Niewöhner
2018-11-11 21:11             ` Michael Niewöhner
2018-11-11 21:42               ` Mimi Zohar
2018-11-14 20:46                 ` Michael Niewöhner
2018-11-16 21:06                   ` Michael Niewöhner
2018-11-18  8:18                     ` Jarkko Sakkinen
2018-11-18 14:10                       ` Michael Niewöhner
2018-11-19 13:49                         ` Jarkko Sakkinen
2018-11-25 20:06                           ` Michael Niewöhner
2018-11-26 19:15                             ` Michael Niewöhner
2018-11-26 21:13                               ` Jarkko Sakkinen
2018-11-27 22:31                               ` Ken Goldman
2018-11-28 15:04                                 ` Michael Niewöhner [this message]
2018-11-13 10:50               ` Jarkko Sakkinen
2019-01-11 15:40     ` Mimi Zohar
2019-01-12  9:52       ` Michael Niewöhner
2019-01-12 10:49         ` Michael Niewöhner
2018-11-11 18:33 ` Mimi Zohar
2018-11-11 18:51   ` Michael Niewöhner
2018-11-13 10:28 ` Jarkko Sakkinen

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=660e6a212c9048a6a9660722f2468406b70acb1c.camel@mniewoehner.de \
    --to=linux@mniewoehner.de \
    --cc=kgold@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).