Cool, thanks! Do you have the device tree snippet (or a reference to the DTS) handy by any chance? Oskar. On Tue, Dec 17, 2019 at 9:29 PM CS20 CTCchien wrote: > Hi, > > > > Yes, I just echo string to device node to bind and unbind. > > c0000000 is the FIU address in my system > > > > B.R. > > Medad > > *From:* Oskar Senft > *Sent:* Wednesday, December 18, 2019 10:23 AM > *To:* CS20 CTCchien > *Cc:* Vijay Khemka ; OpenBMC Maillist < > openbmc@lists.ozlabs.org> > *Subject:* Re: Bios upgrade > > > > Hi > > > > How do you do the rescan? That was the part I was curious about :-D > > > > Is it this ( > https://github.com/Nuvoton-Israel/openbmc/blob/runbmc/meta-phosphor/nuvoton-layer/recipes-phosphor/ipmi/phosphor-ipmi-flash/bios-update.sh#L38 > > )? > > cd /sys/bus/platform/devices/c0000000.fiu/driver > > echo -n "c0000000.fiu" > unbind > > echo -n "c0000000.fiu" > bind > > > > If so, what's the magic "c0000000.fiu"? > > > > Thanks > > Oskar > > > > On Tue, Dec 17, 2019 at 7:33 PM CS20 CTCchien > wrote: > > Hi, > > > > We have a gpio which could control the MUX > > When I want to do BIOS upgrade, I will shut down the host and operate the > gpio, and rescan, then BIOS flash will be accessible from BMC now. > > > > B.R. > > Medad > > > > *From:* Oskar Senft > *Sent:* Wednesday, December 18, 2019 4:57 AM > *To:* CS20 CTCchien > *Cc:* Vijay Khemka ; OpenBMC Maillist < > openbmc@lists.ozlabs.org> > *Subject:* Re: Bios upgrade > > > > Hi > > > > How did you configure the BIOS flash device? I assume via the device tree? > I haven't tested this in a while, but I seem to remember that if the BIOS > SPI flash is not accessible Linux doesn't "detect" the device and doesn't > create the MTD, i.e. it's not accessible from the BMC. This can be the case > if the mux between BMC, PCH and BIOS SPI flash) is configured to connect > the SPI flash to the BMC at the time the BMC boots. Or is there a way to > make BMC's Linux "rescan" for SPI flash chips at runtime? > > > > Thanks > > Oskar. > > > > On Tue, Dec 17, 2019 at 12:38 AM CS20 CTCchien > wrote: > > Hi Vijay, > > > > You could build a host daemon and a ipmi library on BMC from > phosphor-ipmi-flash > > Here is the link I implement BIOS upgrade on my system > > > https://github.com/Nuvoton-Israel/openbmc/tree/runbmc/meta-phosphor/nuvoton-layer/recipes-phosphor/ipmi > > . > > > > You need to prepare a BIOS image and a signature file for this BIOS > > After you execute the command on host, ipmid in BMC will launch a script > to upgrade BIOS. > > > > For example, > > sudo ./burn_my_bmc --command update --interface ipmipci --image BIOS.img > --sig BIOS.img.sig --type static > > > > > > B.R. > > Medad > > *From:* Vijay Khemka > *Sent:* Tuesday, December 17, 2019 8:16 AM > *To:* OpenBMC Maillist > *Subject:* Bios upgrade > > > > Hi, > > I am looking for bios upgrade from BMC. I looked at phosphor-ipmi-flash > but > > couldn’t figure out how to use this for bios upgrade. I checked few old > mails > > where oskar was asking about using user space application instead of > kernel. > > Can anyone please give steps to use any existing kernel driver or user > space > > Application for upgrading host firmware. > > > > Regards > > -Vijay > ------------------------------ > > 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. > > ------------------------------ > 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. >