Temperature Sensor Reading not showing up.

AKASH G J akashgj91 at gmail.com
Tue Nov 6 17:39:55 AEDT 2018


#* busctl --no-page list | grep -E "Hwmon1|PID" *outputs


*NAME                            PID                       PROCESS
    USER    *

Also command *# busctl --no-page list | grep "Hwmon|PID" *shows same output.

On Tue, Nov 6, 2018 at 11:46 AM Troy Lee <leetroy at gmail.com> wrote:

> The *service* here doesn't relate to systemd service.
>
> It is the name on D-Bus.
> https://github.com/openbmc/phosphor-hwmon#d-bus-bus-names
>
> Try this command to list all the services related to hwmon:
> # busctl --no-page list | grep -E "Hwmon1|PID"
>
> First column will be the service name.
>
> Yu-Ting Lee (Troy Lee) <LeeTroy at gmail.com>
> AKASH G J <akashgj91 at gmail.com> 於 2018年11月5日 週一 下午4:40寫道:
> >
> > No such service is available in root file system. The output of the
> command ls / -R | grep Hwmon  is
> >
> > root at zaius:~# ls / -R | grep Hwmon
> > xyz.openbmc_project.Hwmon at .service
> > system-xyz.openbmc_project.Hwmon.slice
> >
> /sys/fs/cgroup/systemd/system.slice/system-xyz.openbmc_project.Hwmon.slice:
> > system-xyz.openbmc_project.Hwmon.slice
> >
> /sys/fs/cgroup/unified/system.slice/system-xyz.openbmc_project.Hwmon.slice:
> > root at zaius:~#
> >
> > On Mon, Nov 5, 2018 at 1:20 PM Troy Lee <leetroy at gmail.com> wrote:
> >>
> >> Your service path doesn't look right.
> >>
> >> According to:
> >>
> https://github.com/openbmc/docs/blob/master/sensor-architecture.md#d-bus
> >>
> >> It should be something like this:
> >>   xyz.openbmc_project.Hwmon-<hash>.Hwmon1
> >>
> >>
> >>
> >> Yu-Ting Lee (Troy Lee) <LeeTroy at gmail.com>
> >> AKASH G J <akashgj91 at gmail.com> 於 2018年11月5日 週一 下午2:55寫道:
> >> >
> >> > I tried the command busctl --system introspect
> xyz.openbmc_project.Hwmon at .service
> /xyz/openbmc_project/Sensors/temperature/ambient
> xyz.openbmc_project.sensor.Threshold.Warning | grep property and it outputs
> >> >
> >> > Failed to introspect object
> /xyz/openbmc_project/Sensors/temperature/ambient of service
> xyz.openbmc_project.Hwmon at .service: Invalid argument.
> >> >
> >> > I added the file
> meta-zaius/recipes-phosphor/sensors/phosphor-hwmon%/obmc/hwmon/ahb/apb/i2c at 1e6e2000
> /i2c-bus at 90/tmp75 at 48.conf in machine configuration directory with the
> following contents for dbus mapping.
> >> >
> >> > LABEL_temp1 = ambient
> >> > WARNLO_temp1=-40
> >> > WARNHI_temp1=125
> >> >
> >> > Whether this is correct or not?
> >> >
> >> > On Fri, Nov 2, 2018 at 8:57 PM Emily Shaffer <emilyshaffer at google.com>
> wrote:
> >> >>
> >> >> Have you tried a dbus introspect to see if the sensor is coming
> across dbus correctly? There is a sample introspect command on the sensor
> howto, check out the busctl usage.
> https://github.com/openbmc/docs/blob/master/sensor-architecture.md
> >> >>
> >> >> On Fri, Nov 2, 2018, 3:21 AM AKASH G J <akashgj91 at gmail.com> wrote:
> >> >>>
> >> >>> I added the sensor configuration to phosphor-host-ipmid's sensor
> configuration like.
> >> >>>
> >> >>> 0x12: &temperature
> >> >>>   sensorType: 0x01
> >> >>>   path: /xyz/openbmc_project/sensors/temperature/ambient
> >> >>>   sensorReadingType: 0x01
> >> >>>   multiplierM: 235
> >> >>>   offsetB: 0
> >> >>>   bExp: 0
> >> >>>   unit: xyz.openbmc_project.Sensor.Value.Unit.DegreesC
> >> >>>   scale: -3
> >> >>>   rExp: -3
> >> >>>   serviceInterface: org.freedesktop.DBus.Properties
> >> >>>   readingType: readingData
> >> >>>   interfaces:
> >> >>>     xyz.openbmc_project.Sensor.Value:
> >> >>>       Value:
> >> >>>         Offsets:
> >> >>>           0xFF:
> >> >>>             type: int64_t
> >> >>>
> >> >>>
> >> >>> When I run the command ipmitool -I dbus sdr elist full, it gives
> the following.
> >> >>>
> >> >>> ambient          | 12h | ns  |  0.0 | Disabled
> >> >>>
> >> >>> It is not giving the sensor reading and it is showing the sensor
> device is disabled.
> >> >>>
> >> >>> On Thu, Nov 1, 2018 at 11:28 PM Patrick Venture <venture at google.com>
> wrote:
> >> >>>>
> >> >>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91 at gmail.com>
> wrote:
> >> >>>> >
> >> >>>> > Hi All,
> >> >>>> >
> >> >>>> > I built OpenBMC Linux using Zaius configuration and booted on
> BMC Aspeed AST-2500. The board we are using have one temperature sensor
> (Texas Instruments TMP75) on I2C-12 interface.
> >> >>>> >
> >> >>>> > I added the file
> meta-zaius/recipes-phosphor/sensors/phosphor-hwmon%/obmc/hwmon/ahb/apb/i2c at 1e6e2000
> /i2c-bus at 90/tmp75 at 48.conf in machine configuration directory with the
> following contents.
> >> >>>> >
> >> >>>> > LABEL_temp1 = ambient
> >> >>>> > WARNLO_temp1=-40
> >> >>>> > WARNHI_temp1=125
> >> >>>> >
> >> >>>> > I added the following patch to the kernel file
> linux/arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts.
> >> >>>> >
> >> >>>> >  &i2c12 {
> >> >>>> > -    status = "disabled";
> >> >>>> > +    status = "okay";
> >> >>>> > +
> >> >>>> > +    tmp75 at 48 {
> >> >>>> > +        compatible = "ti,tmp75";
> >> >>>> > +        reg = <0x48>;
> >> >>>> > +    };
> >> >>>> > +
> >> >>>> >  };
> >> >>>> >
> >> >>>> > After booting Linux, the changes are reflected in
> /sys/firmware/devicetree/base/ahb/apb/i2c at 1e78a000/i2c-bus at 440/tmp75 at 48.
> Also,
> >> >>>> > tmp78.conf is showing in
> /etc/default/obmc/hwmon/ahb/apb/i2c at 1e78a000/i2c-bus at 90.
> >> >>>> >
> >> >>>> > when I am running the ipmitool command: ipmitool -I dbus sdr
> elist full it is not showing the temperature sensor and its reading.
> >> >>>> >
> >> >>>> > Please someone help to resolve the problem.
> >> >>>>
> >> >>>> You'll need to add the sensor configuration to the
> >> >>>> phosphor-host-ipmid's sensor configuration, see:
> >> >>>>
> >> >>>>
> https://github.com/openbmc/openbmc/blob/master/meta-ingrasys/meta-zaius/recipes-phosphor/ipmi/phosphor-ipmi-sensor-inventory%25/config.yaml
> >> >>>>
> >> >>>> >
> >> >>>> >
> >> >>>> > Thanks and Regards,
> >> >>>> >
> >> >>>> > Akash
> >> >>>> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20181106/084a9755/attachment.html>


More information about the openbmc mailing list