Dear community,
I would like to ask about using Ozone SW (ver. 2.70.3 - 64 bit Debian) with debugging U-Boot.
U-Boot itself work with two sets of "locations". One matches the address set of u-boot elf binary just after
starting it from SPL (or loading it via GDB - e.g. 0x17800000).
However, after successful startup the U-Boot relocates itself to the area being near the top of available
SDRAM.
Hence my question - is it possible to relocate symbols in Ozone GUI for easy debugging?
I mean to have something similar to:
(gdb) add-symbol-file u-boot 0x4ff8b000
In that way I could debug U-Boot after it relocates itself.
Thanks in advance for your help.
I would like to ask about using Ozone SW (ver. 2.70.3 - 64 bit Debian) with debugging U-Boot.
U-Boot itself work with two sets of "locations". One matches the address set of u-boot elf binary just after
starting it from SPL (or loading it via GDB - e.g. 0x17800000).
However, after successful startup the U-Boot relocates itself to the area being near the top of available
SDRAM.
Hence my question - is it possible to relocate symbols in Ozone GUI for easy debugging?
I mean to have something similar to:
(gdb) add-symbol-file u-boot 0x4ff8b000
In that way I could debug U-Boot after it relocates itself.
Thanks in advance for your help.