"Yeah, Sophie in RTICv1, prioriti..." <- > <@jamesmunns:beeper.com> Yeah, Sophie in RTICv1, priorities work the way you think, BUT if you share resources between two tasks, the lower task is "escalated" to the priority of the higher task for the length of the lock. The intent is that you keep your locks as short as possible, usually just long enough to read or write some value. > > It sounds like you have it sorted out now, but if you need the high prio task to not be inhibited, you can look at potentially using something like a channel between low and high to pass information without requiring a lock Makes sense (: