From: "Yong Li" <yong.b.li@linux.intel.com>
To: "'Zheng Bao'" <fishbaoz@hotmail.com>,
"'Andrew Jeffery'" <andrew@aj.id.au>,
"'AKASH G J'" <akashgj91@gmail.com>, <openbmc@lists.ozlabs.org>
Subject: RE: Enable KCS interface in zaius
Date: Mon, 16 Sep 2019 11:07:43 +0800 [thread overview]
Message-ID: <001601d56c3b$e9151180$bb3f3480$@linux.intel.com> (raw)
In-Reply-To: <MN2PR04MB66693029C6009D3A03416A3FCDB00@MN2PR04MB6669.namprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 4461 bytes --]
Just want to know did you test the image using a real hardware?
You can check your kernel .config file in
build/tmp/work/intel_ast2500-openbmc-linux-gnueabi/linux-aspeed/5.2+gitAUTOI
NC+c01e98d151-r0/linux-intel_ast2500-standard-build
CONFIG_IPMI_KCS_BMC=y
CONFIG_ASPEED_KCS_IPMI_BMC=y
Thanks,
Yong
From: openbmc <openbmc-bounces+yong.b.li=linux.intel.com@lists.ozlabs.org>
On Behalf Of Zheng Bao
Sent: Thursday, September 12, 2019 5:09 PM
To: Yong Li <yong.b.li@linux.intel.com>; 'Andrew Jeffery' <andrew@aj.id.au>;
'AKASH G J' <akashgj91@gmail.com>; openbmc@lists.ozlabs.org
Subject: Re: Enable KCS interface in zaius
I use qemu to test the image. Got the result.
$ qemu-system-arm -m 512 -M ast2500-evb -nographic -drive
file=phosphor-intel-platform-1.bin,format=raw,if=mtd
U-Boot 2016.07 (Sep 11 2019 - 21:38:56 +0000)
SOC : AST2500-A1
RST : 0x01
PLL : 24 MHz
CPU : 792 MHz
MEM : 2.240 MHz, EEC: Disable, Cache: Disable
VGA : 16 MiB
DRAM : init by SOC
Watchdog enabled
DRAM: 496 MiB
Flash: 32 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Error: start and/or end address not on sector boundary
Error: start and/or end address not on sector boundary
Error: start and/or end address not on sector boundary
Zheng
_____
From: Yong Li <yong.b.li@linux.intel.com <mailto:yong.b.li@linux.intel.com>
>
Sent: Tuesday, September 10, 2019 1:26 AM
To: 'Zheng Bao' <fishbaoz@hotmail.com <mailto:fishbaoz@hotmail.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>
<openbmc@lists.ozlabs.org <mailto:openbmc@lists.ozlabs.org> >
Subject: RE: Enable KCS interface in zaius
I would like to know how did you perform the build? Please perform the below
commands:
export TEMPLATECONF=meta-openbmc-mods/meta-wht/conf
source oe-init-build-env
bitbake intel-platforms
Thanks,
Yong
From: Zheng Bao <fishbaoz@hotmail.com <mailto:fishbaoz@hotmail.com> >
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: 11159 bytes --]
prev parent reply other threads:[~2019-09-16 4:44 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
2019-09-10 1:26 ` Yong Li
2019-09-12 9:08 ` Zheng Bao
2019-09-16 3:07 ` Yong Li [this message]
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='001601d56c3b$e9151180$bb3f3480$@linux.intel.com' \
--to=yong.b.li@linux.intel.com \
--cc=akashgj91@gmail.com \
--cc=andrew@aj.id.au \
--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.