Dear coreboot folks,
At work, I have access to a Dediprog EM100Pro, and I am currently to use it to test coreboot on the Asus KGPE-D16.
The utility em100 for the emulator [1], also provides the switch ` --trace`, and the output looks like below [2].
``` Time: 000000.00000000 command # 1 : 0x03 - read 00fffff0 : e9 25 f4 ff Time: 000000.00000879 command # 2 : 0x03 - read 00ffffc0 : 00 00 00 00 Time: 000000.00001635 command # 3 : 0x03 - read 00ffffc4 : 00 00 00 00 Time: 000000.00002333 command # 4 : 0x03 - read 00ffffc8 : 00 00 Warning: EM100pro sends too much data. 00 00 Time: 000000.00003024 command # 5 : 0x03 - read 00ffffcc : 00 00 00 00 Time: 000000.00003780 command # 6 : 0x03 - read 00ffffd0 : 00 00 00 00 Time: 000000.00004471 command # 7 : 0x03 - read 00ffffd4 : 00 00 00 00 Time: 000000.00005227 command # 8 : 0x03 - read 00ffffd8 : 00 00 00 00 Time: 000000.00005918 command # 9 : 0x03 - read 00ffffdc : 00 00 00 00 Time: 000000.00006674 command # 10 : 0x03 - read 00ffffe0 : 00 00 00 00 Time: 000000.00007373 command # 11 : 0x03 - read 00ffffe4 : 00 00 00 00 Time: 000000.00008064 command # 12 : 0x03 - read 00ffffe8 : 00 00 00 00 Time: 000000.00008820 command # 13 : 0x03 - read 00ffffec : 00 00 00 00 Time: 000000.00009576 command # 14 : 0x03 - read 00fffff0 : e9 25 f4 ff Time: 000000.00010267 command # 15 : 0x03 - read 00fffff4 : ff 66 90 66 Time: 000000.00011023 command # 16 : 0x03 - read 00fffff8 : 90 66 90 66 Time: 000000.00011714 command # 17 : 0x03 - read 00fffffc : 38 01 00 ff Time: 000000.00012665 command # 18 : 0x03 - read 00fff400 : ff ff ff ff Time: 000000.00013421 command # 19 : 0x03 - read 00fff404 : ff ff ff ff Time: 000000.00014112 command # 20 : 0x03 - read 00fff408 : ff ff ff ff Time: 000000.00014868 command # 21 : 0x03 - read 00fff40c : ff ff ff ff Time: 000000.00015624 command # 22 : 0x03 - read 00fff410 : ff ff ff ff Time: 000000.00016315 command # 23 : 0x03 - read 00fff414 : ff ff ff ff […] ```
Are there tools available to analyze these traces? For example find out what parts take too long to read for example?
Are there tools available to help work with these traces, and for example map certain areas to the corresponding code?
Is documentation available for working with these traces? What to look for, how to use them to analyze the coreboot code?
How do you use it efficiently?
Thanks,
Paul
[1] https://www.coreboot.org/EM100pro [2] https://www.molgen.mpg.de/~pmenzel/20170210%E2%80%93coreboot/201702 10%E2%80%93kgpe-d16%E2%80%93em100%E2%80%93trace.txt