Hi Felixzhang,

=C2=A0

Yes, you can using op-power-control on X86 m= otherboard for sure.

=C2=A0

Example about using op-power-control:=

systemctl list-dependencies obmc-host-sta= rt@0.target

=C2=A0

obmc-host-start@0.target (Power ON)

-> mapper-wait@-org-openbmc-control-chass= is0.service

-> phosphor-reset-host-reboot-attempts@0.= service

-> obmc-host-startmin@0.target<= /u>

=C2=A0=C2=A0=C2=A0=C2=A0 -> mapper-wait@-= org-openbmc-control-chassis0.service

=C2=A0=C2=A0=C2=A0=C2=A0 -> obmc-enable-h= ost-watchdog@0.service

=C2=A0=C2=A0=C2=A0=C2=A0 -> phosphor-watc= hdog@poweron.service

=C2=A0=C2=A0=C2=A0=C2=A0 -> obmc-chassis-= poweron@0.target

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 -> op-power-start@0.service

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 -> mapper-wait@-xyz-openbmc_project-state-chassis0.service<= u>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 -> phosphor-fan-control-init@0.service=

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 -> phosphor-fan-monitor-init@0.service=

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 -> phosphor-fan-presence-tach@0.service

=C2=A0

BTW, here is the list about the sequence of obmc-host-sta= rt@0.target for you refer it.

When you presss Power ON button from WebUI t= he state RequestedHostTransition change to ON, what happens behind that is = done by systemd units, roughly described as below:

1.=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 Host state manager starts obmc-host-start@0.target

2.=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 The above target requires obmc-host-startmin@0.target

3.=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 The above target requires obmc-chassis-poweron@0.target and start_host@0.service=

4.=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 obmc-chassis-poweron@0.target requires op-power-start@0.service and op-wait-power-on@0.service=

5.=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 op-power-start@0.service is to call the PowerControl service to DC on. And op-wait-power-on@0.se= rvice is to wait for PGood after DC on.

6.=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 After that (DC is on and PGood is OK), start_host@0.service is to start the host CPU.<= /p>

=C2=A0

Best regards,

Tim

From: zhang_cy1989 [mailto:zhang_cy1989@163.com= ]
Sent: Thursday, December 26, 2019 10:22 AM
To: CS20 CHLi30 <CHLI30@nuvoton.com>
Cc: op= enbmc@lists.ozlabs.org
Subject: Re:RE: systemctl start obmc-host-start@0.target fail=

=C2=A0

Dear,Tim

=C2=A0=C2=A0 Thank you for guidance.

=C2=A0=C2=A0 I will study the dbus-mon= itor and the dependencies of obmc-host-sta= rt@0.target.

=C2=A0@CS20 CHLi30

=C2=A0 I need ask you another advice.

=C2=A0

=C2=A0 I use the romulus recipes to bu= ild BMC firmware. And use this fw to the X86 motherboard + AST2500.<= u>

=C2=A0 The romulus is base on openpowe= r. And my platform is X86 motherboard.

=C2=A0 Is it feasible that using romulus BMC firm= ware to X86 motherboard, specially the power control part?

=C2=A0

=C2=A0 Would you have better suggestio= n?

=C2=A0

=C2=A0 Looking forward to your replay.=

=C2=A0

=C2=A0Best Regards

=C2=A0Felixzhang<= /p>

=C2=A0

At 2019-12-26 09:34:09, "CS20 CHLi30" <CHLI30@nuvoton.com>= ; wrote:

Hi Felixzhang,

=C2=A0=

About this kind of systemd = target start fail, you can use dbus-monitor to check target dependency more detail.

BTW, you can also use systemctl list-dependecies obmc-host-start@0.target to get all related servic= es.

=C2=A0=

For example for using x86-p= ower-control:

systemctl list-dependenc= ies obmc-host-sta= rt@0.target

=C2=A0=

obmc-host-start@0.target (Power ON)

-> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service<= span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:black" la= ng=3D"EN-US">

-> phosphor-reset-host-reboot-attempts@0.service

-> obmc-host-= startmin@0.target

=C2=A0=C2=A0=C2=A0=C2=A0 -&= gt; mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service<= span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:black" la= ng=3D"EN-US">

=C2=A0=C2=A0=C2=A0=C2=A0 -&= gt; ob= mc-enable-host-watchdog@0.service

=C2=A0=C2=A0=C2=A0=C2=A0 -&= gt; phos= phor-watchdog@poweron.service=

=C2=A0=C2=A0=C2=A0=C2=A0 -&= gt; obmc-cha= ssis-poweron@0.target

=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 -> intel-powe= r-start@0.service

=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service<= span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:black" la= ng=3D"EN-US">

=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 -> ph= osphor-fan-control-init@0.service

=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 -> ph= osphor-fan-monitor-init@0.service

=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 -> p= hosphor-fan-presence-tach@0.service<= /span>

=C2=A0=

Then you should found that = might some services doesn=E2=80=99t start normally and cause your obmc-host-tart@0.target start fail.=

=C2=A0=

Best regards,

Tim=

From: openbmc [mailto:openbmc-bounces+chli30=3Dnuvoton.com@lists= .ozlabs.org] On Behalf Of zhang_cy1989
Sent: Wednesday, December 25, 2019 7:19 PM
To: op= enbmc@lists.ozlabs.org
Subject: systemctl start obmc-host-start@0.target fail

=C2=A0

=C2=A0

Dear All

=C2=A0=C2=A0 On ast2500+x86 platform, = use the romulus bmc firmware, the detail information:<= /p>

ID=3D"openbmc-phospho= r"
NAME=3D"Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro= )"
VERSION=3D"2.7.0-0"
VERSION_ID=3D"2.7.0-0-gcb91a7773-dirty"
PRETTY_NAME=3D"Phosphor OpenBMC (Phosphor OpenBMC Project Reference= Distro) 2.7.0-0"
BUILD_ID=3D"2.7.0"
OPENBMC_TARGET_MACHINE=3D"romulus"=

=C2=A0

=C2=A0 The BMC ip: 192.168.0.1<= u>

=C2=A0 Remote Computer ip: 192.168.0.2=

=C2=A0

=C2=A0 I use the ipmitool to communica= te with BMC:

ipmitool -I lanplus -H 192.168.0.1 -U = root -P 0penBmc power on

=C2=A0

=C2=A0And from the journalctl results,= I found those infromations:

......

-- The unit op-wait-pow= er-on@0.service has entered the 'failed' state with result '= ;timeout'.
Nov 28 07:55:47 romulus systemd[1]: Failed to start Wait for Power0 to turn= on.
-- Subject: A start job for unit op-wait-power-on@0.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit op-wait-power-on@0.service has finished with a failure. --
-- The job identifier is 906 and the job result is failed.
Nov 28 07:55:47 romulus systemd[1]: Dependency failed for Chassis0 (Power O= n).
-- Subject: A start job for unit obmc-chassis-poweron@0.target has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit obmc-chassis-poweron@0.target has finished with a failu= re.
--
-- The job identifier is 886 and the job result is dependency.
Nov 28 07:55:47 romulus systemd[1]: Dependency failed for Start Host0 Minim= um.
-- Subject: A start job for unit obmc-host-startmin@0.target has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit obmc-host-startmin@0.target has finished with a failure.<= br> --
-- The job identifier is 752 and the job result is dependency.
Nov 28 07:55:47 romulus systemd[1]: Dependency failed for Start Host0.
-- Subject: A start job for unit obmc-host-start@0.target has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit obmc-host-start@0.target has finished with a failure.

Nov 28 08:24:09 romulus systemd[1]: obmc-host-sta= rt@0.target: Job obmc-host-start@0.target/start failed with result 'dependency'.=
Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target: Triggering OnFailure= =3D dependencies.
Nov 28 08:24:10 romulus systemd[1]: obmc-host-startmin@0.target: Job obmc-host-startmin@0.target/start failed with result 'dependency= 9;.
Nov 28 08:24:10 romulus systemd[1]: obmc-host-startmin@0.target: Triggering OnFailure=3D dependencies.
Nov 28 08:24:10 romulus systemd[1]: obmc-chassis-poweron@0.target: Job obmc-chassis-poweron@0.target/start failed with result 'dependency&= #39;.
Nov 28 08:24:10 romulus systemd[1]: obmc-chassis-poweron@0.target: Triggering OnFailure=3D dependencies.=

......

=C2=A0

I alse do the following action:=

systemctl start obmc-host-sta= rt@0.target

And alse get the similar fail result.

=C2=A0

I don't how to debug this isuue.Co= uld you give me some suggestions?

=C2=A0

Best Regards

Felixzhang

=C2=A0

=C2=A0

=C2=A0

=C2=A0=

=C2=A0=

=C2=A0

The privileged confidential information contained in thi= s email is intended for use only by the addressees as indicated by the orig= inal sender of this email. If you are not the addressee indicated in this email or are not responsible for deliv= ery of the email to such a person, please kindly reply to the sender indica= ting this fact and delete all copies of it from your computer and network s= erver immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confiden= tial information of Nuvoton is strictly prohibited; and any information in = this email irrelevant to the official business of Nuvoton shall be deemed a= s neither given nor endorsed by Nuvoton.

=C2=A0