-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manual override of SBE side #3
Comments
I'd tend to lean more towards a openpower setting that could be used to override the boot side selection vs. something like the CFAM override. Maybe a SBE.interface.yaml with a Settings property out at https://github.com/openbmc/openpower-dbus-interfaces/tree/master/org/open_power/Control/? @spinler ? |
@geissonator I'm with you there, not sure why we chose to hide it behind the boot counter initially. |
The current design using the boot counter was just the default rule from previous POWER systems. Providing an override to that policy makes sense to me (for both production and lab debug) |
@geissonator @amboar as long as something is done along those lines I'd be happy. |
This is exactly the way the current code works. We update the active side in Hostboot and then force a reboot. If the reboot succeeds and we boot up to our SBE update step again then we declare it good and write the same image into the backup side. If we can't boot that far, OpenBMC will eventually flip sides and boot us from the backup side. Hostboot knows we're on the wrong side and won't try to update it. |
@dcrowell77 Ah, that's cool. On another note I've actually figured a way I should be able to boot |
So, I'm beginning work on porting coreboot to power9, specifically the Talos II family of boards.
In part of this, I'll be altering the hostboot bootloader to kickstart the coreboot way of doing things, and as such will need to alter the seeproms.
I had the idea to use the RebootAttempts variable to force it one way or the other, keeping a
'normal' seeprom image on one side and working on the other, so as to have a safe fallback
(the way the talos machines are wired up one can easily read/write one seeprom side via i2c,
and not the other). However, using busctl set-property for it resets it to 3.
So, I had an idea based on the cfam override file; what if we took the code below
openpower-proc-control/procedures/p9/start_host.cpp
Lines 70 to 81 in 16ab00c
and altered it to first check for some override file to determine which seeprom side to boot,
then doing the normal RebootAttempts manner? It would keep current behavior, and allow a
bit of flex when doing sbe work.
Do you think this would be a good option for 'everyone' or should it just be a local hack I use
indev?
The text was updated successfully, but these errors were encountered: