From: Michael Richardson <mcr@sandelman.ca>
To: Samuel Herts <sdherts@gmail.com>, openbmc@lists.ozlabs.org
Subject: Re: OpenBMC Starting Point
Date: Sat, 01 Feb 2020 23:44:59 +0100 [thread overview]
Message-ID: <24610.1580597099@dooku> (raw)
In-Reply-To: <7601.1580558972@dooku>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
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? Also, is there a method to read from the computer's BIOS
> chip from this modified state manager?
I'm aware of only one hardware platform that explicitely supports openbmc,
and it was rather expensive. Apparently it can run on quite a few other
boards, and I'd like to try to get a list of things I might be able to get on
ebay... I don't need something new to experiment with... old and well
documented seems better to me.
I don't think you'd ever install the *SDK* on the target system.
You compile it with the build system on an ubuntu server or equivalent
container, and then install the resulting image as the BMC image.
That might require a JTAG load for some systems, and then OTA afterwards.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next parent reply other threads:[~2020-02-01 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7601.1580558972@dooku>
2020-02-01 22:44 ` Michael Richardson [this message]
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
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
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=24610.1580597099@dooku \
--to=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.