Error:"Failed to find the pwm0_gpio40 line"

[khader basha shaik]

Thanks alot Konstantin for the information.

We wanted to verify if the Chassis info is populated properly,
(redfish/v1/Chassis).We need to get the Chassis info and we are using curl
command on path, /redfidh/v1/Chassis.But no information is being populated.

Is there any way to verify chassis information ?

We have used the x86-power-control to populate the /redfish/v1/chassis, but
we no luck with this too. We did not see any data through this .

Any suggestions or input on this would be appreciated.

Thanks & Regards,
Khader B Shaik



On Thu, 5 Nov 2020 at 12:14, Konstantin Klubnichkin <kitsok at yandex-team.ru>
wrote:

> - все
>
> Hello!
>
> This error means GPIO library unable to find line with this name.
> To check you can
> cat /sys/kernel/debug/gpio | grep pwm0_gpio40
> or
> gpioinfo | grep pwm0_gpio40
>
> The most probably cause is missing line name in DTS.
> There must be something like this:
> &gpio {
> status = "okay";
> pinctrl-names = "pass-through";
> pinctrl-0 = <&pinctrl_gpid0_default
> &pinctrl_gpid2_default>;
> gpio-line-names =
> /* A0-A7 */ "A0", "A1", "A2", "A3", "A4", "A5", "A6", "A7",
> /* B0-B7 */ "B0", "B1", "B2", "POST_COMPLETE", "B4", "B5", "PS_PWROK",
> "B7",
> ................
> };
>
> I don't have PI on hands so my example is for AST2500 SoC, but as far as I
> remember there are many guides how to patch DTS for Raspberry.
>
> 05.11.2020, 09:03, "khader basha shaik" <shaikkhaderbasha601 at gmail.com>:
>
> Hi Team,
>
> we are trying to control our board with RPI bmc.we are trying to control
> power on, off and reset
>
> we compiled x86-power-control with openbmc and create a patch for the sane
> with the GPIO name "pwm0_gpio40". and when we are try to use this.
> we are facing the below error.
>
> root at akky:~# systemctl status
> xyz.openbmc_project.Chassis.Control.Power.service
> ● xyz.openbmc_project.Chassis.Control.Power.service - Power Control
> Loaded: loaded
> (/lib/systemd/system/xyz.openbmc_project.Chassis.Control.Power.service;
> enabled; vendor preset: enabled)
> Active: failed (Result: exit-code) since Thu 1970-01-01 00:00:13 UTC; 33s
> ago
> Process: 310 ExecStart=/usr/bin/power-control (code=exited,
> status=255/EXCEPTION)
> Main PID: 310 (code=exited, status=255/EXCEPTION)
>
> Jan 01 00:00:13 akky systemd[1]:
> xyz.openbmc_project.Chassis.Control.Power.service: Scheduled restart job,
> restart counter is at 2.
> Jan 01 00:00:13 akky systemd[1]: Stopped Power Control.
> Jan 01 00:00:13 akky systemd[1]:
> xyz.openbmc_project.Chassis.Control.Power.service: Start request repeated
> too quickly.
> Jan 01 00:00:13 akky systemd[1]:
> xyz.openbmc_project.Chassis.Control.Power.service: Failed with result
> 'exit-code'.
> Jan 01 00:00:13 akky systemd[1]: Failed to start Power Control.
> root at akky:~# /usr/bin/power-control -h
> Start Chassis power control service...
> Failed to find the pwm0_gpio40 line
>
> Could someone help me how to fix this or some pointers regarding this
> error.
>
> Also is physcial connection between the bmc and the server is needed or we
> can test this through someother way.
>
> Thanks & Regards,
> Khader B Shaik
>
>
>
>
> --
> Best regards,
> Konstantin Klubnichkin,
> lead firmware engineer,
> server hardware R&D group,
> Yandex Moscow office.
> tel: +7-903-510-33-33
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20201105/a2f7be2b/attachment-0001.htm>