Google broke reading from the CBFS (coreboot filesystem) in flash on the stock firmware for Brya-based boards, so I had to work around it. Now, it seems they are fixing the issue in some boards, but not all. BANSHEE for example still works. So it seems that I’ll have to keep track for which Brya boards use the “broken” stock firmware and which do not.
I just pushed an RWL update which adds support for the “fixed” Brya boards, but they need to be added manually. Right now OMNIGUL is the only device in that category.
Please test and let me know if it solves the issue.
EDIT:
and just like that, BANSHEE got a firmware update which broke RWL as well. I’ve added it to the new “fixed” group and can confirm that RWL/edk2 works again, so OMNIGUL should be good as well
Thank you @MrChromebox, amazingly fast response and impressed at how you worked it out!
I tested it and I am pleased to say I get into the coreboot screen now.
Does this mean that if Google were to push an update on their side in the future and fixed this, would RW_L break again and require a further intervention on the script?
edk2 screen
what is “this”? As of right now, BANSHEE and OMNIGUL are “fixed” / work just like every other platform. I assume the other Brya-based boards will all be fixed in time as well, in which case I just need to change which RWL file they use in the script.