All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Geissler <geissonator@gmail.com>
To: Samuel Herts <sdherts@gmail.com>
Cc: Michael Richardson <mcr@sandelman.ca>, openbmc@lists.ozlabs.org
Subject: Re: OpenBMC Starting Point
Date: Fri, 31 Jan 2020 15:29:27 -0600	[thread overview]
Message-ID: <4AD6BC0E-9BB2-4D2B-BB15-3B52FFB78247@gmail.com> (raw)
In-Reply-To: <CA+k9xxZXUjn=n1SCnHb28_iTN3cEG0yv_QB+Qh7DgcUNdXD4LA@mail.gmail.com>

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



> On Jan 31, 2020, at 11:15 AM, Samuel Herts <sdherts@gmail.com> wrote:
> 
> We got the Hello World to work perfectly, thank you for the assistance! How would we now go about doing the exact same thing, but hardware implemented? By that, I mean actually running the phosphor state manager modified module on the physical BMC chip? How do we install the OpenBMC sdk?

You would want to use an SDK that you’ve built for your BMC hardware.
bitbake -c populate_sdk obmc-phosphor-image

You’d then use that SDK the same way you used it for Hello World
and then you would scp the compiled binary to your BMC hardware.

If your bmc hardware is similar to the Romulus hardware then you
could just scp the binary you generated for Hello World over
to your hardware.

> Also, is there a method to read from the computer's BIOS chip from this modified state manager?

The BIOS is pretty dependent on the system. Something like this should
list all firmware images on your system, you could then introspect them
to figure out your BIOS and the appropriate D-Bus calls to read them
from an application:

busctl call xyz.openbmc_project.ObjectMapper /xyz/openbmc_project/object_mapper xyz.openbmc_project.ObjectMapper GetSubTreePaths sias "/xyz/openbmc_project/software" 0 1 xyz.openbmc_project.Software.Version


Andrew

> 
> 
> On Tue, Jan 21, 2020 at 11:52 AM Andrew Geissler <geissonator@gmail.com <mailto:geissonator@gmail.com>> wrote:
> 
> 
>> On Jan 20, 2020, at 11:03 AM, Samuel Herts <sdherts@gmail.com <mailto:sdherts@gmail.com>> wrote:
>> 
>> Thank you!
>> I have a supermicro X9 with ast2400 BMC chip. How would we go about installing it? openBMC onto it? We currently have a fresh install of Ubuntu LTS on it, and nothing else.
> 
> The only AST2400 config I’m familiar with is our Palmetto.
> You could start with that machine and tweak it for yours.
> https://github.com/openbmc/openbmc/blob/master/meta-ibm/meta-palmetto/conf/machine/palmetto.conf <https://github.com/openbmc/openbmc/blob/master/meta-ibm/meta-palmetto/conf/machine/palmetto.conf>
> 
> 
>> In terms of the development virtual machine. I keep running into an issue when trying to wget the sdk. 
>> Specifically, this line: wget https://openpower.xyz/job/openbmc-build-sdk/distro=ubuntu,target=romulus/lastSuccessfulBuild/artifact/deploy/sdk/oecore-x86_64-arm1176jzs-toolchain-nodistro.0.sh <https://openpower.xyz/job/openbmc-build-sdk/distro=ubuntu,target=romulus/lastSuccessfulBuild/artifact/deploy/sdk/oecore-x86_64-arm1176jzs-toolchain-nodistro.0.sh> After running that inside the romulus emulator, it runs out of space and won't complete the download. Does this mean I need to either increase the storage for the romulus, or am I simply installing it in the wrong place, and instead need to wget that into the regular VM?
> 
> The SDK is not meant to be downloaded to the actual OpenBMC
> system. I’t meant to be downloaded to your development system.
> You can then use it to build OpenBMC software that you then copy
> over to your OpenBMC and run.
> 
>> Apologies for all the questions, I am doing as much research as I can, and this mailing list seems to be the largest wealth of knowledge I have available.
>> 
>> --Sam
>> 
>> On Mon, Jan 20, 2020 at 1:57 AM Michael Richardson <mcr@sandelman.ca <mailto:mcr@sandelman.ca>> wrote:
>> 
>> Samuel Herts <sdherts@gmail.com <mailto:sdherts@gmail.com>> wrote:
>>     > I am currently working on getting a working OpenBMC test environment
>>     > up and running. I am using VirtualBox and the github Development
>>     > Environment tutorial. I had a couple questions regarding how to make
>>     > our own modules. Would it be possible to upload files to the bmc on
>>     > the virtual server?
>> 
>> You can do that.
>> The disk is rather small by default.
>> If you are using VirtualBox, you may be able to use the vboxfs file system to
>> mount the host. That might require adding modules to the kernel.
>> 
>>     > And would I be able to make a script which can read text off of that
>>     > file inside the bmc chip?
>> 
>>     > I have a physical server which I am not using yet, would I be able to
>>     > install openbmc and the scripts and insert the file onto the actual
>>     > bmc chip, and eventually read from that file?
>> 
>> Maybe. What server do you have?
>> 
>> --
>> ]               Never tell me the odds!                 | ipv6 mesh networks [
>> ]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
>> ]     mcr@sandelman.ca <mailto:mcr@sandelman.ca>  http://www.sandelman.ca/ <http://www.sandelman.ca/>        |   ruby on rails    [
>> 
>> 
>> 
>> -- 
>> Sincerely, 
>> Samuel Herts
> 
> 
> 
> -- 
> Sincerely, 
> Samuel Herts


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

  reply	other threads:[~2020-01-31 21:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 17:38 OpenBMC Starting Point Samuel Herts
2020-01-20  6:57 ` Michael Richardson
2020-01-20 17:03   ` Samuel Herts
2020-01-21 15:21     ` Andrew Geissler
2020-01-21 16:52     ` Andrew Geissler
2020-01-31 17:15       ` Samuel Herts
2020-01-31 21:29         ` Andrew Geissler [this message]
2020-02-06 14:16         ` Michael Richardson
2020-02-24 15:40   ` Samuel Herts
2020-02-24 20:22     ` Andrew Geissler
2020-02-24 20:23     ` Andrew Geissler
2020-02-25 15:31       ` krtaylor
     [not found] <7601.1580558972@dooku>
2020-02-01 22:44 ` Michael Richardson

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=4AD6BC0E-9BB2-4D2B-BB15-3B52FFB78247@gmail.com \
    --to=geissonator@gmail.com \
    --cc=mcr@sandelman.ca \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sdherts@gmail.com \
    /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.