[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Blank screen for hello world qemu-4.2.0

From: abhijeet inamdar
Subject: Re: Blank screen for hello world qemu-4.2.0
Date: Fri, 23 Jul 2021 14:05:01 +0200

Means the memory mapping is not done correctly.  

I have added '-d nochain' and '-singlestep' to the command line it gives me never ending 

 Trace 0: 0x7ff207a5eac0 [00000000/00000572/0x312000c1] HardFault_Handler
R00=2000018c R01=00000000 R02=20000264 R03=20000264
R04=000023f4 R05=000023f4 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=00000000 R11=00000000
R12=00000000 R13=07ffffe0 R14=fffffff9 R15=00000572
XPSR=61000003 -ZC- T handler 

Until i kill it.

On Fri, Jul 23, 2021 at 12:47 PM Peter Maydell <peter.maydell@linaro.org> wrote:
On Fri, 23 Jul 2021 at 11:41, abhijeet inamdar
<abhijeetinamdar3005@gmail.com> wrote:
> Hi,
> What information does this give me and how do I need to sort it out?
> after running qemu-system-arm along with -d in_asm,int,exec,cpu,guest_errors,unimp in the end i get this:

Adding '-d nochain' and '-singlestep' will make the tracing a bit clearer.
Or you can use the gdbstub.

> Taking exception 4 [Data Abort]
> ...with CFSR.PRECISERR and BFAR 0x7ffffd0
> ...BusFault with BFSR.STKERR
> ...taking pending nonsecure exception 3
> ----------------

Your program has crashed early in its startup because it tried
to dereference an invalid address (0x7ffffd0). You need to
debug it to figure out where it got that address from.

> IN: HardFault_Handler
> 0x00000572:  e7fe       b        #0x572

Your program's handler for HardFault (the exception you get for
this data abort) is just "branch to self in a tight loop",
so the guest sits there doing nothing further.

-- PMM

reply via email to

[Prev in Thread] Current Thread [Next in Thread]