Re: [coreboot] qemu-armv7: code execution out of RAM or ROM using latest QEMU

[Piotr Król]

On Mon, Aug 11, 2014 at 01:51:16PM -0700, ron minnich wrote:
> I can't recall for ARM, it's been more than a year since I used qemu
> on that platform. That said, ... on the platforms we use ROM is in low
> memory. What's your coreboot system.map say?

I'm not sure what 'coreboot system.map' is but I will assume that you mean
{bootblock, romstage, ramstage}.map.

CONFIG_BOOTBLOCK_BASE is 0x10000
CONFIG_ROMSTAGE_BASE  is 0x20000
CONFIG_SYS_SDRAM_BASE is 0x1000000

Uploaded files: https://gist.github.com/pietrushnic/7fea530d3498cf5ac5cfo

Meanwhile I objdumped bootblock and found that ldmia instruction that
breaks qemu execution came from dcache_foreach method.

Anyone know how to load bootblock debug symbols to gdb when debugging
using '-s -S' option ?

Thanks,
Piotr

qemu-armv7: code execution out of RAM or ROM using latest QEMU

[ron minnich]

So what this is saying is that we expect the ROM for coreboot to start
at 64K. I hope this makes sense to you. Does this conflict with some
qemu expectation, do you know?

ron

On Mon, Aug 11, 2014 at 3:37 PM, Piotr Król  wrote:
> On Mon, Aug 11, 2014 at 01:51:16PM -0700, ron minnich wrote:
> > I can't recall for ARM, it's been more than a year since I used qemu
> > on that platform. That said, ... on the platforms we use ROM is in low
> > memory. What's your coreboot system.map say?
>
> I'm not sure what 'coreboot system.map' is but I will assume that you mean
> {bootblock, romstage, ramstage}.map.
>
> CONFIG_BOOTBLOCK_BASE is 0x10000
> CONFIG_ROMSTAGE_BASE  is 0x20000
> CONFIG_SYS_SDRAM_BASE is 0x1000000
>
> Uploaded files: https://gist.github.com/pietrushnic/7fea530d3498cf5ac5cfo
>
> Meanwhile I objdumped bootblock and found that ldmia instruction that
> breaks qemu execution came from dcache_foreach method.
>
> Anyone know how to load bootblock debug symbols to gdb when debugging
> using '-s -S' option ?
>
> Thanks,
> Piotr

qemu-armv7: code execution out of RAM or ROM using latest QEMU

[Patrick Georgi]

Am 12.08.2014 um 00:37 schrieb Piotr Król:
> Anyone know how to load bootblock debug symbols to gdb when debugging
> using '-s -S' option ?

add-symbol-file $filename $loadaddr

Patrick

qemu-armv7: code execution out of RAM or ROM using latest QEMU

[Piotr Król]

On Tue, Aug 12, 2014 at 05:30:03AM +0200, Patrick Georgi wrote:
> Am 12.08.2014 um 00:37 schrieb Piotr Król:
> > Anyone know how to load bootblock debug symbols to gdb when debugging
> > using '-s -S' option ?
>
> add-symbol-file $filename $loadaddr

When I try:

gdb$ target remote :1234
Remote debugging using :1234
gdb$ add-symbol-file build/cbfs/fallback/bootblock.debug 0x0
add symbol table from file "build/cbfs/fallback/bootblock.debug" at
        .text_addr = 0x0
        Reading symbols from
        /home/pietrushnic/src/coreboot/build/cbfs/fallback/bootblock.debug...warning:
        section .text not found in
        /home/pietrushnic/src/coreboot/build/cbfs/fallback/bootblock.debug
        done.

Same thing for romstage.debug. When using ramstage without address:

gdb$ add-symbol-file build/cbfs/fallback/ramstage.debug
The address where build/cbfs/fallback/ramstage.debug has been loaded is
missing

And with address:
gdb$ add-symboadd-symbol-file build/cbfs/fallback/ramstage.debug 0x0
add symbol table from file "build/cbfs/fallback/ramstage.debug" at
        .text_addr = 0x0
        Reading symbols from
        /home/pietrushnic/src/coreboot/build/cbfs/fallback/ramstage.debug...done.

But util/crossgcc/xgcc/bin/armv7-a-eabi-gdb doesn't break on methods and
does not show executed line of code. Symbols seems to be loaded but I
cannot use them to debug. Any ideas how to debug qemu system using
armv7-a-eabi-gdb ?

Thanks,
Piotr