OrgACRN
/
sof
mirror of https://github.com/thesofproject/sof.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

coredump-reader: do not hardcode reset vector address 

The gdb script created by coredump-reader has a fixed reset
vector address. This address only works on a subset of supported
SOF platforms and for other platforms, user has to manually fix
the reset address in the gdb script before use.

Modify the script to emit breakpoint for "_MemErrorVector"
symbol. This is not the reset vector, but the simulation will
still be trapped early. The symbol is part of the firmware
binary, so its address can be looked up at runtime.

Also add a second breakpoint for "_MemoryExceptionVector_text_start".
This will cover SOF binaries built with Zephyr as the RTOS.

BugLink: https://github.com/thesofproject/sof/issues/5125
Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
This commit is contained in:
Kai Vehmanen 2022-01-04 15:02:42 +02:00 committed by Liam Girdwood
parent b95d995bd2
commit afaad99125
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
tools/coredumper/sof-coredump-reader.py
View File

@ -718,7 +718,13 @@ class CoreDumpReader(object):
.format(stack_base, stack_dw_num))
stdoutOpen()
stdoutPrint("break *0xbefe0000\nrun\n")
# for XTOS SOF build
stdoutPrint("break _MemErrorVector\n")
# for Zephyr SOF build
stdoutPrint("break _MemoryExceptionVector_text_start\n")
stdoutPrint("run\n")
stdoutPrint(self.core_dump.to_string(1))
#TODO: make this elegant