回复: 回复: About FRU

周 远清 zhouyuanqing8 at outlook.com
Thu May 28 12:11:24 AEST 2020


Hi Vijay and Kwin,

    I will use entity manager package and test it, thank you very much!

Thanks,
Harley.
________________________________
发件人: Vijay Khemka <vijaykhemka at fb.com>
发送时间: 2020年5月28日 5:15
收件人: 周 远清 <zhouyuanqing8 at outlook.com>; Wang, Kuiying <kuiying.wang at intel.com>
抄送: openbmc at lists.ozlabs.org <openbmc at lists.ozlabs.org>
主题: Re: 回复: About FRU


Hi Harley,

You don’t need any configuration for eeprom if you are using entity manager package. Just add this package in your image and at the start /usr/bin/fru-device process will start which will enumerate all eeprom existed in the system and create a dbus interface for each fru device found. In my system, it shows like below.

Service xyz.openbmc_project.FruDevice:

    └─/xyz/openbmc_project/FruDevice

      ├─/xyz/openbmc_project/FruDevice/0_80

      ├─/xyz/openbmc_project/FruDevice/0_81

      ├─/xyz/openbmc_project/FruDevice/1_113

      ├─/xyz/openbmc_project/FruDevice/2_112

      ├─/xyz/openbmc_project/FruDevice/2_16

      ├─/xyz/openbmc_project/FruDevice/2_22

      ├─/xyz/openbmc_project/FruDevice/3_104

      ├─/xyz/openbmc_project/FruDevice/3_108

      ├─/xyz/openbmc_project/FruDevice/3_113

      ├─/xyz/openbmc_project/FruDevice/3_36

      ├─/xyz/openbmc_project/FruDevice/3_68

      ├─/xyz/openbmc_project/FruDevice/3_81

      ├─/xyz/openbmc_project/FruDevice/6_32

      ├─/xyz/openbmc_project/FruDevice/6_33

      ├─/xyz/openbmc_project/FruDevice/6_78

      ├─/xyz/openbmc_project/FruDevice/6_79

      ├─/xyz/openbmc_project/FruDevice/6_80

      ├─/xyz/openbmc_project/FruDevice/7_69

      ├─/xyz/openbmc_project/FruDevice/8_31

      ├─/xyz/openbmc_project/FruDevice/9_39

      ├─/xyz/openbmc_project/FruDevice/9_84

      ├─/xyz/openbmc_project/FruDevice/Ava_M_2_SSD_Adapter

      └─/xyz/openbmc_project/FruDevice/Tioga_Pass_Single_Side



Regards

-Vijay



From: 周 远清 <zhouyuanqing8 at outlook.com>
Date: Wednesday, May 27, 2020 at 1:33 AM
To: "Wang, Kuiying" <kuiying.wang at intel.com>, Vijay Khemka <vijaykhemka at fb.com>
Cc: "openbmc at lists.ozlabs.org" <openbmc at lists.ozlabs.org>
Subject: 回复: About FRU



Hi



     My project uses phosphor-fru, and a phosphor-read-eeprom is generated during compilation. I think when openbmc starts, phosphor-read-eeprom will read the configuration information of eeprom from a configuration file (such as i2c channel number, i2c address), and then read FRU information from eeprom.
     If the entity-manager module is used,add json configuration file for my device into entity-manager. then I use the phoshor-fru method, in which configuration file should I configure the eeprom information?



     phosphor-read-eeprom will exits after reading the eeprom information, so how is the FRU information read to the IPMI process?



Thanks

Harley





________________________________

发件人: Wang, Kuiying <kuiying.wang at intel.com>
发送时间: 2020年5月27日 15:58
收件人: zhouyuanqing8 at outlook.com <zhouyuanqing8 at outlook.com>
抄送: openbmc at lists.ozlabs.org <openbmc at lists.ozlabs.org>
主题: RE: About FRU



Hi Harley,

You could add json configuration file for your device into entity-manager as below:

https://github.com/openbmc/entity-manager/tree/master/configurations





Thanks,

Kwin.





Hello everyone,



       My motherboard has an EEPROM device to store FRU related information. How can I configure it in the openbmc configuration file to see this FRU information through the ipmitool fru print command?



Are there some examples to provide reference, I did not find a place to configure the eeprom device in the openbmc project?



Is there any documentation about FRU indicating that the module reads and parses information from eeprom, and then it can be read by the ipmitool fru print command? What is the process like?



Thanks

Harley




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200528/6c67a343/attachment-0001.htm>


More information about the openbmc mailing list