Good day to all.
I am working from commit "Add manual configured gateway address back
after system reset" by Ye Ting.
I've been trying to build a DUET boot floppy for use with both real
hardware and in QEmu. My QEmu command-line looks like this:
qemu-system-x86_64 -fda duet.vfd
For both the real hardware and the QEmu, shortly after boot the screen
displays red text on a black background beginning with:
*** INT 06h Invalid opcode - HALT!! ***
(0000000000000038:0000000000010240)
followed by 64-bit register dumps and whatever other debugging
information is supposed to be there.
I suspect that this is caused by Efildr being too big, since the
document DuetPkg/ReadMe.txt suggests that Efildr must be less than 470
k. Currently my Build/DuetPkgX64/DEBUG_UNIXGCC/FV/Efildr is 483328 bytes.
In that same document, it is suggested to remove drivers from the
DuetPkg/DuetPkg.fdf file. How does one do this? I have #commented out
the INF lines for SATA and all USB support, cleaned my tree, then
recompiled, but this results in no size difference for Efildr after
running DuetPkg/PostBuild.sh. I don't understand why that is.
So I took another approach and that was to clean and rebuild with:
[BuildOptions]
MSFT:*_*_*_CC_FLAGS = /FAsc /FR$(@R).SBR
+ GCC:*_*_*_CC_FLAGS = -DMDEPKG_NDEBUG
in the DuetPkg/DuetPkgX64.dsc file. After re-arranging ASSERT-style
macros to expand to '((void) (Expression))', after cleaning, rebuilding,
and running PostBuild.sh again, there is _still_ no difference in size
for Efildr.
What am I doing wrong, if you please?
- Shao Miller
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
