RTEMS | Wrong Timer configuration in riscv/rv32imafdc. (#5550)

Thu Apr 9 19:41:26 UTC 2026

SHIVAM DEOLANKAR created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5550

## Summary

https://users.rtems.org/t/unknown-error-while-running-tests-using-qemu/799

Refer to the Threads for more details.

Qemu doesnt seem to execute tests properly and hangs on the terminal.\
For checking whether qemu runs. The log file was created.\
rv32imafdc runs on virt machine configuration.\
no graphic is used to display output on terminal itself.\
On running test in rtems-test, the test face a timeout issue.

On adding -d in_asm,cpu , makes the qemu.log file which in constantly incrementing in size to a eventual memory shortage which is supposedly due to a linker issue.

IOn tracing in gdb, execution winds up in a tight loop on:

`(gdb) stepi 63		j .LRISCV_Exception_handler (gdb) stepi 67		addi	sp, sp, -CPU_INTERRUPT_FRAME_SIZE (gdb)  _RISCV_Vector_table ()     at ../../../cpukit/score/cpu/riscv/riscv-exception-handler.S:70 70		SREG	a0, RISCV_INTERRUPT_FRAME_A0(sp) (gdb)  63		j .LRISCV_Exception_handler`

So this seems quite like a problem of spurious interrupt, probably the timer configuration is wrong in 32-bit risc-v after a bad commit.

## Steps to reproduce

Use the following config.ini

`[DEFAULT] `

`RTEMS_POSIX_API = True `

`BUILD_TESTS = True [`

`riscv/rv32imafdc]` 

After successful building, use the following qemu command

`$ qemu-system-riscv64 -M virt -nographic -bios $RTEMS_EXE `

`$ qemu-system-riscv64 -M spike -nographic -bios $RTEMS_EXE`

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5550
You're receiving this email because of your account on gitlab.rtems.org.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260409/20713a21/attachment.htm>