I built an AP firmware image for bob from the firmware-gru-8785.B branch. The image boots, however on reboot the system stalls without any output on the serial console.
This build was done with cros_workon for the coreboot repository. Initially my tree had a local change in coreboot, which I reverted after running into the stalled reboot, but the issue also occurs without the change. Interestingly an image built without cros_workon does not have the reboot issue. My expectation was that a cros_workon image with no local changes would be functionally equivalent to a non-cros_workon image.
Images from both builds are attached.
Steps taken:
repo init -u https://chrome-internal.googlesource.com/chromeos/manifest-internal.git --repo-url='https://chromium.googlesource.com/external/repo.git' -b firmware-gru-8785.B
repo sync
./setup_board --board=bob
cros_workon-bob start coreboot
cros_workon-bob list
=> sys-boot/coreboot
# in src/third_party/coreboot
git log --oneline
=> 8c4eeee UPSTREAM: cr50: process uninitialized values gracefully
(coincides with the hash in the coreboot ebuild)
emerge-bob chromeos-ec depthcharge coreboot libpayload chromeos-bootimage
flash /build/bob/firmware/image.dev.bin
# no cros_workon
cros_workon-bob stop coreboot
emerge-bob chromeos-ec depthcharge coreboot libpayload chromeos-bootimage
flash /build/bob/firmware/image.dev.bin
|
Deleted:
image.dev.bin.ko
8.0 MB
|
|
Deleted:
image.dev.bin.ok
8.0 MB
|
Comment 1 by diand...@chromium.org
, Oct 25 2017