All of lore.kernel.org
 help / color / mirror / Atom feed
* couple OpenBMC  image build and update  questions
@ 2019-01-21  7:05 Brenden Lai
  2019-01-22 13:29 ` Andrew Geissler
  0 siblings, 1 reply; 3+ messages in thread
From: Brenden Lai @ 2019-01-21  7:05 UTC (permalink / raw)
  To: openbmc

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

Hi all ,
               I have done my first OpenBMC build with ver 2.6 , it do take a long time .
               Here is my questions .

  1.  Attach screenshot , Which one is the BMC FW image  after building?
  2.  Does the image for both QEMU and real machine ?
  3.  How to update it by programming tool like SF600?
  4.  Does it support online update such as AMI YAFU flash ?　


Here is the output of my  build
brenden@brenden-VirtualBox:~/OCP/openbmc/build/tmp/deploy/images/qemuarm$ ls obmc*
obmc-phosphor-debug-tarball-qemuarm-20190119120630.qemuboot.conf
obmc-phosphor-debug-tarball-qemuarm-20190119120630.rootfs.manifest
obmc-phosphor-debug-tarball-qemuarm-20190119120630.rootfs.tar.xz
obmc-phosphor-debug-tarball-qemuarm-20190119120630.testdata.json
obmc-phosphor-debug-tarball-qemuarm.manifest
obmc-phosphor-debug-tarball-qemuarm.qemuboot.conf
obmc-phosphor-debug-tarball-qemuarm.tar.xz
obmc-phosphor-debug-tarball-qemuarm.testdata.json
obmc-phosphor-image-qemuarm-20190119120630.qemuboot.conf
obmc-phosphor-image-qemuarm-20190119120630.rootfs.ext4
obmc-phosphor-image-qemuarm-20190119120630.rootfs.manifest
obmc-phosphor-image-qemuarm-20190119120630.rootfs.tar.bz2
obmc-phosphor-image-qemuarm-20190119120630.testdata.json
obmc-phosphor-image-qemuarm.ext4
obmc-phosphor-image-qemuarm.manifest
obmc-phosphor-image-qemuarm.qemuboot.conf
obmc-phosphor-image-qemuarm.tar.bz2
obmc-phosphor-image-qemuarm.testdata.json

Brenden Lai
SR. BMC Design Engineer
E&I, Jabil Design Services


[-- Attachment #2: Type: text/html, Size: 7029 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: couple OpenBMC image build and update questions
  2019-01-21  7:05 couple OpenBMC image build and update questions Brenden Lai
@ 2019-01-22 13:29 ` Andrew Geissler
  2019-01-23  7:05   ` Brenden Lai
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Geissler @ 2019-01-22 13:29 UTC (permalink / raw)
  To: Brenden Lai; +Cc: openbmc

On Mon, Jan 21, 2019 at 1:05 AM Brenden Lai <Brenden_Lai@jabil.com> wrote:
>
> Hi all ,
>
>                I have done my first OpenBMC build with ver 2.6 , it do take a long time .
>                Here is my questions .
>
> Attach screenshot , Which one is the BMC FW image  after building?

I haven't built the default qemuarm image in a long time. I believe
obmc-phosphor-image-qemuarm.ext4 is the FW image.

> Does the image for both QEMU and real machine ?

I believe this default image would only support QEMU.

> How to update it by programming tool like SF600?

Yes, we use the dediprog tool internally to flash fresh chips.

> Does it support online update such as AMI YAFU flash ?

Not familiar with this but once you get OpenBMC on a systems, it does provide
interfaces to update the firmware via a network connection.

The system we use for our CI work is Romulus. This system is supported in
QEMU and on real hardware if you'd like to give it a shot.

https://github.com/openbmc/openbmc/blob/master/README.md#3-target-your-hardware
talks about setting up your TEMPLATECONF for a system and
https://github.com/openbmc/docs/blob/master/development/dev-environment.md#download-and-start-qemu-session
has some pointers on starting your QEMU session. You'd of course need a Romulus
system to flash on real hardware but hopefully it would help you get
comfortable with
building the image and testing in QEMU.

OpenBMC images are very specific to the hardware so before flashing on
your system
 you'd need to ensure you've got all of the different config options setup.
https://github.com/openbmc/docs/blob/master/development/add-new-system.md
is a reference for how to add a new system.

>
>
> Here is the output of my  build
> brenden@brenden-VirtualBox:~/OCP/openbmc/build/tmp/deploy/images/qemuarm$ ls obmc*
> obmc-phosphor-debug-tarball-qemuarm-20190119120630.qemuboot.conf
> obmc-phosphor-debug-tarball-qemuarm-20190119120630.rootfs.manifest
> obmc-phosphor-debug-tarball-qemuarm-20190119120630.rootfs.tar.xz
> obmc-phosphor-debug-tarball-qemuarm-20190119120630.testdata.json
> obmc-phosphor-debug-tarball-qemuarm.manifest
> obmc-phosphor-debug-tarball-qemuarm.qemuboot.conf
> obmc-phosphor-debug-tarball-qemuarm.tar.xz
> obmc-phosphor-debug-tarball-qemuarm.testdata.json
> obmc-phosphor-image-qemuarm-20190119120630.qemuboot.conf
> obmc-phosphor-image-qemuarm-20190119120630.rootfs.ext4
> obmc-phosphor-image-qemuarm-20190119120630.rootfs.manifest
> obmc-phosphor-image-qemuarm-20190119120630.rootfs.tar.bz2
> obmc-phosphor-image-qemuarm-20190119120630.testdata.json
> obmc-phosphor-image-qemuarm.ext4
> obmc-phosphor-image-qemuarm.manifest
> obmc-phosphor-image-qemuarm.qemuboot.conf
> obmc-phosphor-image-qemuarm.tar.bz2
> obmc-phosphor-image-qemuarm.testdata.json
>
>
> Brenden Lai
> SR. BMC Design Engineer
> E&I, Jabil Design Services
>
>

^ permalink raw reply	[flat|nested] 3+ messages in thread
* RE: couple OpenBMC image build and update questions
  2019-01-22 13:29 ` Andrew Geissler
@ 2019-01-23  7:05   ` Brenden Lai
  0 siblings, 0 replies; 3+ messages in thread
From: Brenden Lai @ 2019-01-23  7:05 UTC (permalink / raw)
  To: Andrew Geissler; +Cc: openbmc



> -----Original Message-----
> From: Andrew Geissler <geissonator@gmail.com>
> Sent: Tuesday, January 22, 2019 9:30 PM
> To: Brenden Lai <Brenden_Lai@jabil.com>
> Cc: openbmc@lists.ozlabs.org
> Subject: Re: couple OpenBMC image build and update questions
> 
> On Mon, Jan 21, 2019 at 1:05 AM Brenden Lai <Brenden_Lai@jabil.com>
> wrote:
> >
> > Hi all ,
> >
> >                I have done my first OpenBMC build with ver 2.6 , it do take a long
> time .
> >                Here is my questions .
> >
> > Attach screenshot , Which one is the BMC FW image  after building?
> 
> I haven't built the default qemuarm image in a long time. I believe
> obmc-phosphor-image-qemuarm.ext4 is the FW image.
The QEMU hang after installing image , see below. 

brenden@brenden-VirtualBox:~/openbmc$ ./qemu-system-arm -m 256 -M romulus-bmc -nographic -drive file=~/OCP/openbmc/build/tmp/deploy/images/qemuarm/obmc-phosphor-image-qemuarm-20190119120630.rootfs.ext4,format=raw,if=mtd -net nic -net user,hostfwd=:127.0.0.1:2222-:22,hostfwd=:127.0.0.1:2443-:443,hostname=qemu
qemu-system-arm: Aspeed iBT has no chardev backend

Are there any checkpoint to clarify this issue ?
> 
> > Does the image for both QEMU and real machine ?
> 
> I believe this default image would only support QEMU.
> 
> > How to update it by programming tool like SF600?
> 
> Yes, we use the dediprog tool internally to flash fresh chips.
If I have 2 SPI flash for redundant purpose , 
How do linux kernel know where  to boot from ?
Are there any configuration file described the offset of uboot , kernal ,filesystem in SPI flash  

> 
> > Does it support online update such as AMI YAFU flash ?
> 
> Not familiar with this but once you get OpenBMC on a systems, it does
> provide interfaces to update the firmware via a network connection.
> 
> The system we use for our CI work is Romulus. This system is supported in
> QEMU and on real hardware if you'd like to give it a shot.
> 
> https://github.com/openbmc/openbmc/blob/master/README.md#3-target-
> your-hardware
> talks about setting up your TEMPLATECONF for a system and
> https://github.com/openbmc/docs/blob/master/development/dev-
> environment.md#download-and-start-qemu-session
> has some pointers on starting your QEMU session. You'd of course need a
> Romulus system to flash on real hardware but hopefully it would help you
> get comfortable with building the image and testing in QEMU.
> 
> OpenBMC images are very specific to the hardware so before flashing on
> your system  you'd need to ensure you've got all of the different config
> options setup.
> https://github.com/openbmc/docs/blob/master/development/add-new-
> system.md
> is a reference for how to add a new system.
> 
> >
> >
> > Here is the output of my  build
> > brenden@brenden-
> VirtualBox:~/OCP/openbmc/build/tmp/deploy/images/qemua
> > rm$ ls obmc*
> > obmc-phosphor-debug-tarball-qemuarm-20190119120630.qemuboot.conf
> > obmc-phosphor-debug-tarball-qemuarm-20190119120630.rootfs.manifest
> > obmc-phosphor-debug-tarball-qemuarm-20190119120630.rootfs.tar.xz
> > obmc-phosphor-debug-tarball-qemuarm-20190119120630.testdata.json
> > obmc-phosphor-debug-tarball-qemuarm.manifest
> > obmc-phosphor-debug-tarball-qemuarm.qemuboot.conf
> > obmc-phosphor-debug-tarball-qemuarm.tar.xz
> > obmc-phosphor-debug-tarball-qemuarm.testdata.json
> > obmc-phosphor-image-qemuarm-20190119120630.qemuboot.conf
> > obmc-phosphor-image-qemuarm-20190119120630.rootfs.ext4
> > obmc-phosphor-image-qemuarm-20190119120630.rootfs.manifest
> > obmc-phosphor-image-qemuarm-20190119120630.rootfs.tar.bz2
> > obmc-phosphor-image-qemuarm-20190119120630.testdata.json
> > obmc-phosphor-image-qemuarm.ext4
> > obmc-phosphor-image-qemuarm.manifest
> > obmc-phosphor-image-qemuarm.qemuboot.conf
> > obmc-phosphor-image-qemuarm.tar.bz2
> > obmc-phosphor-image-qemuarm.testdata.json
> >
> >
> > Brenden Lai
> > SR. BMC Design Engineer
> > E&I, Jabil Design Services
> >
> >

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-01-23  7:05 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-21  7:05 couple OpenBMC image build and update questions Brenden Lai
2019-01-22 13:29 ` Andrew Geissler
2019-01-23  7:05   ` Brenden Lai

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.