Peter Horatschek(deleted)
|
Re: HAM should stop process that is constantly in ISR and high pr iority thread
|
Peter Horatschek(deleted)
10/23/2009 3:54 AM
post40585
|
Re: HAM should stop process that is constantly in ISR and high pr iority thread
Of course there a two ham processes running. One is just the guardian, running at priority 10. The other is the real ham
with 6 threads at priority 10 and 2 at priority 255. I don't realy know how the ham is working, so I can't say what
thread is responsible for starting a new process.
I don't know wether the action or at least the spawn is executed at all. The problem is, I can't contact and analyze the
QNX OS, cause my only connection to the hardware with the PPC is via qconn. As soon as the descripted situation occurs
(too many registered functions) my Momentics IDE shows the hardware as no longer connected. This is, I think, cause the
qconn process is at a too low priority as well. - So I don't have any possibilty to access my hardware. But I know that
QNX is still running, cause in one of the first registered functions I let flash a LED and it is still flashing, so that
function is obviously still executed.
All I can say is, that if I don't send the heartbeat by purpose, the termination of the process works fine. So it's no
problem with the action in general.
I've attached the code I use to attach to the HAM. (Of course there is missing the whole functionality of my process,
I've just included the HAM parts.)
|
|
|