Attention is currently required from: Vladimir Serbinenko.
Arthur Heymans has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81506?usp=email )
Change subject: Disable NULL breakpoint at the end of bootblock ......................................................................
Patch Set 3:
(1 comment)
Commit Message:
https://review.coreboot.org/c/coreboot/+/81506/comment/7b6e25c7_ed55a645 : PS3, Line 9: If stage is older then it will not be able to correctly disable it when : needed. New stages will reenable breakpoint early
It happens in my case. With standard ChromeOS the RW parts are updated and signed by Google and entire OS update fails if the RW part can't be updated. RO is never checked or updated. So after unlock we can replace it with our code as long as it's compatible with the old ABI used by RW part
That's a use case that's generally not supported upstream: other environment things like linker scripts for CAR usage are not guaranteed to match. Why not set DEBUG_NULL_DEREF_BREAKPOINTS to 'n' when building that RO?