Update the blob positions in the RW device trees as well.
The positions of the sub-blobs in a particular region of the FMAP are
recorded in the device tree after they've been appended together and their
relative positions are established. This step was being performed for the RO
device tree, but not the RWs. When booting into RW firmware, the EC position
and size weren't found and the system would reboot into recovery mode.
TEST=Built and booted a U-Boot based firmware on Link. Before this change,
when RO normal mode was disabled, the RW device tree wouldn't have info on the
positon of the EC RW blob, VbExEcGetExpectedRW would return an error, and the
system would reboot into recovery mode. After this change, the info was there
and the system would boot successfully into ChromeOS.
Signed-off-by: Gabe Black <email@example.com>
Commit-Ready: Gabe Black <firstname.lastname@example.org>
Reviewed-by: Gabe Black <email@example.com>
Tested-by: Gabe Black <firstname.lastname@example.org>
1 file changed