Exposing POST codes
Timothy Pearson
tpearson at raptorengineering.com
Sat Apr 14 10:47:43 AEST 2018
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sounds like multiple folks have been working on similar code. Here's ours:
https://git.raptorcs.com/git/talos-skeleton/log/pyiplobserver?h=04-13-2018
The current version just parses the hostboot codes from the serial
console, it used to use pdbg but over time it was found that using pdbg,
even with the BMC kernel driver, destabilizes the IPL process at key
points. It does however also include state monitoring via BMC mailbox
bits for skiboot and skiroot, allowing the BMC to know when the full IPL
process is complete.
I like the approach of hostboot sending data over LPC, and we're willing
to rework the observer daemon to use that approach. Is there any way to
send status codes over LPC from the SBE?
Thanks!
On 02/28/2018 12:56 PM, Patrick Venture wrote:
> I talked to Nancy and I think it's time to revisit previous conversations
> about POST codes. We have a simple daemon that exposes the information
> over Dbus associated with https://gerrit.openbmc-project.xyz/#/c/5006
>
> If there's interest, I can stage it against skeleton for review and comment.
>
> We have a patch to the kernel character device for the aspeed-lpc-snoop
> that is required and enables reading the post codes.
>
> Patrick
- --
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJa0U+sAAoJEK+E3vEXDOFbOM4H/3WJK9SbA6ly4Q/CioC9Yz9L
dzwsKSClKkK1pHru86wPYHadAmatn/ksA5dl4pEzQlfh5RKGBAaoFdVdVG/BdbVA
upKn9WBudQyLCHFWtD3xg4vzX3cCsi3hFgvgGIKkdrxj4uMv+56Fp5Fwh2eWuun8
ITadBt1LVdZlZT7z56zi2gt0eC4QSaAIBjBXq4KYIhXdc/xX9suw7pLKHAfxpb3v
ygSlE+SGeD1jZQfA5y2CxhOYyl+ac3AmCHXlDe70WQgbyPHU6aohuJaoh1+AtJeo
ys2mULcL9Sz2y8YTBXbEQ2QVMCJHw2BpKBmy6gxuDKChUNndqNJBselSVu7jrXU=
=OWnM
-----END PGP SIGNATURE-----
More information about the openbmc
mailing list