RTOS Task Scheduling Visualization

This is a very, very basic interface I wrote to give a rough sense of how pre-emptive RTOSes might handle a typical series of operations like servicing a CAN interrupt by reading a frame from the CAN peripheral in one task, then passing it to a separate task to actually perform some business logic on the contents of the frame.

It's a bit hacky (I half wrote this as a way to try out Cursor, so the code is very spaghetti), but, using the controls at the bottom, you can see how things like increasing interrupt load can eventually starve the system and rapidly increase latency.