<div dir="ltr"><div>Mr. Jeffery,</div><div> Thank you for your insights and comments.</div><div>1) RE: git clone - well, for whatever reason, this worked today. . . (internet gremlins, github trolls, who knows).</div><div>2) RE: building: I reviewed some documentation again, and pieced together that I had built the wrong image (again). So, as I now have a "fresh" clone, I set about with some different steps towards building an ast2500-evb image. <br></div><div> - I verified that the qemu-system-arm, listed in the documentation provided by Mr. Geissler, is indeed a 4.1.0 version, and it does contain the necessary machine support:</div><div><span style="font-family:monospace">sbeckwit@ubuntu:/usr/bin$ qemu-system-arm -machine help | grep ast<br>ast2500-evb Aspeed AST2500 EVB (ARM1176)<br>ast2600-evb Aspeed AST2600 EVB (Cortex A7)<br></span></div><div>3) after 168 minutes, I the "baking" was done and checking the deploy/images directory, I found the ast2500-evb files: kernel, u-boot, initramfs, mtd image, etc. Most Excellent!</div><div>4) I then, as you suggested, reviewed the documentation (again) and crafted some minimal parameters to running QEMU. And Behold:</div><div><span style="font-family:monospace">Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 0.1.0 evb-ast2500 ttyS4<br><br>evb-ast2500 login: root<br>Password: <br>root@evb-ast2500:~# uname -a<br>Linux evb-ast2500 5.2.0-c01e98d #1 Wed Sep 25 16:54:08 UTC 2019 armv6l GNU/Linux</span></div><div> - I got in to this booted image under QEMU. (not the blinking light we Embedded FW Engineers like to see on our boards when something works, but this will do just fine).</div><div>5) RE: runqemu script - My Python is rusty, but I'll take a gander at it, since I will have some time here, as we are only working on an initial PoC for this. The next attempt will be to try and see if we can boot this on our reference platform (AST2500 based). <br></div><div> - I maybe getting back to you should I have an update on this script.</div><div><br></div><div>Thank you for your assistance and support.</div><div><br></div><div>Regards,</div><div>Stephen Beckwith</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 25, 2019 at 11:52 AM Andrew Jeffery <<a href="mailto:andrew@aj.id.au">andrew@aj.id.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
On Wed, 25 Sep 2019, at 22:52, Stephen Beckwith wrote:<br>
> 2) re: qemu machine - the qemu machine being used is the one that was <br>
> built as part fo the opembmc project. If this qemu machine won’t work, <br>
> then why is it built as part of the project?<br>
<br>
Because no-one has looked at removing it from the poky build<br>
configurations that openbmc inherits. Regardless, removing it isn't the<br>
right way to deal with the issue.<br>
<br>
> Why are there 13 copies of <br>
> this machine scattered through out the filesystem, consuming ~ 564MB of <br>
> space, if it’s the “wrong” machine? <br>
<br>
This is a question best asked of the upstream yocto project.<br>
<br>
> - so where do I obtain the “BMC-specific machine” ?<br>
<br>
By running `qemu-system-arm -M ? | grep bmc`. It will give you output like:<br>
<br>
$ qemu-system-arm -M ? | grep bmc<br>
palmetto-bmc OpenPOWER Palmetto BMC (ARM926EJ-S)<br>
rainier-bmc Aspeed AST2600 EVB (Cortex A7)<br>
romulus-bmc OpenPOWER Romulus BMC (ARM1176)<br>
swift-bmc OpenPOWER Swift BMC (ARM1176)<br>
tacoma-bmc Aspeed AST2600 EVB (Cortex A7)<br>
witherspoon-bmc OpenPOWER Witherspoon BMC (ARM1176)<br>
<br>
You need to pick an appropriate one to run your image:<br>
<br>
ARM926EJ-S: AST2400<br>
ARM1176: AST2500<br>
Cortex A7: AST2600<br>
<br>
The remaining differences between listed machines are what peripherals<br>
are attached to e.g. the I2C buses.<br>
<br>
> <br>
> 3) if OpenBMC doesn’t properly integrate into the rumqemu scripts, <br>
> then: A) why is this script here?<br>
<br>
It is provided by the upstream yocto project.<br>
<br>
> B) why hasn’t anyone taken the <br>
> time/effort to correct the script so that it will integrate properly <br>
> with OpenBMC? <br>
<br>
Because no-one sees it as something worth spending time on? I've<br>
wanted to get it done since writing the initial QEMU support for the<br>
ASPEED chips, but it lives at the bottom of my todo list. I've asked<br>
other people asking questions like you to do it as well, but it hasn't<br>
been done yet by them either, so I can only assume it lives at the<br>
bottom of their todo lists too. I'd love it if you contributed a patch<br>
to fix it :)<br>
<br>
Andrew<br>
</blockquote></div>