Re: [Qemu-devel] Trying to execute code outside RAM or ROM at 0x08000230

[Liviu Ionescu]

> On 07 Jun 2015, at 01:11, Peter Maydell <address@hidden> wrote:
> 
> One handy debugging tool for tracking down this kind of thing is to
> use the QEMU monitor's "info mtree" command,

I added "-monitor stdio" to the Eclipse configuration used to start the 
emulator, and I got access to the monitor, but apparently it uses some fancy 
terminal commands, that are not properly handled by the Eclipse console:

(qemu) info mtree
iininfinfoinfo info 
minfo mtinfo 
mtrinfo mtreinfo 
mtree
Execute 'mon info mtree'.

Q: is there any simple way to get rid of them?


as for memory map, I get:

memory
0000000000000000-ffffffffffffffff (prio 0, RW): system
  0000000000000000-000000000001ffff (prio 0, R-): cortexm-mem-flash
  0000000008000000-000000000801ffff (prio 0, R-): alias stm32-mem-flash-alias 
@system 0000000000000000-000000000001ffff
  0000000020000000-0000000020004fff (prio 0, RW): cortexm-mem-sram
  0000000022000000-0000000023ffffff (prio 0, RW): bitband
  0000000040021000-0000000040021027 (prio 0, RW): stm32-rcc
  0000000040022000-0000000040022023 (prio 0, RW): stm32-flash
  00000000e0000000-00000000e0000fff (prio 0, RW): armv7m-itm
  00000000e000e000-00000000e000efff (prio 0, RW): nvic
    00000000e000e000-00000000e000efff (prio 0, RW): nvic_sysregs
    00000000e000e100-00000000e000ecff (prio 1, RW): alias nvic-gic @gic_dist 
0000000000000100-0000000000000cff
  00000000fffff000-00000000ffffffff (prio 0, RW): cortexm-mem-hack

except the NVIC range, which is a bit more complicated than needed, the rest 
seem fine to me.


I/O
0000000000000000-000000000000ffff (prio 0, RW): io

apparently this does not seem to harm anything, but it looks like an old Intel 
thing (which, in my opinion, was harmful enough at its time...)


regards,

Liviu