<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>Dear Tim</div><div> It's exactly what I wanted.</div><div> You are wonderful.</div><div> </div><div> I remember you. <br></div><div> You taught me a lot.</div><div><br></div><div> Following your seggestions, I can power on the chassis by ipmitool.</div><div> But there is still a bit prolems:</div><div> When I do the action: ipmitool -I lanplus -H 192.168.0.1 -U root -P 0penBmc power on.</div><div> Right after, the chassis is power up.</div><div> Waiting for about 4 seconds,the chassis is power off again.</div><div> <br></div><div> I guess this is because the power up pin keeps active for a long time.</div><div> when power up pin keeping active for 4 seconds,the chassis power will lost again. <br></div><div> <br></div><div> <span style="color: rgb(221, 64, 50);"><b>I will debug this problem. If you have more suggestions, welcome to teach me.</b></span></div><div><span style="color: rgb(221, 64, 50);"><b> <br></b></span></div><div><span style="color: rgb(221, 64, 50);"><b> And,Could you show me the dependencies of "obmc-host-shutdown<span ntes_mm_email="@">@0.target</span>"?</b></span></div><div><span style="color: rgb(221, 64, 50);"><b> (power off, still on x86 motherboard and use romulus receipes).</b></span></div><div><br></div><div> Looking forward for your reply.</div><div><br></div><div>Best Regards</div><div>Felix<br></div><div> <br></div><br><pre>At 2019-12-26 15:46:13, "CS20 CHLi30" <CHLI30@nuvoton.com> wrote:
>Hi Felix,
>
>If you need to add your .service unit file into .want or .requires folder, you can use systemd to do that in .bb file.
>
>You can refer obmc-op-control-power_git.bb this file for example:
>
>Install to .requires folder:
>RESET_ON_TMPL = "op-reset-chassis-running@.service"
>RESET_ON_INSTFMT = "op-reset-chassis-running@{0}.service"
>RESET_ON_FMT = "../${RESET_ON_TMPL}:${RESET_TGTFMT}.requires/${RESET_ON_INSTFMT}"
>
>Install to .want folder:
># Force the standby target to run the chassis reset check target
>RESET_TMPL_CTRL = "obmc-chassis-powerreset@.target"
>SYSD_TGT = "multi-user.target"
>RESET_INSTFMT_CTRL = "obmc-chassis-powerreset@{0}.target"
>RESET_FMT_CTRL = "../${RESET_TMPL_CTRL}:${SYSD_TGT}.wants/${RESET_INSTFMT_CTRL}"
>SYSTEMD_LINK_${PN} += "${@compose_list_zip(d, 'RESET_FMT_CTRL', 'OBMC_CHASSIS_INSTANCES')}"
>
>Sincerely,
>Tim
>-----Original Message-----
>From: openbmc [mailto:openbmc-bounces+chli30=nuvoton.com@lists.ozlabs.org] On Behalf Of Lei YU
>Sent: Thursday, December 26, 2019 3:37 PM
>To: zhang_cy1989 <zhang_cy1989@163.com>
>Cc: openbmc@lists.ozlabs.org
>Subject: Re: How to change the soft link in target.requires or target.wants directory
>
>On Thu, Dec 26, 2019 at 3:18 PM zhang_cy1989 <zhang_cy1989@163.com> wrote:
>>
>> Dear All
>> The target.requires or target.wants contains some soft link.
>> Ex:
>> /lib/systemd/system/obmc-host-startmin@0.target.requires
>> lrwxrwxrwx 1 root root 31 Nov 29 2019 obmc-chassis-poweron@0.target -> ../obmc-chassis-poweron@.target
>> lrwxrwxrwx 1 root root 25 Nov 28 09:51 op-occ-enable@0.service -> ../op-occ-enable@.service
>> lrwxrwxrwx 1 root root 22 Nov 28 09:57 start_host@0.service -> ../start_host@.service
>>
>> Now, I want to add or delete soft link:op-occ-enable@0.service
>> I can use "rm -rf ./op-occ-enable@0.service" to achieve the goal.
>> But,I'm not exactly sure this is formal operation. And I'm afraid this will be side effect.
>>
>> Are there other tools or formal methods to do this?
>
>These links are expected to be managed by systemd.
>You could disable or mask the services by `systemctl [disable|mask] <service>`. If you need them later, just enable or unmask them.
>________________________________
>________________________________
> The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.
</pre></div><br><br><span title="neteasefooter"><p> </p></span>