<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>Hi Patrick,</div><div><br></div><div>  1.  According to your 
suggestion, I can scan my FRU information via busctl command, but 
entity-manager did not start and can not be accessed.</div><div>The log is as below:<br></div><div>"</div><div>busctl tree --no-pager xyz.openbmc_project.FruDevice <br>`-/xyz <br>  `-/xyz/openbmc_project <br>    `-/xyz/openbmc_project/FruDevice <br>      |-/xyz/openbmc_project/FruDevice/10_64 <br>      |-/xyz/openbmc_project/FruDevice/10_65 <br>      |-/xyz/openbmc_project/FruDevice/10_67 <br>      |-/xyz/openbmc_project/FruDevice/3_80 <br>      |-/xyz/openbmc_project/FruDevice/6_72 <br>      |-/xyz/openbmc_project/FruDevice/6_74 <br>      |-/xyz/openbmc_project/FruDevice/6_76 <br>      |-/xyz/openbmc_project/FruDevice/7_81 <br>      |-/xyz/openbmc_project/FruDevice/7_89 <br>      `-/xyz/openbmc_project/FruDevice/test</div><div><br></div><div>busctl introspect --no-pager xyz.openbmc_project.FruDevice \ <br>>  /xyz/openbmc_project/FruDevice/Brahma______________ <br>NAME                                TYPE      SIGNATURE RESULT/VALUE                       FLAGS <br>org.freedesktop.DBus.Introspectable interface -         -                                  - <br>.Introspect                         method    -         s                                  - <br>org.freedesktop.DBus.Peer           interface -         -                                  - <br>.GetMachineId                       method    -         s                                  - <br>.Ping                               method    -         -                                  - <br>org.freedesktop.DBus.Properties     interface -         -                                  - <br>.Get                                method    ss        v                                  - <br>.GetAll                             method    s         a{sv}                              - <br>.Set                                method    ssv       -                                  - <br>.PropertiesChanged                  signal    sa{sv}as  -                                  - <br>xyz.openbmc_project.FruDevice       interface -         -                                  - <br>.ADDRESS                            property  u         80                                 emits-change <br>.BOARD_FRU_VERSION_ID               property  s         "UVD050"                           emits-change <br>.BOARD_INFO_AM1                     property  s         "V1  "                             emits-change <br>.BOARD_INFO_AM2                     property  s         "0123456789ABCDE001TAG0000002  " emits-change <br>.BOARD_INFO_AM3                     property  s         "R1B "                             emits-change <br>.BOARD_INFO_AM4                     property  s         "XX1 "                             emits-change <br>.BOARD_INFO_AM5                     property  s         "0E11223344E0"                     emits-change <br>.BOARD_INFO_AM6                     property  s         "02"                               emits-change <br>.BOARD_LANGUAGE_CODE                property  s         "0"                                emits-change <br>.BOARD_MANUFACTURER                 property  s         "Huaqin Telecom  "                 emits-change <br>.BOARD_MANUFACTURE_DATE             property  s         "1996-07-07 - 10:57:00"            emits-change <br>.BOARD_PART_NUMBER                  property  s         "NA                  "             emits-change <br>.BOARD_PRODUCT_NAME                 property  s         "test              "             emits-change <br>.BOARD_SERIAL_NUMBER                property  s         "3120E33900011X0010            " emits-change <br></div><div><br></div><div>root@sky:/etc/default/obmc/eeproms/system/chassis# echo "24c64 0x50 > /sys/bus/i2c/devices/i2c-3/new_device" <br>24c64 0x50 > /sys/bus/i2c/devices/i2c-3/new_device <br><b>root@sky:/etc/default/obmc/eeproms/system/chassis# busctl tree --no-pager xyz.openbmc_project.EntityManager </b><br><b>Failed to introspect object / of service xyz.openbmc_project.EntityManager: The name is not activatable </b><br><b>No objects discovered. </b><br></div><div>"</div><div><br></div><div>I
 modified one of the configuration which is in 
entity-manager/configuration folder, its name is Mt_jade.json, The 
modification is as below from line 759:</div><div>      "Name": "$bus test",<br>      "Probe": "xyz.openbmc_project.FruDevice({'PRODUCT_PRODUCT_NAME': 'test'})",<br>        "Type": "Chassis",</div><div><br></div><div>Still occurred the above log.<br></div><div><br></div><div>2. According to meta-quanta's commit, I did not find they modify entity-manager/configuration files. And I tried the method, however <b>I can not display them to "ipmitool fru" </b><br></div><div><br></div><div>"</div><div>commit 0de4856d037ff2525b3dd74ce2cbafdd4dcff443<br>Author: Joseph Fu <joseph.fu@quantatw.com><br>Date:   Wed Jan 26 14:37:42 2022 +0800<br><br>    meta-quanta: s6q: add fru yaml config files<br>    <br>    Add fru setting config and device json file.<br></div><div>" <br></div><div style="margin: 0;"><br></div>Could you provide some suggestions?<p style="margin: 0;"><br></p><p style="margin: 0;"><br></p><p style="margin: 0;"><br></p><p style="margin: 0;"><br></p><div style="position:relative;zoom:1"></div><div id="divNeteaseMailCard"></div><p style="margin: 0;"><br></p><pre><br>At 2022-02-16 03:34:38, "Patrick Williams" <patrick@stwcx.xyz> wrote:
>On Tue, Feb 15, 2022 at 11:13:22AM +0800, damon3000 wrote:
>> Hi All,
>> 
>> I am new to openbmc. I am started porting openbmc features to new hardware.
>> So, I want to add support for FRUID EEPROM. FRUID contents should be available as dbus objects. What changes needs to done in the application side.
>> 
>> Please provide the steps or suggestions to follow.
>
>You should probably look at https://github.com/openbmc/entity-manager and
>existing systems that leverage it.  There is already support for specifying the
>location of your EEPROM and interpreting it / exposing as dbus objects.
>
>'FruDevice' is typically involved in the EEPROM parsing and then there is
>entity-manager JSON that exposes specific EEPROM fields as the Inventory
>object(s).
>
>-- 
>Patrick Williams
</pre></div><br><br><span title="neteasefooter"><p> </p></span>