Fix vbexport_test display

It turns out that running 'vbexport_test display' on coreboot
platforms fails to display bitmap images, sometimes reporting memory
corruption and rebooting the system.

The problem was twofold:

  - the gbb pointer is not properly initialized (as it is supposed to
    when CONFIG_HARDWARE_MAPPED_SPI is defined).

  - the bitmap images block includes an element which in fact is not a
    bitmap. When scanning the block, the test tried displaying all
    elements, generating an error when this one-off element is
    encountered.

This change fixes both issues.

BUG=chromium-os:26586
TEST=manual
  . build a new chromeos-bootimage
  . reboot the system stopping it in u-boot console dialogue
  . run `vbexport_test display' command from the console

 The test was failing before this change, it is passing now.

Change-Id: Iee9491d150b9ce5513f7446ab4df806d23e6d4d8
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/16206
Reviewed-by: Bill Richardson <wfrichar@chromium.org>

0 files changed, 0 insertions, 0 deletions