From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=none (mailfrom) smtp.mailfrom=linux.vnet.ibm.com (client-ip=148.163.158.5; helo=mx0a-001b2d01.pphosted.com; envelope-from=mspinler@linux.vnet.ibm.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.vnet.ibm.com Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 43tXHt1YDkzDqL8 for ; Tue, 5 Feb 2019 02:51:21 +1100 (AEDT) Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x14FbCYA162331 for ; Mon, 4 Feb 2019 10:51:19 -0500 Received: from e17.ny.us.ibm.com (e17.ny.us.ibm.com [129.33.205.207]) by mx0b-001b2d01.pphosted.com with ESMTP id 2qepvs55h9-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 04 Feb 2019 10:51:19 -0500 Received: from localhost by e17.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 4 Feb 2019 15:51:18 -0000 Received: from b01cxnp23034.gho.pok.ibm.com (9.57.198.29) by e17.ny.us.ibm.com (146.89.104.204) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Mon, 4 Feb 2019 15:51:15 -0000 Received: from b01ledav002.gho.pok.ibm.com (b01ledav002.gho.pok.ibm.com [9.57.199.107]) by b01cxnp23034.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x14FpElM23920780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 4 Feb 2019 15:51:14 GMT Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id F157012405B; Mon, 4 Feb 2019 15:51:13 +0000 (GMT) Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 89B3F124053; Mon, 4 Feb 2019 15:51:13 +0000 (GMT) Received: from ltc.linux.ibm.com (unknown [9.16.170.189]) by b01ledav002.gho.pok.ibm.com (Postfix) with ESMTP; Mon, 4 Feb 2019 15:51:13 +0000 (GMT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 04 Feb 2019 09:57:37 -0600 From: Matt Spinler To: AKASH G J Cc: openbmc@lists.ozlabs.org, openbmc Subject: Re: LED not Blinking In-Reply-To: References: X-Sender: mspinler@linux.vnet.ibm.com User-Agent: Roundcube Webmail/1.0.1 X-TM-AS-GCONF: 00 x-cbid: 19020415-0040-0000-0000-000004BC1148 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00010535; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000279; SDB=6.01156291; UDB=6.00593882; IPR=6.00936750; MB=3.00025433; MTD=3.00000008; XFM=3.00000015; UTC=2019-02-04 15:51:16 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19020415-0041-0000-0000-000008C72A71 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-02-04_11:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=860 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1902040122 X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2019 15:51:22 -0000 On 2019-02-04 06:18, AKASH G J wrote: > Hi all, > > We have a board containing BMC Aspeed AST-2500. One LED is connected > to GPIO-E0. I am using zaius machine configuration for building the > image. I want that LED to blink after BMC is booted. So I changed the > following files. > > Patched the device tree file aspeed-bmc-opp-zaius.dts > > leds { > compatible = "gpio-leds"; > + power { > + gpios = <&gpio ASPEED_GPIO(E, 0) GPIO_ACTIVE_LOW>; > + }; > }; > > Added the following configuration to sensor inventory file > openbmc/meta-ingrasys/meta-zaius/recipes-phosphor/ipmi/phosphor-ipmi-sensor-inventory%/config.yaml > > bmc_booted: > power: > Action: 'Blink' > DutyOn: 50 > Period: 1000 > Priority: 'On' > > The LED is glowing when the BMC boots up. But it is not blinking. > Please someone help to resolve the issue. > Hi, The LEDs are defined in a different file, check out, for example, meta-ibm/meta-romulus/recipes-phosphor/leds/romulus-led-manager-config/led.yaml. You can tell it should be working when you see a /xyz/openbmc_project/led/groups/bmc_booted object on D-Bus. > Thanks in advance.