[MinnowBoard] SOURCE_DEBUG_ENABLE fails on .76 MinnowMax
Edward Chicopee
edward.chicopee at gmail.com
Mon Apr 6 13:26:37 UTC 2015
Unlike other threads, I only care about normal serial-based debug, like I
used to use on the Minnow v1, NOT USB-based.
So has anyone made source level debug actually work on the MinnowMax?
Because I do:
DEFINE SOURCE_DEBUG_ENABLE = TRUE
in
C:\MinMAX076\Vlv2TbltDevicePkg\PlatformPkgConfig.dsc
and get the same sort of easy and obvious error that other people have
reported.
Generate Region at Offset 0x0
Region Size = 0x3E000
Region Name = DATA
Generate Region at Offset 0x3E000
Region Size = 0x2000
Region Name = DATA
Generate Region at Offset 0x40000
Region Size = 0x40000
Region Name = None
Padding region starting from offset 0x80000, with size 0x80000
Generate Region at Offset 0x80000
Region Size = 0x80000
Region Name = None
Generate Region at Offset 0x100000
Region Size = 0x30000
Region Name = FV
Generating MICROCODE_FV FV
##
Generate Region at Offset 0x130000
Region Size = 0x176000
Region Name = FV
Generating FVMAIN_COMPACT FV
Generating FVMAIN FV
########################################
########################################
########################################
########################################
########################################
##################################Return Value = 2
GenFv: ERROR 3000: Invalid
the required fv image size 0x199528 exceeds the set fv image size 0x176000
What's the correct way around this, since everyone else has reported that
manually editing the FVMAIN layout never ends up working for them? Does
this "just work" in .78 and I have to update to that more cumbersome build
process? Because I definitely don't want to update unless it's known to
work.
Ed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elinux.org/pipermail/elinux-minnowboard/attachments/20150406/ff9813dc/attachment.html>
More information about the elinux-MinnowBoard
mailing list