phosphor-ipmi-flash: A problem in BMC FW update over LPC

Patrick Venture venture at google.com
Tue Sep 10 03:27:14 AEST 2019


On Sun, Sep 1, 2019 at 8:02 PM CS20 CTCchien <CTCCHIEN at nuvoton.com> wrote:
>
> Hi Patrick,
>
> I use latest phosphor-ipmi-flash, and I met an error about /flash/image in bmc/config-static-bmc-reboot.json.in,
> I change it to /flash/static, then the issue disappeared.
> Did I miss something?

The name of the thing in the json file is the type to use now with the
"--type" parameter, not the whole name, just the ending.  So
/flash/static becomes --type static, and /flash/image becomes --type
image

It was a change related to needing to support arbitrary update targets.
>
> Thanks
>
> B.R.
> Medad
>
>
> -----Original Message-----
> From: Patrick Venture <venture at google.com>
> Sent: Friday, August 23, 2019 10:43 PM
> To: CS20 KWLiu <KWLIU at nuvoton.com>; Benjamin Fair <benjaminfair at google.com>
> Cc: CS20 CTCchien <CTCCHIEN at nuvoton.com>; Corey Chen (陳志銘) <Corey.Chen at quantatw.com>; Fran Hsu (徐誌謙) <Fran.Hsu at quantatw.com>; Samuel Jiang (江騏先) <Samuel.Jiang at quantatw.com>; George Hung (洪忠敬) <George.Hung at quantatw.com>; openbmc at lists.ozlabs.org
> Subject: Re: phosphor-ipmi-flash: A problem in BMC FW update over LPC
>
> On Fri, Aug 23, 2019 at 4:13 AM CS20 KWLiu <KWLIU at nuvoton.com> wrote:
> >
> > Hello Patrick:
> >
> >
> >
> > We are currently trying to enable the BMC FW update over LPC on our platform (nuvoton BMC), but we encounter a problem with BIOS.
> > The BIOS engineer has reserved memory region as mmio space, but we couldn't see any data change in this region during run burn_my_bmc.
> > We have checked the BMC setting(in lpc_nuvoton.c and LDN SHM) but we couldn't identify the root cause of this problem.
>
> +Benjamin Fair
>
> I don't know the Nuvoton BMC that well, but I do know that I tested it on a system we have that uses it.  I'm adding Benjamin as he's more familiar with any nuances associated with Nuvoton's BMC.
>
> >
> >
> >
> > Is there any settings we lost?
> >
> >
> >
> > Thanks,
> >
> > Joseph
> >
> > ________________________________
> > The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.
> ________________________________
> ________________________________
>  The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.


More information about the openbmc mailing list