Hi,
Running the nucleo_l152re example with avatar qemu @branches dev/qemu-6.2 or dev/qemu-5.1 we face a crash issue of qemu.
It’s like the registers and ram synchronizations are ok between the board and the qemu. The crash happens just after the synchronization, when doing continue in qemu.
Starting from the trace “terminal derived exception” and debugging a bit we see that there is a call to abort inside do_armv7m_nvic_set_pending resulting from an arm_v7m_cpu_do_interrupt.
Please find attach 2 call stacks obtained from a gdb instance attached to qemu.
It’s like the vector table is not correct (probably an issue with the configurable machine ?). Any clue to fix the issue ?
Has it been validated with the latest qemu versions ?
It ‘s like the latest qemu versions from /dev/qemu-6.2 branch has also some troubles with u-boot example.
qemu_crash.txt
qemu_crash1.txt
Hi,
Running the nucleo_l152re example with avatar qemu @branches dev/qemu-6.2 or dev/qemu-5.1 we face a crash issue of qemu.
It’s like the registers and ram synchronizations are ok between the board and the qemu. The crash happens just after the synchronization, when doing continue in qemu.
Starting from the trace “terminal derived exception” and debugging a bit we see that there is a call to abort inside do_armv7m_nvic_set_pending resulting from an arm_v7m_cpu_do_interrupt.
Please find attach 2 call stacks obtained from a gdb instance attached to qemu.
It’s like the vector table is not correct (probably an issue with the configurable machine ?). Any clue to fix the issue ?
Has it been validated with the latest qemu versions ?
It ‘s like the latest qemu versions from /dev/qemu-6.2 branch has also some troubles with u-boot example.
qemu_crash.txt
qemu_crash1.txt