From: Matt Spinler <mspinler@linux.vnet.ibm.com>
To: AKASH G J <akashgj91@gmail.com>
Cc: openbmc@lists.ozlabs.org,
openbmc
<openbmc-bounces+mspinler=linux.vnet.ibm.com@lists.ozlabs.org>
Subject: Re: LED not Blinking
Date: Mon, 04 Feb 2019 09:57:37 -0600 [thread overview]
Message-ID: <f9f2f2ecdbfbc94f8a6afcbd7ab06ced@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAE33tLEsh+Oh8LYY0tkO98tVzVDjZwbxO9J49zp2fAWz_dysbQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2019-02-04 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 12:18 LED not Blinking AKASH G J
2019-02-04 15:57 ` Matt Spinler [this message]
2019-02-05 4:34 ` AKASH G J
2019-02-05 15:31 ` Matt Spinler
2019-02-07 14:11 ` vishwa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9f2f2ecdbfbc94f8a6afcbd7ab06ced@linux.vnet.ibm.com \
--to=mspinler@linux.vnet.ibm.com \
--cc=akashgj91@gmail.com \
--cc=openbmc-bounces+mspinler=linux.vnet.ibm.com@lists.ozlabs.org \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.