From: "Yong Li" <yong.b.li@linux.intel.com>
To: "'Zheng Bao'" <fishbaoz@hotmail.com>, <openbmc@lists.ozlabs.org>
Subject: RE: Enable KCS interface in zaius
Date: Tue, 10 Sep 2019 09:24:36 +0800 [thread overview]
Message-ID: <000901d56776$82cf6750$886e35f0$@linux.intel.com> (raw)
In-Reply-To:
[-- Attachment #1: Type: text/plain, Size: 3145 bytes --]
I also would like to know how did you perform the build?
export TEMPLATECONF=meta-openbmc-mods/meta-wht/conf
source oe-init-build-env
bitbake intel-platforms
Thanks,
Yong
From: Yong Li <yong.b.li@linux.intel.com>
Sent: Monday, September 9, 2019 4:53 PM
To: 'Zheng Bao' <fishbaoz@hotmail.com>; 'Andrew Jeffery' <andrew@aj.id.au>;
'AKASH G J' <akashgj91@gmail.com>; 'openbmc@lists.ozlabs.org'
<openbmc@lists.ozlabs.org>
Subject: RE: Enable KCS interface in zaius
Can you find the image-mtd file? You can flash this file with this
command(scp it to /tmp folder on the board):
flashcp /tmp/image-mtd /dev/mtd0
Thanks,
Yong
From: openbmc <openbmc-bounces+yong.b.li=linux.intel.com@lists.ozlabs.org
<mailto:openbmc-bounces+yong.b.li=linux.intel.com@lists.ozlabs.org> > On
Behalf Of Zheng Bao
Sent: Saturday, September 7, 2019 7:34 PM
To: Yong Li <yong.b.li@linux.intel.com <mailto:yong.b.li@linux.intel.com> >;
'Andrew Jeffery' <andrew@aj.id.au <mailto:andrew@aj.id.au> >; 'AKASH G J'
<akashgj91@gmail.com <mailto:akashgj91@gmail.com> >;
openbmc@lists.ozlabs.org <mailto:openbmc@lists.ozlabs.org>
Subject: Re: Enable KCS interface in zaius
I check out the https://github.com/Intel-BMC/openbmc
and build the board: meta-openbmc-mods/meta-wolfpass/conf
But got the error,
dd: failed to open
'/home/baozheng/bmc/openbmc-github/build/tmp/deploy/images/intel-ast2500/fit
Image-rootfs-intel-ast2500.bin': No such file or directory
Did I miss something?
Zheng
_____
From: openbmc <openbmc-bounces+fishbaoz=hotmail.com@lists.ozlabs.org
<mailto:openbmc-bounces+fishbaoz=hotmail.com@lists.ozlabs.org> > on behalf
of Yong Li <yong.b.li@linux.intel.com <mailto:yong.b.li@linux.intel.com> >
Sent: Friday, August 30, 2019 6:29 AM
To: 'Andrew Jeffery' <andrew@aj.id.au <mailto:andrew@aj.id.au> >; 'AKASH G
J' <akashgj91@gmail.com <mailto:akashgj91@gmail.com> >;
openbmc@lists.ozlabs.org <mailto:openbmc@lists.ozlabs.org>
<openbmc@lists.ozlabs.org <mailto:openbmc@lists.ozlabs.org> >
Subject: RE: Enable KCS interface in zaius
It seems that the kernel needs to enable KCS, and disable BT.
CONFIG_ASPEED_KCS_IPMI_BMC=y
Suggest to check on this: https://github.com/Intel-BMC/openbmc
Thanks,
Yong
-----Original Message-----
From: openbmc <openbmc-bounces+yong.b.li=linux.intel.com@lists.ozlabs.org
<mailto:openbmc-bounces+yong.b.li=linux.intel.com@lists.ozlabs.org> >
On Behalf Of Andrew Jeffery
Sent: Friday, August 30, 2019 12:42 PM
To: AKASH G J <akashgj91@gmail.com <mailto:akashgj91@gmail.com> >;
openbmc@lists.ozlabs.org <mailto:openbmc@lists.ozlabs.org>
Subject: Re: Enable KCS interface in zaius
On Thu, 29 Aug 2019, at 09:05, AKASH G J wrote:
> Hi all,
>
> I am using server platform with Intel processor and Aspeed AST-2500
> BMC. OpenBMC firmware with zaius configuration is used for BMC.
>
Zaius is an OpenPOWER platform (and our OpenPOWER platforms use the BT
interface rather than KCS). You're using an Intel-based processor for the
host, so perhaps it's better to start with an x86-based platform such as the
s2600wf. This should already have KCS IPMI enabled for you.
Andrew
[-- Attachment #2: Type: text/html, Size: 7755 bytes --]
next prev parent reply other threads:[~2019-09-10 1:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 23:35 Enable KCS interface in zaius AKASH G J
2019-08-30 3:59 ` AKASH G J
2019-08-30 4:42 ` Andrew Jeffery
2019-08-30 6:29 ` Yong Li
2019-09-07 11:34 ` Zheng Bao
2019-09-09 8:53 ` Yong Li
2019-09-09 14:10 ` Zheng Bao
2019-09-10 1:24 ` Yong Li [this message]
2019-09-10 1:26 ` Yong Li
2019-09-12 9:08 ` Zheng Bao
2019-09-16 3:07 ` Yong Li
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='000901d56776$82cf6750$886e35f0$@linux.intel.com' \
--to=yong.b.li@linux.intel.com \
--cc=fishbaoz@hotmail.com \
--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.