<div dir="ltr">Thanks for the help.<br><br>I changed "Probe" : "TRUE", now entity manager configuration file is parsed and published to dbus a configuration.<br><br><span style="color:rgb(0,0,255)">root@rudra:~# busctl introspect --no-pager xyz.openbmc_project.EntityManager \<br>> /xyz/openbmc_project/inventory/system/board/Rudra_Baseboard/bmc_temp<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.Configuration.TMP75 interface - - -<br>.Address property s "0x4a" emits-change<br>.Bus property t 5 emits-change<br>.Name property s "bmc_temp" emits-change<br>.Type property s "TMP75" emits-change<br>xyz.openbmc_project.Configuration.TMP75.Thresholds0 interface - - -<br>.Delete method - i -<br>.Direction property s "greater than" emits-change writable<br>.Name property s "upper critical" emits-change writable<br>.Severity property d 1 emits-change writable<br>.Value property d 80 emits-change writable</span><br><br>dbus-sensors hwmon temperature sensor daemon is not recognizing the configuration interface: xyz.openbmc_project.Configuration.TMP75 <br><br><span style="color:rgb(0,0,255)">root@rudra:~# busctl tree --no-pager xyz.openbmc_project.HwmonTempSensor<br>Failed to introspect object / of service xyz.openbmc_project.HwmonTempSensor: The name is not activatable<br>No objects discovered.</span><br><br>In journalctl log the following messages are coming.<br><span style="color:rgb(0,0,255)"><br>hwmontempsensor[153]: Error communicating to entity manager<br>hwmontempsensor[566]: terminate called after throwing an instance of 'std::bad_variant_access'<br>hwmontempsensor[566]: what(): Unexpected index<br>phosphor-mapper[210]: Introspect call failed with error: generic:110, Connection timed out on process: xyz.openbmc_project.HwmonTempSensor path: /<br>systemd[1]: xyz.openbmc_project.hwmontempsensor.service: Main process exited, code=killed, status=6/ABRT<br>systemd[1]: xyz.openbmc_project.hwmontempsensor.service: Failed with result 'signal'.<br>systemd[1]: xyz.openbmc_project.hwmontempsensor.service: Service RestartSec=5s expired, scheduling restart.<br>systemd[1]: xyz.openbmc_project.hwmontempsensor.service: Scheduled restart job, restart counter is at 4.<br>systemd[1]: Stopped Hwmon Temp Sensor.<br>phosphor-mapper[210]: Introspect call failed with error: generic:110, Connection timed out on process: xyz.openbmc_project.HwmonTempSensor path: /<br>systemd-udevd[97]: Spawned process '/usr/bin/start_hwmon.sh start /devices/platform/ahb/ahb:apb/ahb:apb:bus@1e78a000/1e78a180.i2c-bus/i2c-5/5-004c/hwmon/hwmon2 /ahb/apb/bus@1e78a000/i2c-bus@180/tmp75@4c' [104] is taking longer than 59s to complete</span><br><br><br><br>Thanks and Regards,<br><br>Akash<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Dec 20, 2019 at 12:42 AM James Feist <<a href="mailto:james.feist@linux.intel.com">james.feist@linux.intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 12/19/19 1:12 AM, AKASH G J wrote:<br>
> Hi all,<br>
> I am using OpenBMC firmware for server board having Aspeed AST-2500.<br>
> <br>
> Followed <br>
> <a href="https://github.com/openbmc/entity-manager/blob/master/docs/my_first_sensors.md" rel="noreferrer" target="_blank">https://github.com/openbmc/entity-manager/blob/master/docs/my_first_sensors.md</a> <br>
> for populating sensor value to dbus. Entity manager configuration file <br>
> is given below.<br>
> {<br>
> "Exposes": [<br>
> {<br>
> "Address": "0x4f",<br>
> "Bus": 5,<br>
> "Name": "cpu0_vrd_temp",<br>
> "Thresholds": [<br>
> {<br>
> "Direction": "greater than",<br>
> "Name": "upper critical",<br>
> "Severity": 1,<br>
> "Value": 80<br>
> }<br>
> ],<br>
> "Type": "TMP75"<br>
> }<br>
> ],<br>
> "Name": "Rudra Baseboard",<br>
> "Probe": "xyz.openbmc_project.FruDevice({'PRODUCT_PRODUCT_NAME': <br>
> 'RUDRA'})",<br>
> "Type": "Board",<br>
> "xyz.openbmc_project.Inventory.Decorator.Asset": {<br>
> "Manufacturer": "$BOARD_MANUFACTURER",<br>
> "Model": "$BOARD_PRODUCT_NAME",<br>
> "PartNumber": "$BOARD_PART_NUMBER",<br>
> "SerialNumber": "$BOARD_SERIAL_NUMBER"<br>
> }<br>
> }<br>
> <br>
> Wrote sample FRU information on eeprom with the following content. Used <br>
> dd command for writing to eeprom.<br>
> <br>
> root@s2600wf:/sys/bus/i2c/devices/3-0056# cat eeprom<br>
> Product:<br>
> MANUFACTURER "ABC"<br>
> PART_NUMBER "12345"<br>
> PRODUCT_NAME "SAMPLENAME"<br>
> SERIAL_NUMBER "12312490840"<br>
<br>
This is not a legal IMPI FRU. FRU Device only allows legal fru based on <br>
the spec: <br>
<a href="https://www.intel.com/content/www/us/en/servers/ipmi/ipmi-platform-mgt-fru-infostorage-def-v1-0-rev-1-3-spec-update.html" rel="noreferrer" target="_blank">https://www.intel.com/content/www/us/en/servers/ipmi/ipmi-platform-mgt-fru-infostorage-def-v1-0-rev-1-3-spec-update.html</a><br>
<br>
For testing purposes using "Probe" : "TRUE" can be used as well.<br>
> <br>
> The dbus tree not showing /xyz/openbmc_project/FruDevice/SAMPLENAME<br>
> <br>
> root@s2600wf:~# busctl tree --no-pager xyz.openbmc_project.FruDevice<br>
> `-/xyz<br>
> `-/xyz/openbmc_project<br>
> `-/xyz/openbmc_project/FruDevice<br>
> <br>
> In journalctl log the following messages are printed.<br>
> <br>
> systemd[1]: Started Hwmon Temp Sensor.<br>
> hwmontempsensor[120]: Error communicating to entity manager<br>
> hwmontempsensor[120]: error communicating to entity manager<br>
> <br>
> Look like FruDevice daemon is not parsing the contents of eeprom and <br>
> publish them to dbus.<br>
> <br>
> Is there any thing missing in configuration? Please help to resolve the <br>
> problem.<br>
> <br>
> <br>
> <br>
> Thanks,<br>
> <br>
> Akash<br>
> <br>
</blockquote></div>