<div dir="ltr">Well the temp1_input not showing in sysfs is related to linux kernel, not with userspace. Please double check your device tree node matches physical bus, and the corresponding kernel configs are enabled. Attach dmesg and bootlog would be helpful for people to help debug.</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 6, 2018 at 1:53 AM AKASH G J <<a href="mailto:akashgj91@gmail.com">akashgj91@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>I corrected the path of the environment file to be meta-zaius/recipes-phosphor/sensors/phosphor-hwmon%/obmc/hwon/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.conf.</div><div><br></div><div>Still temp1_input is not coming on the sysfs (/sys/class/hwmon/hwmon0)<br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 6, 2018 at 12:01 PM Kun Yi <<a href="mailto:kunyi@google.com" target="_blank">kunyi@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_quote"><div dir="ltr">On Mon, Nov 5, 2018 at 10:17 PM Troy Lee <<a href="mailto:leetroy@gmail.com" target="_blank">leetroy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The *service* here doesn't relate to systemd service.<br>
<br>
It is the name on D-Bus.<br>
<a href="https://github.com/openbmc/phosphor-hwmon#d-bus-bus-names" rel="noreferrer" target="_blank">https://github.com/openbmc/phosphor-hwmon#d-bus-bus-names</a><br>
<br>
Try this command to list all the services related to hwmon:<br>
# busctl --no-page list | grep -E "Hwmon1|PID"<br>
<br>
First column will be the service name.<br>
<br>
Yu-Ting Lee (Troy Lee) <<a href="mailto:LeeTroy@gmail.com" target="_blank">LeeTroy@gmail.com</a>><br>
AKASH G J <<a href="mailto:akashgj91@gmail.com" target="_blank">akashgj91@gmail.com</a>> 於 2018年11月5日 週一 下午4:40寫道：<br>
><br>
> No such service is available in root file system. The output of the command ls / -R | grep Hwmon is<br>
><br>
> root@zaius:~# ls / -R | grep Hwmon<br>
> xyz.openbmc_project.Hwmon@.service<br>
> system-xyz.openbmc_project.Hwmon.slice<br>
> /sys/fs/cgroup/systemd/system.slice/system-xyz.openbmc_project.Hwmon.slice:<br>
> system-xyz.openbmc_project.Hwmon.slice<br>
> /sys/fs/cgroup/unified/system.slice/system-xyz.openbmc_project.Hwmon.slice:<br>
> root@zaius:~#<br>
><br>
> On Mon, Nov 5, 2018 at 1:20 PM Troy Lee <<a href="mailto:leetroy@gmail.com" target="_blank">leetroy@gmail.com</a>> wrote:<br>
>><br>
>> Your service path doesn't look right.<br>
>><br>
>> According to:<br>
>> <a href="https://github.com/openbmc/docs/blob/master/sensor-architecture.md#d-bus" rel="noreferrer" target="_blank">https://github.com/openbmc/docs/blob/master/sensor-architecture.md#d-bus</a><br>
>><br>
>> It should be something like this:<br>
>> xyz.openbmc_project.Hwmon-<hash>.Hwmon1<br>
>><br>
>><br>
>><br>
>> Yu-Ting Lee (Troy Lee) <<a href="mailto:LeeTroy@gmail.com" target="_blank">LeeTroy@gmail.com</a>><br>
>> AKASH G J <<a href="mailto:akashgj91@gmail.com" target="_blank">akashgj91@gmail.com</a>> 於 2018年11月5日 週一 下午2:55寫道：<br>
>> ><br>
>> > I tried the command busctl --system introspect xyz.openbmc_project.Hwmon@.service /xyz/openbmc_project/Sensors/temperature/ambient xyz.openbmc_project.sensor.Threshold.Warning | grep property and it outputs<br>
>> ><br>
>> > Failed to introspect object /xyz/openbmc_project/Sensors/temperature/ambient of service xyz.openbmc_project.Hwmon@.service: Invalid argument.<br>
>> ><br>
>> > I added the file meta-zaius/recipes-phosphor/sensors/phosphor-hwmon%/obmc/hwmon/ahb/apb/i2c@1e6e2000/i2c-bus@90/tmp75@48.conf in machine configuration directory with the following contents for dbus mapping.<br>
>> ><br>
>> > LABEL_temp1 = ambient<br>
>> > WARNLO_temp1=-40<br>
>> > WARNHI_temp1=125<br>
>> ><br>
>> > Whether this is correct or not?<br>
>> ><br>
>> > On Fri, Nov 2, 2018 at 8:57 PM Emily Shaffer <<a href="mailto:emilyshaffer@google.com" target="_blank">emilyshaffer@google.com</a>> wrote:<br>
>> >><br>
>> >> 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. <a href="https://github.com/openbmc/docs/blob/master/sensor-architecture.md" rel="noreferrer" target="_blank">https://github.com/openbmc/docs/blob/master/sensor-architecture.md</a><br>
>> >><br>
>> >> On Fri, Nov 2, 2018, 3:21 AM AKASH G J <<a href="mailto:akashgj91@gmail.com" target="_blank">akashgj91@gmail.com</a>> wrote:<br>
>> >>><br>
>> >>> I added the sensor configuration to phosphor-host-ipmid's sensor configuration like.<br>
>> >>><br>
>> >>> 0x12: &temperature<br>
>> >>> sensorType: 0x01<br>
>> >>> path: /xyz/openbmc_project/sensors/temperature/ambient<br>
>> >>> sensorReadingType: 0x01<br>
>> >>> multiplierM: 235<br>
>> >>> offsetB: 0<br>
>> >>> bExp: 0<br>
>> >>> unit: xyz.openbmc_project.Sensor.Value.Unit.DegreesC<br>
>> >>> scale: -3<br>
>> >>> rExp: -3<br>
>> >>> serviceInterface: org.freedesktop.DBus.Properties<br>
>> >>> readingType: readingData<br>
>> >>> interfaces:<br>
>> >>> xyz.openbmc_project.Sensor.Value:<br>
>> >>> Value:<br>
>> >>> Offsets:<br>
>> >>> 0xFF:<br>
>> >>> type: int64_t<br>
>> >>><br>
>> >>><br>
>> >>> When I run the command ipmitool -I dbus sdr elist full, it gives the following.<br>
>> >>><br>
>> >>> ambient | 12h | ns | 0.0 | Disabled<br>
>> >>><br>
>> >>> It is not giving the sensor reading and it is showing the sensor device is disabled.<br>
>> >>><br>
>> >>> On Thu, Nov 1, 2018 at 11:28 PM Patrick Venture <<a href="mailto:venture@google.com" target="_blank">venture@google.com</a>> wrote:<br>
>> >>>><br>
>> >>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <<a href="mailto:akashgj91@gmail.com" target="_blank">akashgj91@gmail.com</a>> wrote:<br>
>> >>>> ><br>
>> >>>> > Hi All,<br>
>> >>>> ><br>
>> >>>> > 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.<br>
>> >>>> ><br>
>> >>>> > I added the file meta-zaius/recipes-phosphor/sensors/phosphor-hwmon%/obmc/hwmon/ahb/apb/i2c@1e6e2000/i2c-bus@90/tmp75@48.conf in machine configuration directory with the following contents.<br>
>> >>>> ><br>
>> >>>> > LABEL_temp1 = ambient<br>
>> >>>> > WARNLO_temp1=-40<br>
>> >>>> > WARNHI_temp1=125<br>
>> >>>> ><br>
>> >>>> > I added the following patch to the kernel file linux/arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts.<br>
>> >>>> ><br>
>> >>>> > &i2c12 {<br>
>> >>>> > - status = "disabled";<br>
>> >>>> > + status = "okay";<br>
>> >>>> > +<br>
>> >>>> > + tmp75@48 {<br>
>> >>>> > + compatible = "ti,tmp75";<br>
>> >>>> > + reg = <0x48>;<br>
>> >>>> > + };<br>
>> >>>> > +<br>
>> >>>> > };<br>
>> >>>> ><br>
>> >>>> > After booting Linux, the changes are reflected in /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48. Also,<br>
>> >>>> > tmp78.conf is showing in /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@90.<br></blockquote><div><br></div><div>Besides what others suggested looks like you have a mismatch between your device path and the path for the environment file. They need to have the same path.<br></div><div><br></div><div>Steps to try:</div><div>1. Fix the path of your environment file to be meta-zaius/recipes-phosphor/sensors/phosphor-hwmon%/obmc/hwon/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.conf </div><div>2. Make sure the hwmon sysfs interface shows up and temp1_input reads a valid value</div><div>3. Play with busctl as others suggested and make sure the sensor value is reported over DBus</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
>> >>>> ><br>
>> >>>> > when I am running the ipmitool command: ipmitool -I dbus sdr elist full it is not showing the temperature sensor and its reading.<br>
>> >>>> ><br>
>> >>>> > Please someone help to resolve the problem.<br>
>> >>>><br>
>> >>>> You'll need to add the sensor configuration to the<br>
>> >>>> phosphor-host-ipmid's sensor configuration, see:<br>
>> >>>><br>
>> >>>> <a href="https://github.com/openbmc/openbmc/blob/master/meta-ingrasys/meta-zaius/recipes-phosphor/ipmi/phosphor-ipmi-sensor-inventory%25/config.yaml" rel="noreferrer" target="_blank">https://github.com/openbmc/openbmc/blob/master/meta-ingrasys/meta-zaius/recipes-phosphor/ipmi/phosphor-ipmi-sensor-inventory%25/config.yaml</a><br>
>> >>>><br>
>> >>>> ><br>
>> >>>> ><br>
>> >>>> > Thanks and Regards,<br>
>> >>>> ><br>
>> >>>> > Akash<br>
>> >>>> ><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-7536202244457219981m_-4733956080620071153m_5375469761459664922gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Regards,<div>Kun</div></div></div></div>
</blockquote></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Regards,<div>Kun</div></div></div>