中级会员
 
- 积分
- 263
- 金钱
- 263
- 注册时间
- 2019-9-22
- 在线时间
- 53 小时
|
发表于 2021-12-30 10:02:57
|
显示全部楼层
μC-OS-III 3.06.01 API Reference.pdf, 第45页最下面一行可能对你有用,我传不了图片.
Do not call the scheduler after the post, therefore the caller is resumed even if the mutexwas posted and tasks of higher priority are waiting for the mutex.
Use this option if the task calling OSMutexPost() will be doing additional posts, if theuser does not want to reschedule until all is complete, and multiple posts should take effect simultaneously.
μC-OS-III 3.06.01 API Reference.pdf,,276页
OSSched() can only be called by task-level code. Also, if the scheduler is locked (i.e., OSSchedLock() was previously called), then OSSched() will have no effect. |
|