* Temperature Sensor Reading not showing up.
@ 2018-10-31 5:13 AKASH G J
2018-11-01 17:57 ` Patrick Venture
0 siblings, 1 reply; 13+ messages in thread
From: AKASH G J @ 2018-10-31 5:13 UTC (permalink / raw)
To: openbmc
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
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@1e6e2000/i2c-bus@90/tmp75@48.conf*
in machine configuration directory with the following contents.
*LABEL_temp1 = ambientWARNLO_temp1=-40WARNHI_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@48
{+ compatible = "ti,tmp75";+ reg = <0x48>;+ };+ };*
After booting Linux, the changes are reflected in
*/sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48*.
Also,
*tmp78.conf* is showing in
*/etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@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.
Thanks and Regards,
Akash
[-- Attachment #2: Type: text/html, Size: 1384 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-10-31 5:13 Temperature Sensor Reading not showing up AKASH G J
@ 2018-11-01 17:57 ` Patrick Venture
2018-11-02 10:19 ` AKASH G J
0 siblings, 1 reply; 13+ messages in thread
From: Patrick Venture @ 2018-11-01 17:57 UTC (permalink / raw)
To: AKASH G J; +Cc: OpenBMC Maillist
On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000/i2c-bus@90/tmp75@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@48 {
> + compatible = "ti,tmp75";
> + reg = <0x48>;
> + };
> +
> };
>
> After booting Linux, the changes are reflected in /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48. Also,
> tmp78.conf is showing in /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@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
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-01 17:57 ` Patrick Venture
@ 2018-11-02 10:19 ` AKASH G J
2018-11-02 15:27 ` Emily Shaffer
0 siblings, 1 reply; 13+ messages in thread
From: AKASH G J @ 2018-11-02 10:19 UTC (permalink / raw)
To: venture; +Cc: openbmc
[-- Attachment #1: Type: text/plain, Size: 2409 bytes --]
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@google.com> wrote:
> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000
> /i2c-bus@90/tmp75@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@48 {
> > + compatible = "ti,tmp75";
> > + reg = <0x48>;
> > + };
> > +
> > };
> >
> > After booting Linux, the changes are reflected in
> /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.
> Also,
> > tmp78.conf is showing in /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000
> /i2c-bus@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
> >
>
[-- Attachment #2: Type: text/html, Size: 3534 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-02 10:19 ` AKASH G J
@ 2018-11-02 15:27 ` Emily Shaffer
2018-11-05 6:54 ` AKASH G J
0 siblings, 1 reply; 13+ messages in thread
From: Emily Shaffer @ 2018-11-02 15:27 UTC (permalink / raw)
To: AKASH G J; +Cc: openbmc, venture
[-- Attachment #1: Type: text/plain, Size: 2832 bytes --]
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@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@google.com>
> wrote:
>
>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000
>> /i2c-bus@90/tmp75@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@48 {
>> > + compatible = "ti,tmp75";
>> > + reg = <0x48>;
>> > + };
>> > +
>> > };
>> >
>> > After booting Linux, the changes are reflected in
>> /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.
>> Also,
>> > tmp78.conf is showing in /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000
>> /i2c-bus@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
>> >
>>
>
[-- Attachment #2: Type: text/html, Size: 4166 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-02 15:27 ` Emily Shaffer
@ 2018-11-05 6:54 ` AKASH G J
2018-11-05 7:50 ` Troy Lee
0 siblings, 1 reply; 13+ messages in thread
From: AKASH G J @ 2018-11-05 6:54 UTC (permalink / raw)
To: Emily Shaffer; +Cc: openbmc, Patrick Venture
[-- Attachment #1: Type: text/plain, Size: 3679 bytes --]
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
*Failed to introspect object
/xyz/openbmc_project/Sensors/temperature/ambient of service
xyz.openbmc_project.Hwmon@.service: Invalid argument.*
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.
*LABEL_temp1 = ambientWARNLO_temp1=-40WARNHI_temp1=125*
*Whether this is correct or not?*
On Fri, Nov 2, 2018 at 8:57 PM Emily Shaffer <emilyshaffer@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@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@google.com>
>> wrote:
>>
>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000
>>> /i2c-bus@90/tmp75@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@48 {
>>> > + compatible = "ti,tmp75";
>>> > + reg = <0x48>;
>>> > + };
>>> > +
>>> > };
>>> >
>>> > After booting Linux, the changes are reflected in
>>> /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.
>>> Also,
>>> > tmp78.conf is showing in /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000
>>> /i2c-bus@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
>>> >
>>>
>>
[-- Attachment #2: Type: text/html, Size: 5386 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-05 6:54 ` AKASH G J
@ 2018-11-05 7:50 ` Troy Lee
2018-11-05 8:40 ` AKASH G J
0 siblings, 1 reply; 13+ messages in thread
From: Troy Lee @ 2018-11-05 7:50 UTC (permalink / raw)
To: akashgj91; +Cc: emilyshaffer, venture, openbmc
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@gmail.com>
AKASH G J <akashgj91@gmail.com> 於 2018年11月5日 週一 下午2:55寫道：
>
> 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
>
> Failed to introspect object /xyz/openbmc_project/Sensors/temperature/ambient of service xyz.openbmc_project.Hwmon@.service: Invalid argument.
>
> 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.
>
> 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@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@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@google.com> wrote:
>>>>
>>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000/i2c-bus@90/tmp75@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@48 {
>>>> > + compatible = "ti,tmp75";
>>>> > + reg = <0x48>;
>>>> > + };
>>>> > +
>>>> > };
>>>> >
>>>> > After booting Linux, the changes are reflected in /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48. Also,
>>>> > tmp78.conf is showing in /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@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
>>>> >
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-05 7:50 ` Troy Lee
@ 2018-11-05 8:40 ` AKASH G J
2018-11-06 6:16 ` Troy Lee
0 siblings, 1 reply; 13+ messages in thread
From: AKASH G J @ 2018-11-05 8:40 UTC (permalink / raw)
To: leetroy; +Cc: Emily Shaffer, Patrick Venture, openbmc
[-- Attachment #1: Type: text/plain, Size: 4938 bytes --]
No such service is available in root file system. The output of the command *ls
/ -R | grep Hwmon *is
*root@zaius:~# ls / -R | grep
Hwmon
xyz.openbmc_project.Hwmon@.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@zaius:~#*
On Mon, Nov 5, 2018 at 1:20 PM Troy Lee <leetroy@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@gmail.com>
> AKASH G J <akashgj91@gmail.com> 於 2018年11月5日 週一 下午2:55寫道：
> >
> > 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
> >
> > Failed to introspect object
> /xyz/openbmc_project/Sensors/temperature/ambient of service
> xyz.openbmc_project.Hwmon@.service: Invalid argument.
> >
> > 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.
> >
> > 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@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@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@google.com>
> wrote:
> >>>>
> >>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000
> /i2c-bus@90/tmp75@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@48 {
> >>>> > + compatible = "ti,tmp75";
> >>>> > + reg = <0x48>;
> >>>> > + };
> >>>> > +
> >>>> > };
> >>>> >
> >>>> > After booting Linux, the changes are reflected in
> /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.
> Also,
> >>>> > tmp78.conf is showing in
> /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@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
> >>>> >
>
[-- Attachment #2: Type: text/html, Size: 7664 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-05 8:40 ` AKASH G J
@ 2018-11-06 6:16 ` Troy Lee
2018-11-06 6:30 ` Kun Yi
2018-11-06 6:39 ` AKASH G J
0 siblings, 2 replies; 13+ messages in thread
From: Troy Lee @ 2018-11-06 6:16 UTC (permalink / raw)
To: AKASH G J; +Cc: Emily Shaffer, Patrick Venture, openbmc
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@gmail.com>
AKASH G J <akashgj91@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@zaius:~# ls / -R | grep Hwmon
> xyz.openbmc_project.Hwmon@.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@zaius:~#
>
> On Mon, Nov 5, 2018 at 1:20 PM Troy Lee <leetroy@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@gmail.com>
>> AKASH G J <akashgj91@gmail.com> 於 2018年11月5日 週一 下午2:55寫道：
>> >
>> > 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
>> >
>> > Failed to introspect object /xyz/openbmc_project/Sensors/temperature/ambient of service xyz.openbmc_project.Hwmon@.service: Invalid argument.
>> >
>> > 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.
>> >
>> > 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@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@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@google.com> wrote:
>> >>>>
>> >>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000/i2c-bus@90/tmp75@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@48 {
>> >>>> > + compatible = "ti,tmp75";
>> >>>> > + reg = <0x48>;
>> >>>> > + };
>> >>>> > +
>> >>>> > };
>> >>>> >
>> >>>> > After booting Linux, the changes are reflected in /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48. Also,
>> >>>> > tmp78.conf is showing in /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@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
>> >>>> >
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-06 6:16 ` Troy Lee
@ 2018-11-06 6:30 ` Kun Yi
2018-11-06 9:53 ` AKASH G J
2018-11-06 6:39 ` AKASH G J
1 sibling, 1 reply; 13+ messages in thread
From: Kun Yi @ 2018-11-06 6:30 UTC (permalink / raw)
To: leetroy; +Cc: akashgj91, Emily Shaffer, Patrick Venture, OpenBMC Maillist
[-- Attachment #1: Type: text/plain, Size: 6363 bytes --]
On Mon, Nov 5, 2018 at 10:17 PM Troy Lee <leetroy@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@gmail.com>
> AKASH G J <akashgj91@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@zaius:~# ls / -R | grep Hwmon
> > xyz.openbmc_project.Hwmon@.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@zaius:~#
> >
> > On Mon, Nov 5, 2018 at 1:20 PM Troy Lee <leetroy@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@gmail.com>
> >> AKASH G J <akashgj91@gmail.com> 於 2018年11月5日 週一 下午2:55寫道：
> >> >
> >> > 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
> >> >
> >> > Failed to introspect object
> /xyz/openbmc_project/Sensors/temperature/ambient of service
> xyz.openbmc_project.Hwmon@.service: Invalid argument.
> >> >
> >> > 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.
> >> >
> >> > 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@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@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@google.com>
> wrote:
> >> >>>>
> >> >>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000
> /i2c-bus@90/tmp75@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@48 {
> >> >>>> > + compatible = "ti,tmp75";
> >> >>>> > + reg = <0x48>;
> >> >>>> > + };
> >> >>>> > +
> >> >>>> > };
> >> >>>> >
> >> >>>> > After booting Linux, the changes are reflected in
> /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.
> Also,
> >> >>>> > tmp78.conf is showing in
> /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@90.
>
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.
Steps to try:
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
2. Make sure the hwmon sysfs interface shows up and temp1_input reads a
valid value
3. Play with busctl as others suggested and make sure the sensor value is
reported over DBus
> >> >>>> >
> >> >>>> > 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
> >> >>>> >
>
--
Regards,
Kun
[-- Attachment #2: Type: text/html, Size: 9974 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-06 6:16 ` Troy Lee
2018-11-06 6:30 ` Kun Yi
@ 2018-11-06 6:39 ` AKASH G J
1 sibling, 0 replies; 13+ messages in thread
From: AKASH G J @ 2018-11-06 6:39 UTC (permalink / raw)
To: Troy Lee; +Cc: Emily Shaffer, Patrick Venture, openbmc
[-- Attachment #1: Type: text/plain, Size: 6038 bytes --]
#* 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@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@gmail.com>
> AKASH G J <akashgj91@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@zaius:~# ls / -R | grep Hwmon
> > xyz.openbmc_project.Hwmon@.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@zaius:~#
> >
> > On Mon, Nov 5, 2018 at 1:20 PM Troy Lee <leetroy@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@gmail.com>
> >> AKASH G J <akashgj91@gmail.com> 於 2018年11月5日 週一 下午2:55寫道：
> >> >
> >> > 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
> >> >
> >> > Failed to introspect object
> /xyz/openbmc_project/Sensors/temperature/ambient of service
> xyz.openbmc_project.Hwmon@.service: Invalid argument.
> >> >
> >> > 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.
> >> >
> >> > 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@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@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@google.com>
> wrote:
> >> >>>>
> >> >>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000
> /i2c-bus@90/tmp75@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@48 {
> >> >>>> > + compatible = "ti,tmp75";
> >> >>>> > + reg = <0x48>;
> >> >>>> > + };
> >> >>>> > +
> >> >>>> > };
> >> >>>> >
> >> >>>> > After booting Linux, the changes are reflected in
> /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.
> Also,
> >> >>>> > tmp78.conf is showing in
> /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@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
> >> >>>> >
>
[-- Attachment #2: Type: text/html, Size: 9527 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-06 6:30 ` Kun Yi
@ 2018-11-06 9:53 ` AKASH G J
2018-11-06 19:22 ` Kun Yi
0 siblings, 1 reply; 13+ messages in thread
From: AKASH G J @ 2018-11-06 9:53 UTC (permalink / raw)
To: kunyi; +Cc: Troy Lee, Emily Shaffer, Patrick Venture, openbmc
[-- Attachment #1: Type: text/plain, Size: 6879 bytes --]
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.
Still temp1_input is not coming on the sysfs (/sys/class/hwmon/hwmon0)
On Tue, Nov 6, 2018 at 12:01 PM Kun Yi <kunyi@google.com> wrote:
>
> On Mon, Nov 5, 2018 at 10:17 PM Troy Lee <leetroy@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@gmail.com>
>> AKASH G J <akashgj91@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@zaius:~# ls / -R | grep Hwmon
>> > xyz.openbmc_project.Hwmon@.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@zaius:~#
>> >
>> > On Mon, Nov 5, 2018 at 1:20 PM Troy Lee <leetroy@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@gmail.com>
>> >> AKASH G J <akashgj91@gmail.com> 於 2018年11月5日 週一 下午2:55寫道：
>> >> >
>> >> > 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
>> >> >
>> >> > Failed to introspect object
>> /xyz/openbmc_project/Sensors/temperature/ambient of service
>> xyz.openbmc_project.Hwmon@.service: Invalid argument.
>> >> >
>> >> > 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.
>> >> >
>> >> > 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@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@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@google.com> wrote:
>> >> >>>>
>> >> >>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000
>> /i2c-bus@90/tmp75@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@48 {
>> >> >>>> > + compatible = "ti,tmp75";
>> >> >>>> > + reg = <0x48>;
>> >> >>>> > + };
>> >> >>>> > +
>> >> >>>> > };
>> >> >>>> >
>> >> >>>> > After booting Linux, the changes are reflected in
>> /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.
>> Also,
>> >> >>>> > tmp78.conf is showing in
>> /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@90.
>>
>
> 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.
>
> Steps to try:
> 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
> 2. Make sure the hwmon sysfs interface shows up and temp1_input reads a
> valid value
> 3. Play with busctl as others suggested and make sure the sensor value is
> reported over DBus
>
>
>> >> >>>> >
>> >> >>>> > 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
>> >> >>>> >
>>
>
>
> --
> Regards,
> Kun
>
[-- Attachment #2: Type: text/html, Size: 10647 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-06 9:53 ` AKASH G J
@ 2018-11-06 19:22 ` Kun Yi
2018-11-08 6:26 ` AKASH G J
0 siblings, 1 reply; 13+ messages in thread
From: Kun Yi @ 2018-11-06 19:22 UTC (permalink / raw)
To: akashgj91; +Cc: leetroy, Emily Shaffer, Patrick Venture, OpenBMC Maillist
[-- Attachment #1: Type: text/plain, Size: 7461 bytes --]
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.
On Tue, Nov 6, 2018 at 1:53 AM AKASH G J <akashgj91@gmail.com> wrote:
> 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.
>
> Still temp1_input is not coming on the sysfs (/sys/class/hwmon/hwmon0)
>
> On Tue, Nov 6, 2018 at 12:01 PM Kun Yi <kunyi@google.com> wrote:
>
>>
>> On Mon, Nov 5, 2018 at 10:17 PM Troy Lee <leetroy@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@gmail.com>
>>> AKASH G J <akashgj91@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@zaius:~# ls / -R | grep Hwmon
>>> > xyz.openbmc_project.Hwmon@.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@zaius:~#
>>> >
>>> > On Mon, Nov 5, 2018 at 1:20 PM Troy Lee <leetroy@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@gmail.com>
>>> >> AKASH G J <akashgj91@gmail.com> 於 2018年11月5日 週一 下午2:55寫道：
>>> >> >
>>> >> > 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
>>> >> >
>>> >> > Failed to introspect object
>>> /xyz/openbmc_project/Sensors/temperature/ambient of service
>>> xyz.openbmc_project.Hwmon@.service: Invalid argument.
>>> >> >
>>> >> > 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.
>>> >> >
>>> >> > 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@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@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@google.com> wrote:
>>> >> >>>>
>>> >> >>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000
>>> /i2c-bus@90/tmp75@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@48 {
>>> >> >>>> > + compatible = "ti,tmp75";
>>> >> >>>> > + reg = <0x48>;
>>> >> >>>> > + };
>>> >> >>>> > +
>>> >> >>>> > };
>>> >> >>>> >
>>> >> >>>> > After booting Linux, the changes are reflected in
>>> /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440/tmp75@48.
>>> Also,
>>> >> >>>> > tmp78.conf is showing in
>>> /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@90.
>>>
>>
>> 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.
>>
>> Steps to try:
>> 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
>> 2. Make sure the hwmon sysfs interface shows up and temp1_input reads a
>> valid value
>> 3. Play with busctl as others suggested and make sure the sensor value is
>> reported over DBus
>>
>>
>>> >> >>>> >
>>> >> >>>> > 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
>>> >> >>>> >
>>>
>>
>>
>> --
>> Regards,
>> Kun
>>
>
--
Regards,
Kun
[-- Attachment #2: Type: text/html, Size: 11416 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Temperature Sensor Reading not showing up.
2018-11-06 19:22 ` Kun Yi
@ 2018-11-08 6:26 ` AKASH G J
0 siblings, 0 replies; 13+ messages in thread
From: AKASH G J @ 2018-11-08 6:26 UTC (permalink / raw)
To: Kun Yi; +Cc: Troy Lee, Emily Shaffer, Patrick Venture, openbmc
[-- Attachment #1: Type: text/plain, Size: 23088 bytes --]
Actually the I2C address mentioned in board schematics is 0x90. When I gave
that in device tree file, it is showing the following error message.
i2c i2c-12: Invalid 7 bit I2C address 0x90
i2c i2c-12: of_i2c: Failure registering /ahb/apb/i2c1e78a000/i2c-bus@440
/tmp75@90
i2c i2c-12: of_i2c: Failed to create I2C device for
/ahb/apb/i2c1e78a000/i2c-bus@440/tmp75@90
So I took first 7 MSB bits 0f 0x90, that is 0x48 and I used that in device
tree file.
Following is the content of dmesg.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version
4.18.7-b7ba2a0af62b835fb3cac7bd3bbc72dcb1955b65 (oe-user@oe-host) (gcc
version 7.3.0 (GCC)) #1 Thu Nov 8 06:06:20 UTC 2018
[ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7
(ARMv7), cr=00c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing
instruction cache
[ 0.000000] OF: fdt: Machine model: Zaius BMC
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] cma: Reserved 16 MiB at 0x9cc00000
[ 0.000000] On node 0 totalpages: 110592
[ 0.000000] Normal zone: 992 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 110592 pages, LIFO batch:31
[ 0.000000] random: get_random_bytes called from start_kernel+0x8c/0x4b4
with crng_init=0
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 109600
[ 0.000000] Kernel command line: console=ttyS4,115200n8 root=/dev/ram rw
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144
bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072
bytes)
[ 0.000000] Memory: 396452K/442368K available (6144K kernel code, 373K
rwdata, 1208K rodata, 1024K init, 143K bss, 29532K reserved, 16384K
cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0x9f800000 - 0xff800000 (1536 MB)
[ 0.000000] lowmem : 0x80000000 - 0x9f000000 ( 496 MB)
[ 0.000000] .text : 0x(ptrval) - 0x(ptrval) (7136 kB)
[ 0.000000] .init : 0x(ptrval) - 0x(ptrval) (1024 kB)
[ 0.000000] .data : 0x(ptrval) - 0x(ptrval) ( 374 kB)
[ 0.000000] .bss : 0x(ptrval) - 0x(ptrval) ( 144 kB)
[ 0.000000] ftrace: allocating 19300 entries in 57 pages
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] i2c controller registered, irq 16
[ 0.000000] clocksource: FTTMR010-TIMER2: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 77222644334 ns
[ 0.000017] sched_clock: 32 bits at 24MHz, resolution 40ns, wraps every
86767015915ns
[ 0.000085] Switching to timer-based delay loop, resolution 40ns
[ 0.001073] Calibrating delay loop (skipped), value calculated using
timer frequency.. 49.50 BogoMIPS (lpj=247500)
[ 0.001125] pid_max: default: 32768 minimum: 301
[ 0.001802] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001843] Mountpoint-cache hash table entries: 1024 (order: 0, 4096
bytes)
[ 0.003239] CPU: Testing write buffer coherency: ok
[ 0.004862] Setting up static identity map for 0x80100000 - 0x80100038
[ 0.009381] devtmpfs: initialized
[ 0.024442] clocksource: jiffies: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.024495] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.027637] pinctrl core: initialized pinctrl subsystem
[ 0.028592] NET: Registered protocol family 16
[ 0.031007] DMA: preallocated 256 KiB pool for atomic coherent
allocations
[ 0.033079] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[ 0.033111] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.130549] usbcore: registered new interface driver usbfs
[ 0.130740] usbcore: registered new interface driver hub
[ 0.130947] usbcore: registered new device driver usb
[ 0.141551] clocksource: Switched to clocksource FTTMR010-TIMER2
[ 0.184913] NET: Registered protocol family 2
[ 0.186058] tcp_listen_portaddr_hash hash table entries: 512 (order: 0,
4096 bytes)
[ 0.186138] TCP established hash table entries: 4096 (order: 2, 16384
bytes)
[ 0.186226] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.186320] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.186539] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.186597] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.186965] NET: Registered protocol family 1
[ 0.189270] Unpacking initramfs...
[ 19.439065] Freeing initrd memory: 15708K
[ 19.446805] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[ 19.447297] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 19.447335] jffs2: version 2.2. (SUMMARY) �© 2001-2006 Red Hat, Inc.
[ 19.452647] NET: Registered protocol family 38
[ 19.452725] io scheduler noop registered
[ 19.452899] io scheduler cfq registered (default)
[ 19.453388] aspeed-g5-pinctrl 1e6e2000.syscon:pinctrl: could not map pin
config for "C7"
[ 19.453512] aspeed-g5-pinctrl 1e6e2000.syscon:pinctrl: could not map pin
config for "B7"
[ 19.453850] aspeed-g5-pinctrl 1e6e2000.syscon:pinctrl: pin_config_set op
failed for pin 233
[ 19.453872] gpio_aspeed 1e780000.gpio: Error applying setting, reverse
things back
[ 19.454219] GPIO line 396 (iso_u164_en) hogged as output/high
[ 19.454304] GPIO line 400 (ncsi_mux_en_n) hogged as output/low
[ 19.454372] GPIO line 401 (bmc_i2c2_sw_rst_n) hogged as output/high
[ 19.454435] GPIO line 403 (bmc_i2c5_sw_rst_n) hogged as output/high
[ 19.455906] ipmi-bt-host 1e789140.ibt: Found bt bmc device
[ 19.456944] ipmi-bt-host 1e789140.ibt: Using IRQ 32
[ 19.467271] Serial: 8250/16550 driver, 6 ports, IRQ sharing enabled
[ 19.474908] 1e787000.serial: ttyS5 at MMIO 0x1e787000 (irq = 32,
base_baud = 1546875) is a 16550A
[ 19.479132] 1e783000.serial: ttyS0 at MMIO 0x1e783000 (irq = 30,
base_baud = 1500000) is a 16550A
[ 19.481258] 1e784000.serial: ttyS4 at MMIO 0x1e784000 (irq = 31,
base_baud = 1500000) is a 16550A
[ 19.963806] console [ttyS4] enabled
[ 20.110086] timeriomem_rng 1e6e2078.hwrng: 32bits from 0x(ptrval) @ 1us
[ 20.119184] aspeed_gfx 1e6e6000.display: failed to initialize reserved
mem: -19
[ 20.136001] random: fast init done
[ 20.150290] loop: module loaded
[ 20.155637] aspeed-lpc-ctrl 1e789080.lpc-ctrl: Loaded at [mem
0x98000000-0x9bffffff flags 0x200]
[ 20.171871] aspeed-smc 1e620000.flash-controller: Using 50 MHz SPI
frequency
[ 20.179140] aspeed-smc 1e620000.flash-controller: mx25l25635e (32768
Kbytes)
[ 20.186217] aspeed-smc 1e620000.flash-controller: CE0 window [
0x20000000 - 0x22000000 ] 32MB
[ 20.194856] aspeed-smc 1e620000.flash-controller: CE1 window [
0x22000000 - 0x2a000000 ] 128MB
[ 20.203483] aspeed-smc 1e620000.flash-controller: read control register:
203b0641
[ 20.689020] 5 fixed-partitions partitions found on MTD device bmc
[ 20.695136] Creating 5 MTD partitions on "bmc":
[ 20.699685] 0x000000000000-0x000000060000 : "u-boot"
[ 20.708545] 0x000000060000-0x000000080000 : "u-boot-env"
[ 20.717721] 0x000000080000-0x0000004c0000 : "kernel"
[ 20.727542] 0x0000004c0000-0x000001c00000 : "rofs"
[ 20.737317] 0x000001c00000-0x000002000000 : "rwfs"
[ 20.749007] aspeed-smc 1e630000.flash-controller: Using 100 MHz SPI
frequency
[ 20.756392] aspeed-smc 1e630000.flash-controller: mx25l25635e (32768
Kbytes)
[ 20.763470] aspeed-smc 1e630000.flash-controller: CE0 window [
0x30000000 - 0x32000000 ] 32MB
[ 20.772110] aspeed-smc 1e630000.flash-controller: CE1 window [
0x32000000 - 0x38000000 ] 96MB
[ 20.780646] aspeed-smc 1e630000.flash-controller: read control register:
203b0241
[ 20.813318] aspeed-smc 1e630000.flash-controller: Calibration area too
uniform, using low speed
[ 20.828013] aspeed-smc 1e631000.flash-controller: Using 50 MHz SPI
frequency
[ 20.835142] aspeed-smc 1e631000.flash-controller: unrecognized JEDEC id
bytes: 00, 00, 00
[ 20.843331] aspeed-smc 1e631000.flash-controller: Aspeed SMC probe
failed -2
[ 20.858037] aspeed-smc: probe of 1e631000.flash-controller failed with
error -2
[ 20.867590] libphy: Fixed MDIO Bus: probed
[ 20.872732] ftgmac100 1e660000.ethernet: Generated random MAC address
62:0e:a0:5b:c9:d8
[ 20.880773] ftgmac100 1e660000.ethernet: Using NCSI interface
[ 20.887639] ftgmac100 1e660000.ethernet eth0: irq 19, mapped at (ptrval)
[ 20.894956] ftgmac100 1e680000.ethernet: Read MAC address
00:de:ad:be:ef:01 from chip
[ 20.922800] libphy: ftgmac100_mdio: probed
[ 20.968049] random: crng init done
[ 21.005895] Broadcom BCM54612E 1e680000.ethernet--1:01: attached PHY
driver [Broadcom BCM54612E] (mii_bus:phy_addr=1e680000.ethernet--1:01,
irq=POLL)
[ 21.020452] ftgmac100 1e680000.ethernet eth1: irq 20, mapped at 52db8149
[ 21.027520] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 21.034112] ehci-platform: EHCI generic platform driver
[ 21.040400] i2c /dev entries driver
[ 21.063218] aspeed-i2c-bus 1e78a040.i2c-bus: i2c bus 0 registered, irq 34
[ 21.072475] aspeed-i2c-bus 1e78a080.i2c-bus: i2c bus 1 registered, irq 35
[ 21.082579] aspeed-i2c-bus 1e78a140.i2c-bus: i2c bus 4 registered, irq 36
[ 21.092719] aspeed-i2c-bus 1e78a300.i2c-bus: i2c bus 7 registered, irq 37
[ 21.102868] aspeed-i2c-bus 1e78a340.i2c-bus: i2c bus 8 registered, irq 38
[ 21.113105] aspeed-i2c-bus 1e78a440.i2c-bus: i2c bus 12 registered, irq
39
[ 21.122370] i2c i2c-7: Added multiplexed i2c bus 215
[ 21.127366] pca9541 7-0070: registered master selector for I2C pca9541
[ 21.138262] pca954x 1-0071: probe failed
[ 21.142888] pca954x 4-0071: probe failed
[ 21.155079] pmbus 7-0061: PMBus status register not found
[ 21.165593] ucd9000 0-0064: Failed to read device ID
[ 21.173323] usbcore: registered new interface driver usbhid
[ 21.179018] usbhid: USB HID core driver
[ 21.202652] NET: Registered protocol family 10
[ 21.218129] Segment Routing with IPv6
[ 21.222653] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 21.229964] NET: Registered protocol family 17
[ 21.234478] 8021q: 802.1Q VLAN Support v1.8
[ 21.248244] console [netcon0] enabled
[ 21.251931] netconsole: network logging started
[ 21.257926] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 21.266549] hctosys: unable to open rtc device (rtc0)
[ 21.283017] Freeing unused kernel memory: 1024K
[ 21.290261] Checked W+X mappings: passed, no W+X pages found
[ 21.390012] systemd[1]: systemd 237 running in system mode. (+PAM -AUDIT
-SELINUX -IMA -APPARMOR -SMACK +SYSVINIT -UTMP -LIBCRYPTSETUP -GCRYPT
-GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID)
[ 21.412916] systemd[1]: Detected architecture arm.
[ 21.452208] systemd[1]: Set hostname to <zaius>.
[ 21.457517] systemd[1]: Initializing machine ID from random generator.
[ 22.750590] systemd[1]: Created slice System Slice.
[ 22.784248] systemd[1]: Created slice
system-phosphor\x2ddiscover\x2dsystem\x2dstate.slice.
[ 22.823433] systemd[1]: Listening on udev Kernel Socket.
[ 22.863473] systemd[1]: Started Dispatch Password Requests to Console
Directory Watch.
[ 22.903540] systemd[1]: Listening on Syslog Socket.
[ 22.943952] systemd[1]: Created slice
system-obmc\x2dled\x2dgroup\x2dstart.slice.
[ 24.937714] systemd-journald[501]: Received request to flush runtime
journal from PID 1
[ 28.126038] 8021q: adding VLAN 0 to HW filter on device eth0
[ 28.432290] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 30.331771] ftgmac100 1e660000.ethernet eth0: NCSI: No channel found
with link
[ 32.674557] ftgmac100 1e680000.ethernet eth1: Link is Up - 1Gbps/Full -
flow control rx/tx
[ 32.682901] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 34.826333] ftgmac100 1e680000.ethernet eth1: Link is Down
[ 36.988855] ftgmac100 1e680000.ethernet eth1: Link is Up - 1Gbps/Full -
flow control rx/tx
[ 39.057815] ftgmac100 1e680000.ethernet eth1: Link is Down
[ 41.254826] ftgmac100 1e680000.ethernet eth1: Link is Up - 100Mbps/Full
- flow control rx/tx
root@zaius:~# Stopping Network Time Synchronization...
[ OK ] Started Phosphor Time Manager daemon.
[ OK ] Reached target Phosphor System - Standby.
Starting Assert bmc_booted LED...
[ OK ] Reached target Power0 On (Pre).
[ OK ] Reached target Power0 On.
[ OK ] Reached target Power0 (On).
[ OK ] Started Phosphor Fan Monitor Initialization.
Starting Scan FSI devices...
[ OK ] Started Phosphor Fan Control Initialization.
[ OK ] Started Phosphor Fan Presence Tach Daemon.
[ OK ] Created slice system-phosphor\x2dfan\x2dcontrol.slice.
[ OK ] Started Phosphor Fan Control Daemon.
[ OK ] Created slice system-phosphor\x2dfan\x2dmonitor.slice.
[ OK ] Started Phosphor Fan Monitor Daemon.
[ OK ] Reached target Fan Control Ready.
[ OK ] Started Assert bmc_booted LED.
[FAILED] Failed to start Scan FSI devices.
See 'systemctl status fsi-scan@0.service' for details.
[DEPEND] Dependency failed for Chassis0 (Power On).
[ OK ] Stopped Start chassis0 on after BMC reset.
[ OK ] Stopped target Host0 running after reset.
[ OK ] Created slice system-avsbus\x2ddisable.slice.
Starting Wait for /org/openbmc/control/chassis0...
[ OK ] Stopped target Chassis0 power on after reset.
[ OK ] Stopped target Host0 (Reset Check).
[ OK ] Created slice system-obmc\x2dled\x2dgroup\x2dstop.slice.
[ OK ] Created slice system-op\x2dpowered\x2doff.slice.
[ OK ] Stopped Check Host0 status on BMC reset.
[ OK ] Created slice system-op\x2dwait\x2dpower\x2doff.slice.
[ OK ] Created slice system-vcs\x2doff.slice.
Starting Assert power_on LED...
[ OK ] Stopped target Power0 (On).
[ OK ] Stopped target Power0 On.
[ OK ] Stopped target Power0 On (Pre).
[ OK ] Stopped Reload mboxd during power on.
[ OK ] Stopped Assert power_on LED.
[ OK ] Created slice system-op\x2dpower\x2dstop.slice.
[ OK ] Stopped target Chassis0 (Reset Check).
Starting Turn VCS rails off...
[ OK ] Created slice system-op\x2docc\x2ddisable.slice.
Starting OpenPOWER OCC Active Disable...
[ OK ] Started Wait for /org/openbmc/control/chassis0.
[FAILED] Failed to start Turn VCS rails off.
See 'systemctl status vcs-off@0.service' for details.
[ OK ] Started Assert power_on LED.
[ OK ] Started OpenPOWER OCC Active Disable.
[ OK ] Reached target Stop Host0 (Pre).
[ OK ] Reached target Host0 (Stopping).
[ OK ] Reached target Host0 (Stopped).
[ OK ] Reached target Power0 Off (Pre).
[ OK ] Started Stop Power0.
Starting Wait for Power0 to turn off...
[ OK ] Started Wait for Power0 to turn off.
[ OK ] Started Power is off to chassis0.
[ OK ] Reached target Chassis0 (Power Off).
[ OK ] Reached target Stop Host0.
[ OK ] Reached target Power0 Off.
On Wed, Nov 7, 2018 at 12:53 AM Kun Yi <kunyi@google.com> wrote:
> 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.
>
> On Tue, Nov 6, 2018 at 1:53 AM AKASH G J <akashgj91@gmail.com> wrote:
>
>> 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.
>>
>> Still temp1_input is not coming on the sysfs (/sys/class/hwmon/hwmon0)
>>
>> On Tue, Nov 6, 2018 at 12:01 PM Kun Yi <kunyi@google.com> wrote:
>>
>>>
>>> On Mon, Nov 5, 2018 at 10:17 PM Troy Lee <leetroy@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@gmail.com>
>>>> AKASH G J <akashgj91@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@zaius:~# ls / -R | grep Hwmon
>>>> > xyz.openbmc_project.Hwmon@.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@zaius:~#
>>>> >
>>>> > On Mon, Nov 5, 2018 at 1:20 PM Troy Lee <leetroy@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@gmail.com>
>>>> >> AKASH G J <akashgj91@gmail.com> 於 2018年11月5日 週一 下午2:55寫道：
>>>> >> >
>>>> >> > 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
>>>> >> >
>>>> >> > Failed to introspect object
>>>> /xyz/openbmc_project/Sensors/temperature/ambient of service
>>>> xyz.openbmc_project.Hwmon@.service: Invalid argument.
>>>> >> >
>>>> >> > 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.
>>>> >> >
>>>> >> > 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@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@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@google.com> wrote:
>>>> >> >>>>
>>>> >> >>>> On Tue, Oct 30, 2018 at 10:13 PM AKASH G J <akashgj91@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@1e6e2000
>>>> /i2c-bus@90/tmp75@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@48 {
>>>> >> >>>> > + compatible = "ti,tmp75";
>>>> >> >>>> > + reg = <0x48>;
>>>> >> >>>> > + };
>>>> >> >>>> > +
>>>> >> >>>> > };
>>>> >> >>>> >
>>>> >> >>>> > After booting Linux, the changes are reflected in
>>>> /sys/firmware/devicetree/base/ahb/apb/i2c@1e78a000/i2c-bus@440
>>>> /tmp75@48. Also,
>>>> >> >>>> > tmp78.conf is showing in
>>>> /etc/default/obmc/hwmon/ahb/apb/i2c@1e78a000/i2c-bus@90.
>>>>
>>>
>>> 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.
>>>
>>> Steps to try:
>>> 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
>>> 2. Make sure the hwmon sysfs interface shows up and temp1_input reads a
>>> valid value
>>> 3. Play with busctl as others suggested and make sure the sensor value
>>> is reported over DBus
>>>
>>>
>>>> >> >>>> >
>>>> >> >>>> > 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
>>>> >> >>>> >
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> Kun
>>>
>>
>
> --
> Regards,
> Kun
>
[-- Attachment #2: Type: text/html, Size: 28390 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2018-11-08 6:27 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-31 5:13 Temperature Sensor Reading not showing up AKASH G J
2018-11-01 17:57 ` Patrick Venture
2018-11-02 10:19 ` AKASH G J
2018-11-02 15:27 ` Emily Shaffer
2018-11-05 6:54 ` AKASH G J
2018-11-05 7:50 ` Troy Lee
2018-11-05 8:40 ` AKASH G J
2018-11-06 6:16 ` Troy Lee
2018-11-06 6:30 ` Kun Yi
2018-11-06 9:53 ` AKASH G J
2018-11-06 19:22 ` Kun Yi
2018-11-08 6:26 ` AKASH G J
2018-11-06 6:39 ` AKASH G J
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).