Re: Assistance Required for QEMU Hardfault Error with Cortex-M33 on MPS2AN505

[Peter Maydell]

On Tue, 16 Jan 2024 at 14:16, sanjana gogte <sanj27272@gmail.com> wrote:
>
> I hope this message finds you well. I am reaching out to seek your expertise 
> regarding a persistent issue I have encountered while working with QEMU, 
> specifically a hardfault error when emulating the MPS2AN505 with a Cortex-M33 
> core.
>
> I have been grappling with this issue for some time and am unsure of the next 
> steps to take. Could you please advise on potential areas to investigate or 
> adjustments that might resolve this error? I am particularly curious if the 
> issue lies with the vector table placement or the configuration in my linker 
> script.
>
> The error I am facing is as follows:
> qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)
>
> This occurs when I attempt to run my kernel.elf file using the following QEMU 
> command:
>
> qemu-system-arm -machine mps2-an505 -cpu cortex-m33 \
>                 -m 16M \
>                 -nographic -serial mon:stdio \
>                 -device loader,file=kernel.elf

(1) Tell us what QEMU version you're using.

(2) Give us the debug logs, by adding
 -D qemu.log -d
in_asm,exec,cpu,int,cpu_reset,unimp,guest_errors,nochain -singlestep

Your guest is probably crashing in early bootup, and the
only way to tell where is to debug it.

Also, your interrupt vector table is too short, because
you've only put in the first two entries (SP and reset PC).
This will result in unhelpfully confusing behaviour if
the CPU ever takes some other kind of exception.

thanks
-- PMM