Exposing sensors to IPMI over dbus
James Feist
james.feist at linux.intel.com
Fri Dec 20 06:12:39 AEDT 2019
On 12/19/19 1:12 AM, AKASH G J wrote:
> Hi all,
> I am using OpenBMC firmware for server board having Aspeed AST-2500.
>
> Followed
> https://github.com/openbmc/entity-manager/blob/master/docs/my_first_sensors.md
> for populating sensor value to dbus. Entity manager configuration file
> is given below.
> {
> "Exposes": [
> {
> "Address": "0x4f",
> "Bus": 5,
> "Name": "cpu0_vrd_temp",
> "Thresholds": [
> {
> "Direction": "greater than",
> "Name": "upper critical",
> "Severity": 1,
> "Value": 80
> }
> ],
> "Type": "TMP75"
> }
> ],
> "Name": "Rudra Baseboard",
> "Probe": "xyz.openbmc_project.FruDevice({'PRODUCT_PRODUCT_NAME':
> 'RUDRA'})",
> "Type": "Board",
> "xyz.openbmc_project.Inventory.Decorator.Asset": {
> "Manufacturer": "$BOARD_MANUFACTURER",
> "Model": "$BOARD_PRODUCT_NAME",
> "PartNumber": "$BOARD_PART_NUMBER",
> "SerialNumber": "$BOARD_SERIAL_NUMBER"
> }
> }
>
> Wrote sample FRU information on eeprom with the following content. Used
> dd command for writing to eeprom.
>
> root at s2600wf:/sys/bus/i2c/devices/3-0056# cat eeprom
> Product:
> MANUFACTURER "ABC"
> PART_NUMBER "12345"
> PRODUCT_NAME "SAMPLENAME"
> SERIAL_NUMBER "12312490840"
This is not a legal IMPI FRU. FRU Device only allows legal fru based on
the spec:
https://www.intel.com/content/www/us/en/servers/ipmi/ipmi-platform-mgt-fru-infostorage-def-v1-0-rev-1-3-spec-update.html
For testing purposes using "Probe" : "TRUE" can be used as well.
>
> The dbus tree not showing /xyz/openbmc_project/FruDevice/SAMPLENAME
>
> root at s2600wf:~# busctl tree --no-pager xyz.openbmc_project.FruDevice
> `-/xyz
> `-/xyz/openbmc_project
> `-/xyz/openbmc_project/FruDevice
>
> In journalctl log the following messages are printed.
>
> systemd[1]: Started Hwmon Temp Sensor.
> hwmontempsensor[120]: Error communicating to entity manager
> hwmontempsensor[120]: error communicating to entity manager
>
> Look like FruDevice daemon is not parsing the contents of eeprom and
> publish them to dbus.
>
> Is there any thing missing in configuration? Please help to resolve the
> problem.
>
>
>
> Thanks,
>
> Akash
>
More information about the openbmc
mailing list