Paul Brook wrote:
But PC is still wrong. Who sets the PC to KERNEL_LOAD_ADDR
(0x10000)?
What makes you think ti's wrong? There's a small bootloader built into qemu.
Uups. Then it seems that I start things the wrong way. I
start QEMU with -S -s, then I attach GDB, and GDB
"complains" that PC is at 0x0 (and not 0x10000). How do I
have to invoke things in the correct way (and that this
bootloader is used) so that system is at 0x10000 if I
attach GDB and can start with si debugging from there?
Then I tried the other way around: Instead of adapting
u-boot, it should be possible to adapt hw/integratorcp.c to
the address u-boot is linked to by default. This is
0x11080000. For my changes see below. With this, I get
You're obviously using the wrong u-boot config then. 0x11080000 isn't even a
RAM address.
Yes, seems that I was unclear here. Sorry. It's for an other
board. Take this question as the first step for a new
machine description using integrator as an example.
Thanks for your help and patience!
Dirk
_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
