Firmware Upstreaming

From RCS Wiki
Revision as of 15:14, 27 December 2019 by TimothyPearson (talk | contribs) (Tone down my earlier comments a bit :))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This page should cover firmware upstreaming for Talos and other RaptorCS systems. Because it would be very useful to be able to build new firmware directly from upstream sources.

Host firmware

working with the 04-16-2019 branch, which is in the v2 firmware


same for Blackbird and Talos =


same for Blackbird and Talos =

-> no changes needed


same for Blackbird and Talos =, resp., but they carry the same patches

  • cap voltage offset when biased
  • Add detailed ISTEP output option to hostboot
  • Don't try to add proprietary CAPP microcode image to PNOR (could be skipped in upstream)


same for Blackbird and Talos =

  • remove prebuilt GPU1 binary - not required for upstream
  • Fix build failure on GCC8


Tracked in patchwork:


Other things to consider from Raptor's branch:

  • skiroot kernel config changes
  • adds openpower/scripts/talos-extra-cleanup script - could be generally useful
  • adds pnv_lpc tool - possibly could be omitted for Talos if skiboot uses LPC observer same as Blackbird
    • From a technical perspective, sending the IPL complete code from skiboot is a UX violation. That particular code fires off a number of user visible events including the IPL complete beep, and it must only be sent once petitboot's userspace is online (i.e. the chance of something firmware-related having gone wrong is vanishingly small). Sending it from skiboot not only adds significant delay from the purposefully attention-getting beep to anything showing up on the screen (the boot delay with no graphical output is already a major problem on POWER), but it also allows a lot of things to potentially go wrong after we've just told the user "the system passed all of its boot checks and is online". I'm working on a lockdown-compliant LPC driver module to be upstreamed, but won't have it before Jan. 2020. (Yes, I know none of this was documented; once we have an upstreamed version of this I'll go back and see about writing proper documentation). TimothyPearson (talk)


OpenBMC firmware

OpenBMC <-> host firmware communication

works by writing bytes over LPC to ports 0x80, 0x81, 0x82

  • SBE sends ISTEPs to ports 0x81, 0x82
  • hostboot sends ISTEPs to ports 0x81, 0x82
  • skiboot sends single byte describing module and status to port 0x80
  • skiroot signals the user-space is ready by writing 0xfe, 0xfe to ports 0x81, 0x82