tsk_unlock issue/query

We have RTX 3.01 in a product on LPC2214.
We are attempting to isolate a problem whereby a task which is called by 'os_dly_wait' every 350 milliseconds, appears to 'stop' for over 30 seconds, usually after about 4 days running.
This question is to do with an experiment. We have written code which stops 'tsk_unlock()' from calling 'OS_UNLOCK()' (macro in our configuration)under a controlled condition for 30 seconds. The controlled condition definitely occurs, but suppression of 'OS_UNLOCK' appears to have no effect whatsoever on the system. Everything we have carries on normally. Why is this?
All suggestions gratefully received.

Parents
  • If you have called tsk_lock and then call ANY function that does a os_block (such as os_dly_wait) the OS will essentially do an OS_UNLOCK() for you. The only other choice would be to lockup your system forever (because you have disabled interrupts with not chance for them to ever be reenabled)

Reply
  • If you have called tsk_lock and then call ANY function that does a os_block (such as os_dly_wait) the OS will essentially do an OS_UNLOCK() for you. The only other choice would be to lockup your system forever (because you have disabled interrupts with not chance for them to ever be reenabled)

Children
More questions in this forum