analyzing the code to simulate ChibiOS under Win32, I found that the biggest difference between embedded execution and simulated execution is the way it makes the context switch (CS).
In embedded execution CS is driven by an interrupt, instead in simulated execution CS is done into Idle thread.
In order to simulate better the embedded execution, I've thought about a timer in a windows thread connected to a callback function, called every 10 ms.
I use this callback function to generate the system tick, CS, and to process serial messages from console. It's simply an interrupt simulation.
The system runs good, but when I try to do the command "test", at the point 3.2 it freezes... 50% of CPU is used (I've got a 4 processor pc)... and never returns!
With some debug technique I found that my interrupt simulation thread freezes! I think that there's a loop in the test that blocks all other threads in the program.
Calling regularly the function ChkIntSources() (I've commented it to do my tests
), the 3.2 point fails, but does not stall!!!!The interrupt simulation is based on a windows thread and a windows timer. I report here the API functions used:
CreateWaitableTimer
SetWaitableTimer
SleepEx
CreateThread
SetThreadPriority
ResumeThread
In my opinion the program stalls because the timer thread is part of the same program process. But I don't know how to resolve this problem.
Does anyone have an idea on how to solve this?
Thank you very much,
Alessandro
