Account for 5422 based devices

USB download requires an entry for each possible compatibility string
to figure out addresses to use.

Also, we don't want to use the 5250 case as a default, it is much
better to report error if there is no valid compatibility string.

BRANCH=ToT
BUG=chrome-os-partner:25112
TEST=none
  . cros_write_firmware works for both pit and pi USB downloads

Change-Id: Iae38c96c9802f69a1cd20c3847ddf3bcdaeff768
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/182933
diff --git a/host/lib/write_firmware.py b/host/lib/write_firmware.py
index 4bc5d2b..9b04093 100644
--- a/host/lib/write_firmware.py
+++ b/host/lib/write_firmware.py
@@ -24,6 +24,11 @@
         'bl2': 0x02024400,
         'u-boot': 0x23e00000,
         },
+    'samsung,exynos5422': {
+        'bl1': 0x02022400,
+        'bl2': 0x02024400,
+        'u-boot': 0x23e00000,
+        },
   }
 
 
@@ -603,10 +608,7 @@
       if addresses:
         break
     else:
-      # TODO(sjg@chromium.org): Remove this when upstream U-Boot has the
-      # 'samsung,exynos5250' compatible string.
-      addresses = exynos_addresses.get('samsung,exynos5250')
-      self._out.Warning('No exynos compatible string, assuming Exynos 5250')
+      raise CmdError('No exynos compatible string found')
 
     if not addresses:
       raise CmdError("Unable to determine USB download addresses, compatible" +