[coreboot] Working with flash emulator traces (Dediprog EM100Pro)

[Peter Stuge]

Paul Menzel via coreboot wrote:
> find out what parts take too long to read for example?

Nothing will "take too long to read" - the emulator always replies
quickly.


> Are there tools available to help work with these traces, and for
> example map certain areas to the corresponding code?

The address is shown for each command. Just translate that to the
cbfs .rom file. Flash lives at end of 4 GB.


> Is documentation available for working with these traces?
> What to look for, how to use them to analyze the coreboot code?

It's not really so useful for analyzing coreboot code.. The only thing
it tells you is when what parts of coreboot.rom are read by the CPU.


> How do you use it efficiently?

The only thing that comes to my mind as far as performance goes is to
make a histogram of addresses being accessed with a count, and see if
there are any with a particularly high count. Then you can map those
to coreboot.rom manually (cbfstool print and one subtraction) to find
out what is at that address.


//Peter