Issue created by Sebastian Huber: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5690
The BSP has no CPU counter of its own and no timecounter below the resolution of the clock tick. The uptime therefore advances once per tick, and a test which needs a time point inside a tick cannot work. `T_interrupt_test()` places its action a quarter of a tick before the tick it wants the interrupt in, so the interrupt critical tests run into their iteration limit. The CPU counter also sits in the CPU port, where a BSP cannot replace it. Found while running the full test suite on the GDB simulator. This description was created with Claude Code assistance. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5690 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-citny8t7cujzyaf3vds4jfh78-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
