Flip the overlay logic.

The default dts will be 2GB memory configuration, and if EVT1 is
detected, the EVT1 config will be applied. This also helps with the dts
overlay failure case as the default would support EVT2+ memory config
moving forward.

Tested: Flash and boot both EVT1 and EVT2 boards. Chech the memory

Change-Id: Ib9a400390b19f6cd6c3ce73282386c726ffe8b3d
diff --git a/boot.txt b/boot.txt
index cf61a02..c98214a 100644
--- a/boot.txt
+++ b/boot.txt
@@ -13,12 +13,12 @@
 # Load overlays to arbitrary address beyond fdt location (will apply them later).
 setexpr fdtovaddr ${fdt_addr} + F0000
-# Overlay memory config for EVT2
-if test "${evt2_board}" -eq 1; then
-	if ext2load mmc ${mmcdev}:${boot_partition} ${fdtovaddr} coral-evt2.dtbo && fdt apply ${fdtovaddr}; then
-		echo Loaded EVT2 config
+# Overlay memory config for EVT1
+if test "${evt2_board}" -eq 0; then
+	if ext2load mmc ${mmcdev}:${boot_partition} ${fdtovaddr} coral-evt1.dtbo && fdt apply ${fdtovaddr}; then
+		echo Loaded EVT1 config
-		echo Overlay EVT2 config failed
+		echo Overlay EVT1 config failed
 		ext2load mmc ${mmcdev}:${boot_partition} ${fdt_addr} ${fdt_file}