Here is a python script I wrote to extract debug symbols from XIP FV: https://github.com/tianocore/edk2/blob/master/ArmPlatformPkg/Scripts/Ds5/fir mware_volume.py
This set of python script relies on ARM DS-5 to access memory and registers. But it should be quite easy to add an abstraction layer to use these scripts with any debugger that supports Python (eg: GDB). > -----Original Message----- > From: Laszlo Ersek [mailto:[email protected]] > Sent: 01 April 2014 19:04 > To: [email protected] > Subject: Re: [edk2] Is it possible to patch a PCD after an FD has been > constructed? > > On 04/01/14 19:17, Andrew Fish wrote: > > Are there any tools in the edk2 to patch a PCD in an FD? > > > > I was looking at what a debugger has to do to load symbols for the > SEC > > or PEI and it seems like a lot of work. It looks like all you know is > > the base of the FV. You then have to search that FV for an FFS file > then > > open up the sections of the file to find the PE/COFF section, and > then > > parse the PE/COFF section of that file. > > > > It seems bad that you have to include FV cracking code in SEC, just > to > > load symbols. Especially given the data you needs ends up in the > > *.Fv.map file. The PI spec caches a copy of the PEI Entry Point at a > > known location so you would not have to include FV cracking code in > yet > > another location. > > I've learned about LMFA by sneaking a peek at this commit in Jordan's > repo: > > https://github.com/jljusten/edk2/commit/e34569a9 > > Could be what you want. > > Laszlo > > > ----------------------------------------------------------------------- > ------- > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/edk2-devel ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
