mkamsboot: fix for newer fuzev2
These models are restricted to OF >= v02.3.31, probably because of a
hardware change
The OF checks a version string located between 0x0 and 0x200 in the
firmware block, so let's keep this part unmodified
We put our dualboot code at 0x200, and insert a branch + vectors at 0x0
That way our patched file will present the OF version to the fuzev2 OF
patching it, and we only waste 512 bytes on other models
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@27441 a1c6a512-1295-4272-9138-f99709370657
diff --git a/rbutil/mkamsboot/dualboot.h b/rbutil/mkamsboot/dualboot.h
index c9f375b..76d4641 100644
--- a/rbutil/mkamsboot/dualboot.h
+++ b/rbutil/mkamsboot/dualboot.h
@@ -1,11 +1,11 @@
/* Generated by bin2c */
extern unsigned char nrv2e_d8[168];
-extern unsigned char dualboot_clip[256];
-extern unsigned char dualboot_e200v2[236];
-extern unsigned char dualboot_c200v2[432];
-extern unsigned char dualboot_m200v4[212];
-extern unsigned char dualboot_fuze[236];
-extern unsigned char dualboot_clipv2[280];
-extern unsigned char dualboot_clipplus[372];
-extern unsigned char dualboot_fuzev2[364];
+extern unsigned char dualboot_clip[224];
+extern unsigned char dualboot_e200v2[204];
+extern unsigned char dualboot_c200v2[400];
+extern unsigned char dualboot_m200v4[180];
+extern unsigned char dualboot_fuze[204];
+extern unsigned char dualboot_clipv2[248];
+extern unsigned char dualboot_clipplus[340];
+extern unsigned char dualboot_fuzev2[332];