cd edk2\r
svn co https://edk2-fatdriver2.svn.sourceforge.net/svnroot/edk2-fatdriver2/trunk/FatPkg FatPkg --username guest\r
\r
-3. Apply BaseTools patches (BaseTools-Pending-Patches.patch combines all the currently pending BaseTools patches)\r
-patch -p1 < ArmPlatformPkg/Documentation/patches/BaseTools-Pending-Patches.patch\r
-\r
-4. Set up the environment. And build the EDK2\92s tools\r
+3. Set up the environment. And build the EDK2\92s tools\r
export EDK_TOOLS_PATH=`pwd`/BaseTools\r
-. edksetup.sh `pwd`/BaseTools/\r
+. edksetup.sh\r
make -C $EDK_TOOLS_PATH\r
\r
-5. Ensure the ARMGCC toolchain is in your PATH environment variable or defined by the ARMGCC_TOOLS_PATH environment variable. Example:\r
+4. Ensure the ARMGCC toolchain is in your PATH environment variable or defined by the ARMGCC_TOOLS_PATH environment variable. Example:\r
export ARMGCC_TOOLS_PATH=/opt/toolchains/arm-2010.09-arm-none-eabi-i686-pc-linux-gnu/bin/\r
\r
-6. Build the ARM Versatile Express UEFI Firmware\r
+5. Build the ARM Versatile Express UEFI Firmware\r
build -a ARM -p ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-CTA9x4.dsc -t ARMGCC\r
\r
-7. Edit the ARM Versatile Express configuration file config.txt to declare the location of the UEFI firmware in NOR Flash\r
+6. Edit the ARM Versatile Express configuration file config.txt to declare the location of the UEFI firmware in NOR Flash\r
TOTALIMAGES: 5 ;Number of Images (Max : 32)\r
NOR0UPDATE: AUTO ;Image Update:NONE/AUTO/FORCE\r
NOR0ADDRESS: BOOT ;Image Flash Address\r
NOR4NAME: BOOTSCRIPT ;Image Name\r
NOR4FILE: \SOFTWARE\bootscr.txt ;Image File Name\r
\r
-8. To select second NOR Flash as a booting device, replace in the ARM Versatile Express file \SITE1\HBI0191B\board.txt:\r
+7. To select second NOR Flash as a booting device, replace in the ARM Versatile Express file \SITE1\HBI0191B\board.txt:\r
SCC: 0x004 0x00001F09\r
By:\r
SCC: 0x004 0x10001F09\r
\r
-9. Copy Build/ArmVExpress-CTA9x4/DEBUG_ARMGCC/FV/SEC_ARMVEXPRESS_EFI.fd to the ARM Versatile Express mass storage (available when the board is connected through USB to your host machine) under the folder SOTWARE and name sec_uefi.bin. Example for cygwin:\r
+8. Copy Build/ArmVExpress-CTA9x4/DEBUG_ARMGCC/FV/SEC_ARMVEXPRESS_EFI.fd to the ARM Versatile Express mass storage (available when the board is connected through USB to your host machine) under the folder SOTWARE and name sec_uefi.bin. Example for cygwin:\r
cp Build/ArmVExpress-CTA9x4/DEBUG_ARMGCC/FV/SEC_ARMVEXPRESS_EFI.fd /cygdrive/e/SOFTWARE/sec_uefi.bin\r
\r
-10. Start the ARM Versatile Express board. You should read \93Waiting for firmware at 0x80000000 ...\94 on the serial port. \r
+9. Start the ARM Versatile Express board. You should read \93Waiting for firmware at 0x80000000 ...\94 on the serial port. \r
\r
-11. Copy ARMVEXPRESS_EFI.fd at 0x80000000 with RealView Debugger\r
+10. Copy ARMVEXPRESS_EFI.fd at 0x80000000 with RealView Debugger\r
readfile,raw,nowarn "[EDK2_PATH]\Build\ArmVExpress-CTA9x4\DEBUG_ARMGCC\FV\ARMVEXPRESS_EFI.fd"=0x80000000\r
\r
-12. Resume the execution from RealView Debugger\r
+11. Resume the execution from RealView Debugger\r
\r
For all subsequent times\r
************************\r