couple OpenBMC image build and update questions

[Andrew Geissler]

On Mon, Jan 21, 2019 at 1:05 AM Brenden Lai <Brenden_Lai at 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 at 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
>
>