From 0641c5405cf66979307fb20d19f94bbd8424d341 Mon Sep 17 00:00:00 2001 From: oliviermartin Date: Thu, 22 Sep 2011 23:25:39 +0000 Subject: BeagleBoardPkg: The FDF file does not reserve any more the area for the OMAP35xxx header It is the tool BeagleBoardPkg/Tools/generate_image which will add a CH header to a the BeagleBoard FD file. The build macro EDK2_SECOND_STAGE_BOOTOLADER is not required any more. git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@12433 6f19259b-4bc3-4df7-8a09-765794883524 --- BeagleBoardPkg/build.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'BeagleBoardPkg/build.sh') diff --git a/BeagleBoardPkg/build.sh b/BeagleBoardPkg/build.sh index 6f48ebd78f..3ce923e9ee 100755 --- a/BeagleBoardPkg/build.sh +++ b/BeagleBoardPkg/build.sh @@ -132,12 +132,12 @@ rm -f $FLASH_BOOT # # Ram starts at 0x80000000 -# OMAP 3530 TRM defines 0x80008208 as the entry point +# OMAP 3530 TRM defines 0x80008000 as the entry point # The reset vector is caught by the mask ROM in the OMAP 3530 so that is why this entry # point looks so strange. # OMAP 3430 TRM section 26.4.8 has Image header information. (missing in OMAP 3530 TRM) # -$GENERATE_IMAGE -D $WORKSPACE/BeagleBoardPkg/ConfigurationHeader.dat -E 0x80008208 -I $BUILD_ROOT/FV/BEAGLEBOARD_EFI.fd -O $FLASH_BOOT +$GENERATE_IMAGE -D $WORKSPACE/BeagleBoardPkg/ConfigurationHeader.dat -E 0x80008000 -I $BUILD_ROOT/FV/BEAGLEBOARD_EFI.fd -O $FLASH_BOOT echo Creating debugger scripts process_debug_scripts $WORKSPACE/BeagleBoardPkg/Debugger_scripts -- cgit v1.2.3