New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 605638 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit 26 days ago
Closed: Sep 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

chromeos-bootimage is breaking gale-release: Selected image region is not a valid CBFS

Project Member Reported by denniskempin@chromium.org, Apr 21 2016

Issue description

Hi dnojiri! 

I just noticed a build failure on gale-release. The past two builds have been failing with in build_packages while building chromeos-bootimage with the following log:

chromeos-bootimage-0.0.2-r990: Creating GBB...
chromeos-bootimage-0.0.2-r990:                
chromeos-bootimage-0.0.2-r990: Command failed: /usr/bin/cbfstool /build/gale/tmp/portage/sys-boot/chromeos-bootimage-0.0.2-r990/work/chromeos-bootimage-0.0.2/out.ro/cb_with_fmap add-payload -f /build/gale/firmware/depthcharge/depthcharge.elf -n fallback/payload -c lzma -r FW_MAIN_A
chromeos-bootimage-0.0.2-r990: Performing operation on 'FW_MAIN_A' region...
chromeos-bootimage-0.0.2-r990: E: Selected image region is not a valid CBFS.
chromeos-bootimage-0.0.2-r990: E: Failed while operating on 'FW_MAIN_A' region!
chromeos-bootimage-0.0.2-r990: E: The image will be left unmodified.
chromeos-bootimage-0.0.2-r990: 
chromeos-bootimage-0.0.2-r990: 
chromeos-bootimage-0.0.2-r990:                
chromeos-bootimage-0.0.2-r990:  * ERROR: sys-boot/chromeos-bootimage-0.0.2-r990::chromiumos failed (compile phase):
chromeos-bootimage-0.0.2-r990:  *   failed to build production image.

I saw you were looking into a similar issue before. Could you have a look? If this is unrelated to what you're doing, please assign the bug to someone who you think would know what's going on.

Thanks a lot! :)
 
Owner: pgeorgi@chromium.org
I ran into a similar issue on another board, where coreboot's chromeos.fmd and depthcharge's fmap.dts diverged, but I didn't see that on gale (but maybe I'm on the wrong branch?).

In any case, could you try, in coreboot's source tree: util/scripts/dts-to-fmd.sh ../../platform/depthcharge/board/gale/fmap.dts > src/mainboard/google/gale/chromeos.fmd

Then please check if there's any difference in chromeos.fmd. If so, rebuild coreboot and chromeos-bootimage (at least coreboot needs to be cros_workon'd) and see if that fixes things.
Status: Verified (was: Assigned)
Builds are working again for a long time, so closing.

Sign in to add a comment